EFI (using the bootmgr from Solus)

dbarron

Ok, while EFI isn't new, and I can usually juggle things, I am seeking guidance from those who must know more than I do here.
Currently, I had KaOS and Solus playing nicely with my EFI, even though every darn distro was installed as EFI. I think they stepped all over each other, because most assume the files are in /boot/efi and are the same names.
In an effort to get ArcoLinux working, I created it an entry in /boot/efi/loader/entries and create a /boot/arco subdirectory for the kernel and initramfs-linux files. It works fine, but..of course I'm going to have to maintain it with each kernel update. Obviously I can script it..but surely there's a better way.
I run about 7 different distros at a given time, and I don't really want to do this for them unless there is a better way.
Linux gurus, help me, I seek your wisdom. What have I missed?

gohlip

At these non-systemd-boot OS installation, manually set /boot to that EFI and do not install grub. All linux distros (that I know) have enabled bootctl and you can either use theirs or your existing default.

I think you have KaOS systemd-boot in effect as Solus does not really make a complete systemd-boot system unless you manually make one.

dbarron

That is possible, Solus was the last installed, but I may be using pre-existing. Hmm, not quite sure what to do with my existing (other than perhaps reinstalling). I always chose EFI where possible during installation, but grub has managed to sneak in there in some. I believe some distros may use EFI to boot grub.
Is there a methodology to 'fix' me?

gohlip

dbarron Is there a methodology?

There are 2 ways to go about it.
We can copy over the kernels and initrd (or initramfs) files to the EFI and make manual entries for them.
Or we can copy over just the efi files (core.efi or grub.efi) to that EFI and just boot the efi files (thereby booting the grub menu).

Naturally when kernels change we need to copy over kernels (when copying kernels) and manually change again the entries.conf. If copying efi files, we don't need to do that when kernels change but when there's a new grub version, we need to copy the new copy of core.efi or grub.efi

Now all this is assuming we have systemd-boot fully implemented (which it is in KaOS), and is not the case in Solus and needs to be done by a simple 'bootctl install' (and after installing efibootmgr package).

dbarron but grub has managed to sneak in there

Yes, the efi-firmware (at bios) will include all efiboot entries and that will include grub entries.
We can check with 'efibootmgr' but that efibootmgr package is not installed in Solus. Just install this package.

Separate off-topic, grub can boot any installed OS regardless of their bootloader (or none) and regardless where their EFI partition is. I also have refind (sharing the same EFI as systemd-boot) but I almost always boot from grub. grub EFI must be /boot/efi and systemd-boot must be /boot. rEFInd EFI can be /boot or /boot/efi but I personally think rEFInd is best in /boot, and slightly unreliable unless there is a refind.conf with entries specified.

Personally again, I think grub is best in all situations and systemd-boot is good for single OS systems.
I have lots of OS's but I can make rEFInd and systemd-boot boot all these OS's.

[EDIT] - I get the impression that Solus developers think the best (only?) way to boot is through the efi-firmware at bios,
like EFISTUB booting. Of course, personal preferences are always valid and non-debatable. And the full right of any developer to choose what they want in their distro.
I added this edit to explain the philosophy of Solus developers (correctly, I hope) and not to impugn any other attribute.