You are not logged in.
Hello,
I've been successfully using the nvidia drivers for years, possibly even decades at this point. Only recently have I had the issue where kernel updates have started to arrive without the corresponding nvidia module update. For example, right now the current version of linux is 7.2.3, but 610.57.04-13 is still in Extra-Testing.
I had always assumed there was some automated process that kept these packages locked together. But over the last few weeks, I've had to withhold updates. This morning I failed to notice and had to downgrade the kernel from a TTY.
Did something change in the build/release process?
Thank you!
Offline
I agree, it's my 1st time (I use an UKI):
Packages (1) linux-7.2.3.arch1-2
Total Download Size: 148.38 MiB
Total Installed Size: 148.75 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
linux-7.2.3.arch1-2-x86_64 148.4 MiB 95.5 MiB/s 00:02 [####################################] 100%
(1/1) checking keys in keyring [####################################] 100%
(1/1) checking package integrity [####################################] 100%
(1/1) loading package files [####################################] 100%
(1/1) checking for file conflicts [####################################] 100%
(1/1) checking available disk space [####################################] 100%
:: Processing package changes...
(1/1) reinstalling linux [####################################] 100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: ''
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k 7.2.2-arch1-1
7.2.3-arch1-2 -U /efi/efi/boot/bootx64.efi
==> ERROR: '/lib/modules/7.2.2-arch1-1
7.2.3-arch1-2' is not a valid kernel module directory
error: command failed to execute correctlyindeed there are /usr/lib/modules/7.2.2-arch1-1 & /usr/lib/modules/7.2.3-arch1-2 ... When https://archlinux.org/packages/extra/x8 … idia-open/ will be updated?
Offline
It's updated!
Offline
Agree, I encountered this issue few times before and thought it was an accident. But now it happened again.
It's not convenient to watch every time whether linux and nvidia-open packages are in the same upgrade bulk, and restart upgrade manually ignoring linux and linux-headers packages if they aren't.
Online
You could workaround it by using nvidia-open-dkms, because at least the kernel and corresponding headers are built from the same package and those definitely should be in lockstep, but of course not a good solution if you don't want the couple 100 megs of the headers + the compile time.
Offline