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
  • vepro@lemmy.worldOP
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Had the problem only on one machine. Do you have, by chance, a MSI motherboard? Can’t myself think of other causes and having the kernel and initrd on btrfs instead of ext4 can’t be the problem?

    • Dnn@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      No MSI board and fs is ext4 so that cannot be it either. I downgraded for now but also decided to switch to systemd-boot since this is not the first time GRUB causes trouble for me…

      • vepro@lemmy.worldOP
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Do you have GRUB installed into the ESPs fallback path? (esp/EFI/BOOT/BOOTX64.EFI) I haven’t tried grub-install --removable yet, but maybe stuff got confused.

        • Dnn@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          No, I only had grub in its default path. I’ve folded now though. Moved to systemd-boot. Works fine and config seems cleaner. Cannot recommend with just a few days of experience of course.