Bug#919791: [grub-efi-amd64-bin] After upgrading grub-efi-amd64-signed GRUB was no longer bootable and I was thrown to UEFI settings
Steve McIntyre
steve at einval.com
Wed Jan 23 12:46:33 GMT 2019
[ Please make sure you CC the Debian BTS on replies too, so other
people can see responses too ]
On Tue, Jan 22, 2019 at 11:53:15AM +0000, Mikaela Suomalainen wrote:
>Hi,
>
>On Tue, 22 Jan 2019 at 00:30, Steve McIntyre <steve at einval.com> wrote:
>> Has the Windows update somehow re-enabled Secure Boot? Could you check
>> in yor firmware/BIOS settings please?
>
>I didn't have secure boot enabled. Some time after reporting this bug,
>I tried secure boot out of curiosity following
>https://wiki.debian.org/SecureBoot/Testing but I ended up disabling it
>as I value the ability to hibernate to disk more than secure boot. It
>was disabled until I enrolled the key and enabled it manually.
Bah, OK. So much for my theory. :-(
>Thinking afterwards I should probably have kept the broken grub or
>cloned the EFI partition for this issue.
ACK. It's often quite difficult to reproduce bugs like this
otherwise...
--
Steve McIntyre, Cambridge, UK. steve at einval.com
We don't need no education.
We don't need no thought control.
More information about the Pkg-grub-devel
mailing list