-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Secure Boot Violation after updating BIOS to the latest version #519
Comments
You likely need to update the bootloader manually. See #355 |
Tkanks, @travier ! Is there somewhere a conclusive list of steps on how to do it? |
Unfortunately there isn't. You can try #120 (comment) (with an updated package), but it's at your own risk. Make sure to mount/remount Hopefully we get #120 in soon and you will be able to use that to update the bootloader. |
Thanks, @travier !
Do you mean latest shim from Fedora repository?
As in "unmount both partitions and mount them rw"? Does Maybe I could just extract the necessary files from shim rpm and copy them to the partition, is that possible? |
Ok, I have updated shim and updated grub2.
@travier I didn't have to do that, because they are
To answer myself: it doesn't. I did
Copying shim files from |
Describe the bug
Secure Boot Violation after updating BIOS to the latest version.
To Reproduce
Please describe the steps needed to reproduce the bug:
Expected behavior
Fedora signature should be valid.
Screenshots
Secure Boot Violation
OS version:
Additional context
The firmware is ROG CROSSHAIR VIII HERO(WI-FI) BIOS 4702 (with AGESA ComboV2PI 1.2.0.B). AFAIK, the new BIOS resets fTPM state on update. I was stuck on dbx 77 but now fwupdmgr says it's up to date.
The system booted fine before updating and resetting BIOS. Now secure boot has to be disabled in order to boot the system and Gnome reports that the Kernel Lockdown is disabled in addition to UEFI Secure Boot.
The text was updated successfully, but these errors were encountered: