I ran grub-install manually and grubx64.efi disappeared from the boot
entry. I am not sure, but the problem seems to be solved for the time being.
On 2025-04-14 17:43, Pascal Hambourg wrote:
(Please reply to the bug mail address, not only mine)
On 14/04/2025 at 09:05, Tanaka wrote:
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0003,0002
Boot0002* debian HD(1,GPT,b2796776-253a-4c36-80e1-
cc3d71cc5259,0x800,0x32000)/File(\EFI\DEBIAN\SHIMX64.EFI)
Boot0003* debian HD(1,GPT,b2796776-253a-4c36-80e1-
cc3d71cc5259,0x800,0x32000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BO
Boot003 does not look like it was created by grub-install or
efibootmgr. In my experience, such EFI boot entries never have "..BO"
appended. However I have seen this "suffix" in EFI boot entries
created by the UEFI firmware. Example:
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033686#10>
I have also seen an Asus laptop UEFI firmware automatically and
wrongly register an EFI boot entry for grubx64.efi.
/boot/efi/EFI/debian:
total 5.9M
-rwxr-xr-x 1 root root 108 Oct 10 2024 BOOTX64.CSV
-rwxr-xr-x 1 root root 86K Oct 10 2024 fbx64.efi
-rwxr-xr-x 1 root root 112 Oct 10 2024 grub.cfg
-rwxr-xr-x 1 root root 4.1M Oct 10 2024 grubx64.efi
-rwxr-xr-x 1 root root 831K Oct 10 2024 mmx64.efi
-rwxr-xr-x 1 root root 938K Oct 10 2024 shimx64.efi
Running apt (full-)upgrade updates EFI boot entries only on grub or
shim package installation or update, but it looks like this last
happened on october 2024. So if something changed BootOrder since
then, it is not apt.
You can run grub-install -v (the last lines show what it does with EFI
boot variables) and efibootmgr -v. It should show only one "debian"
entry pointing to shimx64.efi and first in BootOrder. Then reboot and
run efibootmgr -v again to see if there is any change.
