Good job 
I hope you enjoy your time here.MX330 (Pascal) user reporting. 590 is basically broken on that one, so highly likely everything pre-Turing. Luckily I have Timeshift working, so the moment I saw ā590ā on the update list I made a snapshot and boy was it a good decision.
Luckily #2, running nvidia-inst -n was an immediate relief, so all is good, and I guess thatās the price for using old cards.
Iām posting this for others who may use that card, and as Iām using ThinkPad T14 (1st gen) there may be others impacted. All is good though. 
Yes, they dropped support for everything pre-Turing.
Please note that nvidia-inst version 25.12-1 is on its way to all mirrors (which will take even a few hours).
This should handle much better the current situation with the changed Nvidia packages.
Please run it first in the test mode (nvidia-inst --test) to see what it suggests, and if the suggestion makes sense for your use case.
Then report here. Both success and failure report is appreciated, and in the latter case thereās material for more fixes.
ty for the heads up! i was able to switch over smoothly on my 1050 ti desktop 
It was almost too late for me also. I did the update and stupidly answered āyesā to all of the questions, including ādo you want to replace ānvidia-dkmsā with ānvidia-open-dkms.āā Thankfully, the install took a long time. I hadnāt rebooted my computer before I decided to do a Google search for nvidia-open-dkms, discovered that it didnāt support Pascal (10xx), and that I had to use nvidia-580xx-dkms. Also, there is no easy way to switch to the nvidia-580xx packages without ignoring the steam vulkan dependencies.
Yeah well thatās what happens when you donāt pay attention and/or are tired from work. 
It was a pain to fix but it didnāt take that long to fix.
Just use the -Rdd command to get rid of them.
Worked here with GTX 1060.
yay -Rdd nvidia nvidia-utils nvidia-settings lib32-nvidia-utils
yay -S nvidia-580xx-dkms nvidia-580xx-utils nvidia-580xx-settings lib32-nvidia-580xx-utils
BTW: Thx for your notification and your help
Just posting this here for the info (I follow his channelāsome people like himā¦..some do not): https://www.youtube.com/watch?v=2-obijeo_bU
Thanks i saw that one and I donāt get why some people donāt like Brodieās videos thy are informative.
Hi @manuel
Just ran nvidia-inst --test with 580.119.02-1 already installed, and I am not receiving suggestion to update to 590.48.01-1 for my 5090 card:
Summary
$ nvidia-inst --test
2025-12-26 14:55:43: Info: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GB202 [GeForce RTX 5090] [10de:2b85] (rev a1) (prog-if 00 [VGA controller])
2025-12-26 14:55:43: Info: Currently installed packages related to Nvidia:
2025-12-26 14:55:43: egl-gbm 1.1.2.1-1
2025-12-26 14:55:43: egl-wayland 4:1.1.21-1
2025-12-26 14:55:43: egl-x11 1.0.4-1
2025-12-26 14:55:43: libvdpau 1.5-3
2025-12-26 14:55:43: linux-firmware-nvidia 20251125-2
2025-12-26 14:55:43: nvidia-hook 1.5.3-1
2025-12-26 14:55:43: nvidia-inst 25.12-1
2025-12-26 14:55:43: nvidia-open-dkms 580.119.02-1
2025-12-26 14:55:43: nvidia-utils 580.119.02-1
2025-12-26 14:55:43: Info: inxi -Gza
Graphics:
Device-1: NVIDIA GB202 [GeForce RTX 5090] vendor: Micro-Star MSI
driver: nvidia v: 580.119.02 alternate: nouveau,nvidia_drm
non-free: 550-580.xx+ status: current (as of 2025-11) arch: Lovelace
code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 1
speed: 2.5 GT/s lanes: 16 link-max: gen: 5 speed: 32 GT/s ports:
active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:2b85
class-ID: 0300
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
display-ID: 0
Monitor-1: DP-1 model: MSI MPG341CX OLED built: 2023 res: mode: 3440x1440
hz: 240 scale: 100% (1) dpi: 109 gamma: 1.2 size: 800x337mm (31.5x13.27")
diag: 868mm (34.2") modes: max: 3440x1440 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: nvidia inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.119.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 5090/PCIe/SSE2
memory: 31.1 GiB display-ID: :1.0
API: Vulkan v: 1.4.335 layers: 2 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 5090 driver: nvidia v: 580.119.02
device-ID: 10de:2b85 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
2025-12-26 14:55:44: Info: nvidia-inst version 25.12-1
2025-12-26 14:55:44: Info: Command line: nvidia-inst --test
2025-12-26 14:55:44: Info: Selected mode: nvidia (Nvidiaās open source)
2025-12-26 14:55:44: Note: Package nvidia-open-dkms is set for install but it is installed already.
2025-12-26 14:55:44: Note: Package nvidia-hook is set for install but it is installed already.
2025-12-26 14:55:44: Info: Installing packages: nvidia-settings
2025-12-26 14:55:44: Info: Removing packages: nvidia-utils
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
COMMANDS TO RUN:
pacman -Rs --noconfirm --noprogressbar --nodeps nvidia-utils
pacman -Syuq --noconfirm --noprogressbar --needed nvidia-settings
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Is this the current expected behaviour?
Cheers
R
Hello, does anybody know if this affects an Quadro T2000 in a Thinkpad P53? Thanks!
You probably need to run
sudo pacman -Syu
or
eos-update
i.e. update the system.
nvidia-inst does not update packages.
Edit: the output of nvidia-inst may look confusing, but as said above, package updates are not considered by nvidia-inst but are the responsibility of the tools that update the system.
That is Turing so it should work with the new drivers. It is on the NVIDIA supported list for the 590 driver. I donāt have on to test with but you should be able to accept the replacement to move to nvidia-open
Thank you!
Thanks for your response. I did not know nvidia-inst did not handle updates. I was using in an attempt to force updates because I was stuck on 580 even though I had run pacman updates several times. I think it was because my mirrors were not up to date. I updated mirrors tried again and Iām now updated to 590.
For posterityās sake, in case BOINC throws the following error (Primegrid), donāt forget to install the AUR opencl packages:
Stderr output
<core_client_version>8.2.8</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
geneferg version 25.04.0 (linux x64, gcc-7.5.0, boinc-8.2.0)
Copyright (c) 2022, Yves Gallot
genefer is free source code, under the MIT license.
Command line: '-boinc -p -n 17 -b 383042732 -f gproof'
Error: boinc_get_opencl_ids() failed, err = -1.
Error: opencl error: CL_UNKNOWN_ERROR.
2025-12-26 19:00:06 (11506): called boinc_finish(1)
</stderr_txt>
]]>
PS using the nouveau driver will make your GPU unrecognized in BOINC.
Hi all - relatively new user (~1yr) with a 1080. This was my first time truly bricking my installation. I wanted to share my experience just in case someone else has issues because I think my particular brand of mess-up was unique.
I canāt explain exactly what I did wrong, but on 24-Dec-2025 I tried installing the -dkms solution and ran into dependency issues with Steam. After backing up data and uninstalling Steam, at some point I attempted to also install the nouveau drivers. This caused serious issues where, after I boot and login, my screen would go cycle between my desktop and a black screen about 4 times before going dark and showing my mouse. I concluded something had gone horribly wrong with my drivers. This may have been related to how the -dkms drivers will blacklist the nouveau drivers, but I cannot confirm.
I tried unsuccessfully to use rescue mode to fix my driver problems. I had a combination of problems related to (a) not being able to connect to the internet and (b) not being able to run pacman due to being root user. I decided the easiest solution would be a clean install. However, my installation USB was running Mercury (as opposed to Ganymede).
I was able to install by doing the following:
- Install without a GUI
- Once logged in via command line, manually install the nvidia-inst script via yay, and run nvidia-inst -n
- Reboot when prompted, then install my desktop of choice (KDE) via yay.
So far, it seems that I have been successful.