Nvidia driver updated partially?

General system Newbie
1

Updated legacy nvidia 470 driver from AUR through yay, rebooted when was prompted to do so but something went wrong.

pacman states that all relevant packages were updated yet inxi -Ga outputs old driver:

pacman -Qm
lib32-nvidia-470xx-utils 470.182.03-1
libxnvctrl-470xx 470.182.03-1
nvidia-470xx-dkms 470.182.03-1
nvidia-470xx-settings 470.182.03-1
nvidia-470xx-utils 470.182.03-1

inxi -Ga
Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics vendor: Lenovo driver: i915
    v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports:
    active: HDMI-A-1,LVDS-1 empty: DP-1,VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:0166 class-ID: 0300
  Device-2: NVIDIA GK107M [GeForce GTX 660M] vendor: Lenovo driver: nvidia
    v: 470.161.03 alternate: nouveau,nvidia_drm non-free: series: 470.xx+
    status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx
    process: TSMC 28nm built: 2012-18 pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:0fd4 class-ID: 0300

nvidia-smi also throws an error:

nvidia-smi
Failed to initialize NVML: Driver/library version mismatch

Quick googling suggested rebooting, but that didn’t do the trick. Switching kernels (from my main lts to current used as backup) also did nothing.
Kinda strange because I didn’t recall yay throwing any errors during update :confused:

Would highly appreciate any ideas regarding potential source of the problem / fix.

2

If you are using dracut, try running sudo dracut-rebuild

3

@dalto, I’d shake your hand if I could :slight_smile:
Can you please clarify: is manual rebuilding of images when updating drivers through yay generally a must step? Or such things are handled automatically and that was just some random bug?

4

The nvidia drivers are built into the dracut image by default. However, I don’t know if the hooks look for the AUR packages.

2 Likes
5

I see. Well, in that case I’m bookmarking this thread :slight_smile:
Thank you!

6

Added nvidia-470xx-dkms in the hooks of package nvidia-hook, version 1.3-1.

Can you please test the hook by re-installing your Nvidia driver:

yay -Syu nvidia-470x-dkms

Please check also that package nvidia-hook was updated to the new version.

7

Thanks for the input! Turned out I didn’t have nvidia-hook at all. Probably because when I was installing EOS, I chose non Nvidia option since I already knew that I needed legacy driver.

I’m happy to test and report back but first one question (sorry if dumb): do I have to uninstall nvidia-470x-dkms before installing it again or simply installing “over” is totally fine?

1 Like
8

You don’t need to uninstall it first.

2 Likes
9

It gives me this output:

:: Synchronizing package databases...
 endeavouros is up to date
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Searching databases for updates...
:: Searching AUR for updates...
 -> Could not find all required packages:
        nvidia-470x-dkms (Target)
10

The second x was missing after 470. Sorry about that typo.
Should be

yay -Syu nvidia-470xx-dkms
11

No worries. I should also pay more attention to the output messages :slight_smile:

Can confirm: during the reinstall process, dracut did its job, I rebooted machine and everything works as it should.
Thanks for the great work and prompt fixes/updates! :+1: :enos:

1 Like
12

Thanks for testing and reporting! :+1:

13

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.