On Sun, Nov 24, 2002 at 01:49:07PM -0700, Tom Schutter wrote:
| On Sun, 2002-11-24 at 07:44, Charles Baker wrote:
| > I had the same problem when I first moved to a 2.4.x
| > kernel on a plain intel based machine. The problem wa
| > slack of initrd line in lilo.conf . For example,
| >
| > image=/vmlinuz
| > initrd=/initrd.img
| > label=Linux
| > read-only
| > # restricted
| > # alias=1
|
| AFAIK this is only required by 2.4.19, and I am running 2.4.18.
| But of course, I could be wrong...
The initrd line is required for _all_ 2.4.x kernels (at least since
2.4.7 when I started using 2.4) /which were configured with initrd
support/. The debian-packaged 2.4 kernels use an initrd, and thus you
need that option. If you compiled the kernel yourself you can disable
that feature. One common cause for failure to mount the root
partition is a missing driver (usually for the disk controller). With
the initrd-compiled kernels you'll definitely have missing drivers if
you don't load the initrd.
HTH,
-D
--
How great is the love the Father has lavished on us,
that we should be called children of God!
1 John 3:1
http://dman.ddts.net/~dman/
Attachment:
pgpgif3SwEFiZ.pgp
Description: PGP signature