Kernel 3.4.6 no boot option

[Kakao]

Kernel 3.4.6-2 is installed but it does not appear as boot option although there is an entry in /boot/grub2/grub.cfg:

menuentry 'Fedora (3.4.6-2.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-047568b1-c806-4a34-a4bc-f188264dc3e8' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod part_msdos
        insmod diskfilter
        insmod mdraid1x
        insmod ext2
        set root='mduuid/e74b42397715f5b5a0cb22deefeb3a5e'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint='mduuid/e74b42397715f5b5a0cb22deefeb3a5e'  09f33b13-b722-4321-84a7-f2167220d718
        else
          search --no-floppy --fs-uuid --set=root 09f33b13-b722-4321-84a7-f2167220d718
        fi
        echo 'Loading Fedora (3.4.6-2.fc17.x86_64)'
        linux   /vmlinuz-3.4.6-2.fc17.x86_64 root=/dev/mapper/luks-906ec399-c797-4d9c-8cb0-91e66dd62ad5 ro rd.lvm=0 rd.dm=0 SYSFONT=True  KEYTABLE=br-abnt2 rd.luks.uuid=luks-8f7ede84-309c-4504-9792-e049ef55f705 rd.md.uuid=43544800:8b65b2d9:65fc4d69:4095800b rd.luks.uuid=luks-906ec399-c797-4d9c-8cb0-91e66dd62ad5 rd.md.uuid=e74b4239:7715f5b5:a0cb22de:efeb3a5e rd.md.uuid=85b41a35:96a82ab8:2db5deae:533b944b LANG=en_US.UTF-8 rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau
        echo 'Loading initial ramdisk ...'
        initrd /initramfs-3.4.6-2.fc17.x86_64.img
}

How to make the boot option appear?

[AlexanderFloyd]

Try to use grub2-mkconfig to recreate configuration.

#grub2-mkconfig -o /boot/grub2/grub.cfg

[stoat]

Originally Posted by Kakao

Kernel 3.4.6-2 is installed but it does not appear as boot option although there is an entry in /boot/grub2/grub.cfg

I've been playing around with Fedora 17 for a day or so and noticed that, too. I did find a boot menu entry for the new kernel in "Advanced options for Fedora". I had already tried the grub2-mkconfig idea. It did not change the situation for me.

P.S.: I just checked again, and the new kernel now is booted by the Fedora menu entry at the top. Maybe the grub2-mkconfig thing did fix it. Thinking about it more, I don't trust my memory of this event at all now. I regret posting here now. Sorry. I hope you get yours fixed the way you want it.

[Kakao]

grub2-mkconfig did not work for me neither yum removing and reinstalling.

[dd_wizard]

Originally Posted by stoat

I've been playing around with Fedora 17 for a day or so and noticed that, too. I did find a boot menu entry for the new kernel in "Advanced options for Fedora". I had already tried the grub2-mkconfig idea. It did not change the situation for me.

P.S.: I just checked again, and the new kernel now is booted by the Fedora menu entry at the top. Maybe the grub2-mkconfig thing did fix it. Thinking about it more, I don't trust my memory of this event at all now. I regret posting here now. Sorry. I hope you get yours fixed the way you want it.

Yup, that's what grub2-mkconfig does, normally. The old grubby generated entry at the top of the menu disappears, as well.

Kakao, have you tried opening the Advanced options grub entry? You should see the 3.4.6 kernel listed there.

dd_wizard

[Kakao]

Where do I find the "Advanced options grub entry"? I searched for it without success.

[Kakao]

After installing 3.5.0 I now have it in /boot/grub2/grub.cfg but still on option to boot it:

menuentry 'Fedora (3.5.0-2.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.4.5-2.fc17.x86_64-advanced-047568b1-c806-4a34-a4bc-f188264dc3e8' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod diskfilter
        insmod mdraid1x
        insmod ext2
        set root='mduuid/e74b42397715f5b5a0cb22deefeb3a5e'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint='mduuid/e74b42397715f5b5a0cb22deefeb3a5e'  09f33b13-b722-4321-84a7-f2167220d718
        else
          search --no-floppy --fs-uuid --set=root 09f33b13-b722-4321-84a7-f2167220d718
        fi
echo 'Loading Fedora (3.5.0-2.fc17.x86_64)'
        linux   /vmlinuz-3.5.0-2.fc17.x86_64 root=/dev/mapper/luks-906ec399-c797-4d9c-8cb0-91e66dd62ad5 ro rd.lvm=0 rd.dm=0 SYSFONT=True  KEYTABLE=br-abnt2 rd.luks.uuid=luks-8f7ede84-309c-4504-9792-e049ef55f705 rd.md.uuid=43544800:8b65b2d9:65fc4d69:4095800b rd.luks.uuid=luks-906ec399-c797-4d9c-8cb0-91e66dd62ad5 rd.md.uuid=e74b4239:7715f5b5:a0cb22de:efeb3a5e rd.md.uuid=85b41a35:96a82ab8:2db5deae:533b944b LANG=en_US.UTF-8 rhgb quiet
        echo 'Loading initial ramdisk ...'
initrd /initramfs-3.5.0-2.fc17.x86_64.img
}

---------- Post added at 07:50 PM ---------- Previous post was at 07:24 PM ----------

This is the output of grub2-mkconfig

# grub2-mkconfig -o /boot/grub2/grub.cfg 
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.5.0-2.fc17.x86_64
Found initrd image: /boot/initramfs-3.5.0-2.fc17.x86_64.img
/usr/sbin/grub2-probe: warning: Couldn't find physical volume `(null)'. Some modules may be missing from core image..
Found linux image: /boot/vmlinuz-3.4.6-2.fc17.x86_64
Found initrd image: /boot/initramfs-3.4.6-2.fc17.x86_64.img
Found linux image: /boot/vmlinuz-3.4.5-2.fc17.x86_64
Found initrd image: /boot/initramfs-3.4.5-2.fc17.x86_64.img
  No volume groups found
done

---------- Post added at 08:41 PM ---------- Previous post was at 07:50 PM ----------

I just discovered that while booting with only one of the 2 HDs of the RAID 1 array alternately one boots to 3.4.5 and the other to 3.5.0. Now to try to fix...

[lightman47]

Another fly in the ointment - when I did yum update on my FC17 machines, it downloaded what it said was 3.4.6-2 ... but it INSTALLED 3.5 during the installation of that. <?????> What the heck?? Incidentally, this happened on all FOUR of my FC 17 machines 32 and 64 bit alike!

Not looking for answers - just wanted to toss that out there ...

[dcharlespyle]

Watch those enabled repositories. That's what I think got you this time around. You had 3.4.6-2 on the regular updates repository and you may well have a debug or updates-testing repository enabled at the same time. If so, that would explain why both kernel versions were available to Yum and why you got the 3.5.0 kernel, too.

I've had that happen to me before, so I have experienced that. Don't know about your RAID configuration, though, as I have not used RAID configurations since 2006.