Nvidia Driver problem, Full system freeze while system idling on KDE Desktop

Big problem for me after the latest release update, it looks my nvidia card is unstable now. The only thing i was doing, was watching a movie and after i was done, i closed it and went away from PC.

After i came back i saw a full system freeze, only Steam was running minimized… nothing else was open.

TTY wasn’t working, all what i could do was REISUB.

In 5 year’s since im using Manjaro, i never had this problem before :frowning:
But in combination with gaming and nvidia Flatpak driver, there was sometimes issues like that.

Aug 16 18:20:59 koboldx-z170 org_kde_powerdevil[1396]: No traced function stack for current thread
Aug 16 18:20:59 koboldx-z170 org_kde_powerdevil[1396]: [  1396] Error(s) opening ddc devices
Aug 16 18:20:59 koboldx-z170 org_kde_powerdevil[1396]: [  1396] Error EACCES(-13): Permission denied opening /dev/i2c-0
Aug 16 18:21:00 koboldx-z170 pulseaudio[1382]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': unit failed
Aug 16 20:05:34 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 16 20:05:34 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:0:0:0x0000000f
Aug 16 20:05:34 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:2:0:0x0000000f
Aug 16 20:05:34 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:4:0:0x0000000f
Aug 16 20:05:34 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c57e:6:0:0x0000000f
Aug 16 20:05:34 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: DP-4: Failed to disable DisplayPort audio stream-3
Aug 16 20:05:34 koboldx-z170 kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Aug 16 20:05:34 koboldx-z170 kernel: handlers:
Aug 16 20:05:34 koboldx-z170 kernel: [<00000000978ae924>] i801_isr [i2c_i801]
Aug 16 20:05:34 koboldx-z170 kernel: [<00000000cb7c273d>] azx_interrupt [snd_hda_codec]
Aug 16 20:05:34 koboldx-z170 kernel: Disabling IRQ #16
Aug 16 20:05:39 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:05:44 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:05:49 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:05:54 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:05:59 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:04 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:09 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:14 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:19 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:24 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:29 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:34 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:39 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:44 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:49 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:54 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:06:59 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:04 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:09 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:14 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:19 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:24 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:29 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:34 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:39 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:44 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:49 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:54 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:07:59 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:04 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:09 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:14 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:19 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:24 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:29 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:34 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:39 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:44 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:49 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:54 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:08:59 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:04 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:09 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:14 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:19 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:24 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:29 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:34 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:39 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:44 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:49 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
Aug 16 20:09:54 koboldx-z170 kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c57d:0 5:0:4048:4036
$ inxi --admin --verbosity=5 --filter --no-host --width
System:
  Kernel: 6.12.41-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/vmlinuz-6.12-x86_64
    root=UUID=eb235aa7-d461-413d-800e-ea57385703fb rw sysrq_always_enabled=1
    retbleed=off resume=UUID=717b267e-7322-4bf9-a840-f1210d422d1a
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.17.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: Z170X-UD3 v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: Z170X-UD3-CF v: x.x serial: <superuser required>
    uuid: <superuser required> UEFI-[Legacy]: American Megatrends v: F23d
    date: 12/01/2017
