I installed a GRUB theme and changed some options in the config but now I need to run update-grub (alias for grub2-mkconfig -o /etc/grub2-efi.cfg) after every kernel update or else that new kernel version won’t boot. Does anybody know a fix for this?
Checking inside
/usr/lib/kernel/install.d/, you can see the mechanisms in place for installing new kernel entries. Not knowing what you did to your config (did you back it up before making changes?), you should check if the entries are being populated properly in/boot/loader/entries/. If they are, you have likely toyed with the BLS config in some way that broke being able to load dynamic entries without mkconfig.If that is indeed the case, I wouldn’t know exactly what you touched to break it, but this discussion forum might give some insight.
If this isn’t the problem, it might be helpful to post your grub config minus any sensitive details to help determine what is going wrong.
I only installed the theme (I think by using grub customizer) and then I changed some options in
/etc/default/grubto e.g. show a submenu for the kernel versions instead of having them all in one list. I don’t know what BLS is but I have the optionGRUB_ENABLE_BLSCFGset to false, if I remember correctly, I set that to false because the theme wouldn’t show up otherwise or something. But from your comment, it sounds like BLS has something to do with dynamically loading kernel entries, so maybe setting that to false is the source of my issue.Based on how the script
/usr/lib/kernel/install.d/99-grub-mkconfig.install(a script that runs on kernel installations) behaves, unless you are running in Xen Hypervisor or are on an architecture that doesn’t support it, Fedora by default expects to haveGRUB_ENABLE_BLSCFGset to true. This script is provided by the packagegrub2-common, so it’s unlikely it can be removed without removing the GRUB bootloader’s management system entirely.More than likely, most customizations will work just fine with
GRUB_ENABLE_BLSCFGset to true as long as you properly rungrub-mkconfig(or justupdate-grub) after you make those changes so that they get applied to the bootloader portion of GRUB itself.If for some reason you do absolutely need to disable BLS in order to get the customization you want, the proper way to enforce
grub-mkconfigon new kernels would be to write a script in the/usr/lib/kernel/install.d/directory titled like98-grub-manual-mkconfig.installthat would forcibly run the proper mkconfig command after kernel installation and initramfs generation.I just tested it, enabling
GRUB_ENABLE_BLSCFGfixed the issue. Unfortunately, submenus don’t work with it enabled. That was probably why I disabled it. Thanks for your help.
ChatGPT gave the following. Follow at your own risk. Most important is to check if the file locations are compatible with Fedora.
To automate running the update-grub command after each kernel update, you can create a script and set it up to run automatically. Here’s a more direct approach:
-
Open a text editor and create a new script file. For example, you can name it “update_grub.sh”.
-
In the script file, add the following lines:
#!/bin/bash /usr/sbin/update-grub -
Save the script file in a location where it can be easily accessed, such as your home directory.
-
Make the script executable by running the following command in the terminal:
chmod +x /path/to/update_grub.sh -
Next, you can set up a cron job to run this script automatically. Open your crontab file by running:
crontab -e -
Add a new line at the end of the crontab file to schedule the script to run after each kernel update. For example:
@reboot /path/to/update_grub.sh -
Save and exit the crontab file.
With these steps, the update-grub command will be executed automatically after each kernel update, ensuring that the new kernel version boots successfully.
This seems like a terrible bandage fix rather than letting the system mechanisms do what they are supposed to.
I’ll probably end up doing something like this if I don’t find out how to actually solve this issue but yeah, it’s just a bandaid fix for another issue. I wonder if it might be an issue that needs to be fixed by the Fedora maintainers themselves but I’d like to find out what’s actually causing it before reporting it.
-
