First post - and really the first “problem” I encountered with openSUSE, that I can’t find a simple solution to. I’ve been a long time Arch user, and recently (about 2 weeks ago) switched to openSUSE Tumbleweed. So far it’s been a great experience. No major issues, and for (almost) any problem I was able to find a solution from your online community. Except for this one…
I installed my Tumbleweed with systemd boot (selected systemd boot in the installer, I didn’t set it up manually). I prefer sdboot for its simplicity. I have multiversion enabled in zypp.conf “multiversion = provides:multiversion(kernel)” and “multiversion.kernels = latest,latest-1,running”. From my experience with Arch (also sdboot) I was expecting Tumbleweed to automatically boot to the newest kernel after update (zypper dup), and purge the oldest kernel after the boot, but what I see is - it is still booting the old one, it never sets the new loader entry as default.
I can see it creates a new .conf in /boot/efi/loader/entries named opensuse-tumbleweed-[VERSION]-default.conf, but it also leaves the old entry as “default”. This is confirmed by looking at the output of “bootctl list” right after the update - the old entry is still marked as (default). I can of course change it manually to whatever I want with “bootctl set-default …”, but is there a way to automate it during update? I have my boot menu disabled for a “clean/no text” boot and now after every update I have to make sure it’s actually running the newest kernel manually…
