OK, so I noticed that 0002 (shimx64.efi) was not enabled so I did this,
Code: Select all
user@LC2:~$ sudo efibootmgr -v
[sudo] password for user:
BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 0003,0000,0002
Boot0000* Windows Boot Manager HD(1,GPT,d9324c6c-28bb-4996-aa60-904510f83e00,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0002 debian HD(1,GPT,d9324c6c-28bb-4996-aa60-904510f83e00,0x800,0x32000)/File(\EFI\DEBIAN\SHIMX64.EFI)
Boot0003* debian HD(1,GPT,d9324c6c-28bb-4996-aa60-904510f83e00,0x800,0x32000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BO
user@LC2:~$ sudo efibootmgr -o 0002,0000,0003
BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 0002,0000,0003
Boot0000* Windows Boot Manager
Boot0002 debian
Boot0003* debian
user@LC2:~$ sudo efibootmgr -b 0002 -a
BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 0002,0000,0003
Boot0000* Windows Boot Manager
Boot0002* debian
Boot0003* debian
user@LC2:~$
Which made absolutely no difference. Booted once fine, the next time to the grub editing screen.
I have checked the BOOT64.CSV file and all appears in order.
Code: Select all
sudo cat /boot/efi/EFI/debian/BOOTX64.CSV
[sudo] password for user:
shimx64.efi,debian,,This is the boot entry for debian
So to think out loud, it doesn't change anything to boot off SHIMX64.EFI or GRUBX64.EFI. The fallback BOOTX64.CSV specifies SHIMX64.EFI as the boot device so no help there. Would the next fallback location be bootx64.efi in the top level Boot directory?
Code: Select all
sudo tree -l /boot/efi/
/boot/efi/
├── EFI
│ ├── Boot
│ │ └── bootx64.efi
│ ├── debian
│ │ ├── BOOTX64.CSV
│ │ ├── fbx64.efi
│ │ ├── grub.cfg
│ │ ├── grubx64.efi
│ │ ├── mmx64.efi
│ │ └── shimx64.efi