Arch Linux

ReinhardK

Member

Registered: 2024-05-30

Posts: 2

[Solved] Grub runs into error: prohibited by secure boot though ...

I installed Arch Linux according to the Installation guide for booting in UEFI mode including the Grub bootloader. I disabled secure boot in the Bios settings as recommended. The FDD was partitioned to sda1 EFI partion, sda2 swap partition and sd3 root partition. After rebooting I ended up at the grub rescue prompt with error message "error: prohibited by secure boot policy". There is no other OS or hardware that requires secure boot. What went wrong?

Hardware:
MB: MSI B550-A PRO with Bios Version E7C56AMS.AF0
FDD: WDC WS20EZRX-00D8PB0
CPU: AMD Ryzen 5 5600G with Radeon Graphics
No graphic card. The GPU is on the processor chip.

Last edited by ReinhardK (2024-05-30 21:37:08)

cryptearth

Member

Registered: 2024-02-03

Posts: 1,337

Re: [Solved] Grub runs into error: prohibited by secure boot though ...

first: update the bios - current stable is AH
although I don't know what you mean by "FDD" (as there're either HDDs or SSDs (or HHDs)) - as you get to GRUB at all means you did something right so far
as for why secure boot may still active? from the top of my head (as the manual doesn't help as cheat sheet here): make sure to wipe the keys ...

you know what - have me a quick look at it (as I have the same board) ... be right back in 2 minutes

// ...

it is
Settings > Advanced > Windows OS Configuration > Secure Boot
make sure you have option Secure Boot set to Disabled and option Secure Boot Mode set to Standard
if you want to make sure set Secure Boot Mode to Custom - switch to > Key Management and hit Delete all Secure Boot variables

Last edited by cryptearth (2024-05-30 19:29:09)

ReinhardK

Member

Registered: 2024-05-30

Posts: 2

Re: [Solved] Grub runs into error: prohibited by secure boot though ...

Thanks a lot, I must have missed that.

Funny0facer

Member

From: Germany

Registered: 2022-12-03

Posts: 159

Re: [Solved] Grub runs into error: prohibited by secure boot though ...

if this resolved your issue, please remember to edit your first post and add a [SOLVED] prefix to the title.

---

BBCode