Bug 11483 - Latest kernel update does not become the default
Summary: Latest kernel update does not become the default
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-17 03:19 CEST by Doug Laidlaw
Modified: 2013-12-06 04:32 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:

Attachments
/boot/grub2/grub.cfg (13.72 KB, application/octet-stream)
2013-10-27 02:08 CET, Doug Laidlaw 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Doug Laidlaw 2013-10-17 03:19:52 CEST 
Description of problem: 
On upgrading to latest kernel 3.12.0, the symlinks in /boot point to it, but Grub2 still selects the existing kernel 3.11.4


Version-Release number of selected component (if applicable):
As above.

How reproducible:


Steps to Reproduce:
1.
2.
3.

I have tried re-creating the grub2 menu.

This may disappear with the next kernel.

Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-10-17 22:19:59 CEST 
ll /boot ?
Comment 2 Doug Laidlaw 2013-10-18 01:58:58 CEST 
ll /boot
total 35168
-rw-r--r-- 1 root root   152897 Oct  4 03:00 config-3.11.4-server-1.mga4
-rw-r--r-- 1 root root   154411 Oct 14 18:07 config-3.12.0-server-0.rc5.1.mga4
drwxr-xr-x 2 root root     4096 Oct 14 08:15 dracut/
-rwxr-xr-x 1 root root   548352 Oct 17 05:46 gfxmenu*
drwxr-xr-x 2 root root     4096 Sep  5 17:22 grub/
drwxr-xr-x 6 root root     4096 Oct 17 05:48 grub2/
-rw------- 1 root root 10147844 Oct  6 12:26 initrd-3.11.4-server-1.mga4.img
-rw------- 1 root root 10151986 Oct 15 12:37 initrd-3.12.0-server-0.rc5.1.mga4.img
lrwxrwxrwx 1 root root       37 Oct 15 12:37 initrd.img -> initrd-3.12.0-server-0.rc5.1.mga4.img
lrwxrwxrwx 1 root root       31 Oct  6 12:27 initrd-server.img -> initrd-3.11.4-server-1.mga4.img
-rw-r--r-- 1 root root   308314 Jan 21  2013 mageia.bmp
-rw-r--r-- 1 root root   202316 Oct  4 03:00 symvers-3.11.4-server-1.mga4.xz
-rw-r--r-- 1 root root   225524 Oct 14 18:07 symvers-3.12.0-server-0.rc5.1.mga4.xz
-rw-r--r-- 1 root root  2276036 Oct  4 03:00 System.map-3.11.4-server-1.mga4
-rw-r--r-- 1 root root  2305635 Oct 14 18:07 System.map-3.12.0-server-0.rc5.1.mga4
lrwxrwxrwx 1 root root       34 Oct 15 12:37 vmlinuz -> vmlinuz-3.12.0-server-0.rc5.1.mga4
-rw-r--r-- 1 root root  4725632 Oct  4 03:00 vmlinuz-3.11.4-server-1.mga4
-rw-r--r-- 1 root root  4779232 Oct 14 18:07 vmlinuz-3.12.0-server-0.rc5.1.mga4
lrwxrwxrwx 1 root root       28 Oct  6 12:27 vmlinuz-server -> vmlinuz-3.11.4-server-1.mga4
Comment 3 Manuel Hiebel 2013-10-26 22:40:02 CEST 
what's your grub2 config ?
Comment 4 Doug Laidlaw 2013-10-27 02:08:55 CET 
Created attachment 4462 [details]
/boot/grub2/grub.cfg

My bootloader is grub2 from Official, but it has been grub2 from Cauldron, then changed back again.

The default kernel is always the earlier one.
Comment 5 Doug Laidlaw 2013-11-13 12:01:12 CET 
Booting into the latest kernel and running grub2-config from there was no help.

I notice an updated grub2 in the submission queue.  It hasn't reached me yet. I will keep a lookout for it.
Comment 6 Doug Laidlaw 2013-12-03 02:08:38 CET 
There is nobody on the cc list.  It must be only me.  I have a couple of hardware-related bootup problems.
Comment 7 Doug Laidlaw 2013-12-06 04:32:44 CET 
A new kernel has just come down and this bug has fixed itself.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.