[Tutorial] Convert to systemd-boot

@dalto

Okay i have installed Xfce to use the efi partition from my Kde install but the only way i could get the installer to let me do that was to use replace partition. Then it automatically picks up the efi partition. This has been a common issue with users installing dual boot with Windows and things not working also because of this. I had to install both with grub first in order to be able to have the installer find the efi on kde using replace partition.

You can’t set a swap file when using replace partition.

So i converted both again to systemd-boot and this is what i have at boot. I did have an issue with grub booting again related to this grub issue even on a new install. Had to fix that and it wasn’t letting me chroot. But i just ran the grub update command and i was able to boot.

I don’t like the numbering system on the folders either. All the info related to this grub problem is confusing. Does one run sudo grub-install or do you have to have all the other info to go along with the command? Depending on how you do this the folder gets named differently. Not sure what all the numbering is on the menu here? What are the numbers in brackets for?

IMG_20220903_204233

It does work but the first entry is Xfce. Second one is Kde.

The identifier in the parens are probably part of your machineid. It is probably because you have entries that are otherwise identical. I don’t see those on any of my installs because I don’t dual-boot the same distro

Well at least i know how i can install it. It might be better to install to the same drive and just create another root partition and use the same swap file? Not sure i can if it’s swap on btrfs?

@dalto
Looks like those numbers are part of the intrid numbering? Or it’s using those numbers for identification?

initrd=\205eef08a62e44d896afadd2ca60113c\5.19.6-arch1-1\initrd

Yeah, that is your machineid

But why two different numbers then? Isn’t the machine id the same or it changes for each install?

Are you able to install other kernels with akm on systemd-boot?

No, it is unique per install.

Of course.

2 Likes

That one I can answer, yes it can as long as there is enough space.

3 Likes

What are you saying. A 256 GB drive is too small? :wink:

The kernels and initrams get installed into the EFI partition.

1 Like

No, when converting to Systemd boot you had to check if the efi partition is large enough.

@dalto already answered :wink:

1 Like

I didn’t see that? I’m only using the default size.

Edit: Okay now i see it. :man_facepalming:

1 Like

It’s this part and someone in this thread had the issue of it being too small because of the number of kernels installed.

What size do we need?

I think that depends on how many kernels you want to install. I have the main kernel and LTS installed and it fits with ease on the standard partition Calamares is dedicating it.

1 Like

Depends how many kernels you want to install. With mkinitcpio, kernels+initrams+ucode will be 50-70MB each for most people.

2 Likes

Is there a conf file to change the boot order in the menu?

You can change the order using a sort-key.

However, it is usually easier just to set a default entry instead of actually re-ordering them.

Not sure how to do that?