Help with a boot error

Hi all!

Bit of a beginner with Fedora but hoping I can get some help here.

So I went to apply some updates a few days ago, and I think I mistakenly tried to apply both firmware and kernel updates at the same restart to my machine. What has ended up happening is that I end up in a weird grub error boot loop where it will ask me which kernel to boot, and then tell me “protocol not found” and “you need to load the kernel first” before kicking me back to the choice of kernel.

If I boot directly into the uefi though and then click “continue boot” everything works fine.

I tried changing the sudo efibootmgr order but that doesn’t make a difference.

when I mount and run

`

sudo ls -R /boot/efi/EFI/`

`I get`

`/boot/efi/EFI/:`

`BOOT fedora HP Microsoft`

`/boot/efi/EFI/BOOT:`

`BOOTIA32.EFI BOOTX64.EFI fbia32.efi fbx64.efi`

`/boot/efi/EFI/fedora:`

`BOOTIA32.CSV BOOTX64.CSV fw fwupdx64.efi gcdia32.efi gcdx64.efi grub.cfg grubia32.efi grubx64.efi mmia32.efi mmx64.efi shim.efi shimia32.efi shimx64.efi`

`/boot/efi/EFI/fedora/fw:`

`/boot/efi/EFI/HP: DEVFW FWUPDLOG`

Bit out of my depth at the moment but would love to hear any advice on how to proceed

Do you have an Acer?

This StackExchange question deals with a similar error. The top answer suggests you may need to go into the BIOS and mark Fedora’s EFI file as “trusted for executing”.

Hmm interesting! I have an hp and this install has been working fine until recently, so I don’t think that’s it – but I did try to boot windows from an external drive the other day, so maybe that’s the problem?

Windows has definitely been known to cause boot issues, but I’m not sure about that here since all the Fedora stuff on your EFI partition seems to be intact. The boot process at least gets as far as loading and running the grub EFI, since the errors you see come from grub.

And it sounds like you can successfully boot into Fedora - when you go to the BIOS and choose “continue boot”

What does efibootmgr output when run in a terminal in Fedora?

Also, can you boot “normally” if you disable Secure Boot in BIOS?

I wonder if the firmware upgrade has meant that you need to reset the Secure Boot shim, as mentioned here.

Hey I appreciate the response! I did try resetting the secure boot shim but no dice unfortunately.

What did work was creating a fresh boot entry pointing to shim. I can’t say exactly why it happened - gonna have to look over the documentation to better understand.

1 Like

Great you got it working again!

I can’t think of an obvious explanation for that either. Interested in anything you find out!