[lkml]   [2001]   [Dec]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: pivot_root and initrd kernel panic woes
Boy, what a detailed report!

I never used lilo, but:

> After which I added this line my /etc/lilo.conf file:
> image=/boot/vmlinuz-2.4.9-12smp
> label=2.4.9smp
> append="initrd=/boot/initrd-2.4.9-12smp.img root=/dev/ram0
> init=/linuxrc rw"
> Reran lilo
> [root@tinkerbell /root]# lilo -v
> LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
> 'lba32' extensions Copyright (C) 1999,2000 John Coffman
> Reading boot sector from /dev/sda
> Merging with /boot/boot.b
> Mapping message file /boot/message
> Boot image: /boot/vmlinuz-2.4.2-2smp
> Mapping RAM disk /boot/initrd-2.4.2-2smp.img
> Added linux
> Boot image: /boot/vmlinuz-2.4.2-2
> Mapping RAM disk /boot/initrd-2.4.2-2.img
> Added linux-up *
> Boot image: /boot/vmlinuz-2.4.9-12smp ## Entry for SMP kernel
> Added 2.4.9smp
> Boot image: /boot/vmlinuz-2.4.9-12-smp-4th
> Added custom
> /boot/boot.0800 exists - no backup copy made.
> Writing boot sector.

"Mapping RAM disk" seems to be missing for 2.4.9-12, so you'll get:

> "VFS: Cannot open root device "ram0" or 01:00
> Please append a correct "root=" boot option
> Kernel panic: VFS: unable to mount root fs on 01:00 "

Check your lilo conf. Include it in your reply.

BTW, don't go for 2.4x, x>10. initrd is broken there and is still unfixed.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:14    [W:0.087 / U:0.296 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site