Written by Dalto
Full transparency on the GRUB issue
Since the recent grub issue has impacted a lot of people, we wanted to provide full transparency based on the information we have so far. The situation with this package is still evolving and we will update this post with more information as it becomes available.
After updating to grub 2.06.r322 many users reported that their machines could fail to boot or booted directly into the BIOS or another OS.
Starting with this commit, grub introduced a call to
fwsetup --is-supported in
/etc/grub.d/30_uefi-firmware. If the version of grub you have installed via the
grub-install command didn’t support that command, it caused grub to fail.
Prior to the most recent version, grub only registered the
fwsetup if detected support. If your machine detected support, you would have had the
fwsetup command registered and the failure wouldn’t occur.
Follow the instructions in this post 1 to chroot into your system and run
grub-install to install the latest version.
Follow the instructions in this post 1 that relate to that scenario. Basically, run
grub-install after upgrading but before rebooting.
According to the bug report 1, Arch will produce a version of the package without that commit while working with grub upstream to determine next steps
We can’t answer this question absolutely but there are at least two factors to consider:
- Not all grub users were impacted by this issue
- Many Arch users don’t run grub
We are exploring all options here but the reality is that this has never happened before. Blindly running
grub-install everytime would be knee-jerk reaction and probably create more problems than it would solve.
We were already considering moving away from grub by default and that may happen at some point in the future.
First we will wait to see what Arch decides to do moving forward and then we will make a long-term decision.
UPDATE 29 August 2022: An updated Artemis Neo 22_8 is released to address the Grub issue for the offline installation. When performing the online installation, the latest packages are already fetched, therefore it never caused the Grub issue in the first place.
For updates on this topic follow https://forum.endeavouros.com/t/full-transparency-on-the-grub-issue/30784