this post was submitted on 05 Jul 2023
7 points (100.0% liked)

Arch Linux

7733 readers
2 users here now

The beloved lightweight distro

founded 4 years ago
MODERATORS
 

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
top 8 comments
sorted by: hot top controversial new old
[–] Zenzio@lemmy.world 3 points 1 year ago* (last edited 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...

[–] wallmenis@lemmy.one 1 points 1 year ago

Just installed the package... Rebooted... No issue... Did not install via grub-install yet though... Will be formating my system soon anyway so I will let you know if i get the same issue.

[–] Dnn@lemmy.world 1 points 1 year ago (1 children)

I have the very same problem. Grub-installed and mkconfig as usual and never had secure boot enabled.

Just booted from USB, chrooted in, rebuilt the images (mkinitcpio -P), then repeated the grub commands, no luck.

Time to downgrade grub, I guess...

ps. First time I found a Fediverse thread for a tech problem, so yay, the crawlers do see it.

[–] vepro@lemmy.world 0 points 1 year ago (1 children)

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 0 points 1 year ago (1 children)

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.world 0 points 1 year ago (1 children)

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 1 points 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.

[–] StefanT@lemmy.world 1 points 1 year ago

I find systemd-boot so much easier to use and it's configuration is much smaller. So maybe consider to switch (if you are on UEFI).

load more comments
view more: next ›