When installing the GRUB version above, I got symbol grub_is_shim_lock_enabled not found and can’t boot, so I downgraded back to grub-2:2.06.r566.g857af0e17-1-x86_64. I tried --disable-shim-lock but it didn’t help. I don’t secure boot and don’t use TPM.

Package was pushed just 5 hours ago, anyone by chance ran into the same problem?

EDIT: Tried again today, worked. Problem was likely caused because I installed GRUB into the “arch” NVRAM entry (esp/EFI/arch) instead of the Fallback which my board only supports (esp/EFI/BOOT). To do this add --removable to grub-install. The full procedure is:

# grub-install --removable /dev/sdX ## or /dev/nvme0nX
# grub-mkconfig -o /boot/grub/grub.cfg
  • Zenzio@lemmy.world
    3·
    1 year ago

    I just upgraded and didn’t have any issues. I’m not experienced in this regard at all. But just to be sure, did you execute the following after the upgrade?

    sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi

sudo grub-mkconfig -o /boot/grub/grub.cfg

    Assuming of course your grub setup doesn’t differ from mine. These two commands are all I know about grub troubleshooting…

    • vepro@lemmy.worldOP
      1·
      1 year ago

      Did grub-install /dev/sdX, x86_64-efi and ESP get detected automatically and no errors were reported. Also created grub config. Will try in a few days again. Maybe I really overlooked something or had “bad luck”. Worked fine in a VM.

      Could the BIOS firmware have a part in this or is the BIOS firmware irrelevant to the bootloaders functionality?