Hi

I�m trying to boot a kernel (2.4.19-pre5) with an initrd image I created
with mkinitrd , but I always get a kernel panic saying

...
ds: no socket drivers loaded!
VFS: cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00 



My grub.conf looks like this:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file # NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,1)
#          kernel /boot/vmlinuz-version ro root=/dev/hda2
#          initrd /boot/initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,1)/boot/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-8)
        root (hd0,1)
        kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/ hde=ide-scsi
        initrd /boot/initrd-2.4.20-8.img
### the above is the default and properly working kernel

title DOS
        rootnoverify (hd0,0)
        chainloader +1
### this is windows

title Red Hat Linux (2.4.19-pre5-aio)
        root (hd0,1)
        kernel /boot/vmlinuz-2.4.19-pre5-aio ro root=LABEL=/
hde=ide-scsi
        initrd /boot/initrd-2.4.19-pre5-aio.img
### this is the kernel I compiled and that causes the kernel panic


As you can see I only changed the title and the filenames of the kernel
image and initrd image, so I don�t understand why does one work and one
not? If anyone needs more information, just let me know. Thanks alot for
any help.

Greetings
Markus

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Reply via email to