You are not logged in.

#1 2020-03-10 15:42:22

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

[Solved]Systemd-boot has 'own will' after update

This is very odd, somehow systemd-boot decided to set arch-lts as default kernel.
Normally arch(default kernel) is set and when a reboot is performed this kernel is started again.
However after the latest update (systemd 245) lts is started as default kernel!?

I can still choose arch(default) which is then used without problems.
What I'm curious about is why?

I did not change loader.conf so 'default arch' is still set.
Did anyone with multiple kernels see this behavior?

Last edited by qinohe (2020-03-10 16:30:12)

Offline

#2 2020-03-10 16:09:41

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,466

Re: [Solved]Systemd-boot has 'own will' after update

Offline

#3 2020-03-10 16:29:52

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: [Solved]Systemd-boot has 'own will' after update

Thanks Scimmia, seems I missed that one;)

Offline

#4 2020-03-10 16:34:02

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,466

Re: [Solved]Systemd-boot has 'own will' after update

I think a whole lot of people missed it, I know I did, but hadn't rebooted yet. I updated the wiki as well.

Offline

#5 2020-03-10 17:03:48

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: [Solved]Systemd-boot has 'own will' after update

Well done Scimmia, wish we could say the same about the systemd documentation 'man loader.conf'.

Offline

#6 2020-03-12 07:13:20

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [Solved]Systemd-boot has 'own will' after update

This is weird.

I updated my conf file to use the .conf suffix for the default value.

I ran `bootctl set-default option2.conf` and then `bootctl list` to confirm that option2 was the default entry (of four).

Rebooted and it autoselected option 4.

Changed the loader default to option2 (removed the .conf) and rebooted and the correct image, option2 was autoselected.

Can someone please confirm that the .conf is in fact not necessary, as per the man page, and when used in conjunction with bootctl set-default actually breaks the intended functionality?

systemd 245-3

Last edited by jasonwryan (2020-03-12 07:14:17)


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#7 2020-03-12 09:48:40

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,494

Re: [Solved]Systemd-boot has 'own will' after update

Well not here at least. (245-3)

Ran bootctl to use another kernel and checked 'bootctl list' it was correct, it was! (out of list of 3 and choose it to use 1)

Rebooted and it did what I asked it to do with .conf suffix, nr. 1 was booted.

Haven't removed the suffix though, I could if you like me to try but I think as it is working as it should, it will actually break things...

edit:
Out of curiosity I tried it and WTF it doesn't even matter!?

So I removed the suffix(loader.conf) I ran 'bootctl update' and changed the kernel to nr 2 with bootctl..

Fine, no problems it boots nr 2.

Now I have tried to do the same without the suffix, so: 'bootctl set-default hardened' (nr 2)

If then ran 'bootctl list', it than shows nr 3 in list, so that's wrong!

So yes indeed as long as you use 'bootctl set-default *.conf' it seems to not matter if the suffix is in loader.conf or not.

edit2:
I should also mention, I have tested with an empty loader.conf.

That is, only containing 'timeout' & 'editor', no problem 'bootctl' still finds the entries!

So 'bootctl' is loading entries in 'loader/entries' directly and a simple loader.conf(without entries) should be sufficient.

Last edited by qinohe (2020-03-12 15:38:52)

Offline

Board footer

Powered by FluxBB