#not able to boot and getting grub errors after attempting to enable secure boot

1 messages · Page 1 of 1 (latest)

pseudo plume
#

I dual boot Arch and Windows 11 on my machine. I have had secure boot disabled since I installed Arch, but I wanted to play Battlefield Redsec (On Windows obv) and that requires it to be enabled.

I was reading the Wiki on the proper steps to enable secure boot, I may have done something incorrectly, but I typed the command sudo grub-install --target=x86_64-efi --efi-directory=/boot/EFI --bootloader-id=GRUB --modules="tpm" --disable-shim-lock

After doing this I ran sbctl status and it instructed me to change settings in my motherboard firmware specific to my hardware. I rebooted and changed these settings, and then when I try and boot back into arch linux I get this error code.

error: symbol 'grub_is_using_legacy_shim_lock_protocol' not found

I haven't been able to find much info online, the one thing that I found and tried was to chroot into the system and reinstall grub (grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=GRUB). I am still getting the error after trying this.

I guess I was supposed to finish creating and signing my keys before rebooting? I'm not sure where I went wrong. Does anybody have any recommendations?

Here are the wiki links I followed:
https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot#Implementing_Secure_Boot
https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot#Assisted_process_with_sbctl
https://wiki.archlinux.org/title/GRUB#Secure_Boot_support

pseudo plume
#

Since posting I have chrooted into my system and finished creating and signing my keys. However, when I enable secure boot and then reboot I can't get grub to load, I keep getting stuck at error: prohibited by secure boot policy

cyan sapphire
west lotusBOT
pseudo plume
#

After some more investigation, I now have two bootable entries for grub in my BIOS. The one that I was using, would give the error just mentioned when selecting Arch linux or Windows. If I boot into the other entry, I can now boot into Arch or Windows with secure boot disabled.

This boot entry though still does not work if I enable secure boot, and there is additional information in the error message.
error: kern/efi/sb.c:shim_lock_verifier_init:175:prohibited by secure boot policy