PDA

View Full Version : New Kernel 2.6.16 In Grub....But Not At Boot!



Flyboy917
30th March 2006, 02:24 AM
I just installed the new kernel and grub.conf updated, but when I boot, the new kernel is not an option. The boot screen has my current kernel and the original install, but not the new one! 2.6.16 isn't listed as an option.

grub.conf:
# 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 (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
#hiddenmenu
title Fedora Core (2.6.16-1.2080_FC5)
root (hd1,0)
kernel /vmlinuz-2.6.16-1.2080_FC5 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.16-1.2080_FC5.img
title Fedora Core (2.6.15-1.2054_FC5)
root (hd1,0)
kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.15-1.2054_FC5.img
title Other
rootnoverify (hd0,0)
chainloader +1

rpm -qa |grep kernel
kernel-2.6.15-1.2054_FC5
kernel-devel-2.6.16-1.2080_FC5
kernel-2.6.16-1.2080_FC5


What?????

stanmc
30th March 2006, 03:54 AM
Do you have a System.map, initrd and vmlinuz for this kernel in your /boot directory. My install didn't and I had to reinstall with SELinux set to setenforce 0.

Flyboy917
30th March 2006, 04:30 AM
Do you have a System.map, initrd and vmlinuz for this kernel in your /boot directory. My install didn't and I had to reinstall with SELinux set to setenforce 0.

Yes,
Now for more: I logged in as root, no su or su -, ran yumex, and removed a kernel that rpm -qa didn't list. Quit yumex, restarted yumex, and kernel 2......16-2080 showed up as an update...although I had already installed it, it was in my grub conf, and was showing up in rpm -qa!
I ran yum clean headers, yum clean metadata. re-ran yumex....still showing up as an update. went ahead and installed it...again. checked boot. current kernel and 16 listed.
reboot, current kernel and non-existant kernel showing in grub boot screen.
for grins, booted non existant kerenl.....error, error....freeze.
reboot..........same crap.

I'm thinking my system is hosed....

bob
30th March 2006, 05:05 AM
Try 'rpm -e kernel-2.6.16-1.2080_FC5' and 'rpm -e kernel-devel-2.6.16-1.2080_FC5' then 'yum clean all' and then 'yum update' to see if it installs correctly this time. Beats reinstalling the system!

Flyboy917
30th March 2006, 06:44 AM
When I installed FC5 I chose NOT to use a large linux partition on hda and just to put Fedora on hdb.
Last week, while playing with LVM tools, I noticed that LVM Volume 00 was still tied to hda but it wasn't (was) being utilized. I failed to notice the 0.10meg partition that was grub and detached hda from the LVM volume.
So tonight, when I installed the new kernel, it wrote to grub.conf, but it didn't write to grub!
So...I re-initialized hdax to LVM, Linux rescue from the cd, re-install grub, and wa lah!
Back with the correct new kernel!

Thanks for the help....JOB...you got the wheels going.

Dubious Dave
30th March 2006, 01:55 PM
This sounds like the problem I ran into last night. I used yumex & yum (separately) to update the kernel, but it never boots into that kernel. I haven't checked since updating the second time to see if the kernel is still available for update.

FC5 is installed on hda with the default settings.

What should I do?

stanmc
30th March 2006, 04:34 PM
FC5 is installed on hda with the default settings.

What should I do?
Have you checked /boot to see if the installation using yum or yumex produced the System.map, initrd and vmlinuz for the new kernel(s)?

Dubious Dave
30th March 2006, 05:09 PM
I will do that tonight. I assume all I need to do is look in /boot and I will see those three files....? (Newbie here)

Dubious Dave
1st April 2006, 02:21 PM
Today it booted up into the correct kernel and System.map, initrd and vmlinuz exsist in /boot. I don't know what happened, but it works now. Maybe operator error.