On 04/28/04 11:47, Simon Wong wrote:
<console>
RAMDISK: Couldn't find valid RAM disk image starting at 0
VFS: Cannot open root device "305" or 03:05
Please append correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:05
</console>

It seems to be trying to use devfs which I do not have included in my
lilo.conf.

It's not telling you it's using devfs. That's the kernel trying to find an initrd image, and not being able to. It can't boot any further because the modules it needs to mount the root partition are in the initrd image. :-)


A default debian installation has a line like
initrd = /initrd.img

in lilo.conf. Like the /vmlinuz files, /initrd.img is then a symlink to /boot/initrd.img-kernel-version . Do you have an initrd line in lilo.conf, and does it point to a valid initrd image?

Using my Fedora installation I can see that the partitions and data are all
okay.

If you're using an unmodified lilo.conf, specifying "linuxOLD" on the lilo boot prompt should boot with your old kernel.


Hope this helps,
--
Pete
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to