Description of problem: I have installed MGA7b2 to a formatted sdb partition, my /home dir is untouched from the old MGA6. I have update beta2 many times and sometimes It involves new kernels update. Two day ago I update to kernel 5.0.x, but uname -r is still 4.20.9-desktop-1.mga7 after reboot. The MCC boot sections is untouched from installation time. Now I have try to set 5.0.x as kernel in MCC boot section but the kernel remain to 4.20.9. Now I have set "Mageia" as kernel version in MCC/boot as the original default choice. The kernel is not updated, this is the trouble. In MGA7b2 boot partition I had the MGA6 boot MBR, so the list of kernel is very long and comprise MGA6, MGA7b2, 4.x, 5.0x version kernel.
Thanks for the report. Please attach the output of: ls -al /boot | sort and also attach /boot/grub2/grub.cfg and /boot/grub2/custom.cfg
CC: (none) => marja11Keywords: (none) => NEEDINFO
Created attachment 10957 [details] /boot
Created attachment 10958 [details] grub.cfg
Created attachment 10959 [details] custom.cfg
Created attachment 10960 [details] MCC/boot
In the between (yesterday) I have change my boot disk to sda and set in MCC/boot as bootloader Grub and not grub2. Now I have uname -r as linux 5.0.8, the last. Today if I open MCC/boot I have this option: https://bugs.mageia.org/attachment.cgi?id=10960 with GRUB2, /dev/sdb Now I reboot and in the BIOS I see like boot device my sda (an old mechanical HD sata). So it is unclear from MCC/boot to see what is boot disk and boot loader actually setted. Maybe it is another bug that I can fill-up.
@Sandro The situation has become too confused - the previous comment. You have changed things so that the original situation has gone - particularly the actual Grub2 boot menu (to compare with the attachments in comments 2 & 3), what it offered and what happened when you chose different entries. Did none of them yield the latest kernel? It was confusing to revert to Grub from Grub2. We are now well into M7 beta 3 (already 5.0.9-desktop-1.mga7). Would you be willing to install that and start all over again? If you hit the same sort of problem again, we need to persue it before you change anything. And no new bug yet, please. TIA
CC: (none) => lewyssmith
@Lewis Sorry, it is my first try to download and use a beta version, I have a lot to learn. Next time I will stay on the bug without looking for a workaround. TY for your time.
Thank you for your understanding. Leaving the bug open just in case. Come back here if you hit the same problem, with the attachments noted in comment 1.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
Does it help to run "update-grub2 && grub2-install" as root but without the quotes and then reboot?
CC: (none) => hamnisdude
(In reply to Kristoffer Grundström from comment #10) > Does it help to run "update-grub2 && grub2-install" as root but without the > quotes and then reboot? In non UEFI systems grub2-install needs parameters. update-grub2 may help assuming that /etc/default/grub has correct settings.
CC: (none) => zen25000
I am getting a strange result from uname which might go back to the same origin as this bug: uname -r replies 5.0.5-desktop-2.mga7 although I have installed several newer kernels, and although /boot/vmlinuz is a link to the latest kernel (and the other links in /boot are also correct); uname -a gives the date of Mar 29 20:36 which roughly corresponds to the date when 5.0.5 had been installed. I am using cauldron, originally beta-1, and continuously updated. Today I installed beta-3; to decide whether the problem persists with beta-3 I need to wait until the kernel has been updated a couple of times. Or should I submit this as a bug on uname ? (I do not see any reference to grub2)
CC: (none) => juergen.harms
(In reply to Juergen Harms from comment #12) > ...Today I > installed beta-3; to decide whether the problem persists with beta-3 I need > to wait until the kernel has been updated a couple of times. Thank you for installing beta-3. It will certainly help to start with a clean situation. If you have updated *that*, you should certainly have more recent kernels as well as that installed. These should be shown in the Grub2 boot menu. > Or should I submit this as a bug on uname ? If the 'uname' problem persists, it warrants a separate bug. Before submitting it, please try choosing different Grub menu entries (effectively different kernels) to see what 'uname' reports for each one. In the new bug, please attach the output of: $ ls -al /boot | sort and /boot/grub2/grub.cfg
Closing at it refers to too old beta time.
Status: UNCONFIRMED => RESOLVEDCC: (none) => ouaurelienResolution: (none) => OLD