On Mon, 14 Jan 2002, Richard B. Johnson wrote: > RAMDISK: Compressed image found at block 0 > Freeing initrd memory: 581k freed > kernel panic: VFS: Unable to mount root fs on 01:00 > > Has somebody fixed this or is it expected that nobody uses > an initial RAM disk on 2.4.17 ..or.. is this not the latest > "stable" version of Linux to use? RAMDISK: Compressed image found at block 0 Freeing initrd memory: 5384k freed VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 172k freed I booted with Linux-2.4.0 up to 2.4.18-pre3. Did you specify root=/dev/hda2 in your boot file? Jeff. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: initrd failure on Linux-2.4.17"Richard B. Johnson" <root _at_ chaos.analogic.com>
- initrd failure on Linux-2.4.17"Richard B. Johnson" <root _at_ chaos.analogic.com>
- Prev by Date: Linux 2.5.1-dj15
- Next by Date: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Previous by thread: initrd failure on Linux-2.4.17
- Next by thread: Re: initrd failure on Linux-2.4.17
- Indexes:[Main][Thread]