Re: mysterious kernel panic at start up and it's workaround
(I'll answer this only once, even though there are two parallel
threads)
On Wed, Feb 06, 2002 at 01:40:20PM -0600, Gary Turner wrote:
| On Wed, 06 Feb 2002 12:22:47 -0500, dman wrote:
|
| >On Wed, Feb 06, 2002 at 06:01:34AM -0600, Gary Turner wrote:
| >
| >| I'm gonna feel pretty stupid about this, I think. Like Aaron, I could
| >| get a rescue disk to work. No amount of fiddling with "root=" or
| >| "append=root=" in either lilo.conf or at boot would get 2.4 up and
| >| running.
| >
| >Did you specify any "initrd" stuff? I don't use lilo, but for grub
| >the config looks like (with hda1 as root) :
| >
| >title Debian GNU/Linux (2.4.17-k7 , 1280x1024x16)
| >root (hd0,0)
| >kernel /boot/vmlinuz-2.4.17-k7 root=/dev/hda1 read-only video=vesa vga=0x31A
| >initrd /boot/initrd.img-2.4.17-k7
| >
| >(the key is the "initrd" line at the end instead of a "boot" line)
|
| OK, I added the line "initrd=/initrd.img" to the lilo.conf file last
| night (don't remember why), but it should be
| "initrd=/initrd.img-2.4.17-686"?
It should be the path to your initrd image. I don't like those
symlinks sitting in / and prefer to put the full (version and all)
patn in my boot loader config. The actual file will reside in /boot,
but there may be a symlink on your box for it. It's not there on
mine.
-D
--
"GUIs normally make it simple to accomplish simple actions and
impossible to accomplish complex actions."
--Doug Gwyn (22/Jun/91 in comp.unix.wizards)
Reply to: