From a google check for the default grub kernel boots it seems that if you add the following two statements into /etc/default/grub and then run grub2-mkconfig grub will use the last selected kernel as the default boot kernel.On Sat, 2023-01-07 at 20:40 -0500, Sam Varshavchik wrote:Can anyone try using grubby --set-default to change the default boot kernel to something other than the most recently-installed kernel, successfully? It tells me that it obeys my request, and grubby --info=DEFAULT shows that the default boot kernel is what I specified. But at boot the grub menu still highlights the most recently installed kernel, and that's what boots by default.As I recall, there was always several aspects to this. Each menu stanza for the particular kernel you booted needed to have a "set default" option set in it. So that when you picked that menu option at boot time, it set the default variable to itself *and* *then* booted that kernel. If you booted from a menu choice that didn't include that option, it wouldn't set itself as the default for the next boot. It was a per-stanza thing, not a once in the GRUB config, thing. And at boot/reboot, GRUB had to be configured to read the default variable to see which menu item to boot. I lack the perseverance to read through the conglomeration of GRUB menu files to see what it does these days.
GRUB_SAVEDEFAULT=true
GRUB_DEFAULT=savedregards,
Steve
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
