At 06:19 17/02/2003 -0800, you wrote:
I compiled module support for ext3 which is the filesystem I use. I did not
rebuild initrd with mkinitrd but I thought that the make install did that
for me. Is this not correct?
Hmm - not sure if "make install" does rebuild initrd. That's not a standard
feature so unless RedHat tweaked the Makefile then I don't suppose it will.

Personally I build my kernels with hardwired support for the root filesystem and whatever
hardware i need (eg scsi raid controller) to access said filesystem. Some
say this is best others not..... YMMV.


hih
nick@nexnix


-----Original Message-----
From: Nick Lindsell [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 9:18 AM
To: [EMAIL PROTECTED]
Subject: Re: Custom Kernel wont boot


At 06:00 17/02/2003 -0800, you wrote:
>I have Red Hat 8 setup with all the kernel-devel packages installed.  I
just
>downloaded the 2.4.20 kernel and attempted to configure it. After I do
setup
>everything I rebooted. I am currently using the Grub boot manager and when
I
>boot it gives me the following error:
>'Cannot open root device "LABEL=/" or 00:00
>Please append a correct "root=" boot option
>Kernel panic: VFS:
>Unable to mount root on 00:00'
>
>I did a make install to add the line into the grub.conf file but this error
>still occurs. Any ideas?

Did you build the relevant root filesystem support into the kernel or make
it
as a module and rebuilt initrd?


hih
nick@nexnix


>Michael
>
>
>
>--
>redhat-list mailing list
>unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
>https://listman.redhat.com/mailman/listinfo/redhat-list



--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list



--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list


--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to