Why does this happen?

[loops84]

I installed fedora 8 on a partition dual booting with windows XP. The install goes fine, and the yum update goes fine. The nvidia driver installs fine too, but when I reboot I get to the section in grub where I get to choose what to boot, and It shows two different linux kernels. The one from the original install and the one from the update. When I select the updated kernel I get errors saying that it can't find / and is unable to mount it. The other kernel option works but does not allow me to use the nvidia driver from livna. How do I fix this? is this something that is supposed to happen when the kernel get's updated?

[loops84]

I get cannot find file system, failed to boot or something like that. I know it aint supposed to happen but it's a drag. I can install and update fedora 8 just fine in VMware. But as soon I get it installed on a partition the kernel update screws things up.

[jtang613]

Show us your /boot/grub/grub.conf

[loops84]

here is my grub.conf file



# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,1)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda2
default=0
timeout=5
splashimage=(hd0,1)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.24.5-85.fc8)
root (hd0,1)
kernel /vmlinuz-2.6.24.5-85.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.24.5-85.fc8.img
title Fedora (2.6.23.1-42.fc8)
root (hd0,1)
kernel /vmlinuz-2.6.23.1-42.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.23.1-42.fc8.img
title Other
rootnoverify (hd0,0)
chainloader +1

[meowdin]

duno why but my grub is something like

root (hd0,0)
kernel /boot/vmlinuz-2.6.23.1-42.fc8 ro root=Label=/ rhgb quiet
initrd /initrd-2.6.23.1-42.fc8.img

hopefully got referencial value