On Fri, May 01, 2015 at 03:44:02PM -0400, LM wrote: > On Fri, May 1, 2015 at 3:00 PM, > <[email protected]> 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
