Page 1 of 1

Old nVidia Drivers and new hardware, is there a solution?

Posted: Fri Nov 15, 2024 2:55 pm
by AVLinux
Hi,

Well as documented elsewhere I updated my Video card to a recent nVidia one and even though the one I installed is 'supported' it's not supported very well with the rather old existing nVidia drivers. I'm getting some visual glitching and weird things like log out not working and Video-centric software is crashing regularly. I'm apparently also needing a newer version of CUDA. I haven't owned nVidia hardware for many years and I remember in my early Debian days I used SGFXI but it doesn't work on systems set up for sudo, only with a separate Root account and it seems like an extreme leap to go outside of APT..

I'm guessing there is no middle ground, is there any recourse for those who need nVidia drivers newer that Debian Bookworm and Trixie provide?

*mini-rant: People can slag Windows all they want and there are occasional bad hardware drivers on every OS but by and large this stuff just works and works to the top degree of functionality, although Linux has made huge leaps and bounds there is still a lot of half-assery to be reckoned with for multimedia setups.

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Fri Nov 15, 2024 6:44 pm
by dolphin_oracle

Code: Select all

sudo ddm-mx -N -i nvidia
will pull from the nvidia developer repo.

you can use

Code: Select all

sudo su
to get to a root prompt for SGFXI

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Fri Nov 15, 2024 11:06 pm
by AVLinux
dolphin_oracle wrote: Fri Nov 15, 2024 6:44 pm

Code: Select all

sudo ddm-mx -N -i nvidia
will pull from the nvidia developer repo.

you can use

Code: Select all

sudo su
to get to a root prompt for SGFXI
Hi, and thanks for the help!

I opted for the ddm development option and it said it installed the 565 driver but on boot QSI says I'm running on Nouveau and Davinci Resolve can't find an OpenGL GPU... Like I said I've been blissfully away from nVidia for many years, is this a Nouveau blacklist thing? I had assumed since the original install of the 535 Driver seemed to look after Nouveau that the develoment Driver would too, is that not the case?

Code: Select all

