On Sat, 2 Oct 2004, Alexandre Van Haecke wrote: > > Hi all, > Switching from Fedora kernel 2.6.5-1.358 to 2.6.8-1.521, I get the > following message at the very beginning of the boot sequence : > "Kernel Panic : VFS Unable to mount root fs on unknown-block (0, 0)" > I rebuilt the kernel and got the same behavior with my new custom > kernel. > To be precise, I use Fedora Core 2 x86_64 on a Shuttle SN95G5 (Athlon 64 > 3500+ socket 939, nVidia nForce3 Ultra). > If someone with the same hardware architecture got the 2.6.8 to work, I > am interested ! > Bye, > > Alex Van Haecke > > > > PS : Here is my grub.conf file (I use grub) : > > default=2 > timeout=10 > splashimage=(hd0,5)/boot/grub/splash.xpm.gz > title Fedora Core (2.6.8-1.521custom) > root (hd0,5) > kernel /boot/vmlinuz-2.6.8-1.521custom ro root=LABEL=/ quiet > initrd /boot/initrd-2.6.8-1.521custom.img > title Fedora Core (2.6.8-1.521) > root (hd0,5) > kernel /boot/vmlinuz-2.6.8-1.521 ro root=LABEL=/ quiet > initrd /boot/initrd-2.6.8-1.521.img > title Fedora Core (2.6.5-1.358) > root (hd0,5) > kernel /boot/vmlinuz-2.6.5-1.358 ro root=LABEL=/ quiet > initrd /boot/initrd-2.6.5-1.358.img I don't have the same hardware, but have run into this issue, before. Does your system actually have initrd-2.6.8-1.521custom.img and/or initrd-2.6.8-1.521.img in its /boot directory? If not, boot back to 2.6.5-1.358, then, as root, run: mkinitrd /boot/initrd-2.6.8-1.521custom.img 2.6.8-1.521custom and mkinitrd /boot/initrd-2.6.8-1.521.img 2.6.8-1.521 to create the initrd images you need. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit http://www.bubbanfriends.org/mailman/listinfo/site-update, or send a message to: site-update-request@xxxxxxxxxxxxxxxxx with a message of: subscribe
