Arch Linux

avlec

Member

Registered: 2021-01-17

Posts: 4

[SOLVED] Kernel Version Mismatch after System Upgrade

After doing a system upgrade this morning the running versus installed kernel version seems to be out of sync? This is causing audio drivers to not load but the system seems otherwise usable.

The dmesg indicates it's running 6.9.6 while pacman says it has 6.10.3 installed.

[    0.000000] Linux version 6.9.6-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 14.1.1 20240522, GNU ld (GNU Binutils) 2.42.0) #1 ZEN SMP PREEMPT_DYNAMIC Fri, 21 Jun 2024 19:48:59 +0000
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=2b98cec1-638b-477f-bd99-aa706eada9e4 rw loglevel=3 quiet

Querying the installed version (which was apparently published earlier today)

[avlec@solaria ~]$ pacman -Q linux-zen
linux-zen 6.10.3.zen1-1

This causes modules to not get found presumably because there's no module directory for 6.10.3.

[avlec@solaria ~]$ ls /lib/modules
6.10.3-zen1-1-zen

I tried reinstalling explicitly with pacman -S linux-zen and rebooted and still stuck in purgatory. Wondering if there's something else I can try to get out of this state? Could this be caused by low disk space when I upgraded, if so should that be fixed?

Last edited by avlec (2024-08-06 03:02:01)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,182

Re: [SOLVED] Kernel Version Mismatch after System Upgrade

You're booting from a boot partition so the standard-mistake is that you didn't mount that before updating the kernel - and now you likely can't mount it because you're lacking the vfat module.

lsblk -f

Boot the install iso, mount the system root into /mnt, the boot partition into /mnt/boot, arch-chroot mnt and re-install the kernel

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

avlec

Member

Registered: 2021-01-17

Posts: 4

Re: [SOLVED] Kernel Version Mismatch after System Upgrade

Yeah did a quick check and Kernel didn't have the vfat (let alone other modules). Got it sorted out by using the install ISO as you mentioned.

I think I accidentally ran umount -a, forgetting that wouldn't just un-mount my NFS mounts, a few days ago and that caused this.

Thanks for the help seth!