[Tutorial] Convert to systemd-boot

General system
220

arch1 seems to be part of the name. I scrolled the last 100 or so kernel versions to check.

It is often arch1-2 though.

2 Likes
221

So, the kernel updated today and I got to watch the pacman hook do itā€™s thing and all seems to be correct. Was waiting for that to happen just to make sure I hadnā€™t buggered anything up.

2 Likes
222

I did the conversion once long time ago but i find it hard to understand. I donā€™t know how it works to multi boot? I would like to see these guides in the wiki without multiple posts about so many different things. I find it just way too confusing. :dizzy_face:

1 Like
223

I have a question about this part.
I noticed that my auto generated /efi/loader/entries/ file contains:

GNU nano 6.4                                    /efi/loader/entries/fd7db8933ea94c5a9ca6443d8d133a53-5.19.5-arch1-1.conf                                              
title      EndeavourOS
version    5.19.5-arch1-1
machine-id fd7db8933ea94c5a9ca6443d8d133a53
options    root=UUID=82ddd00a-9b5a-4043-953c-ae91a7d8f83e rw loglevel=3 nowatchdog nomodeset
linux      /fd7db8933ea94c5a9ca6443d8d133a53/5.19.5-arch1-1/linux
initrd     /fd7db8933ea94c5a9ca6443d8d133a53/5.19.5-arch1-1/amd-ucode.img
initrd     /fd7db8933ea94c5a9ca6443d8d133a53/5.19.5-arch1-1/initrd

so loglevel=3 nowatchdog nomodeset in options.
This is what I had also previously set in my /etc/default/grub config file.

Today I got a kernel update via yay and the file in /efi/loader/entries/ got newly generated (I used the kernel-install method when installing systemd-boot) but the loader file still contains loglevel=3 nowatchdog nomodesetā€¦?

So you can edit them, and that will work but the next time you install/update a kernel they will be reset.

Because of this I was under the assumption that the loglevel=3 nowatchdog nomodeset part would not survive the kernel update / auto generation of a new loader file.

What is happening here? Or am I misunderstanding something?

224

No, if you edit them, those edits wonā€™t survive. The options wonā€™t be deleted arbitrarily.

225

Okay, then how could I remove this options again (permanently)? Grub is uninstalled and the /etc/default/grub file where I had previously set those options is also goneā€¦

Iā€™d like to get rid of nowatchdog nomodeset and only keep loglevel=3

226

Edit /etc/kernel/cmdline. Whatever is in that file is what ends up on the options line.

1 Like
227

Thanks!
So Grub just previouslty filled /etc/kernel/cmdline for me when I edited something in /etc/default/grub
e.g.: GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 nowatchdog nomodeset"?

228

No exactly.

  • /etc/default/grub is what grub-mkconfig uses.
  • /etc/kernel/cmdline is what kernel-install uses.
2 Likes
229

Then itā€™s mistery for me as to why loglevel=3 nowatchdog nomodeset is in /etc/kernel/cmdline since I never edited this file beforeā€¦ only /etc/default/grub.

Thank you for your help!

230

Oh, I can explain that. If that file doesnā€™t exist, I look at the running command line and populate it for you.

The reason I do that is so that if you ever need to rescue your system from a chroot, it will get the correct parameters.

1 Like
231

Iā€™m beginning to suspect that the reason it was working more consistently for GRUB is because it took longer to boot up and gave enough time for DP to turn on the monitor. My current situation is, sometimes it works, sometimes not. Some MSI related forums Iā€™ve found have suggested a better quality DP cable.

232

To make default to boot? Isnt that select a entrance and type d ?

233

Yes, however every single time the kernel gets updated, itā€™ll reset, so youā€™ll have to select and type d all over again. Since Arch kernels get updated frequently, Iā€™d rather not have to select d multiple times a week. The way I have it setup now is just a set it and forget approach which I much prefer.

1 Like
234

true :slight_smile: have to figure daltoā€™s kernel-install :slight_smile: never did that i always editted the files :slight_smile:

1 Like
235

Well if you have any questions most likely @dalto can answer them, but since I do have a little experience now as well I may be able to help as well. Thereā€™s lots of useful information in this thread if youā€™ve got a little time to read too :wink:

1 Like
236

Yesterday, my laptop almost slipped out of my hand whilst I was trying it to put it in my backpack and with that I made an uncontrolled movement on my touch pad, probably messing things up.
Systemd doesnt use the 3 second timer anymore, instead I have to press enter in the menu to confirm the kernel boot. I did disable and enable the timer and even changed the time from 3 to 4 seconds in the /efi/loader/loader.conf to make it work again but no avail.
How do I make it work again?

237

Try pressing t at the boot menu and adjusting the timeout that way.

2 Likes
238

That did the trick, thanks!

2 Likes
239

Thatā€™s a relief, I was thinking you might need to switch to grub!! :rofl:

1 Like