Re: can't boot livedvd64_SL54_2009-11-20.iso
Hi Stephen, Stephen Isard wrote: On Wed, 17 Mar 2010 16:11:47 -0500, Stephen Isard 7p03xy...@sneakemail.c OM wrote: On Wed, 17 Mar 2010 20:23:12 +0100, Urs Beyerle urs.beye...@env.ethz.ch 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
Re: can't boot livedvd64_SL54_2009-11-20.iso
On Mon, 22 Mar 2010 12:31:12 +0100, Urs Beyerle urs.beye...@env.ethz.ch wrote: Therefore norhgb as no effect. As you already mentioned, only linux n ox 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? Is it out of the question to configure X before rhgb starts? For my case at least, the problem isn't that SL can't figure out how to run X on my hardware, just that it doesn't do so early enough. What would be the consequences of turning off rhgb? Would it stop gdm f rom running and force all users to type 'startx' after logging in if they wan t an X session? Or does rhgb just hide the details of the boot process? I f the second, then I personally would be happy with your option 1. Btw, what is the 'nox' option supposed to do? It evidently doesn't stop X from being configured. Does it really just mean 'no graphical login'? I t doesn't get consulted in /etc/rc.sysinit. Where does it have its effect?
Re: can't boot livedvd64_SL54_2009-11-20.iso
Stephen Isard wrote: 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? Is it out of the question to configure X before rhgb starts? For my case at least, the problem isn't that SL can't figure out how to run X on my hardware, just that it doesn't do so early enough. As far as I know rhgb (= redhat graphical boot) starts a temporary X server, which has its own configuration. So I guess that in your case just rhgb fails to configure its own X server. See /usr/share/doc/rhgb-0.16.4/HOW_IT_WORKS What would be the consequences of turning off rhgb? Would it stop gdm from running and force all users to type 'startx' after logging in if they want an X session? Or does rhgb just hide the details of the boot process? If the second, then I personally would be happy with your option 1. It's the second. So, I have already two votes for 1. Btw, what is the 'nox' option supposed to do? It evidently doesn't stop X from being configured. Does it really just mean 'no graphical login'? It doesn't get consulted in /etc/rc.sysinit. Where does it have its effect? nox only sets the default runlevel to 3. The X server is still configured. Having runlevel=3, rhgb does not start up (see /usr/share/doc/rhgb-0.16.4/HOW_IT_WORKS)
Re: can't boot livedvd64_SL54_2009-11-20.iso
On 22 March 2010 14:39, Urs Beyerle urs.beye...@env.ethz.ch wrote: Stephen Isard wrote: 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? +1 to option 1. :-) Alan.
Re: can't boot livedvd64_SL54_2009-11-20.iso
Alan Bartlett wrote: On 22 March 2010 14:39, Urs Beyerle urs.beye...@env.ethz.ch wrote: Stephen Isard wrote: 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? +1 to option 1. :-) Alan. Although I don't use Urs' livecd (I do build my own using his scripts), I'd have to lean toward 1 or 3. I know for a fact that rhgb can cause problems if using the ati fglrx module as well. To me, 'failsafe' should mean no fancy options or actions during boot. -Mark -- Mr. Mark V. Stodola Digital Systems Engineer National Electrostatics Corp. P.O. Box 620310 Middleton, WI 53562-0310 USA Phone: (608) 831-7600 Fax: (608) 831-9591
Re: nox - [was can't boot livedvd64_SL54_2009-11-20.iso]
On Mon, 22 Mar 2010 15:39:47 +0100, Urs Beyerle urs.beye...@env.ethz.ch wrote: nox only sets the default runlevel to 3. The X server is still configu red. Having runlevel=3, rhgb does not start up (see /usr/share/doc/rhgb-0.16.4/HOW_IT_WORKS) Just for my general education, do you know what program interprets the 'n ox' parameter and sets the runlevel? As I understand it, init usually gets t he runlevel from /etc/inittab, so nox must somehow be overriding that. I've run strings on the init and grub binaries and grepped the output for nox, but not come up with anything. HOW_IT_WORKS doesn't mention nox either.
Re: nox - [was can't boot livedvd64_SL54_2009-11-20.iso]
On 03/22/2010 07:47 PM, Stephen Isard wrote: On Mon, 22 Mar 2010 15:39:47 +0100, Urs Beyerle urs.beye...@env.ethz.ch wrote: nox only sets the default runlevel to 3. The X server is still configu red. Having runlevel=3, rhgb does not start up (see /usr/share/doc/rhgb-0.16.4/HOW_IT_WORKS) Just for my general education, do you know what program interprets the 'n ox' parameter and sets the runlevel? As I understand it, init usually gets t he runlevel from /etc/inittab, so nox must somehow be overriding that. I've run strings on the init and grub binaries and grepped the output for nox, but not come up with anything. HOW_IT_WORKS doesn't mention nox either. The nox parameter is my invention ;-) It only works with the SL LiveCD. If you specify nox, /etc/inittab is modified at the very beginning of the LiveCD bootup process (before chroot to the SL filesystem, inside the linuxrc of the initial ram disk). Search for nox in the script linuxrc: https://svn.iac.ethz.ch/pub/livecd/trunk/linux-live.sl/initrd/linuxrc Cheers, Urs
Re: can't boot livedvd64_SL54_2009-11-20.iso
On Wed, 17 Mar 2010 16:11:47 -0500, Stephen Isard 7p03xy...@sneakemail.c OM wrote: On Wed, 17 Mar 2010 20:23:12 +0100, Urs Beyerle urs.beye...@env.ethz.ch 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.
can't boot livedvd64_SL54_2009-11-20.iso
Machine is a Compaq dx5150 64 bit desktop with 3Gb of memory. It has bee n having no problems with 64 bit SL5.3. Before upgrading to SL5.4, I thoug ht I'd be cautious and try out the live dvd, but it won't boot. Even if I t ry failsafe, the boot sequence prints the ok after starting udev and the n the screen goes blank and never comes back again. I have no other reason to suspect the machine itself. The only time I ne ed to reboot is for new kernels or drivers. I tried the memtest program on the dvd and it didn't report any problems. Md5sum gives the right answer for the dvd containing the iso image. I downloaded and burned it again just in case, but it didn't make any diffe rence. The dvd drive is ok as far as I can tell. I'm able to boot and run from an old Knoppix dvd. Any suggestions for what to try? Thanks
Re: can't boot livedvd64_SL54_2009-11-20.iso
Hi Stephen, 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. Cheers, Urs On 03/17/2010 07:37 PM, Stephen Isard wrote: Machine is a Compaq dx5150 64 bit desktop with 3Gb of memory. It has bee n having no problems with 64 bit SL5.3. Before upgrading to SL5.4, I thoug ht I'd be cautious and try out the live dvd, but it won't boot. Even if I t ry failsafe, the boot sequence prints the ok after starting udev and the n the screen goes blank and never comes back again. I have no other reason to suspect the machine itself. The only time I ne ed to reboot is for new kernels or drivers. I tried the memtest program on the dvd and it didn't report any problems. Md5sum gives the right answer for the dvd containing the iso image. I downloaded and burned it again just in case, but it didn't make any diffe rence. The dvd drive is ok as far as I can tell. I'm able to boot and run from an old Knoppix dvd. Any suggestions for what to try? Thanks
Re: can't boot livedvd64_SL54_2009-11-20.iso
On Wed, 17 Mar 2010 20:23:12 +0100, Urs Beyerle urs.beye...@env.ethz.ch 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 trie 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 normal except that the time was off by 4 hours (ntpd wasn't running). This machine has a Radeon X1300 card - actually I think it's on the motherboard - and I've been using version 8.36 of the linux driver from t he Radeon website, with fglrx as the driver in my xorg.conf file.
