I just decided to update my system and I don’t like what’s happening here. It’s replacing my nvidia drivers with the problematic ones.
@Team Garuda, how do I stop this and keep nvidia-dkms drivers?
I have moved your post to a new topic, as your issue has nothing to do with the other thread. Please post your garuda-inxi here.
Which GPU are you referring to, your GTX 1660 Ti? If so, the nvidia-open-dkms 590 are the correct drivers for your Turing GPU.
3 Likes
System:
Kernel: 6.17.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=90f38fa6-2f61-4ff4-8aed-3355bf0cd0f1 rw rootflags=subvol=@
quiet resume=UUID=25c0f7a4-6014-4e50-adaf-09327feba0fb loglevel=3
Desktop: KDE Plasma v: 6.5.3 tk: Qt v: N/A info: frameworks v: 6.20.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: P8Z77-V v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
Firmware: BIOS vendor: American Megatrends v: 2104 date: 08/13/2013
CPU:
Info: model: Intel Core i7-3770K bits: 64 type: MT MCP arch: Ivy Bridge
gen: core 3 level: v2 built: 2012-15 process: Intel 22nm family: 6
model-id: 0x3A (58) stepping: 9 microcode: 0x21
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 4100 min/max: 1600/4100 scaling: driver: intel_cpufreq
governor: performance cores: 1: 4100 2: 4100 3: 4100 4: 4100 5: 4100 6: 4100
7: 4100 8: 4100 bogomips: 57686
Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: ASUSTeK P8 series
driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports:
active: none empty: DP-4, DP-5, DP-6, HDMI-A-2, HDMI-A-3, HDMI-A-4, VGA-1
bus-ID: 00:02.0 chip-ID: 8086:0162 class-ID: 0300
Device-2: NVIDIA TU116 [GeForce GTX 1660 Ti] vendor: Micro-Star MSI
driver: nvidia v: 580.105.08 alternate: nouveau,nvidia_drm
non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx)
arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s lanes: 16
ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 02:00.0
chip-ID: 10de:2182 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: modesetting,nvidia
unloaded: nouveau alternate: fbdev,intel,nv,vesa dri: crocus
gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0
Monitor-1: HDMI-A-1 model: Samsung S24C450 serial: <filter> built: 2013
res: mode: 1920x1200 hz: 60 scale: 100% (1) dpi: 94 gamma: 1.2
size: 518x324mm (20.39x12.76") diag: 611mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
API: EGL v: 1.5 hw: drv: intel crocus drv: nvidia platforms: device: 0
drv: nvidia device: 1 drv: crocus device: 3 drv: swrast gbm: drv: crocus
surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
inactive: device-2
API: OpenGL v: 4.6.0 compat-v: 4.2 vendor: nvidia mesa v: 580.105.08
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2
memory: 5.86 GiB display-ID: :1.0
API: Vulkan v: 1.4.328 layers: 16 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 1660 Ti driver: nvidia v: 580.105.08 device-ID: 10de:2182
surfaces: N/A device: 1 type: integrated-gpu name: Intel HD Graphics 4000
(IVB GT2) driver: mesa intel v: 25.3.1-arch1.2 device-ID: 8086:0162
surfaces: N/A device: 2 type: cpu name: llvmpipe (LLVM 21.1.6 256 bits)
driver: mesa llvmpipe v: 25.3.1-arch1.2 (LLVM 21.1.6)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl,nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20
class-ID: 0403
Device-2: NVIDIA TU116 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 8
link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 02:00.1
chip-ID: 10de:1aeb class-ID: 0403
Device-3: JMTek LLC. CMTECK driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:3
chip-ID: 0c76:165f class-ID: 0300 serial: <filter>
API: ALSA v: k6.17.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel 82579V Gigabit Network vendor: ASUSTeK P8P67 Deluxe
driver: e1000e v: kernel port: f080 bus-ID: 00:19.0 chip-ID: 8086:1503
class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: ASUSTeK
driver: ath9k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 07:00.0 chip-ID: 168c:0032 class-ID: 0280
IF: wlp7s0 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 4-1.3:3 chip-ID: 0bda:a725
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci1 rfk-id: 4 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 2.73 TiB used: 699.07 GiB (25.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: PNY model: CS900 1TB SSD
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 06B5 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: Backup+ Hub BK
size: 1.82 TiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.1
spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: D781 scheme: MBR
Partition:
ID-1: / raw-size: 897.38 GiB size: 897.38 GiB (100.00%)
used: 110.44 GiB (12.3%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-2: /home raw-size: 897.38 GiB size: 897.38 GiB (100.00%)
used: 110.44 GiB (12.3%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-3: /var/log raw-size: 897.38 GiB size: 897.38 GiB (100.00%)
used: 110.44 GiB (12.3%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-4: /var/tmp raw-size: 897.38 GiB size: 897.38 GiB (100.00%)
used: 110.44 GiB (12.3%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.03 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
ID-2: swap-2 type: partition size: 34.13 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda2 maj-min: 8:2
Sensors:
System Temperatures: cpu: 35.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 31.03 GiB used: 3.29 GiB (10.6%)
Processes: 317 Power: uptime: 19m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.37 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1888 libs: 522 tools: octopi,paru Compilers:
clang: 21.1.6 gcc: 15.2.1 Shell: Bash v: 5.3.8 default: fish v: 4.2.1
running-in: konsole inxi: 3.3.40
Garuda (2.11.1-1):
System install date: 2025-11-15
Garuda release: 251002
Last full system update: 2025-12-23 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut nvidia-utils nvidia-open-dkms garuda-hardware-profile-nvidia garuda-hardware-profile-standard garuda-hardware-profile-standard-x11
Windows dual boot: <superuser required>
Failed units:
--- System Health Check Report ---
24/26 checks run in 0.83 seconds ⌛
Powered by garuda-health 🦅
--- LOW ---
- Old Btrfs snapshots found that can be deleted (fix available)
--- INFO ---
- A reboot is pending (update applied since last reboot)
Run garuda-health --fix to apply fixes.
I’ve just had a really terrible experience with the 590.48.01-1 nvidia-open-dkms drivers after doing a garuda-update to update my system.
My resolution went to 640 x 480 and could not be changed. Fortunately I have kept an old snapshot that captured the day I installed nvidia proprietary drivers and I just jumped back to them and I’m back. That nvidia 590 driver is just terribly off!
Yes it’s for my GTX 1660 Ti, I need a way to stop garuda update from changing my current drivers as I update the rest of the system otherwise it’s ruining my hibernation and resolution.
I’ve just come from actually testing hibernation on the 580 drivers I fell back to and it turns out they failed. On checking whether I had open source or proprietary drivers. I fell back to open source which breaks hibernation so I had to do this:
After the above, hibernation works as it should. I’d really appreciate if there’s a way to have garuda update just draw proprietary drivers alone without seeking out the open source ones because the proprietary ones tick all the boxes for me (from fast paced fps multiplayer shooter with no screen tearing to tasks on the desktop like hibernation flawlessly)
Please don’t post pics from the terminal, pics are not searchable and difficult to read. Terminal output always belongs in a code block. Thanks.
Perhaps it would make more sense to fix the issues with your GPU, which is supported by the nvidia-open-dkms 590 drivers, instead of wanting to keep the proprietary 580 drivers.
I personally can’t help you with that because I don’t use Nvidia anymore. Just wait until someone jumps in and helps you.
5 Likes
Not a Nvidia user here too…
I just wanted to confirm that this is a known upstream problem:
6 Likes
Yes i understand it too 
dont blame me garuda fellas. I did uninstalled garuda-hardware-profile and installed the 340. driver to kept off flickering on wired screen behavior insted of open sources one. I did it on the pkg ignoring list for updatings and is working without graphical issues.
Frankly my experience with the opensource ones before the Nvidia GPU worked quite well. I guess the opensource drivers in an Nvidia gpu setup need more work hopefully Garuda devs will manage to encorp power management into them so that the Nvidia gpus don’t consume too much power and there’s support for steam. (This problem really is an Nvidia thing, reason I went with this gpu is I have had like all my past Radeon gpus die on me prematurely but the Nvidias I’d stay with them till I end up selling them, I’ve never had an Nvidia gpu die on me ever.)
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.