The story of my encounter with EndeavourOS
As a long-time linux user I like to learn new things. Reading positive reviews about Arch-based distro’s I decided to give EndeavourOS a try
I had been running Fedora as my daily driver
On my Framework laptop I started the EndeavourOS installer. At the first question: “do you want to install EnOS next to Fedora” my answer was yes.
Installation was very smooth.
The problem started after the first reboot. The laptop would always boot straight into EnOS. The boot process seems unaware of any other OS on my system.
Looking through a lot Q&A it became clear that EnOS uses efi boot which does not look for other instances of an OS
Some answers advice to change one line in /etc/default/grub
Only problem: in EnOS /etc/default is empty
Other answers advice to install grub
Sudo grub-install results in “grub-install: command not found”
Looking further I come across explanations of efi boot and installing grub on efi partition that exceed my knowledge of how linux works
I acknowledge the fantastic amount of energy and time experts are prepared to spend to help people like me
But for now I sadly have to abandon my attempt to get to know EnOS
(adding to your response) which does not probe for or automatically add other OSs to the EFI boot.
So, in essence, the OP has given himself a self-inflicted flesh wound.
Sorry, completely missed the choice of grub at installation. Maybe because I had up to now not come acrosse a distro with this choice.
Thank for your answer. I will probably give EnOS another try
Except when I had EndeavourOS installed with Windows 10, it immediately show Windows 10 with no problems after install. I didn’t do anything to get that.
Yes, if you’re using the same EFI, it will typically add it in, however, the default MS EFI is 100 MB (if I recall) and can’t be used by linux distros of this era without resizing or specifically making it larger during Windows installation, etc.
If I remember correctly, I had Windows 10 installed first, with its own EFI partition and then I let EndeavourOS create its own EFI partition.
EDIT: Either way, I wanted to say this because I personally never had issues with systemd-boot and other OSes. Maybe you know more than I do. I am just saying my own experience.
During the install process, the installer asks you what bootloader you want to use. By default, it is systemd-boot.
You can remove systemd-boot and replace it with grub if you absolutely want to, but…
I imagine that the Framework laptop allows you to select what boot entry you want, so you don’t need both of those OSes to have show up in the bootloader if this goes beyond your level of understanding (which is fine, by the way; no problem).
Not sure what bootloader Fedora uses by default, but it is also likely systemd-boot. It might see EndeavourOS, but I don’t know.
Well I have fedora installed and EOS is recognized by grub of Fedora which uses by default BTRFS , and I think that can’ t be changed. So EOS default grub probably doesn’t find Fedora.
Not without reinstalling the entire OS. I don’t think the partition’s file system really matters here. My theory here is that systemd-boot didn’t automatically search for other entries, for some reason I don’t really know, and it just never made an EFI entry for Fedora.
Well I think the file system does matter because when updating EOS grub it didn’t find Fedora.
Don’t know about systemd though. In BIOS however Fedora creates a Uefi OS entry , so if you set that as first boot device Fedora grub gets started with EOS in it.
My Framework laptop is brand new and did not contain data yet. So I had the luxurury of being able to start all over again.
Made two partitions on my hdd. Installed Fedora41 on one partition. Next installed EnOS on the second partition after choosing grub as bootloader
The computer still only sees EnOS on restart.
Pressing F12 immediately after power on brings up a screen where I can choose between the two OS
Not the most beautyful solution, but it woks!!
Thanks everybody
But if you boot Fedora you will get a grub menu right ? So EOS should be on that Grub menu. On both the grub menu’s there should be an option to go into the BIOS (something with EUFI at the bottom). When in the BIOS there must be a boot options submenu. If you choose the Fedora as first boot option you don’t have to F12 anymore.