I recently set up a dual-boot system, aiming to use Solus as my stable main OS and Cachy for experimenting. The previous time I installed Linux, Grub was the go-to bootloader. However, it looks like systems now default to systemd-boot. I started by installing Cachy with systemd-boot, then installed Solus on a separate partition, but it didn't ask for a bootloader choice and also defaulted to systemd-boot. Now, it seems like Solus is the only OS recognized on boot, while Cachy is completely missing from the options. I really want to avoid digging into manual configurations. I tried using "bootctl install" but ran into EFI boot partition issues, and now I'm stuck. Can anyone suggest how to make systemd-boot detect both installations like how Grub used to do with update-grub?
2 Answers
You can definitely set up both Linux systems using systemd-boot; they just need to share the EFI partition, even if their root partitions are on different drives. I currently manage seven different Linux root setups with a single systemd-boot menu. So it should be possible, but it sounds like something went wrong in your installation process.
I totally get your frustration! When you install a second Linux with systemd-boot, it should ideally automatically detect the first one, but sometimes it doesn’t. If you’re looking for a quick fix, check if both OS installations are using the same EFI partition—this could be what's preventing Cachy from showing up. I know it’s a hassle, but this setup can be tricky.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures