Hi Stephen,

Stephen Isard wrote:
> On Wed, 17 Mar 2010 16:11:47 -0500, Stephen Isard <[log in to unmask]
> OM>
> wrote:
> 
>> On Wed, 17 Mar 2010 20:23:12 +0100, Urs Beyerle <[log in to unmask]
>>
>> wrote:
>>
>>> Try to boot with boot parameter "norhgb/"/
>>>
>>> linux norhgb
>>>
>>> norhgb turns graphical bootup off.
>>>
>>> If this help I should add norhgb to the failsafe option in the next
>>> LiveCD release.
>> Thanks, Urs.  Booting with norhgb didn't change anything, but then I tri
> e
>> d
>> "nox" and that got me a console session.  After I logged in as sluser, I
>  
>> was able to start an X session with "startx" and everything seemed norma
> l
>> except that the time was off by 4 hours (ntpd wasn't running).
> 
> Hi Urs,
> 
> Is it possible that the reason "norhgb" has no effect is the line in
> /etc/rc.sysinit that begins "if strstr "$cmdline" rhgb &&amp; ".  rhg
> b won't get
> invoked if the command line doesn't mention rhbg at all, but since
> "rhgb" is a substring of "norhgb" ...
> 
> My problem seems to be that an xorg.conf that works for my hardware doesn
> 't
> get configured until your runlast script, and whatever default configurat
> ion
> there is at the beginning causes a crash if rhgb is allowed to run.


I think you are right. In fact, because "rhgb" is already in $cmdline per default, and "linux norhgb" only adds norhgb
to $cmdline, "rhgb" still matches $cmdline.

Therefore "norhgb" as no effect. As you already mentioned, only "linux nox" and a manual "startx" is working. :-(

To avoid this problem in future releases of the SL LiveCDs, I see three possibilities:

1. remove "rhgb" from the default boot options - no graphical bootup per default.
2. make "norhgb" working - /etc/rc.sysinit has to be modified.
3. (at least) remove "rhgb" from failsafe bootup options.

or just leave it like it is.

Anybody has an opinion on that?


Cheers,

	Urs