I do not what I did, but certainly I was doing something wrong, since I have to manually sudo reinstall-kernels and sudo bootctl set-default 12345.conf every time there is a new kernel update…
Anyone got any hints?
what may led up to this
I remember doing something with dracut and mkinitcpio… deinstalling first dracut because it had some conflicts with mkinitcpio and then reinstalling dracut… and then running something like dracut --force
Talking from a bit of experience of having messed up systems, it is a good idea to keep track of changes you make to your system by taking notes to know what has been done and what not in order to being able to troubleshoot things easier and hopefully resolve the issue.
With that out of the way, check if you have the package kernel-install-for-dracut installed.
If not, install it and run: sudo reinstall-kernels afterwards.
thanks to you both, kernel-install-for-dracut 1.7-5 is installed. somehow both the aur version and the endeavouros version are installed… See below… [@-Desktop ~]$ yay kernel-install-for-dracut 2 endeavouros/kernel-install-for-dracut 1.7-5 (15.4 KiB 19.3 KiB) (Installed) Enables systemd-boot automation using kernel-install with dracut 1 aur/kernel-install-for-dracut 1.7-1 (+4 0.97) (Installed: 1.7-5) Enables systemd-boot automation using kernel-install with dracut ==> Packages to install (eg: 1 2 3, 1-3 or ^4)
If I run sudo reinstall-kernels, does it really fix the issue? I run it almost every week, and it did not change anything yet…
Thank you also for the note taking tip, I will take that into consideration! Which software are you both using for notetaking btw? Or do you use just any text editor? I am looking for some self-hosted cloud service…
dracut: dracut module 'dash' will not be installed, because command 'dash' could not be found!
dracut: dracut module 'mksh' will not be installed, because command 'mksh' could not be found!
dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found!
dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found!
dracut: dracut module 'connman' will not be installed, because command 'connmand' could not be found!
dracut: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found!
dracut: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found!
dracut: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!
dracut: dracut module 'dmraid' will not be installed, because command 'kpartx' could not be found!
dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
dracut: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'dcbtool' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'fipvlan' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'lldpad' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'fcoemon' could not be found!
dracut: dracut module 'fcoe' will not be installed, because command 'fcoeadm' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found!
dracut: dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found!
dracut: dracut module 'nbd' will not be installed, because command 'nbd-client' could not be found!
dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found!
dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found!
dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found!
dracut: memstrack is not available
dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng
dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found!
dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found!
# /boot/efi/loader/loader.conf
timeout 0
default 12345123123123123123-*
editor no
the newest kernel should then always be selected, right? I do not understand the editor option. In the wiki it says: “The editor will be disabled, so it is not possible to alter the kernel command line.” Does it make sense to turn in on?
If the newest kernel is what is specified in this conf then yes.
That is a security measure. If enabled, a malicious agent with physical access to your machine may be able to manipulate the kernel command line to get root access to your system.
There might be cases when you want to change the the kernel command line yourself.
You would need to decide if you want it enabled or not.
I am updating a kernel now and am checking if it ist getting automatically installed and selected in bootctl…