On Thu, Jul 30, 2020 at 04:26:55PM +0100, Janek Stolarek wrote: >> Are you using Secure Boot on this machine? >Yes: > >[root@skynet : ~] dmesg | grep secu >[ 0.000000] secureboot: Secure boot enabled
OK. >> Can you please confirm if going back to the previous >> versions of the Grub packages fixes the problem for you? >I can confirm that performing the following downgrade fixes the problem: > >[DOWNGRADE] grub-common:amd64 2.02+dfsg1-20+deb10u1 -> 2.02+dfsg1-20 >[DOWNGRADE] grub-efi-amd64:amd64 2.02+dfsg1-20+deb10u1 -> 2.02+dfsg1-20 >[DOWNGRADE] grub-efi-amd64-bin:amd64 2.02+dfsg1-20+deb10u1 -> 2.02+dfsg1-20 >[DOWNGRADE] grub-efi-amd64-signed:amd64 1+2.02+dfsg1+20+deb10u1 -> >1+2.02+dfsg1+20 >[DOWNGRADE] grub2-common:amd64 2.02+dfsg1-20+deb10u1 -> 2.02+dfsg1-20 OK, thanks very much for the quick response! We *think* we have identified the problem. Would you be able to test some locally-built (non-SB) grub binaries for me please? >Also, I have seen posts on reddit complaining about the same problem >so it's not just me. Nod. :-/ -- Steve McIntyre, Cambridge, UK. st...@einval.com "... the premise [is] that privacy is about hiding a wrong. It's not. Privacy is an inherent human right, and a requirement for maintaining the human condition with dignity and respect." -- Bruce Schneier
