Re: [blfs-support] Firmware updates
On 2 May 2015 at 18:06, Ken Moffat wrote: > On Sat, May 02, 2015 at 02:06:46PM +0100, Richard Melville wrote: > > Just a point of information regarding the frame buffer and linux-4.0.1. > On > > running this kernel I was greeted with a blank screen. It turned out > that > > CONFIG_X86_SYSFB=y (for which I have no use) had been set which succeeded > > in overriding my normal frame buffer settings resulting in the blank > > screen. I don't remember selecting this option, but who knows? Any > way, I > > then discovered that setting CONFIG_FB_SIMPLE=y returns the system to > > normality (for me) whether CONFIG_X86_SYSFB has been set or not. > > > > I just wondered if anybody else had come across this. > > > > Richard > > I see that I've got CONFIG_X86_SYSFB=y on 4.0.1 on my r600+ machine > (RS780L) where CONFIG_FB_SIMPLE is not set, and all is working for me > with radeon KMS. > Ah, I now see that I don't have Intel KMS enabled, and I'm using the legacy vesafb. I think my reasoning was that my lowly, embedded Intel graphics chip wasn't supported but I'm probably wrong. I'll look into it. Thanks Ken. Richard -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Sat, May 02, 2015 at 02:06:46PM +0100, Richard Melville wrote: > Just a point of information regarding the frame buffer and linux-4.0.1. On > running this kernel I was greeted with a blank screen. It turned out that > CONFIG_X86_SYSFB=y (for which I have no use) had been set which succeeded > in overriding my normal frame buffer settings resulting in the blank > screen. I don't remember selecting this option, but who knows? Any way, I > then discovered that setting CONFIG_FB_SIMPLE=y returns the system to > normality (for me) whether CONFIG_X86_SYSFB has been set or not. > > I just wondered if anybody else had come across this. > > Richard I see that I've got CONFIG_X86_SYSFB=y on 4.0.1 on my r600+ machine (RS780L) where CONFIG_FB_SIMPLE is not set, and all is working for me with radeon KMS. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
Just a point of information regarding the frame buffer and linux-4.0.1. On running this kernel I was greeted with a blank screen. It turned out that CONFIG_X86_SYSFB=y (for which I have no use) had been set which succeeded in overriding my normal frame buffer settings resulting in the blank screen. I don't remember selecting this option, but who knows? Any way, I then discovered that setting CONFIG_FB_SIMPLE=y returns the system to normality (for me) whether CONFIG_X86_SYSFB has been set or not. I just wondered if anybody else had come across this. Richard -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Fri, May 1, 2015 at 12:36 PM, alex lupu wrote: > On Thu, Apr 30, 2015 at 11:03 PM, alex lupu wrote: > >> On Thu, Apr 30, 2015 at 4:11 PM, Ken Moffat >> wrote: >> >>> On Thu, Apr 30, 2015 at 01:08:34PM -0400, LM wrote: >>> > On Wed, Apr 29, 2015 at 3:00 PM, William wrote: >>> ... >>> you >>> >>> don't see penguins if you're in framebuffer mode. >>> >>> Penguins are optional for framebuffer >>> >>> users (and not available if you don't use a framebuffer) >> >> >> I haven't seen a framebuffer (fbcon) since 3.19.1 (or thereabouts). >> >> > I managed to set up a framebuffer on 4.0.1 too! > > I > 'm trying to track down the critical missing/extra setting(s) in my 4.0.1 ' > .config' > (especially vs 3.19.1 where, as I said, framebuffer comes "naturally"). > Apologies for the false scare > . > > First, Ken, Unfortunately our letters crossed in the mail (so I had been tracking down all alone). Thank you for your configuration sample and overall help. Now back to the "tracking down" I promised in my previous post. To summarize the situation. System: 32-bit BLFS, init (no systemd), i915 intel, 4.0.1 Finally, I got to the bottom of my "missing" fbcon module (the problem, in general). The kernel config developers (could be them "systemd" guys?) threw me a curve: By changing the Device Drivers Graphics support Frame buffer Devices Support for frame buffer devices (CONFIG_FB) from Y to M, I got my fbcon module back. === 3.19.1 With "Support for frame buffer devices" = Y the module 'fbcon.ko' IS created!!! (as had been created for many previous kernels) === 3.19.3 With "Support for frame buffer devices" = Y NO LONGER creates module 'fbcon.ko' !!! The framebuffer console support is created "statically" (as they say). === 4.0.1 Same as 3.19.3 (and for many kernel versions to come) Note: The new situation (3.19.3+) started when the kernel founding fathers decided it was time to bring the reality in line with the '/linux-x.y.z/Documentation/fb/fbcon.txt' words (i.e., Y -> static, M -> module). With renewed apologies for taking this long to untangle the situation, -- Alex -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Fri, May 01, 2015 at 03:44:02PM -0400, LM wrote: > On Fri, May 1, 2015 at 3:00 PM, > wrote: > > Sorry, that could mislead. Penguins are optional for framebuffer > > users (and not available if you don't use a framebuffer), and they > > appear (if selected, and once the required firmware has loaded) just > > after the screen changes from 80x25 to whatever your monitor > > permits. > > So how would one turn them on and off if optional? > Looking at my /proc/config.gz, some or all of the following: CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y Yeah, I'm obviously wasting a bit of space for the mono and vga16 logos, must remember to turn those off. That seems to at / under Graphics support Bootup logo > This is was what I was referring to when I mentioned no penguins: > http://forums.debian.net/viewtopic.php?f=10&t=60126 > I guess I should have clarified that to when KMS was turned on, not > when framebuffer was being used. To me, some of that looks bogus. But then, I do not usually build the radeon stuff as a module - my kernels are each specific to one machine and I know that I always want the welcome sight of two or four penguins when I boot, to give me a lift before things maybe go downhill (often, I'm using -rc kernels). Also, that's four years old, I think the details of how firmware gets loaded might have changed (but I still don't really understand _all_ the details) - probably, I'm thinking of the situation described in https://lwn.net/Articles/518942/ and whatever happened after that. The guy who started this discussion has two separate radeons (Kaveri and Oland XT, which need different firmware) and part of what he noted was that he doesn't see them if the firmware is built as modules - I guessed that it takes so long to load it all, but his comment that when built-in, the penguins remain until the screen is cleared does not match my experience using sysvinit. On my previous R200 machines (firmware in the kernel tree) I used to just build the radeon framebuffer driver into the kernel. When I got my first R600+ desktop machine, it took me a while to find out that I needed extra firmware, and then I went with building it in because that seemed easier - in those days, I think the details of how firmware got loaded (if not built in) were slightly different. So, all I can suggest is that you try building in the drivers if you are using modules. Of course, that gives lots of scope for not specifying all the pieces of radeon/ firmware that you need, or not telling the kernel to look in /lib/firmware (been there, made most of the possible mistakes :) > > > KMS is nothing to do with the bootloader, nor with the commandline > > arguments - unless I'm missing something ? > > If you search KMS and grub2, there are articles on how to disable KMS > from grub2. I've experimented with some of the grub2 settings and was > able to disable and enable. > > Here's one example that mentions it: > http://www.linuxquestions.org/questions/linux-general-1/how-do-i-disable-kms-with-grub2-922290/ That mentions how to add nomodeset to the linux boot args from within grub: I've never looked that deeply into grub (_all_ bootloaders are nasty, in their own individual ways), I just edit grub.cfg. I'd misunderstood, and assumed you were referring to some weird and wonderful setting in grub.cfg ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
LM wrote: On Fri, May 1, 2015 at 3:00 PM, wrote: Sorry, that could mislead. Penguins are optional for framebuffer users (and not available if you don't use a framebuffer), and they appear (if selected, and once the required firmware has loaded) just after the screen changes from 80x25 to whatever your monitor permits. So how would one turn them on and off if optional? In the kernel configuration. Device Drivers -> Graphics Support -> Bootup logo This is was what I was referring to when I mentioned no penguins: http://forums.debian.net/viewtopic.php?f=10&t=60126 I guess I should have clarified that to when KMS was turned on, not when framebuffer was being used. KMS is nothing to do with the bootloader, nor with the commandline arguments - unless I'm missing something ? If you search KMS and grub2, there are articles on how to disable KMS from grub2. I've experimented with some of the grub2 settings and was able to disable and enable. Here's one example that mentions it: http://www.linuxquestions.org/questions/linux-general-1/how-do-i-disable-kms-with-grub2-922290/ That the hard way. Just add nomodeset to the linux line in grub.cfg. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Fri, May 1, 2015 at 3:00 PM, wrote: > Sorry, that could mislead. Penguins are optional for framebuffer > users (and not available if you don't use a framebuffer), and they > appear (if selected, and once the required firmware has loaded) just > after the screen changes from 80x25 to whatever your monitor > permits. So how would one turn them on and off if optional? This is was what I was referring to when I mentioned no penguins: http://forums.debian.net/viewtopic.php?f=10&t=60126 I guess I should have clarified that to when KMS was turned on, not when framebuffer was being used. > KMS is nothing to do with the bootloader, nor with the commandline > arguments - unless I'm missing something ? If you search KMS and grub2, there are articles on how to disable KMS from grub2. I've experimented with some of the grub2 settings and was able to disable and enable. Here's one example that mentions it: http://www.linuxquestions.org/questions/linux-general-1/how-do-i-disable-kms-with-grub2-922290/ -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Thu, Apr 30, 2015 at 11:03:48PM -0400, alex lupu wrote:
> On Thu, Apr 30, 2015 at 4:11 PM, Ken Moffat wrote:
>
> > On Thu, Apr 30, 2015 at 01:08:34PM -0400, LM wrote:
> > > On Wed, Apr 29, 2015 at 3:00 PM, William wrote:
> > ...
> > you
> >
> > don't see penguins if you're in framebuffer mode.
> >
> > Penguins are optional for framebuffer
> >
> > users (and not available if you don't use a framebuffer)
>
>
> Curiouser and curiouser!
> Penguins or no, at least on my pretty recent i915 intel machine,
> I haven't seen a framebuffer (fbcon) since 3.19.1 (or thereabouts).
>
> I'm talking about the "/linux-x.y.z/Documentation/fb/fbcon.txt".
> Excerpt:
> The framebuffer console can be enabled by using your favorite kernel
> configuration tool. It is under
> Device Drivers->Graphics Support->Support for framebuffer devices->
> Framebuffer Console Support.
> Select 'y' to compile support statically, or 'm' for module support.
> The module will be fbcon.
> (it's a text carried over form kernel to kernel unchanged).
>
I build it in, always have done (80x25 is so restrictive ;)
> This is what I have:
>
> === For both 3.19.1 and 4.0.1
>
> Device Drivers -> Graphics Support:
> ...
> Direct Rendering Manager --->
> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
> ...
> Intel 8xx/9xx/G3x/G4x/HD Graphics
> [ ] Enable modesetting on intel by default
I turn that on - I prefer to try out interesting new options when I
see them in -rc kernels - but I don't think it makes the difference.
> [*] Enable legacy fbdev support for the modesetting intel driver
> ...
>
> Frame buffer Devices --->
> {*} Support for frame buffer devices --->
>--- Support for frame buffer devices
>(with its < Help >:
> CONFIG_FB:
> The frame buffer device provides an abstraction for the graphics
> ...)
>[*] Enable firmware EDID
>
> ...
> VGA 16-color graphics support
> [*] VESA VGA graphics support
> [*] EFI-based Framebuffer Support
> ...
>
> === For 3.19.1
>
> $ ls /lib/modules/3.19.1/kernel/drivers/video/
> backlight console fbdev
>
> with /lib/modules/3.19.1/kernel/drivers/video/console/fbcon.ko
>
> $ modprobe -v fbcon
> insmod /lib/modules/3.19.1/kernel/lib/fonts/font.ko
> insmod /lib/modules/3.19.1/kernel/drivers/video/console/softcursor.ko
> insmod /lib/modules/3.19.1/kernel/drivers/video/console/bitblit.ko
> insmod /lib/modules/3.19.1/kernel/drivers/video/console/fbcon.ko
>
> $ lsmod | grep fbcon
> fbcon 28798 0
> bitblit 3318 1 fbcon
> font4808 1 fbcon
>
> === For 4.0.1
>
> $ ls /lib/modules/4.0.1/kernel/drivers/video
> backlight fbdev vgastate.ko
>
> $ modprobe -v fbcon
> FATAL: Module fbcon not found.
>
> --
> A puzzled and confused,
> -- Alex
Excerpts from my i3's config
#
# Direct Rendering Manager
#
CONFIG_DRM=y
CONFIG_DRM_MIPI_DSI=y
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_KMS_FB_HELPER=y
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
CONFIG_DRM_I915=y
CONFIG_DRM_I915_KMS=y
CONFIG_DRM_I915_FBDEV=y
...
CONFIG_DRM_PANEL=y
...
#
# Frame buffer Devices
#
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_CMDLINE=y
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
...
# CONFIG_FB_SIMPLE is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_GENERIC=y
# CONFIG_BACKLIGHT_APPLE is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_VGASTATE is not set
CONFIG_HDMI=y
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_DUMMY_CONSOLE_COLUMNS=80
CONFIG_DUMMY_CONSOLE_ROWS=25
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_SOUND=y
The elided ... parts are all not set.
I'll let you compare that to your own config.
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Thu, Apr 30, 2015 at 11:03 PM, alex lupu wrote: > On Thu, Apr 30, 2015 at 4:11 PM, Ken Moffat > wrote: > >> On Thu, Apr 30, 2015 at 01:08:34PM -0400, LM wrote: >> > On Wed, Apr 29, 2015 at 3:00 PM, William wrote: >> ... >> you >> >> don't see penguins if you're in framebuffer mode. >> >> Penguins are optional for framebuffer >> >> users (and not available if you don't use a framebuffer) > > > I haven't seen a framebuffer (fbcon) since 3.19.1 (or thereabouts). > > I managed to set up a framebuffer on 4.0.1 too! % ls /lib/modules/4.0.1/kernel/drivers/video/ backlight console fbdev % ls /lib/modules/4.0.1/kernel/drivers/video/console bitblit.ko fbcon.ko softcursor.ko I'm trying to track down the critical missing/extra setting(s) in my 4.0.1 ' .config' (especially vs 3.19.1 where, as I said, framebuffer comes "naturally"). Apologies for the false scare, -- Alex -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Thu, Apr 30, 2015 at 4:11 PM, Ken Moffat wrote:
> On Thu, Apr 30, 2015 at 01:08:34PM -0400, LM wrote:
> > On Wed, Apr 29, 2015 at 3:00 PM, William wrote:
> ...
> you
>
> don't see penguins if you're in framebuffer mode.
>
> Penguins are optional for framebuffer
>
> users (and not available if you don't use a framebuffer)
Curiouser and curiouser!
Penguins or no, at least on my pretty recent i915 intel machine,
I haven't seen a framebuffer (fbcon) since 3.19.1 (or thereabouts).
I'm talking about the "/linux-x.y.z/Documentation/fb/fbcon.txt".
Excerpt:
The framebuffer console can be enabled by using your favorite kernel
configuration tool. It is under
Device Drivers->Graphics Support->Support for framebuffer devices->
Framebuffer Console Support.
Select 'y' to compile support statically, or 'm' for module support.
The module will be fbcon.
(it's a text carried over form kernel to kernel unchanged).
This is what I have:
=== For both 3.19.1 and 4.0.1
Device Drivers -> Graphics Support:
...
Direct Rendering Manager --->
Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
...
Intel 8xx/9xx/G3x/G4x/HD Graphics
[ ] Enable modesetting on intel by default
[*] Enable legacy fbdev support for the modesetting intel driver
...
Frame buffer Devices --->
{*} Support for frame buffer devices --->
--- Support for frame buffer devices
(with its < Help >:
CONFIG_FB:
The frame buffer device provides an abstraction for the graphics
...)
[*] Enable firmware EDID
...
VGA 16-color graphics support
[*] VESA VGA graphics support
[*] EFI-based Framebuffer Support
...
=== For 3.19.1
$ ls /lib/modules/3.19.1/kernel/drivers/video/
backlight console fbdev
with /lib/modules/3.19.1/kernel/drivers/video/console/fbcon.ko
$ modprobe -v fbcon
insmod /lib/modules/3.19.1/kernel/lib/fonts/font.ko
insmod /lib/modules/3.19.1/kernel/drivers/video/console/softcursor.ko
insmod /lib/modules/3.19.1/kernel/drivers/video/console/bitblit.ko
insmod /lib/modules/3.19.1/kernel/drivers/video/console/fbcon.ko
$ lsmod | grep fbcon
fbcon 28798 0
bitblit 3318 1 fbcon
font4808 1 fbcon
=== For 4.0.1
$ ls /lib/modules/4.0.1/kernel/drivers/video
backlight fbdev vgastate.ko
$ modprobe -v fbcon
FATAL: Module fbcon not found.
--
A puzzled and confused,
-- Alex
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Thu, Apr 30, 2015 at 01:08:34PM -0400, LM wrote: > On Wed, Apr 29, 2015 at 3:00 PM, William wrote: > >. First, no Penguins! > > I have an ATI video card as well. I did a lot of trying to look up > information on framebuffer, KMS, etc. From my understanding, you > don't see penguins if you're in framebuffer mode. Sorry, that could mislead. Penguins are optional for framebuffer users (and not available if you don't use a framebuffer), and they appear (if selected, and once the required firmware has loaded) just after the screen changes from 80x25 to whatever your monitor permits. > When Kernel Mode > Setting (KMS) is active (in Grub or Lilo), KMS is nothing to do with the bootloader, nor with the commandline arguments - unless I'm missing something ? > it sets up the resolution > so you don't see flashes (or resolution changes) when switching > between say console/terminal mode and a GUI. Yes. And if your kernel oopses while you are in X you might see the end of the trace - I did once, but mostly I still just get a locked X :-P > You also typically have > a horrible looking high resolution default screen (with very small > font) if you don't log directly into X and want to work directly in a > terminal mode. There's a large Terminus font ( > http://terminus-font.sourceforge.net/ ) that helps with readability in > that mode, but still doesn't look as pretty as when KMS is off. When I used my G5 ppc64 mac with an nvidia card and a big monitor, it gave what you describe - until I added something like video=1024x768 to the bootargs. I now use that, or 800x600, on some installations with 8x16 fonts (for 12x22 I don't usually need to bother). > However, with the higher resolution (KMS on), you can run programs in > Framebuffer mode including any SDL based programs if SDL is built > using DirectFB or Framebuffer support. You don't need to start X to > run them. Programs like the links web browser use Framebuffer to > display graphics in a terminal outside of X Windows. > > So, in short, if you don't see a penguin and your system is on, KMS is > probably set and framebuffer is working. I did find a way to add > penguins to my login though. > > Sincerely, > Laura ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Wed, Apr 29, 2015 at 3:00 PM, William wrote: >. First, no Penguins! I have an ATI video card as well. I did a lot of trying to look up information on framebuffer, KMS, etc. From my understanding, you don't see penguins if you're in framebuffer mode. When Kernel Mode Setting (KMS) is active (in Grub or Lilo), it sets up the resolution so you don't see flashes (or resolution changes) when switching between say console/terminal mode and a GUI. You also typically have a horrible looking high resolution default screen (with very small font) if you don't log directly into X and want to work directly in a terminal mode. There's a large Terminus font ( http://terminus-font.sourceforge.net/ ) that helps with readability in that mode, but still doesn't look as pretty as when KMS is off. However, with the higher resolution (KMS on), you can run programs in Framebuffer mode including any SDL based programs if SDL is built using DirectFB or Framebuffer support. You don't need to start X to run them. Programs like the links web browser use Framebuffer to display graphics in a terminal outside of X Windows. So, in short, if you don't see a penguin and your system is on, KMS is probably set and framebuffer is working. I did find a way to add penguins to my login though. Sincerely, Laura -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Wed, Apr 29, 2015 at 08:08:24PM -0400, William K Helbig Jr wrote: > > > Yes, there are two video controllers, the Kaveri APU and the Oland XT, > together requiring 16 pieces of microcode. That probably explains why it takes so long. > > My remark re the Penguins was meant more to report what the system was (not) > doing when the firmware was loaded as modules instead of being built into > the kernel. My main concern was/is why the different results between modules > and built-ins, particularly Ken has suggested that maybe it has to do with > loading order and/or timing of events and that seems a reasonable guess. > > And speaking of the Penguins, on my system they do not scroll off the top of > the screen. Even after logging in, they stay around until something actually > clears the entire screen. While they are present I have a 60 line by 210 > character display area in which text scrolls. I presume that is a function > of the framebuffer driver. > > Skip H > On all of my machines, the penguins always disappear a little while after the console is set up, and certainly before the boot has completed (but I do have a bit of BLFS in my minimal builds - rpcbind, nfs-client, ntpd, postfix, fcron all add bootscripts). With systemd, perhaps the penguins staying in place is normal. What I might be doing differently to you is that I set up the console font. My machines all default to 8x16. On some I use my own 8x16 font to get better coverage, on others I use my own 12x22 font. I don't think I could handle trying to read 60x210, let alone whatever your full screen gives you. At times in the past I have used video= on the kernel command line, e.g. video=1024x768 or video=800x600 when the screen is actually 1600x1200. I also set a keymap, which probably doesn't affect things, and enable unicode which, in the sysv build, causes some kbd commands to be run on each tty (the S70console script in rcS.d). ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On 04/29/2015 04:35 PM, Ken Moffat wrote: On Wed, Apr 29, 2015 at 02:07:08PM -0500, Bruce Dubbs wrote: William K Helbig Jr wrote: Firstly a minor typo in the third paragraph of the About Firmware section of Chapter 3 in the SVN version of the BLFS book. The line reads “firmware files can be accessed vau wget”. That probably should be ”firmware files can be accessed via wget”. I'll update that at the next commit. Next a comment/question about Firmware for ATI video chips. The method shown in this chapter shows making the radeon driver a module but when I do this then boot the resulting system two things happen. First, no Penguins! Second, and more importantly, the login prompt does not appear until I hit the enter key. The system seems to work properly otherwise, meaning I have an active framebuffer device that I can write to and see a response. When the firmware is built into the kernel everything functions as expected. The nuts and bolts of my system: LFS-systemd 7.7 AMD A10-7850K APU Kaveri [Radeon R7 200 Series] Oland XT [Radeon HD 8670 / R7 250] An APU (KAveri) plus a separate video card (Oland XT) ? The question is, Since this behavior is not a show stopper is it a problem I need to be concerned about, or is it just the way things want to work? I don't have any ATI video cards so I can't really help there. Perhaps Ken may have some ideas. -- Bruce Just finished building all of Xorg (BLFS-style instead of my normal reduced build) using gcc-5, I'm a little short of resources here for looking things up (only one xterm, trying twm). For the login prompt, I assume that is something to do with systemd and I can't help - AFAICS it cannot know when the kernel has loaded the video firmware, but I can see that it might theoretically need to load some other firmware, e.g. for the network, and perhaps it is the total time to find and load which causes the problem. That seems unlikely, but I've no real idea. For the lack of penguins - yes, the A10-7850K needs a _lot_ of firmware, and by the time that has loaded they tend to have disappeared as the screen scrolled up. Even with the firmware built into the kernel, the penguins don't hang around for long. Building the firmware in should still be covered in the Xorg ATI driver in BLFS, but you seem to have covered that. ĸen Yes, there are two video controllers, the Kaveri APU and the Oland XT, together requiring 16 pieces of microcode. My remark re the Penguins was meant more to report what the system was (not) doing when the firmware was loaded as modules instead of being built into the kernel. My main concern was/is why the different results between modules and built-ins, particularly Ken has suggested that maybe it has to do with loading order and/or timing of events and that seems a reasonable guess. And speaking of the Penguins, on my system they do not scroll off the top of the screen. Even after logging in, they stay around until something actually clears the entire screen. While they are present I have a 60 line by 210 character display area in which text scrolls. I presume that is a function of the framebuffer driver. Skip H -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
On Wed, Apr 29, 2015 at 02:07:08PM -0500, Bruce Dubbs wrote: > William K Helbig Jr wrote: > >Firstly a minor typo in the third paragraph of the About Firmware section of > >Chapter 3 in the SVN version of the BLFS book. The line reads “firmware > >files > >can be accessed vau wget”. That probably should be ”firmware files can be > >accessed via wget”. > > I'll update that at the next commit. > > >Next a comment/question about Firmware for ATI video chips. The method > >shown in > >this chapter shows making the radeon driver a module but when I do this then > >boot the resulting system two things happen. First, no Penguins! Second, and > >more importantly, the login prompt does not appear until I hit the enter key. > >The system seems to work properly otherwise, meaning I have an active > >framebuffer device that I can write to and see a response. When the firmware > >is > >built into the kernel everything functions as expected. > > > >The nuts and bolts of my system: > > LFS-systemd 7.7 > > AMD A10-7850K APU > > Kaveri [Radeon R7 200 Series] > > Oland XT [Radeon HD 8670 / R7 250] An APU (KAveri) plus a separate video card (Oland XT) ? > > > >The question is, Since this behavior is not a show stopper is it a problem I > >need to be concerned about, or is it just the way things want to work? > > I don't have any ATI video cards so I can't really help there. Perhaps Ken > may have some ideas. > > -- Bruce > Just finished building all of Xorg (BLFS-style instead of my normal reduced build) using gcc-5, I'm a little short of resources here for looking things up (only one xterm, trying twm). For the login prompt, I assume that is something to do with systemd and I can't help - AFAICS it cannot know when the kernel has loaded the video firmware, but I can see that it might theoretically need to load some other firmware, e.g. for the network, and perhaps it is the total time to find and load which causes the problem. That seems unlikely, but I've no real idea. For the lack of penguins - yes, the A10-7850K needs a _lot_ of firmware, and by the time that has loaded they tend to have disappeared as the screen scrolled up. Even with the firmware built into the kernel, the penguins don't hang around for long. Building the firmware in should still be covered in the Xorg ATI driver in BLFS, but you seem to have covered that. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] Firmware updates
William K Helbig Jr wrote: Firstly a minor typo in the third paragraph of the About Firmware section of Chapter 3 in the SVN version of the BLFS book. The line reads “firmware files can be accessed vau wget”. That probably should be ”firmware files can be accessed via wget”. I'll update that at the next commit. Next a comment/question about Firmware for ATI video chips. The method shown in this chapter shows making the radeon driver a module but when I do this then boot the resulting system two things happen. First, no Penguins! Second, and more importantly, the login prompt does not appear until I hit the enter key. The system seems to work properly otherwise, meaning I have an active framebuffer device that I can write to and see a response. When the firmware is built into the kernel everything functions as expected. The nuts and bolts of my system: LFS-systemd 7.7 AMD A10-7850K APU Kaveri [Radeon R7 200 Series] Oland XT [Radeon HD 8670 / R7 250] The question is, Since this behavior is not a show stopper is it a problem I need to be concerned about, or is it just the way things want to work? I don't have any ATI video cards so I can't really help there. Perhaps Ken may have some ideas. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
