Hello there,
I recently noticed that the Limine EFI fallback loader is not being updated on my system. I’m using a Gigabyte B650M DS3H motherboard and every time I update the BIOS the regular Limine boot entry disappears and I’m forced to use on the EFI fallback entry in order to get the usual Limine NVRAM entry back.
This is how I discovered that my fallback loader was quite outdated, to the point where its interface looked different from the current Limine entry stored in NVRAM.
I have a few questions:
-
Is this intended? Like on a fresh install of Cachy OS is the fallback EFI loader created once and then intentionally left unchanged afterwards?
-
If the fallback loader becomes significantly outdated over time, could that eventually lead to boot issues when it is actually needed?
-
Would it make sense to automatically update the fallback loader via a pacman hook when Limine is updated, or is there a preferred/safer way to handle this?
For my two CachyOS installations, I ended up creating a pacman hook to overwrite the fallback EFI binary with the current Limine version on each update:
cat /etc/pacman.d/hooks/95-limine-fallback.hook
[Trigger]
Operation = Install
Operation = Upgrade
Type = Package
Target = limine
[Action]
Description = Updating Limine EFI fallback loader...
When = PostTransaction
Exec = /usr/bin/install -Dm644 /usr/share/limine/BOOTX64.EFI /boot/EFI/BOOT/BOOTX64.EFI