| 1 |
Joshua Hoblitt wrote: |
| 2 |
> On Fri, Aug 03, 2007 at 12:01:23PM -0700, Chris Gianelloni wrote: |
| 3 |
>> On Thu, 2007-08-02 at 19:01 -0500, Andrew Gaffney wrote: |
| 4 |
>>> Joshua Hoblitt wrote: |
| 5 |
>>>> On Wed, Aug 01, 2007 at 05:26:03PM -0700, Chris Gianelloni wrote: |
| 6 |
>>>>> Normally, yes, it would only be good for kernel output, but as someone |
| 7 |
>>>>> else mentioned, you have livecd-functions.sh that re-writes the inittab. |
| 8 |
>>>>> Well, guess what triggers it? That's right, a "console=" option on the |
| 9 |
>>>>> command line. If you type (or via catalyst, add) console=something, |
| 10 |
>>>>> livecd-functions.sh (via functions.sh in baselayout) will interpret it |
| 11 |
>>>>> and modify inittab accordingly before we ever even hit runlevel 3, so it |
| 12 |
>>>>> starts a console on that serial line for login. |
| 13 |
>>>> So I tried setting 'livecd/bootargs: console=ttyS0,115200' in |
| 14 |
>>>> installcd-stage2-minimal.spec and indeed it does setup a tty on the |
| 15 |
>>>> serial line. However, it doesn't actually seem to pass "bootargs" to |
| 16 |
>>>> the kernel or there is some other wierdness going on as the dmesg |
| 17 |
>>>> information AND all of the sysvinit output remains only on the vga |
| 18 |
>>>> console. The last output on the fbconsole is some wierd error message |
| 19 |
>>>> about bootsplash right before attaching a tty to the serial line. This |
| 20 |
>>>> is an improvement for me but I would really like to see the kernel |
| 21 |
>>>> output/etc. so I can see if the boot processes has hung. |
| 22 |
>>> You're positive that it's not being passed to the kernel? I'm pretty sure that |
| 23 |
>>> livecd-tools would read it from /proc/cmdline, which is the arguments passed to |
| 24 |
>>> the kernel. If it shows up in /proc/cmdline, then it's the kernel that isn't |
| 25 |
>>> honoring it, not catalyst/genkernel/isolinux that is doing something wrong. |
| 26 |
>> I think it is an ordering issue, rather than it not being passed. I |
| 27 |
>> just checked the code and the splash code appends to the very end of the |
| 28 |
>> kernel command line, meaning it takes precedence. |
| 29 |
> |
| 30 |
> I won't be able to test anything until Monday. Would an option to |
| 31 |
> completely disable the splash be reasonable? |
| 32 |
|
| 33 |
That's what the -nofb kernel does. However, there isn't currently an option to |
| 34 |
have a framebuffer without splash. I'm not sure if it would still pass the |
| 35 |
splash options if you don't enable splash stuff in livecd-stage2.spec, but I bet |
| 36 |
it would. |
| 37 |
|
| 38 |
-- |
| 39 |
Andrew Gaffney http://dev.gentoo.org/~agaffney/ |
| 40 |
Gentoo Linux Developer Catalyst/Installer + x86 release coordinator |
| 41 |
-- |
| 42 |
gentoo-catalyst@g.o mailing list |
Archives