On Thu, May 06, 2021 at 09:24:34AM +0900, Norbert Preining wrote: >Hi Steve, > >> Hmmm. Do you have an EFI system here? > >Yes. >$ efibootmgr >BootCurrent: 0001 >Timeout: 1 seconds >BootOrder: 0001,0002,0000,0009,0004,000A,000B >Boot0000* Windows Boot Manager >Boot0001* grub >Boot0002* rEFInd Boot Manager >Boot0004 Hard Drive >Boot0009* debian >Boot000A Hard Drive >Boot000B USB Floppy >$
Thanks for the debug information, it's really helpful! I *think* I might see what's going on here. Did you switch your system to using EFI by hand at some point? On a system installed via d-i etc., I would expect to see grub-efi-amd64 installed. And that's the package that would normally hold the grub debconf settings that shim is looking for... >> What does "dpkg -l '*grub*'" > >un grub <none> <none> (no description available) >un grub-cloud-amd64 <none> <none> (no description available) >ii grub-common 2.04-18 amd64 GRand Unified Bootloader >(common files) >un grub-coreboot <none> <none> (no description available) >ii grub-customizer 5.1.0-3 amd64 GUI to configure GRUB2 and >BURG >un grub-doc <none> <none> (no description available) >un grub-efi <none> <none> (no description available) >un grub-efi-amd64 <none> <none> (no description available) >ri grub-efi-amd64-bin 2.04-18 amd64 GRand Unified Bootloader, >version 2 (EFI-AMD64 modules) >ii grub-efi-amd64-signed 1+2.04+18 amd64 GRand Unified Bootloader, >version 2 (amd64 UEFI signed by Debian) >un grub-efi-arm <none> <none> (no description available) >un grub-efi-arm64 <none> <none> (no description available) >un grub-efi-ia32 <none> <none> (no description available) >un grub-efi-ia64 <none> <none> (no description available) >un grub-emu <none> <none> (no description available) >un grub-ieee1275 <none> <none> (no description available) >un grub-legacy <none> <none> (no description available) >un grub-legacy-doc <none> <none> (no description available) >un grub-linuxbios <none> <none> (no description available) >un grub-pc <none> <none> (no description available) >un grub-uboot <none> <none> (no description available) >un grub-xen <none> <none> (no description available) >un grub-yeeloong <none> <none> (no description available) >un grub2 <none> <none> (no description available) >ii grub2-common 2.04-18 amd64 GRand Unified Bootloader >(common files for version 2) In the longer term, I think we'll need to add a trigger for something like "grub-efi-install" to make things quicker, but I'm trying to minimise the impact of the shim changes I'm making this close to release. So for now I'm going to add extra fallback code to deal with db_get failing, and that should fix this bug. -- Steve McIntyre, Cambridge, UK. st...@einval.com Is there anybody out there?
