You are not logged in.
Pages: 1
I was recommended install grub instead lilo (under lilo everything was OK). I proceeded exactly according the Grub ArchWiki: installed grub
grub-install /dev/hda
removed lilo
pacman -R lilo
and configured menu.lst. After reboot grub loaded vmlinuz26 and the bott process run until "kernel panic". The last line told that the root partition was not recognized. The root partition in kernel option was defined as
root=/dev/discs/disc0/part3
just as it is in fstab. What is wrong with that??? I checked grub config lines several times, there were no mistypings there...
Our tomcat for your mice! Archlinux for your comps! Alfa Romeo for your roads! Faster running guaranted!
Offline
kernel 2.6.13 doesn't use that devfs naming scheme anymore, it uses udev. So your root= line should say /dev/hda3 instead of discsblabla. Change your fstab entries too.
Offline
But I have in root= line option
devfs=nomount
With the same fstab partition scheme and lilo.conf (append devfs=nomount) udev was loaded, not devfs... modprobe.conf was working, not modules.conf... I am completely confused...
Our tomcat for your mice! Archlinux for your comps! Alfa Romeo for your roads! Faster running guaranted!
Offline
Doesn't matter - the DevFS naming scheme no longer works. Change both your fstab and menu.lst to the naming scheme used by a static /dev - /dev/hda3, etc.
Offline
As you are told when installing the kernel, Gulluble Jones is right.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
Just as a clarification - the title says that GRUB caused a kernel panic - this is not true. GRUB loads the kernel. Either GRUB fails, or the kernel panics - they do not work together.
In this case, GRUB passes parameters to the kernel. It is the root= parameter which failed, and the kernel itself paniced (Unable to mount root device).
Offline
Pages: 1