OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel high common DISPUTE

systemd-boot still lists the old kernel after an update

archendeavouroscachyossystemd-bootuefidesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

sudo pacman -S kernel-install fails. I searched the Arch package database for name=kernel-install and got zero matches. On Arch the kernel-install binary is shipped inside the systemd package. The EndeavourOS package the record is really thinking of is kernel-install-for-dracut. Pasting the given command into a root shell on a machine that is already one bad boot away from unusable just errors out. Separately, pacman -R mkinitcpio-archiso eos-dracut aborts the entire transaction if either package is absent, so the 'if present' caveat needs to be in the command, not the prose. The bootctl update / systemd-boot-update.service half is correct.

The cause above was rewritten on 2026-08-30 to match this note; the fix was corrected by the audit itself.
RISK

bootctl install (as opposed to update) rewrites \EFI\BOOT\BOOTX64.EFI on the ESP. On a dual-boot machine that can displace another loader, so prefer bootctl update when systemd-boot is already installed.

Symptom

You update, reboot, and land in an emergency shell. bootctl list shows only the *previous* kernel version even though the new initramfs was generated correctly:


type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux
version: 6.1.1-arch1-1        <-- stale

Cause

On distros that use kernel-install to write versioned entries into /efi/loader/entries/, removing or shadowing the package that provides the kernel-install plugin (kernel-install-for-dracut, which eos-dracut and mkinitcpio-archiso conflict with) stops entries being regenerated on kernel upgrade. Note there is no standalone kernel-install package on Arch: the binary ships inside systemd. Separately, the systemd-boot EFI binary itself is not auto-updated when the systemd package updates unless the update service is enabled.

Fix

Boot the old entry (it still works) or chroot from a live USB, then:


# remove conflicting packages, only the ones actually installed
for p in mkinitcpio-archiso eos-dracut; do pacman -Qq "$p" &>/dev/null && sudo pacman -R "$p"; done

There is **no kernel-install package in the Arch repos**: the binary comes from systemd. Check what you have:


command -v kernel-install && pacman -Qo "$(command -v kernel-install)"
  • On Arch: reinstall systemd if the binary is missing (sudo pacman -S systemd).
  • On EndeavourOS with dracut: the entry generator is kernel-install-for-dracut (sudo pacman -S kernel-install-for-dracut).

Force regeneration and confirm:


sudo pacman -S linux
bootctl list        # must now show the NEW version before you reboot

Keep the systemd-boot binary on the ESP in sync with the systemd package:


sudo bootctl update
sudo systemctl enable systemd-boot-update.service

If you write entries by hand (plain Arch + mkinitcpio), use **unversioned** paths so they never go stale, in /boot/loader/entries/arch.conf:


title   Arch Linux
linux   /vmlinuz-linux
initrd  /initramfs-linux.img
options root=UUID=xxxx-xxxx rw

and keep a fallback entry pointing at /initramfs-linux-fallback.img.

Verify

bootctl list shows the current kernel version, bootctl status reports the ESP loader version matching pacman -Q systemd, and a reboot lands in the new kernel (uname -r).

Sources

systemd-boot-entries-not-updated-after-kernel