In article <[EMAIL PROTECTED]>, Josef Oswald <[EMAIL PROTECTED]> wrote: >> Anyway, I think I know what's happening. Something is setting the >> "debug" environment variable to "2". Could you edit /etc/init.d/rc >> and put 'debug=""' at the top? I think that might fix it. I'm not >> sure what exactly sets the 'debug' environment variable though. > >Yes that did it :-)
Right, so now we know the cause of this. >> Oh, what's the output of cat /proc/cmdline ? > >mem=458736K hpt366.c noapic nosmp debug=2 root=/dev/hdg2 hdb=ide-scsi I had a hunch that it would include debug=2 .. apparently the kernel doesn't know the debug= parameter and it passes it to init in the environment. This breaks the /etc/init.d/rc script. >Most likely this is of course wrong now.... >OK what I did it: I used my older Caldera Grub-boot-loader and put > >title = Debian-Raid >root = (hd2,1) >kernel = /boot/vmlinuz-Raid hpt366.c vga=normal noapic nosmp debug=2 >root=/dev/hdg2 hdb=ide-scsi > >Could it be that the debug-level defined in the menu.lst was causing >all of this? Yes, if you take out debug=2 things will work again. Mike. -- I used to drive a Heisenberg mobile but every time I looked at the speedometer - I got lost!
