See forum thread and links within. Docs should be modified to ensure that installs with ext2 filesystem DO NOT use LILO as bootloader, only GRUB can be used. Reproducible: Always Steps to Reproduce: 1. install off iso, using ext2 2. emerge LILO 3. reboot Actual Results: VFS: Mounted root (ext2 filesystem) readonly. mount_devfs():unable to mount devfs, err: -2 Freeing unused kernel memory: 88k freed Warning: unable to open an initial console. Kernel panic: no init found. Try passing init= option to kernel. Expected Results: Booted normally
actually you *can* use ext2+lilo ... theres more going on here ... could you post your /etc/fstab and/or lilo config ?
OK. Dunno, for me all I did was change from LILO to Grub and the box booted perfect. Here's my /etc/fstab: /dev/sda2 /boot ext2 noauto,noatime 1,1 /dev/sda5 / ext2 noatime 0 0 /dev/sda7 none swap sw 0 0 /dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0 proc /proc proc defaults 0 0 tempfs /dev/shm tmpfs defaults 0 0 Also, this is a dual-boot machine, and I had installed Win XP Pro, fat32 on sda1 the day before. Lilo.conf: boot = /dev/sda prompt map = /boot/System.map lba32 timeout=150 default=Windows image = /boot/bzImage root = /dev/sda2 label = Gentoo read-only # read-only for checking other = /dev/sda1 label = Windos table = /dev/sda All other lines were commented out from the default initial lilo.conf
shouldnt the boot line in your lilo be /dev/sda2 instead of /dev/sda ?
I was going by Codelisting 25.5 in the docs: "boot=/dev/hda" http://www.gentoo.org/doc/en/gentoo-x86-install.xml
i'm not saying thats the answer, i'm asking if that makes lilo work ... i dont use lilo myself ...
Sorry, dunno. I used Grub since then. Do you want me to try and go back to LILO and mess with it?
well yes since you reported this bug ;)
OKie. I'll track down the procedure to change bootloaders, replace "boot = /dev/sda" with "boot = /dev/sda2" and report back.
what version of the kernel were you using? I have had this problem with some gentoo-sources-2.4.18 on an Athlon 900 w/ AMD 760 chipset. BTW, boot=/dev/sda is valid: it installs the bootloader on the MBR of sda. boot=/dev/sda2 installs the bootloader on the second partition of sda.
This is an invalid bug - the boot=/dev/sda is fine, your bootloader is installed on your MBR. The line that kills you is: root = /dev/sda2 This is looking for a root fs on sda2, and judging by your fstab, that is your boot partition. The line should read: root=/dev/sda5 (which is your root fs)
