Open mohammedthejihadist opened 1 month ago
Hi there. First of all I need to admit that my knowledge of EFI is not one of my strong points.
Any improvements on this issue would definitely have to happen in the Calamares project, and so far I believe they don't support what you're asking about. Would this request be the same sort of issue? https://github.com/calamares/calamares/issues/2110
I'm also not sure what the difference is between the force_efi_extra_removable
option and the --removable
flag:
https://superuser.com/questions/1756758/what-does-grub-installs-removable-flag-do
EndeavourOS, Manjaro, Kubuntu 24, and some other distributions which use Calamares already boot correctly on these old systems. I am not sure what they do to make it work.
I don't think issue calamares#2110 is describing the exact same issue because when installing Debian, I must use expert mode and say yes to "Force extra installation to the EFI removable media path". If I do not set this option, the boot menu simply won't have an entry for the installation. No errors as calamares#2110 describes.
The --removable flag appears to do the same thing according to the Arch wiki. https://wiki.archlinux.org/title/GRUB
All OS installers installing things to this removable media path will conflict with any other such installers, which is bad and wrong. That's why in Debian we don't do this by default.
Ubuntu, Fedora, Opensuse, and Arch all do this by default, but for some reason vanilla Debian does not. Some people need this feature for their computer to boot. Could you please add this by default?
https://wiki.debian.org/UEFI#Force_grub-efi_installation_to_the_removable_media_path