On Thu, 2007-08-02 at 13:05 -1000, Joshua Hoblitt wrote: > On Wed, Aug 01, 2007 at 05:26:03PM -0700, Chris Gianelloni wrote: > > Normally, yes, it would only be good for kernel output, but as someone > > else mentioned, you have livecd-functions.sh that re-writes the inittab. > > Well, guess what triggers it? That's right, a "console=" option on the > > command line. If you type (or via catalyst, add) console=something, > > livecd-functions.sh (via functions.sh in baselayout) will interpret it > > and modify inittab accordingly before we ever even hit runlevel 3, so it > > starts a console on that serial line for login. > > So I tried setting 'livecd/bootargs: console=ttyS0,115200' in > installcd-stage2-minimal.spec and indeed it does setup a tty on the > serial line. However, it doesn't actually seem to pass "bootargs" to > the kernel or there is some other wierdness going on as the dmesg > information AND all of the sysvinit output remains only on the vga > console. The last output on the fbconsole is some wierd error message > about bootsplash right before attaching a tty to the serial line. This > is an improvement for me but I would really like to see the kernel > output/etc. so I can see if the boot processes has hung.
Try it with nofb and let me know if it works. It looks like the problem is the order in which the command line options are passed. If it does work, file a bug asking me to reverse the order than custom arguments get added with the splash arguments. Currently, the splash stuff is always last. If the kernel has more than one "console=" line, the last one gets the kernel output, so the splash one is getting it. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation
signature.asc
Description: This is a digitally signed message part
