Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#79397 - [linux] Updating from 6.4.8-arch1-1 -> 6.4.10.arch1-1 results in inconsistent boot-fs

Attached to Project: Arch Linux
Opened by Christian Cwienk (dr1fter) - Thursday, 17 August 2023, 06:10 GMT
Last edited by Toolybird (Toolybird) - Thursday, 17 August 2023, 07:02 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I recently updated - among other packages - from linux-6.4.8-arch1-1 -> linux-6.4.10.arch1-1

After reboot, X11 startup failed. According to dmesg, this was due to an inconsistency of nvidia package versions: installed version 535.98 of client differed from installed kernel-module (535.86.05).

I then compared `pacman -Q linux` (6.4.10.arch1-1) and `uname -r` (6.4.8-arch1-1). So it seems that - even though pacman tried to install linux-6.4.10, the kernel used for actually booting was not updated.

I re-installed both nvidia and linux, resulting in recreation of initramfs, but this did not change anything (reboot yielded the same error + command-output). After downgrading nvidia, X11 would at least startup again.


Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:

On my machine (before my workaround):

pacman -Syu && reboot



(application/x-gzip)    Xorg.0.log.old.gz (1.9 KiB)
(application/x-gzip)    dmesg-output-last-boot.gz (25.2 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 17 August 2023, 07:02 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Please use the support channels as indicated.
Comment by Toolybird (Toolybird) - Thursday, 17 August 2023, 07:02 GMT
> the kernel used for actually booting was not updated

This is a clear user misconfiguration problem and not an Arch packaging issue. Please visit the proper Arch support channels (Forum/IRC/Mailing Lists/Reddit/etc) to seek troubleshooting assistance.

Loading...