Page 1 of 1

Nvidia- driver update  [Solved]

Posted: Mon Dec 30, 2024 7:04 pm
by chippy52
The latest Nvidia driver upload has failed to install on my machine.

Code: Select all

System:    Kernel: 6.4.9-1-liquorix-amd64 [6.4-10~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: audit=0 intel_pstate=disable hpet=disable rcupdate.rcu_expedited=1 
           BOOT_IMAGE=/boot/vmlinuz-6.4.9-1-liquorix-amd64 root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower January 15  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B350M-A v: Rev X.0x serial: <filter> 
           UEFI-[Legacy]: American Megatrends v: 5603 date: 07/28/2020 
CPU:       Info: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ family: 17 (23) 
           model-id: 8 stepping: 2 microcode: 800820D cache: L2: 4 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102207 
           Speed: 3391 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 3786 
           2: 1517 3: 1550 4: 1550 5: 2022 6: 1550 7: 1550 8: 3200 9: 3761 10: 1550 11: 2528 
           12: 1517 13: 3667 14: 3792 15: 1550 16: 1550 
           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: 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 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050] vendor: ASUSTeK driver: nouveau v: kernel 
           bus-ID: 09:00.0 chip-ID: 10de:1c81 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: modesetting 
           unloaded: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: DVI-D-1 res: 1920x1080 hz: 60 dpi: 94 size: 521x293mm (20.5x11.5") 
           diag: 598mm (23.5") 
           OpenGL: renderer: NV137 v: 4.3 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus-ID: 09:00.1 chip-ID: 10de:0fb9 class-ID: 0403 
           Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus-ID: 0b:00.3 chip-ID: 1022:1457 class-ID: 0403 
           Sound Server-1: ALSA v: k6.4.9-1-liquorix-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: f000 bus-ID: 07:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.14 TiB used: 528.19 GiB (45.1%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: A-Data model: SX8200PNP size: 238.47 GiB 
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: 32B2T6TA temp: 30.9 C scheme: MBR 
           ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: CC43 scheme: GPT 
Partition: ID-1: / raw-size: 215.96 GiB size: 211.51 GiB (97.94%) used: 15 GiB (7.1%) fs: ext4 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
           ID-2: /home raw-size: 14.65 GiB size: 14.32 GiB (97.74%) used: 4.86 GiB (33.9%) 
           fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:3 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 7.86 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme0n1p2 maj-min: 259:2 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: note: see --pkg apt: 2564 lib: 1423 flatpak: 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/ bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mx.debian.nz/mx/repo/ bullseye main non-free
           2: deb http://mx.debian.nz/mx/repo/ bullseye ahs
Info:      Processes: 354 Uptime: 8h 2m wakeups: 3 Memory: 15.55 GiB used: 3.86 GiB (24.8%) 
           Init: systemd v: 247 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)
I tried to run the Nvidia driver installer but had no luck. This is a partial section fron the output. The current version of libssl3 installed on my machine is 3.0.15.-1~deb12u1~mx21

The following packages have unmet dependencies:
nvidia-driver : Depends: libss13 but it is not installable
Recommends: nvidia-settings (>= 535) but 525.85.05-1~mx21ahs is to be installed
Recommends: nvidia-persistenced (>= 535)
E: Unable to correct problems, you have held broken packages.
POSTINSTALL
symlinks
20_nvidia.conf
Finished

Would be grateful for any suggestions to rectify the issue.

Re: Nvidia- driver update

Posted: Tue Dec 31, 2024 3:57 am
by Eadwine Rose
In the announcement is this, might have something to do with it?

viewtopic.php?t=83172

Re: Nvidia- driver update

Posted: Tue Dec 31, 2024 7:46 pm
by chippy52
As a test I switched the kernel to Kernel: 6.1.0-10mx-ahs2-amd64 and tried again. This threw up the same errors. It appears to have something to do with libss13 ( not installable ) Installed on my machine it is shown as libssl3.

Re: Nvidia- driver update

Posted: Wed Jan 01, 2025 1:10 am
by Stevo
Well, I finish up the old year 2024 by having to correct that typo, so a newer fixed mx21ahs+1 version is coming soon to a repo near you.

It now seems that a new rather complex Liquorix patch is making it impracticable for us to build it on the gcc-10 in MX 21, too. We had a pretty good run with it, though.

Re: Nvidia- driver update

Posted: Wed Jan 01, 2025 2:14 pm
by chippy52
Much appreciated Stevo. If it becomes to difficult I can revert back to the standard kernel.

Re: Nvidia- driver update

Posted: Wed Jan 01, 2025 4:30 pm
by Stevo
chippy52 wrote: Wed Jan 01, 2025 2:14 pm Much appreciated Stevo. If it becomes to difficult I can revert back to the standard kernel.
We have up to 6.12 for MX 21, so it's possible for that update for you.

Re: Nvidia- driver update

Posted: Fri Jan 03, 2025 1:14 am
by chippy52
We have success thank you Stevo.