No currently on that machine it is ALL eos desktops. So that is another thing that makes it more work as with rEFInd i only have to install it on one and then it’s good to go. Hmm? I have had it booting 10 different desktops or other distro’s.
@dalto
I just installed systemd boot in a vm following your tutorial. I did use the script. Not sure if i understand how to do it manually though? I’m not very knowledgeable with bash. I do my best trying to figure stuff out. Works no problem. I may convert my triple boot and try it. You say i have to do this to each installation? Correct? What happens if you install other kernels? Such as zen or lts? Does it take care of it now?
I called it manually vs installing my package but it is worth noting that it isn’t just automation, it is a completely different approach. You are much better off using the kernel-install in eos-systemd-boot approach if you are using it with 3 different EOS installs. It will keep the kernels from conflicting.
Glad to hear it.
Yes, you should do it to all the installations.
Yes, it is automatic.
Keep in mind, for thee installs, if you have a bunch of different kernels per install, you need to ensure your efi parition is large enough to hold all the kernels/initramfs.
I’ll have to check but they are either 300 if i did the automatic install or they will be 550 if i did manual partitioning. I can’t remember as i am always changing things and reinstalling. I’m hoping to stop doing as much desktop hopping and bare metal installs testing. So i think i may dedicate one drive to do that.
Edit:
I can tell you this. I do like it better than booting from the vmlinuz-linux image as you don’t really get anything on the screen and the login just pops up.
Do all the systems share the same ESP or you have a separate one for each?
And if I am to convert an already installed system with only 128MB ESP, looks like that I need to make an XBOOTLDR ax explained in:
https://wiki.archlinux.org/title/Systemd-boot#Installation_using_XBOOTLDR?
Should this get mounted at /boot ?
I have a single esp. I just resized my existing esp to around 900MB.
I just resized mine and the partition next to it so I haven’t played with that. I think it would work fine mount /boot but only if you use the method I describe in my tutorial as “manual”. I think my scripts assume everything is in the ESP. I would have to do some testing with that.
1 Like
Thanks @dalto for the reply! I appreciate it. I’ll be heading to your tutorial and see if I can wrap my head around systemd-boot. I have been wanting to do this for sometime but it always gets postponed.
I don’t how simple something is if its functionality is limited.
When systemd-boot offers the same functionality as grub I’ll look at it again, until then I’ll stick with grub.
Can’t recall the last time grub broke for me.
1 Like
Sorry to jump back into this old thread, but I’m just looking to learn more about systemd-boot. What if I have the LTS kernel installed as a fallback in addition to the main kernel, but I always want to boot from the main kernel. Is there a setting in systemd-boot to make this permanent?
Yes, you can use a wildcard in loader.conf for the default entry.
1 Like
@dalto, I took my old laptop tonight and installed EOS with systemd-boot and btrfs. You write: “Yes, you can use a wildcard in loader.conf for the default entry.” Yes, but how do I know the identifier of the mainkernel? How do I create the default entry? Here is my loader.conf right after installation (currently booting with the LTS kernel):
default 077432ef18794352a9eaa29a56fcc253*
timeout 5
console-mode auto
reboot-for-bitlocker 1
You can look at the files in /efi/loader/entries to see the correct format. In your case, I think this will work:
default 077432ef18794352a9eaa29a56fcc253*arch?-?.conf
The mainline is the hardest one to wildcard because the format it has. The others use much simpler wildcards.
1 Like
OK, I had just found these entries, but probably copied them incorrectly.
Just corrected it and it works. Well, if I ever have to install this on another computer soon.
In addition to this, I found an unexpected pro. When I switched to systemd-boot from grub my wifi adapter stopped randomly being disabled (usually, but not always, on waking from suspend) despite being enabled in the bios. The full saga can be found here: Wifi card disabled on waking from suspend
I have no idea why Grub was the culprit/system-d boot was the cure but, hey, it works.
A post was merged into an existing topic: [Tutorial] Convert to systemd-boot
welcome here and i am sure we can resolve your issue… does not matter if you are running ArchBang or what ever archbased 
But old old thread may similar but make the honor and open your own new thread please you can link to this one if needed.
–closing–
(old aged)