Hi Pascal, Thank you for the quick response.
> On Wed, 22 Jan 2025 23:07:54 +0000 Pascal Hambourg wrote: > On 23/01/2025 at 00:07, M. Dietrich wrote: > > And not in /boot/efi/EFI/BOOT ? > no, a `find /boot/efi` would have shown (i added the ubuntu here manually, but that's how it was if i remember correctly): /boot/efi/EFI/Boot /boot/efi/EFI/Boot/bootx64.efi /boot/efi/EFI/Boot/fbx64.efi /boot/efi/EFI/Boot/mmx64.efi /boot/efi/EFI/Microsoft/Boot/... /boot/efi/EFI/ubuntu /boot/efi/EFI/ubuntu/shimx64.efi /boot/efi/EFI/ubuntu/grubx64.efi /boot/efi/EFI/ubuntu/mmx64.efi /boot/efi/EFI/ubuntu/fbx64.efi /boot/efi/EFI/ubuntu/BOOTX64.CSV /boot/efi/EFI/ubuntu/grub.cfg /boot/efi/EFI/debian /boot/efi/EFI/debian/shimx64.efi /boot/efi/EFI/debian/grubx64.efi /boot/efi/EFI/debian/mmx64.efi /boot/efi/EFI/debian/fbx64.efi /boot/efi/EFI/debian/BOOTX64.CSV /boot/efi/EFI/debian/grub.cfg /boot/efi/System Volume Information > > efibootmgr showed values that seemed to be fine (while there was an > > ubuntu entry) and BootOrder pointed to the debian Boot entry. > What does this mean exactly ? when i issue a `efibootmgr` it shows the list of efi variables (here i again added the ubuntu entry manually as i remember it): BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0002,0003,0004,0005,0006 Boot0000 Windows Boot Manager HD(1,GPT,... Boot0001* debian HD(1,GPT,... Boot0002* ubuntu HD(1,GPT,... Boot0003* Windows Boot Manager HD(1,GPT,... Boot0004* UEFI:CD/DVD Drive BBS(129,,0x0) Boot0005* UEFI:Removable Device BBS(130,,0x0) Boot0006* UEFI:Network Device BBS(131,,0x0) as far as i understand the system uses BootOrder to determin what to boot. it starts with 0001 which is debian, not ubuntu. so i wonder why the leftover ubuntu grub was booted as you say (which i believe, i am not an efi expert). > > or the debian installer should notice that or > Notice what ? that the system wont be able to boot into debian. maybe it could change BootOrder to point to the debian entry only?