System:
  Kernel: 6.11.7-1-liquorix-amd64 [6.11-11~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.11.7-1-liquorix-amd64 root=UUID=<filter> ro
    threadirqs quiet
  Desktop: Enlightenment v: 0.25.4 vt: 7 dm: LightDM v: 1.26.0 Distro: AVL_MXE_BASE-25-PR1_x64
    Greatest Hits October 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: X399 AORUS PRO v: N/A serial: <superuser required>
  Mobo: Gigabyte model: X399 AORUS PRO-CF serial: <superuser required> UEFI: American Megatrends
    v: F3a date: 11/30/2021
Battery:
  Device-1: hidpp_battery_0 model: Logitech M510 serial: <filter> charge: 55% (should be ignored)
    rechargeable: yes status: discharging
CPU:
  Info: model: AMD Ryzen Threadripper 2970WX bits: 64 type: MT MCP arch: Zen+ gen: 2 level: v3
    note: check built: 2018-21 process: GF 12nm family: 0x17 (23) model-id: 8 stepping: 2
    microcode: 0x800820D
  Topology: cpus: 1x cores: 24 tpc: 2 threads: 48 smt: enabled cache: L1: 2.2 MiB desc: d-24x32
    KiB; i-24x64 KiB L2: 12 MiB desc: 24x512 KiB L3: 64 MiB desc: 8x8 MiB
  Speed (MHz): avg: 2946 high: 3000 min/max: 2200/3000 boost: enabled scaling:
    driver: acpi-cpufreq governor: performance cores: 1: 3000 2: 3000 3: 2657 4: 3000 5: 3000 6: 1904
    7: 3000 8: 1862 9: 3000 10: 3000 11: 3000 12: 3000 13: 3000 14: 3000 15: 3000 16: 3000 17: 3000
    18: 3000 19: 3000 20: 3000 21: 3000 22: 3000 23: 3000 24: 3000 25: 3000 26: 3000 27: 3000
    28: 3000 29: 3000 30: 3000 31: 3000 32: 3000 33: 3000 34: 3000 35: 3000 36: 3000 37: 3000
    38: 3000 39: 3000 40: 3000 41: 3000 42: 3000 43: 3000 44: 3000 45: 3000 46: 3000 47: 3000
    48: 3000 bogomips: 287417
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_rstack_overflow mitigation: Safe RET
  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; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA vendor: Gigabyte driver: nouveau v: kernel alternate: nvidia_drm,nvidia
    non-free: N/A status: unknown device ID pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 42:00.0 chip-ID: 10de:2702
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: enlightenment driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
    s-diag: 1165mm (45.88")
  Monitor-1: DP-1 model: Samsung LU28R55 serial: <filter> built: 2023 res: 3840x2160 hz: 60
    dpi: 154 gamma: 1.2 size: 632x360mm (24.88x14.17") diag: 727mm (28.6") ratio: 16:9 modes:
    max: 3840x2160 min: 720x400
  API: OpenGL v: 4.3 Mesa 24.2.2-1~mx23ahs renderer: NV193 direct-render: Yes
Audio:
  Device-1: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 5-4:4
    pcie: chip-ID: 1963:0010 class-ID: 0300 gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0a:00.3
    chip-ID: 1022:1457 class-ID: 0403
  Device-2: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 42:00.1 chip-ID: 10de:22bb class-ID: 0403
  Device-3: IK Multimedia iRig PRO DUO type: USB driver: snd-usb-audio
  API: ALSA v: k6.11.7-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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 I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 04:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8812AE 802.11ac PCIe Wireless Network Adapter driver: rtl8821ae v: kernel
    modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 1000 bus-ID: 07:00.0 chip-ID: 10ec:8812
    class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Drives:
  Local Storage: total: 21.83 TiB used: 7.71 TiB (35.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Crucial model: CT2000P5PSSD8 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: P7CR403 temp: 39.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Crucial model: CT2000P5PSSD8 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: P7CR403 temp: 32.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Crucial model: CT2000BX500SSD1 size: 1.82 TiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 030 scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD2003FYYS-02W0B1 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1D02 scheme: MBR
  ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD2003FYYS-02W0B1 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1D02 scheme: MBR
  ID-6: /dev/sdd maj-min: 8:48 vendor: Western Digital model: WD141KRYZ-01C66B0 size: 12.73 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1H01 scheme: GPT
Partition:
  ID-1: / raw-size: 915.88 GiB size: 900.43 GiB (98.31%) used: 25.06 GiB (2.8%) fs: ext4
    dev: /dev/nvme0n1p3 maj-min: 259:5
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.44%) used: 25.9 MiB (10.3%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:3
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p4
    maj-min: 259:6
  ID-2: swap-2 type: zram size: 256 MiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.2 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2429 libs: 1428 tools: apt,apt-get,aptitude pm: rpm pkgs: 0 pm: flatpak
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
    2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Info:
  Processes: 773 Uptime: 1m wakeups: 2 Memory: 94.27 GiB used: 1.95 GiB (2.1%) Init: systemd v: 252
  target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Fri Nov 15, 2024 11:18 pm
by dolphin_oracle
AVLinux wrote: Fri Nov 15, 2024 11:06 pm
dolphin_oracle wrote: Fri Nov 15, 2024 6:44 pm

Code: Select all

sudo ddm-mx -N -i nvidia
will pull from the nvidia developer repo.

you can use

Code: Select all

sudo su
to get to a root prompt for SGFXI
Hi, and thanks for the help!

I opted for the ddm development option and it said it installed the 565 driver but on boot QSI says I'm running on Nouveau and Davinci Resolve can't find an OpenGL GPU... Like I said I've been blissfully away from nVidia for many years, is this a Nouveau blacklist thing? I had assumed since the original install of the 535 Driver seemed to look after Nouveau that the develoment Driver would too, is that not the case?

Code: Select all

System:
  Kernel: 6.11.7-1-liquorix-amd64 [6.11-11~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.11.7-1-liquorix-amd64 root=UUID=<filter> ro
    threadirqs quiet
  Desktop: Enlightenment v: 0.25.4 vt: 7 dm: LightDM v: 1.26.0 Distro: AVL_MXE_BASE-25-PR1_x64
    Greatest Hits October 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: X399 AORUS PRO v: N/A serial: <superuser required>
  Mobo: Gigabyte model: X399 AORUS PRO-CF serial: <superuser required> UEFI: American Megatrends
    v: F3a date: 11/30/2021
Battery:
  Device-1: hidpp_battery_0 model: Logitech M510 serial: <filter> charge: 55% (should be ignored)
    rechargeable: yes status: discharging
CPU:
  Info: model: AMD Ryzen Threadripper 2970WX bits: 64 type: MT MCP arch: Zen+ gen: 2 level: v3
    note: check built: 2018-21 process: GF 12nm family: 0x17 (23) model-id: 8 stepping: 2
    microcode: 0x800820D
  Topology: cpus: 1x cores: 24 tpc: 2 threads: 48 smt: enabled cache: L1: 2.2 MiB desc: d-24x32
    KiB; i-24x64 KiB L2: 12 MiB desc: 24x512 KiB L3: 64 MiB desc: 8x8 MiB
  Speed (MHz): avg: 2946 high: 3000 min/max: 2200/3000 boost: enabled scaling:
    driver: acpi-cpufreq governor: performance cores: 1: 3000 2: 3000 3: 2657 4: 3000 5: 3000 6: 1904
    7: 3000 8: 1862 9: 3000 10: 3000 11: 3000 12: 3000 13: 3000 14: 3000 15: 3000 16: 3000 17: 3000
    18: 3000 19: 3000 20: 3000 21: 3000 22: 3000 23: 3000 24: 3000 25: 3000 26: 3000 27: 3000
    28: 3000 29: 3000 30: 3000 31: 3000 32: 3000 33: 3000 34: 3000 35: 3000 36: 3000 37: 3000
    38: 3000 39: 3000 40: 3000 41: 3000 42: 3000 43: 3000 44: 3000 45: 3000 46: 3000 47: 3000
    48: 3000 bogomips: 287417
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_rstack_overflow mitigation: Safe RET
  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; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA vendor: Gigabyte driver: nouveau v: kernel alternate: nvidia_drm,nvidia
    non-free: N/A status: unknown device ID pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 42:00.0 chip-ID: 10de:2702
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: enlightenment driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
    s-diag: 1165mm (45.88")
  Monitor-1: DP-1 model: Samsung LU28R55 serial: <filter> built: 2023 res: 3840x2160 hz: 60
    dpi: 154 gamma: 1.2 size: 632x360mm (24.88x14.17") diag: 727mm (28.6") ratio: 16:9 modes:
    max: 3840x2160 min: 720x400
  API: OpenGL v: 4.3 Mesa 24.2.2-1~mx23ahs renderer: NV193 direct-render: Yes
Audio:
  Device-1: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 5-4:4
    pcie: chip-ID: 1963:0010 class-ID: 0300 gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0a:00.3
    chip-ID: 1022:1457 class-ID: 0403
  Device-2: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 42:00.1 chip-ID: 10de:22bb class-ID: 0403
  Device-3: IK Multimedia iRig PRO DUO type: USB driver: snd-usb-audio
  API: ALSA v: k6.11.7-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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 I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 04:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8812AE 802.11ac PCIe Wireless Network Adapter driver: rtl8821ae v: kernel
    modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 1000 bus-ID: 07:00.0 chip-ID: 10ec:8812
    class-ID: 0280
  IF: wlan0 state: down mac: <filter>
Drives:
  Local Storage: total: 21.83 TiB used: 7.71 TiB (35.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Crucial model: CT2000P5PSSD8 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: P7CR403 temp: 39.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Crucial model: CT2000P5PSSD8 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: P7CR403 temp: 32.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Crucial model: CT2000BX500SSD1 size: 1.82 TiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 030 scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD2003FYYS-02W0B1 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1D02 scheme: MBR
  ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD2003FYYS-02W0B1 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1D02 scheme: MBR
  ID-6: /dev/sdd maj-min: 8:48 vendor: Western Digital model: WD141KRYZ-01C66B0 size: 12.73 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1H01 scheme: GPT
Partition:
  ID-1: / raw-size: 915.88 GiB size: 900.43 GiB (98.31%) used: 25.06 GiB (2.8%) fs: ext4
    dev: /dev/nvme0n1p3 maj-min: 259:5
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.44%) used: 25.9 MiB (10.3%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:3
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p4
    maj-min: 259:6
  ID-2: swap-2 type: zram size: 256 MiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.2 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2429 libs: 1428 tools: apt,apt-get,aptitude pm: rpm pkgs: 0 pm: flatpak
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
    2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Info:
  Processes: 773 Uptime: 1m wakeups: 2 Memory: 94.27 GiB used: 1.95 GiB (2.1%) Init: systemd v: 252
  target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
I would have thought so. maybe nvidia changed something. you can attached a ddm.log file and I'll see if anything jumps out at me.

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Sat Nov 16, 2024 12:05 am
by AVLinux
Here's the log, it's quite large from 2 installs and was too big to post on the forum:

https://bandshed.net/files/ddm.log

Hmmm, I do see in the log where it said something about the card being unsupported by the original Driver, I missed that somehow but it went ahead and installed the 535 Driver. It must be supported by the 565 Linux development Driver because I'm using the 566 "Studio" Driver on Windows. I hope I can keep the 565 Driver and a manual blacklist tweak is all that is needed but I'll wait to see what you say..

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Sat Nov 16, 2024 5:51 pm
by AVLinux
@dolphin_oracle OK, some progress...

It turns out the system was a mess of both new and old drivers so I ran ddm to revert to Nouveau... success

The re-ran ddm to install the development 565 Drivers... partial success... I had to manually blacklist Nouveau just like the good old days

Rebooted into the nVidia 565 Driver...success

Code: Select all

Graphics:
  Device-1: NVIDIA vendor: Gigabyte driver: nvidia v: 565.57.01

Launched Davinci Resolve and it wants 'nvidia-opencl-icd' which is tied to the Debian 535 Driver so won't install without me downgrading the driver *pause to scream into pillow...

How do I get a matching nvidia-opencl-icd (or updated CUDA 12) to install..?

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Sat Nov 16, 2024 6:21 pm
by sunrat
CUDA 12.6 is in the Nvidia dev repo - https://developer.download.nvidia.com/c ... 12/x86_64/
Not sure if that will help with the opencl issue though.
Instruction to add that repo and import key are here - https://linuxcapable.com/install-nvidia ... on-debian/ . Whether that's a good idea or not, I can't say. @dolphin_oracle advice needed.

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Sat Nov 16, 2024 6:40 pm
by AVLinux
sunrat wrote: Sat Nov 16, 2024 6:21 pm CUDA 12.6 is in the Nvidia dev repo - https://developer.download.nvidia.com/c ... 12/x86_64/
Not sure if that will help with the opencl issue though.
Instruction to add that repo and import key are here - https://linuxcapable.com/install-nvidia ... on-debian/ . Whether that's a good idea or not, I can't say. @dolphin_oracle advice needed.
Thanks sunrat!

As far as I understand opencl is only needed in the case that CUDA 12+ is not available but I will wait on D_O's opinion..

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Sat Nov 16, 2024 6:41 pm
by dolphin_oracle
sunrat wrote: Sat Nov 16, 2024 6:21 pm CUDA 12.6 is in the Nvidia dev repo - https://developer.download.nvidia.com/c ... 12/x86_64/
Not sure if that will help with the opencl issue though.
Instruction to add that repo and import key are here - https://linuxcapable.com/install-nvidia ... on-debian/ . Whether that's a good idea or not, I can't say. @dolphin_oracle advice needed.
so ddm-mx's goal is to try to keep people from breaking their system, and it disables the developer repo when its done installing the graphics drivers.

you'll need to enable it to get the support library you want.

Code: Select all

wget https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/cuda-keyring_1.1-1_all.deb
sudo dpkg -i cuda-keyring_1.1-1_all.deb 
apt-get update
after than, the nvidia developer repo will be enabled just like any other repo, and you can install what you want.

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Sat Nov 16, 2024 7:34 pm
by AVLinux
dolphin_oracle wrote: Sat Nov 16, 2024 6:41 pm
sunrat wrote: Sat Nov 16, 2024 6:21 pm CUDA 12.6 is in the Nvidia dev repo - https://developer.download.nvidia.com/c ... 12/x86_64/
Not sure if that will help with the opencl issue though.
Instruction to add that repo and import key are here - https://linuxcapable.com/install-nvidia ... on-debian/ . Whether that's a good idea or not, I can't say. @dolphin_oracle advice needed.
so ddm-mx's goal is to try to keep people from breaking their system, and it disables the developer repo when its done installing the graphics drivers.

you'll need to enable it to get the support library you want.

Code: Select all

wget https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/cuda-keyring_1.1-1_all.deb
sudo dpkg -i cuda-keyring_1.1-1_all.deb 
apt-get update
after than, the nvidia developer repo will be enabled just like any other repo, and you can install what you want.
Hmmm I must have missed a step somewhere, I have the cuda keyring installed and the Repo enabled but I only see the MX Packages as install candidates in MXPI after apt updating.. It seems like the actual developer Driver Repo is missing, but the CUDA one is there..?

This is what is in sources.list.d (aside from regular Debian and MX Stuff)

Code: Select all

deb [signed-by=/usr/share/keyrings/cuda-archive-keyring.gpg] https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/ /
shot-2024-11-16_19-25-51.resized.jpg
shot-2024-11-16_19-30-47.resized.jpg

Re: Old nVidia Drivers and new hardware, is there a solution?  [Solved]

Posted: Sat Nov 16, 2024 8:25 pm
by dolphin_oracle
I suggest checking synaptic or apt on the cli. apparently mxpi isn't displaying it. I don't know why.

Code: Select all

apt policy nvidia-opencl-icd
nvidia-opencl-icd:
  Installed: (none)
  Candidate: 565.57.01-1
  Version table:
     565.57.01-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     560.35.03-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     560.28.03-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     555.42.06-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     555.42.02-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     550.127.05-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     550.90.12-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     550.90.07-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     550.54.15-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     550.54.14-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     545.23.08-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     545.23.06-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     535.183.06-1~mx23ahs 500
        500 http://mxrepo.com/mx/repo bookworm/ahs amd64 Packages
        500 http://mxrepo.com/mx/repo bookworm/ahs-staging amd64 Packages
     535.183.01-1~deb12u1 500
        500 http://deb.debian.org/debian bookworm/non-free amd64 Packages
     525.147.05-7~deb12u1 500
        500 http://deb.debian.org/debian bookworm-updates/non-free amd64 Packages
     525.116.04-1~mx23ahs 500
        500 http://mxrepo.com/mx/repo bookworm/non-free amd64 Packages

┌─[dolphin@mx23kde]─[08:24:21 pm]────────────────────────────────────────────────────────────────────────────────[~]
└─> 
***its just the version display in the table. apparently if you actually install, the latest version is downloaded. so something screwy in the version setting in the table. the "right-click" more info option also has the correct version.

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Sat Nov 16, 2024 8:30 pm
by oops
FI ... 565.57.01 is in beta stage ... maybe nvidia-driver_550.127.05-1_amd64.deb is better for you ?
( https://www.nvidia.com/en-us/drivers/details/233008/ )
( https://developer.download.nvidia.com/c ... 12/x86_64/ )

Code: Select all

# example:
$ pinxi -Ga
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nvidia v: 390.157
    non-free: 550.xx+ status: current (as of 2024-10; EOL~2026-12-xx)
    arch: Pascal code: GP10x process: TSMC 16nm built: 2016-2021 pcie: gen: 1
    speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1c82
    class-ID: 0300
    ...

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Sun Nov 17, 2024 12:29 pm
by AVLinux
dolphin_oracle wrote: Sat Nov 16, 2024 8:25 pm I suggest checking synaptic or apt on the cli. apparently mxpi isn't displaying it. I don't know why.

Code: Select all

apt policy nvidia-opencl-icd
nvidia-opencl-icd:
  Installed: (none)
  Candidate: 565.57.01-1
  Version table:
     565.57.01-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     560.35.03-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     560.28.03-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     555.42.06-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     555.42.02-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     550.127.05-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     550.90.12-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     550.90.07-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     550.54.15-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     550.54.14-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     545.23.08-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     545.23.06-1 500
        500 https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64  Packages
     535.183.06-1~mx23ahs 500
        500 http://mxrepo.com/mx/repo bookworm/ahs amd64 Packages
        500 http://mxrepo.com/mx/repo bookworm/ahs-staging amd64 Packages
     535.183.01-1~deb12u1 500
        500 http://deb.debian.org/debian bookworm/non-free amd64 Packages
     525.147.05-7~deb12u1 500
        500 http://deb.debian.org/debian bookworm-updates/non-free amd64 Packages
     525.116.04-1~mx23ahs 500
        500 http://mxrepo.com/mx/repo bookworm/non-free amd64 Packages

┌─[dolphin@mx23kde]─[08:24:21 pm]────────────────────────────────────────────────────────────────────────────────[~]
└─> 
***its just the version display in the table. apparently if you actually install, the latest version is downloaded. so something screwy in the version setting in the table. the "right-click" more info option also has the correct version.
OK, Is that a mxpi pkglist kind of issue? I can install Synaptic if I have to, I have actually removed it from my builds because I thought MXPI was now the one ring to rule them all...lol

*Installed Synaptic and as you said all packages now appear in their correct versions and install cleanly, I still have some occasional weird visual artifacts when using Thunar in particular and I'm wondering if this card is even fully supported even with the Beta Driver...?

I'm having a queasy deja vu feeling of when I bought this Gigabyte Aorus motherboard and AMD threadripper CPU back in 2019, it was 2017 tech and it took several months until Linux kernel 5.18 in 2020 to work without lockups.

Code: Select all

$ inxi -Ga
Graphics:
  Device-1: NVIDIA vendor: Gigabyte driver: nvidia v: 565.57.01
    alternate: nouveau,nvidia_drm non-free: N/A status: unknown device ID pcie:
    gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
    active: none off: DP-1 empty: DP-2,DP-3,HDMI-A-1 bus-ID: 42:00.0
    chip-ID: 10de:2702 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: enlightenment driver:
    X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
    gpu: nvidia,nvidia-nvswitch display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 154 s-size: 633x361mm (24.92x14.21")
    s-diag: 729mm (28.69")
  Monitor-1: DP-1 mapped: DP-0 note: disabled model: Samsung LU28R55
    serial: HCJW301573 built: 2023 res: 3840x2160 hz: 60 dpi: 154 gamma: 1.2
    size: 632x360mm (24.88x14.17") diag: 727mm (28.6") ratio: 16:9 modes:
    max: 3840x2160 min: 640x480
  API: OpenGL v: 4.6.0 NVIDIA 565.57.01 renderer: NVIDIA GeForce RTX 4080
    SUPER/PCIe/SSE2 direct-render: Yes
DevAVL@avl-devbox:~

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Sun Nov 17, 2024 5:43 pm
by AVLinux
I'm going to mark this Solved but for anyone reading be aware of the fine print which I'll summarize:

A special terminal command for enabling nVidia's development Repo was required in the DDM-MX nVidia driver installer:

Code: Select all

sudo ddm-mx -N -i nvidia
In order to satisfy other matching dependencies for other nVidia apps and libs from the development Repo I had to re-enable the Development Repo (DDM-MX usually disables it once the drivers are installed):

Code: Select all

wget https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/cuda-keyring_1.1-1_all.deb
sudo dpkg -i cuda-keyring_1.1-1_all.deb 
apt-get update
So... can you get newer nVidia Drivers than the regular MX Repos? YES.. But you will be straying from the supported and maintained MX Repos if you need other things aside from just the Drivers..

*Note you can always manually disable the nVidia developer Repos manually with MX Tools-->Repo Manager once you have what you need..

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Wed Jul 02, 2025 12:23 am
by tpoindex
Adding on to @AVLinux, I strayed way off into the weeds and out of bounds to upgrade my Nvidia drivers, Cuda and CuDNN packages. Here are some notes that I gathered, building onto the previous post. TL;DR - I several things were in a partially broken state; some symlinks and extra config fixed problems for me. YMMV!

1. Install latest Nvidia driver:

sudo ddm-mx -N -i nvidia
sudo reboot

# I chose the 575.xxx driver. For some reason, when I rebooted, I got the
# noveau driver instead. I simply ran the above ddm-mx command again, and
# finally got the Nvidia 575 driver.

2. OpenGL/GLX fixes:

# Check the current setup:

glxinfo -B

# Mine didn't show that it was using the Nvidia 575 driver. Searching on
# interwebs suggested running update-glx to pick the right version.
# I also had to symlink libglxserver_nvidia.so.575.57.08 to a non-versioned
# link:

cd /usr/lib/xorg/modules/extensions/
sudo ln -s libglxserver_nvidia.so.575.57.08 libglxserver_nvidia.so

sudo apt install update-glx
reboot
sudo update-glx --config glx

glxinfo -B # hopefully should show using the NVIDIA 575.xxx driver

3. VDPAU video decoder fix for Nvidia accelerated codecs.

vdpauinfo

# Check that it shows NVIDIA VDPAU Driver Shared Library 575.xxxx
# If not, fix with a symlink

cd /usr/lib/x86_64-linux-gnu/vdpau
sudo ln -s libvdpau_nvidia.so libvdpau_nvidia.so.575.57.08
sudo ln -s libvdpau_nvidia.so.1 libvdpau_nvidia.so.575.57.08
reboot

# Check by running 'vdpauinfo' again.


4. Remove any existing Cuda, CuDNN, or associated packages:

synaptic ......

# I used the 'Installed' filter, and search for 'cuda', which should
# find most of the cuda packages. Search 'cudnn' to find any
# installed cudnn. Mark for removal and apply.

5. Install cuda-12.9 & cudnn9-cuda-12-9

# goto: https://developer.nvidia.com/cuda-downl ... t_os=Linux
# Follow the instructions to add the Nvidia key to the APT keyring, and
# repo configs & run 'apt udpate'

synaptic .....

# Choose the cuda-12.9 meta package, along with any other
# I think I had to install 'cuda-command-line-tools-12-9', I don't remember
# if it was included in the cuda-12-9 meta package. You can alternatively
# choose the 'cuda-toolkit' meta package (ver 12.9.1-1) , which will upgrade with
# newer versions. I prefer to do this manually and be aware of version
# differences.


Good luck, and remember your are on your own at this point, your system may be left
broken.

Re: Old nVidia Drivers and new hardware, is there a solution?

Posted: Wed Jul 02, 2025 2:13 am
by Eadwine Rose
You can post code on the forum like this:

[code]code output here[/code]