Follow-up Comment #3, bug #60211 (project grub): [comment #0 original submission:] > I have detailed the steps on how to reproduce this issue: > https://md.archlinux.org/F1JuYj5xQtWyhvH8_ilErg
Having the same problem when trying to use only my own keys (following the arch-wiki guide without shim as I don't want any other keys than mine). Adding the tpm module to the core-image via --modules="tpm" on grub-install enabled me to get into grub without said error. When selecting my signed kernel to boot I got an error stating "shim_lock protocol not found". After once again running grub-install, this time with both --modules="tpm" and --disable-shim-lock I was able to successfully boot with enabled Secure Boot. Still not really sure why tpm changes something in the first place and how to properly do it without shim. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?60211> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/