Memory:
  System RAM: total: 16 GiB available: 15.57 GiB used: 2.41 GiB (15.5%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM0 type: no module installed
  Device-2: ChannelA-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G.Skill part-no: F4-2800C16-8GRR
    serial: N/A
  Device-3: ChannelB-DIMM0 type: no module installed
  Device-4: ChannelB-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G.Skill part-no: F4-2800C16-8GRR
    serial: N/A
CPU:
  Info: model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  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: 4500 min/max: 800/4700 scaling: driver: intel_pstate
    governor: performance cores: 1: 4500 2: 4500 3: 4500 4: 4500 5: 4500 6: 4500
    7: 4500 8: 4500 bogomips: 64026
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Vulnerable
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: Micro-Star MSI
    driver: nvidia v: 575.64.05 alternate: nouveau,nvidia_drm
    non-free: 550-570.xx+ status: current (as of 2025-04; EOL~2026-12-xx)
    arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
    gen: 3 speed: 8 GT/s lanes: 8 link-max: lanes: 16 ports: active: none
    off: DP-3 empty: DP-1, DP-2, HDMI-A-1, Unknown-2 bus-ID: 01:00.0
    chip-ID: 10de:1e07 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 122 s-size: 532x302mm (20.94x11.89")
    s-diag: 612mm (24.08")
  Monitor-1: DP-3 mapped: DP-4 note: disabled model: Dell S2417DG
    serial: <filter> built: 2018 res: N/A dpi: 123 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 2560x1440 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 x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.64.05
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
    memory: 10.74 GiB
  API: Vulkan v: 1.4.321 layers: 6 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 2080 Ti driver: nvidia v: 575.64.05 device-ID: 10de:1e07
    surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA TU102 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max:
    lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f7 class-ID: 0403
  Device-3: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
    Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 0b:00.0 chip-ID: 1102:0012 class-ID: 0403
  API: ALSA v: k6.12.41-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.7 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 17.0-43-g3e2bb status: active with:
    1: pulseaudio-alsa type: plugin 2: pulseaudio-jack type: module
    tools: pacat,pactl
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager
Drives:
  Local Storage: total: 5.93 TiB used: 456.93 GiB (7.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: MP600 PRO LPX
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: EIFM31.6 temp: 35.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 PRO 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: HGST (Hitachi) model: HDN724030ALE640
    size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: A5E0 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: Portable SSD T5
    size: 465.76 GiB 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: SSD serial: <filter>
    scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 88.61 GiB size: 86.66 GiB (97.80%) used: 23.63 GiB (27.3%)
    fs: ext4 dev: /dev/sdc1 maj-min: 8:33 label: N/A
    uuid: eb235aa7-d461-413d-800e-ea57385703fb
  ID-2: /boot raw-size: 2.93 GiB size: 2.82 GiB (96.15%)
    used: 219.8 MiB (7.6%) fs: ext3 dev: /dev/sdc3 maj-min: 8:35 label: N/A
    uuid: cbfeca98-b99d-4383-9ded-fe66cd598006
  ID-3: /home raw-size: 332.03 GiB size: 325.75 GiB (98.11%)
    used: 17.17 GiB (5.3%) fs: ext4 dev: /dev/sdc4 maj-min: 8:36 label: N/A
    uuid: ada4a6a2-bd0a-4652-b386-7c637bba7ee9
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sdc2 maj-min: 8:34 label: N/A
    uuid: 717b267e-7322-4bf9-a840-f1210d422d1a
Sensors:
  System Temperatures: cpu: 33.5 C mobo: N/A gpu: nvidia temp: 35 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 25%
Info:
  Processes: 256 Power: uptime: 17m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.2 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 257 default: graphical tool: systemctl
  Packages: 1729 pm: pacman pkgs: 1723 libs: 459 tools: pamac pm: flatpak
    pkgs: 6 Compilers: clang: 20.1.8 gcc: 15.1.1 Shell: Bash v: 5.3.3
    running-in: konsole inxi: 3.3.38

A 2080 is really old. Maybe consider to replace it with something from AMD. Currently stable branch stil ships the 575 sriver series.

My 2080Ti is released 2019 i guess… i bought it for 1150€ and still had good performance.

Im actually thinking more to replace my CPU, i could use more performance there… but when the Nvidia drivers getting worse now… maybe i have to replace… if nothing changed.

Anyways, nvidia 10th Gen is unsupported recently (required legacy driver now?) if i don’t lost the overview.

The 20th Gen like mine, still supports the new (partial open) nvidia driver… so i though im fine now with my 2080Ti or not?

I’m actually looking to create a Topic in nvidia driver… maybe there are still some developers listen to my complains, at least it worked few year’s ago where i had a few nvidia errors in the past.

Do you think i could use the legacy driver’s (470 series) for my 2080Ti, till this problem is fixed from nvidia?

Nvidia is only supporting newer cards. Unix graphics feature deprecation schedule - Linux - NVIDIA Developer Forums

It said Turing or later… and my 2080Ti is Turing… my GPU should have at least 3 year’s additional support, till nvidia put it into legacy state.

Edit:
I also created a Topic in the Nvidia Forum:

You’re reaching a pain point - the Z170 motherboard only supports 6th-7th generation CPUs, getting a little dated so that upgrading on the same platform will bring small gains… so you’re looking at a full platform, Mobo/RAM up to 32GiB upgrade which means maybe if you’re not rich, the GPU might have to wait (or you can try selling your mother).

The RX 7900 XT shows up as being much faster but 42% cheaper… an equivalent card would be the RX 6750… so I guess a lot hinges on whether you can lsit your nVidia in a local market and get some cash in first.

My System aged pretty well… i never had a old PC like this and the Hardware runs pretty good for this age… My skylake system is 10 year’s old, next month.

With saying about to replacing my CPU, i had in mind a full platform update… of course.

Actually it would be nice to have a AMD 9800X3D and a 9700 XT.
I have the money for it… but when i look how powerhungry today’s Hardware is designed today and how hot everything will be and the performance gain’s is almost a joke… when i compare the Performance gains around the last 30 year’s… where i normally did a platform update every 4-5 year’s.

In the past i got faster Hardware that required less and less Watt’s… and since 10 year’s there is only one direction.

When i look at the full picture, im always come to the conclusion… its maybe better that i still wait another 2 year’s, till there is something coming out, which is really worth it.

1 Like

You can try to switch to Testing branch and test if Nvidia 580 series still works for your GPU …

1 Like

That’s the good side of CPUs speeds increasing much slower than before.
10 years later, even the fastest CPUs are only twice as powerful in single thread rating.

And GPUs seem to be getting there too unless we want to use them for heating.

Good point, but i have a question about Testing branch. Isn’t it still the most delayed branch when it comes to security fixes or did this changed in the last 12 month, since i read about it?

It was still one of the most major arguments what i read, when people criticised the Testing Branch.

Security fixes are always fast-tracked in, in either of the three branches.

1 Like