With this post I’d like to vouch for better systemd-boot integration. When its installed at
/boot (I assume) everything works fine. However, when it’s installed at
/boot/efi there are a lot of hurdles to manually overcome.
As I am dual booting with PopOS (transitioning to Manjaro after using it for 3 years), I had an active systemd-boot installation on
/boot/efi. I installed Manjaro with the architect, and although I select install location as
/boot/efi during the installation process, it caused it to wipe all active entries present (PopOS in my case), and did not install a Manjaro entry. To get up and running I had to first copy my boot files from
/boot to a location inside
/boot/efi, as it otherwise couldn’t accessed, in my case
However, the trouble persists even after. I thought I had fixed this by manually amending
/etc/mkinitcpio.d/linux510.conf to use my custom location, however that results in a kernel unsync (see my post for more details).
Thus in the end I still have to manually create new boot entries for every new kernel version, and I have to copy the boot files over manually every time they are regenerated for whatever reason.
Edit: While doing more research on the topic, I came across systemd’s “boot loader specification” link. Sounds like something excellent for this situation, and is something I recognize as Pop has implemented it