On Tue, Jun 22, 2021 at 09:20:36PM +0200, Grzegorz Szymaszek wrote: >On Tue, Jun 22, 2021 at 01:35:51PM +0200, Grzegorz Szymaszek wrote: >> I have recently upgraded several buster amd64 machines; shim-signed went >> up from 1.33 to 1.36~1+deb10u1. […] > >FWIW, upgrading to 1.36~1+deb10u2 brings the problem back. > >Looks like the same as #990158.
Yes, it's the same problem. I'm testing a fix now. Could you please verify if this new build fixes the problem you're seeing on your hardware? https://people.debian.org/~93sam/shim/ has a new *unsigned* amd64 shim binary, and a checksum file. If you would be so kind, please copy that shimx64.efi binary into place on your system and test it boots OK. It may still complain about resource failures and "import_mok_state() failed", but should then boot anyway in non-secure mode. -- Steve McIntyre, Cambridge, UK. st...@einval.com "Further comment on how I feel about IBM will appear once I've worked out whether they're being malicious or incompetent. Capital letters are forecast." Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html
