On Wed, May 30, 2012 at 4:45 AM, Nikos Chantziaras <email@example.com> wrote:
> On 30/05/12 09:42, Paul Hartman wrote:
>> In all my years of Gentoo I've never set up fbsplash and fbcondecor,
>> so I finally did so on my old laptop. It all worked, pretty easy to
>> set up -- however, there are 2 things I have questions about
>> 1) I see much of OpenRC's colorful output before the fbsplash kicks
>> in. Is there any trick to prevent that stuff from showing and/or
>> making the splash screen show up earlier?
> Yes. *Compile the KMS driver in-kernel rather than as a module.
Thanks, that fixed it. I saw my OpenRC through "Waiting for uevents to
be processed" before, so that makes perfect sense now. Radeon starts
in dmesg at 0.3 seconds instead of 2.8 seconds.
I see Tux for a microsecond, then the splash screen appears and
flashes black three times before stabilizing. I don't think it is the
display changing modes (the backlight stays on), it just looks like
it's switching between blank screen and back to showing the graphics.
It happens at the very beginning of the splash, before root is
remounted and the progress bar is moving. I'm using dracut's gensplash
module to generate the initrd, maybe it's doing something funny.
>> 2) With the fbsplash enabled, xdm (slim) starts in the background. I
>> have to alt-7 to see the graphical login screen. xdm starts at default
>> runlevel. With splash disabled, xdm (slim) starts in the foreground.
>> Why is that?
> Sounds like a bug. *I use KDM and it switches to console 7 automatically.
I just tried plain xdm as well as slim and both wind up in the
background when splash is enabled. Weird.
What specifically happens is: I see the graphical login screen for a
split second, then it changes back to tty1, I briefly see the last
parts of OpenRC finishing and then the console login prompt. alt-7
will take me back to the graphical login screen and it works normally
once I'm there.
I will keep hunting.