MX Linux Forum

Posted: **Sun Apr 17, 2022 7:42 am**

I could use some help getting my nvidia graphics card working with nvidia drivers. This box has been very picky about which kernel/nvidia combinations worked on MX-19 and I have yet to get nvidia drivers to install correctly since upgrading to MX21. I have to revert to the nouveau driver. - mike

Code: Select all

[code]
Snapshot created on: 20211215_1132
System:    Kernel: 5.17.0-2.3-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: audit=0 intel_pstate=disable hpet=disable 
           BOOT_IMAGE=/boot/vmlinuz-5.17.0-2.3-liquorix-amd64 
           root=UUID=<filter> ro quiet 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.1_x64 Wildflower October 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: Hewlett-Packard product: HP Z840 Workstation v: N/A 
           serial: <filter> Chassis: type: 6 serial: <filter> 
           Mobo: Hewlett-Packard model: 2129 v: 1.01 serial: <filter> 
           UEFI-[Legacy]: Hewlett-Packard v: M60 v02.38 date: 11/08/2017 
CPU:       Info: 8-Core model: Intel Xeon E5-2630 v3 bits: 64 type: MT MCP arch: Haswell 
           family: 6 model-id: 3F (63) stepping: 2 microcode: 49 cache: L2: 20 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 76621 
           Speed: 1197 MHz min/max: 1200/2401 MHz boost: enabled Core speeds (MHz): 1: 1197 
           2: 1198 3: 1198 4: 1199 5: 1198 6: 1200 7: 1199 8: 1199 9: 1198 10: 1197 11: 1197 
           12: 1197 13: 1197 14: 1198 15: 1202 16: 1203 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           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 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GK107GL [Quadro K420] vendor: Hewlett-Packard driver: nouveau 
           v: kernel alternate: nvidiafb bus-ID: 04:00.0 chip-ID: 10de:0ff3 class-ID: 0300 
           Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo 
           bus-ID: 3-11:6 chip-ID: 046d:0825 class-ID: 0102 serial: <filter> 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 2560x1600 s-dpi: 96 s-size: 677x423mm (26.7x16.7") 
           s-diag: 798mm (31.4") 
           Monitor-1: DP-1 res: 2560x1600 hz: 60 dpi: 109 size: 597x336mm (23.5x13.2") 
           diag: 685mm (27") 
           OpenGL: renderer: NVE7 v: 4.3 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel C610/X99 series HD Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8d20 class-ID: 0403 
           Device-2: NVIDIA GK107 HDMI Audio vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel bus-ID: 04:00.1 chip-ID: 10de:0e1b class-ID: 0403 
           Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo 
           bus-ID: 3-11:6 chip-ID: 046d:0825 class-ID: 0102 serial: <filter> 
           Device-4: Cambridge Silicon Radio Avantree Priva III type: USB 
           driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-5:5 chip-ID: 0a12:1004 
           class-ID: 0300 
           Sound Server-1: ALSA v: k5.17.0-2.3-liquorix-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Ethernet I218-LM vendor: Hewlett-Packard driver: e1000e v: kernel 
           port: 4040 bus-ID: 00:19.0 chip-ID: 8086:15a0 class-ID: 0200 
           IF: eth1 state: down mac: <filter> 
           Device-2: Intel I210 Gigabit Network vendor: Hewlett-Packard driver: igb v: kernel 
           port: 1000 bus-ID: 05:00.0 chip-ID: 8086:1533 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 1000 bus-ID: 07:00.0 
           chip-ID: 8086:2723 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-1:2 
           chip-ID: 8087:0029 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2 
           sub-v: 24bf hci-v: 5.2 rev: 24bf 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff 
           link-mode: slave accept service-classes: rendering, capturing, object transfer, audio 
Drives:    Local Storage: total: 3.66 TiB used: 617.75 GiB (16.5%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Micron model: MTFDDAK1T0TBN-1AR1ZABHA 
           size: 953.87 GiB block-size: physical: 4096 B logical: 512 B type: SSD 
           serial: <filter> rev: 0013 scheme: MBR 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB 
           block-size: physical: 4096 B logical: 512 B type: HDD rpm: 7200 serial: <filter> 
           rev: HP52 scheme: GPT 
Partition: ID-1: / raw-size: 951.92 GiB size: 935.9 GiB (98.32%) used: 21.55 GiB (2.3%) fs: ext4 
           dev: /dev/sda1 maj-min: 8:1 
           ID-2: /home raw-size: 2.73 TiB size: 2.69 TiB (98.39%) used: 596.21 GiB (21.7%) 
           fs: ext4 dev: /dev/sdb1 maj-min: 8:17 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 1.95 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sda2 maj-min: 8:2 
Sensors:   System Temperatures: cpu: 28.0 C mobo: N/A gpu: nouveau temp: 42.0 C 
           Fan Speeds (RPM): N/A gpu: nouveau fan: 2250 
Repos:     Packages: note: see --pkg apt: 3097 lib: 1715 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 non-free contrib main
           2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/opera-stable.list 
           1: deb https://deb.opera.com/opera-stable/ stable non-free
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb https://linux.teamviewer.com/deb/ stable main
Info:      Processes: 332 Uptime: 6m wakeups: 1 Memory: 62.73 GiB used: 1.42 GiB (2.3%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Shell: Bash v: 5.1.4 running-in: quick-system-info-mx 
           inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

[/code]

Posted: **Sun Apr 17, 2022 8:11 am**

You probably need to use an older kernel or wait until the 17 series gets nvidia support.

Posted: **Sun Apr 17, 2022 9:23 am**

what does

Code: Select all

nvidia-detect

tell you?

Posted: **Sun Apr 17, 2022 10:53 am**

Code: Select all

$ nvidia-detect
Detected NVIDIA GPUs:
04:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GL [Quadro K420] [10de:0ff3] (rev a1)

Checking card:  NVIDIA Corporation GK107GL [Quadro K420] (rev a1)
Your card is supported by all driver versions.
Your card is also supported by the Tesla 460 drivers series.
Your card is also supported by the Tesla 450 drivers series.
Your card is also supported by the Tesla 418 drivers series.
It is recommended to install the
    nvidia-driver
package.

btw, I tried installing nvidia booted to the following kernels:
4.19.2.202
5.10.0-10
5.10.0-11
5.10.0-12
5.10.0-13
5.14.0-4
5.15.0-2
and finally steveo's latest liquorix 5.17.0-2-3

Posted: **Sun Apr 17, 2022 11:39 am**

what's the symptom of having the drivers installed? black screen? incorrect resolutions?

Posted: **Sun Apr 17, 2022 11:44 am**

resolution is topped out @ 1024 x 768

Posted: **Sun Apr 17, 2022 11:45 am**

mmikeinsantarosa wrote: Sun Apr 17, 2022 11:44 am resolution is topped out @ 1024 x 768

were the drivers loaded? or were you stuck with vesa?

Posted: **Sun Apr 17, 2022 11:48 am**

dolphin_oracle wrote: Sun Apr 17, 2022 11:45 am
mmikeinsantarosa wrote: Sun Apr 17, 2022 11:44 am resolution is topped out @ 1024 x 768
were the drivers loaded? or were you stuck with vesa?

I forget what the graphics driver field had in it but it wasn't nvidia and it wasn't nouveau.

Posted: **Sun Apr 17, 2022 11:50 am**

the

Code: Select all

nvidia-detect

indicates that nvidia 418 & 450's support my card but and we have nvidia-telsa drivers but I don't know if they are the same thing or not.

Posted: **Sun Apr 17, 2022 11:54 am**

mmikeinsantarosa wrote: Sun Apr 17, 2022 11:48 am
dolphin_oracle wrote: Sun Apr 17, 2022 11:45 am
mmikeinsantarosa wrote: Sun Apr 17, 2022 11:44 am resolution is topped out @ 1024 x 768
were the drivers loaded? or were you stuck with vesa?
I forget what the graphics driver field had in it but it wasn't nvidia and it wasn't nouveau.

that 1024x768 is what vesa maxes out at usually. my current theory is that for some reason the nvidia-driver didn't load, and nouveau was blacklisted (which shouldn't have happened if the nvidia driver didn't build), which would have forced the system to vesa most likely.

is a /etc/X11/xorg.conf file conflicting?

Posted: **Sun Apr 17, 2022 12:17 pm**

dolphin_oracle wrote: Sun Apr 17, 2022 11:54 am is a /etc/X11/xorg.conf file conflicting?

I don't have an xorg.conf file.
just 2 files under xorg.conf.d; 10-evdev.conf & 20-synaptics.conf.

Posted: **Sun Apr 17, 2022 12:51 pm**

got the /var/log/ddm.log file?

Posted: **Sun Apr 17, 2022 1:05 pm**

dolphin_oracle wrote: Sun Apr 17, 2022 12:51 pm got the /var/log/ddm.log file?

ddm.log
*I have only tried installing nvidia from mxtools. I didn't try sgfxi.

Posted: **Sun Apr 17, 2022 1:26 pm**

a couple of things.

1. the drivers in the stable repo (debian's 460 drivers) won't build on any kernel highter than 5.10. so don't bother with the 460 drivers unless you are dropping back to 5.10.

2. the drivers in ahs build on kernels higher than 5.10, and from the looks of the one attempt with the 5.17 liquorix kernel, the modules did build and install on that one. in all the other attempts in the log, the modules did not build, and left a packages not configured.

So i suggest the following:

1. if you are going to use a kernel higher than the 5.10 kernel, you should go ahead an enable ahs, at least for the purposes of installing the nvidia drivers.
2. once you get the drivers installed on a kernel, lets check the inxi -G output after a reboot.

Posted: **Sun Apr 17, 2022 1:27 pm**

if I do use sgfxi to install say the nvidia-driver-460.91.03-1 from stable, can I get back to nouveau using?

Code: Select all

sudo ddm-mx -p nvidia

Posted: **Sun Apr 17, 2022 1:28 pm**

mmikeinsantarosa wrote: Sun Apr 17, 2022 1:27 pm if I do use sgfxi to install say the nvidia-driver-460.91.03-1 from stable, can I get back to nouveau using?
Code: Select all
sudo ddm-mx -p nvidia

no. sgfxi doesn't install debian packages and that's what ddm-mx works with. I think there is an nvidia uninstall command, which I think ddm-mx will tell you about but won't run. my info is

Code: Select all

sudo nvidia-install --uninstall

Posted: **Sun Apr 17, 2022 1:38 pm**

Mike's GPU is Kepler based, so not supported by the 510 series drivers - he needs to use 470.103 from backports. Debian say it builds on 5.17.

Personally it's why I'm stuck on the 5.15 kernel, MX19 doesn't have anything newer than 470.63 which won't build on 5.16 - I've been watching the nvidia driver situation with interest for a while. Hope this helps, I haven't tried it myself..

Posted: **Sun Apr 17, 2022 1:44 pm**

ah kepler...

so either stick with the 5.10 kernel, or

Code: Select all

sudo ddm-mx -i nvidia -b

which will poll backports instead of test (which currently doesn't have any drivers in it anyway). bulleye-backports is still at 470.

@timkb4cq it might be worth it to get a set of 470 drivers in test, since kepler is dropping out of the later nvidia drivers (495 and up).

Posted: **Sun Apr 17, 2022 1:48 pm**

giving 470 a try now

Posted: **Sun Apr 17, 2022 2:23 pm**

standby...

Posted: **Sun Apr 17, 2022 2:38 pm**

1) attempting to get the debian backports driver I get

Code: Select all

The following packages have unmet dependencies:
 nvidia-settings : Depends: libxnvctrl0 (= 470.94-1~bpo11+1) but 510.47.03-1~mx21+1 is to be installed
E: Unable to correct problems, you have held broken packages.

If I try to back down to libxnvctrl0 (= 470.94-1~bpo11+1) other packages need to get removed so I'll move onto trying with ahs enabled.

Posted: **Sun Apr 17, 2022 3:08 pm**

mmikeinsantarosa wrote: Sun Apr 17, 2022 2:38 pm 1) attempting to get the debian backports driver I get
Code: Select all
The following packages have unmet dependencies:
 nvidia-settings : Depends: libxnvctrl0 (= 470.94-1~bpo11+1) but 510.47.03-1~mx21+1 is to be installed
E: Unable to correct problems, you have held broken packages.
If I try to back down to libxnvctrl0 (= 470.94-1~bpo11+1) other packages need to get removed so I'll move onto trying with ahs enabled.

IIRC the only thing besides nvidia drivers that relies on libxnvctrl0 is conky for some reason. I've downgraded that thing in the past before.

Posted: **Sun Apr 17, 2022 3:09 pm**

we ran into this before with kepler parts.

https://forum.mxlinux.org/viewtopic.php ... 33#p674733

Posted: **Sun Apr 17, 2022 3:13 pm**

my display is back to 1024x768

Code: Select all

$ inxi -G
Graphics:
  Device-1: NVIDIA GK107GL [Quadro K420] driver: N/A 
  Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo 
  Display: x11 server: X.Org 1.20.11 driver: loaded: nouveau,vesa 
  unloaded: fbdev,modesetting resolution: 1024x768 
  OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5

on kernel

Code: Select all

$ inxi -S
System:
  Host: mx21BigBox Kernel: 5.17.0-2.3-liquorix-amd64 x86_64 bits: 64 
  Desktop: Xfce 4.16.0 Distro: MX-21.1_x64 Wildflower October 20  2021

Code: Select all

nvidia-driver-bin:
  Installed: 510.47.03-1~mx21+1

Posted: **Sun Apr 17, 2022 3:26 pm**

well, at least I don't need glasses to read screen text.

Which kernel should I back down to now to dump nvidia-510.47.03 and try the 470 set?

Posted: **Sun Apr 17, 2022 3:34 pm**

If you card is Kepler based you can’t go up you got to go down. 470 is going to be the top.

The link I provided is how we did this for another Kepler user.

Posted: **Sun Apr 17, 2022 3:48 pm**

dolphin_oracle wrote: Sun Apr 17, 2022 3:34 pm If you card is Kepler based you can’t go up you got to go down. 470 is going to be the top.

The link I provided is how we did this for another Kepler user.

What I meant is which kernel should I also back down to?
I'm on the 5.17.0-2.3-liquorix-amd64 now. Shouldn't I first back down to 5.10, 5.13 or 5.14 1st or should I be good to go on the liguorix-5.17?

Posted: **Sun Apr 17, 2022 3:54 pm**

I would use the 5.10 for now with either the backports 470 or the debian standard 460.

Posted: **Sun Apr 17, 2022 5:33 pm**

nvidia-tesla-460-driver-460.91.03-1 didn't install correctly as nouveau was still the driver after a restart.. I'll try the 470 before switching/upgrading the kernel.

Posted: **Sun Apr 17, 2022 6:52 pm**

what's the trick to get a force install of a specific driver?
ie;

Code: Select all

sudo ddm-mx -i -f nvidia-tesla-450-driver

Posted: **Sun Apr 17, 2022 8:23 pm**

it would be

Code: Select all

sudo ddm-mx -i nvidia -f nvidia-tesla-450-driver

Posted: **Wed Apr 20, 2022 6:25 pm**

I haven't given up but works got me loaded up.
Is there a list or something for a given nvidia driver for whether it'll build/install for the available kernels? That would be any of the 5.10 thru steveo's 5.17 liquorix?
at present

Code: Select all

$ nvidia-detect
Detected NVIDIA GPUs:
04:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GL [Quadro K420] [10de:0ff3] (rev a1)

Checking card:  NVIDIA Corporation GK107GL [Quadro K420] (rev a1)
Your card is supported by all driver versions.
Your card is also supported by the Tesla 470 drivers series.
Your card is also supported by the Tesla 460 drivers series.
Your card is also supported by the Tesla 450 drivers series.
Your card is also supported by the Tesla 418 drivers series.
It is recommended to install the
    nvidia-driver
package.

I figure on booting to the last 5.10 and then install the Tesla 418, reboot and check for success and if not, remove 418, reboot and install the 450
and repeat for the 460, 470 until I either have success or move onto booting to the next kernel and repeating the process.

Unless someone has a more efficient method.

Posted: **Wed Apr 20, 2022 7:38 pm**

the drivers in the main debian non-free repo will not build on higher than 5.10.

the drivers in backports should build on the backports kernel, but certainly up to 5.16.

ahs drives (510) will build on up to 5.16 kernel.

I'm not sure we have any that build on 5.17 yet.

Posted: **Thu Apr 21, 2022 8:50 am**

dolphin_oracle wrote: Wed Apr 20, 2022 7:38 pm the drivers in the main debian non-free repo will not build on higher than 5.10.

the drivers in backports should build on the backports kernel, but certainly up to 5.16.

ahs drives (510) will build on up to 5.16 kernel.

I'm not sure we have any that build on 5.17 yet.

that helps

Posted: **Thu Apr 21, 2022 8:56 am**

one other thing...that card uses a kepler chipset, which nvidia dropped from the main nvidia-driver drivers after 495.

so of the drivers we have available, you will need to stick to 470 and down.

Posted: **Thu Apr 21, 2022 3:10 pm**

What's the difference between running the

Code: Select all

 sudo ddm-mx

command vs

Code: Select all

apt-get install <package>

besides getting a /var/log/ddm.log file

Posted: **Thu Apr 21, 2022 3:14 pm**

mmikeinsantarosa wrote: Thu Apr 21, 2022 3:10 pm What's the difference between running the
Code: Select all
 sudo ddm-mx
command vs
Code: Select all
apt-get install <package>
besides getting a /var/log/ddm.log file

mostly the decision tree that helps pick the driver.

but if you don't need that, then you can use

Code: Select all

sudo apt-get install --install-recommends nvidia-driver-whatever

as long as you are using apt packages, the ddm-mx purge command will still reverse them.

Posted: **Thu Apr 21, 2022 5:57 pm**

The 510 drivers currently in AHS will build and work on 5.17 kernels, but the driver has to support the particular card. On the 2018 MSI laptop:

Code: Select all

$ uname -a
Linux msigp63 5.17.0-3.2-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 5.17-7~mx21+1 (2022-04-19) x86_64 GNU/Linux

Code: Select all

$ optirun inxi -G
Graphics:  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel 
           Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nvidia v: 510.47.03 
           Device-3: Acer HD Webcam type: USB driver: uvcvideo 
           Display: x11 server: X.Org 1.20.13 driver: loaded: nvidia resolution: 1920x1080~60Hz 
           OpenGL: renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 510.47.03

Since Sid has now added 5.17.3 to their latest kernel, they have probably also patched their older driver series. I'll look into backporting those tomorrow.
We do have a 390xx legacy driver that probably supports your card that also touts 5.17 compatiblility in ahs right now, too.

I'm backporting the 5.17.3 Sid kernel right now. I had to make some guesses as to how to continue disabling the gigantic -dbg packages with the Debian kernels; all that I had to go on in the changelog was

Code: Select all

  * Allow disabling debug info by build profile.

Along with the disappearance of the previous setting that disabled it in the global debian/config/defines file.

Posted: **Thu Apr 21, 2022 6:49 pm**

The 470, like all others I've tried to install mention something similar to

Code: Select all

dpkg: error processing package nvidia-tesla-470-kernel-dkms (--configure):
 installed nvidia-tesla-470-kernel-dkms package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-tesla-470-driver:
 nvidia-tesla-470-driver depends on nvidia-tesla-470-kernel-dkms (= 470.57.02-2~mx21+1) | nvidia-tesla-470-kernel-470.57.02; however:
  Package nvidia-tesla-470-kernel-dkms is not configured yet.
  Package nvidia-tesla-470-kernel-470.57.02 is not installed.
  Package nvidia-tesla-470-kernel-dkms which provides nvidia-tesla-470-kernel-470.57.02 is not configured yet.

and the make.log has this

Code: Select all

test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
echo >&2;							\
echo >&2 "  ERROR: Kernel configuration is invalid.";		\
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";	\
echo >&2 ;

There's nothing about kepler or some incompatibility issue. What's this mean? Do I need the kernel source to assist the build?

Posted: **Fri Apr 22, 2022 4:07 pm**

I haven't looked at 470 yet, but the Tesla 450 series recently updated in Bullseye security is supposed to build now on 5.17. They imported a newer version to overcome some security flaws, and the 5.17 compatibility came along with it.

Code: Select all

nvidia-graphics-drivers-tesla-450 (450.172.01-2~deb11u1) bullseye; urgency=medium

  * Rebuild for bullseye.

 -- Andreas Beckmann <anbe@debian.org>  Sun, 20 Mar 2022 16:53:36 +0100

nvidia-graphics-drivers-tesla-450 (450.172.01-2) unstable; urgency=medium

  * Add xorg-video-abi-25 (Xorg Xserver 21) as alternative dependency.
    (Closes: #1005932)
  * Backport pde_data changes from 470.103.01 to fix kernel module build for
    Linux 5.17.
  * dkms.conf: Use a BUILD_EXCLUSIVE equivalent hack to skip building for -rt
    kernels, not supported upstream (510.54-1).
  * Declare Testsuite: autopkgtest-pkg-dkms (510.54-1).

 -- Andreas Beckmann <anbe@debian.org>  Mon, 28 Feb 2022 21:03:12 +0100

The only time you need kernel source instead of a kernel headers package is if you don't have a headers package available because you manually built and installed your own kernel ye olde-timey way.

I don't think you need any nvidia hardware installed at all to test a driver build with ddm-mx, as long as you specify the driver version. Let me test that on the 5.17 kernel with the 5.10 installed.

Posted: **Fri Apr 22, 2022 4:17 pm**

Yeah, no problem with ddm-mx and that driver--here's the tail end of output:

Code: Select all

Processing triggers for nvidia-tesla-450-alternative (450.172.01-2~deb11u1) ...
Setting up nvidia-tesla-450-kernel-dkms (450.172.01-2~deb11u1) ...
Loading new nvidia-tesla-450-450.172.01 DKMS files...
Building for 5.17.0-3.2-liquorix-amd64
Building initial module for 5.17.0-3.2-liquorix-amd64
Done.

nvidia-tesla-450.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.17.0-3.2-liquorix-amd64/updates/dkms/

nvidia-tesla-450-modeset.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.17.0-3.2-liquorix-amd64/updates/dkms/

nvidia-tesla-450-drm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.17.0-3.2-liquorix-amd64/updates/dkms/

nvidia-tesla-450-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.17.0-3.2-liquorix-amd64/updates/dkms/

depmod...

DKMS: install completed.
Setting up nvidia-tesla-450-driver (450.172.01-2~deb11u1) ...
Processing triggers for glx-alternative-nvidia (1.2.1~deb11u1) ...
Processing triggers for glx-alternative-mesa (1.2.1~deb11u1) ...
Processing triggers for libc-bin (2.31-13+deb11u3) ...
Processing triggers for update-glx (1.2.1~deb11u1) ...
Processing triggers for glx-alternative-nvidia (1.2.1~deb11u1) ...
Processing triggers for libc-bin (2.31-13+deb11u3) ...
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.17.0-3.2-liquorix-amd64
W: Possible missing firmware /lib/firmware/i915/adlp_dmc_ver2_14.bin for module i915
I: The initramfs will attempt to resume from /dev/sdb3
I: (UUID=bbf9b48c-10d8-4d91-afcd-560b264bf78e)
I: Set the RESUME variable to override this.
Processing triggers for bumblebee (3.2.1-27) ...
Please wait, creating menu file - stored in /home/steve/.fluxbox/submenus/full_menu ...
Menu file created and ready to be used
Finished


========================================
========================================

To restore open source drivers later use:  
sudo ddm-mx -p nvidia

========================================
========================================


For recovery help see 
https://mxlinux.org/wiki/hardware/nvidia-driver-install-recovery

Information written to /home/steve/ddm-mx-nvidia_removal_command.txt

Posted: **Sun May 01, 2022 10:41 pm**

Code: Select all

System:
  Kernel: 5.10.0-13-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-13-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.1_KDE_x64 Wildflower April 9  2022 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Z600 Workstation 
  v: N/A serial: <filter> Chassis: type: 6 serial: <filter> 
  Mobo: Hewlett-Packard model: 0AE8h serial: <filter> 
  BIOS: Hewlett-Packard v: 786G4 v01.17 date: 08/19/2009 
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M185 
  serial: <filter> charge: 55% (should be ignored) rechargeable: yes 
  status: Discharging 
CPU:
  Info: 2x Quad Core model: Intel Xeon E5504 bits: 64 type: MCP SMP 
  arch: Nehalem family: 6 model-id: 1A (26) stepping: 5 microcode: 1D 
  cache: L2: 8 MiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31922 
  Speed: 1637 MHz min/max: 1596/1995 MHz Core speeds (MHz): 1: 1637 
  2: 1663 3: 1617 4: 1626 5: 1602 6: 1604 7: 1616 8: 1605 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no 
  microcode; SMT disabled 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, 
  STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GK107GL [Quadro K2000D] driver: nouveau v: kernel 
  bus-ID: 0f:00.0 chip-ID: 10de:0ff9 class-ID: 0300 
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
  loaded: modesetting unloaded: fbdev,vesa display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.7x9.4") 
  s-diag: 485mm (19.1") 
  Monitor-1: DVI-I-1 res: 1600x900 hz: 60 dpi: 92 
  size: 443x249mm (17.4x9.8") diag: 508mm (20") 
  OpenGL: renderer: NVE7 v: 4.3 Mesa 21.2.5 direct render: Yes 
Audio:
  Device-1: Intel 82801JI HD Audio vendor: Hewlett-Packard 
  driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3a3e 
  class-ID: 0403 
  Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel v: kernel 
  bus-ID: 0f:00.1 chip-ID: 10de:0e1b class-ID: 0403 
  Sound Server-1: ALSA v: k5.10.0-13-amd64 running: yes 
  Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:
  Device-1: Broadcom NetXtreme BCM5764M Gigabit Ethernet PCIe 
  vendor: Hewlett-Packard driver: tg3 v: kernel port: c0c0 
  bus-ID: 01:00.0 chip-ID: 14e4:1684 class-ID: 0200 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Intel 82557/8/9/0/1 Ethernet Pro 100 
  vendor: Compaq NC3121 Fast NIC driver: e100 v: kernel port: e000 
  bus-ID: 37:04.0 chip-ID: 8086:1229 class-ID: 0200 
  IF: eth1 state: down mac: <filter> 
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) 
  type: USB driver: btusb v: 0.8 bus-ID: 5-1.4:3 chip-ID: 0a12:0001 
  class-ID: e001 
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> 
  bt-v: 2.1 lmp-v: 4.0 sub-v: 22bb hci-v: 4.0 rev: 22bb 
  Info: acl-mtu: 310:10 sco-mtu: 64:8 
  link-policy: rswitch hold sniff park link-mode: slave accept 
  service-classes: rendering, capturing, object transfer, audio 
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 
  port: c0c0 bus-ID: 00:1f.2 chip-ID: 8086.2822 rev: class-ID: 0104 
Drives:
  Local Storage: total: 4.55 TiB used: 36.41 GiB (0.8%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 QVO 1TB 
  size: 931.51 GiB block-size: physical: 512 B logical: 512 B 
  speed: 3.0 Gb/s type: SSD serial: <filter> rev: 1B6Q scheme: MBR 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM004-2CV104 
  size: 3.64 TiB block-size: physical: 4096 B logical: 512 B 
  speed: 3.0 Gb/s type: HDD rpm: 5425 serial: <filter> rev: 0001 
  temp: 30 C scheme: GPT 
Partition:
  ID-1: / raw-size: 923.5 GiB size: 907.93 GiB (98.31%) 
  used: 36.41 GiB (4.0%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) 
  priority: -2 dev: /dev/sda2 maj-min: 8:2 
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A gpu: nouveau temp: 39.0 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 1770 
Repos:
  Packages: 2793 note: see --pkg apt: 2786 lib: 1586 flatpak: 7 
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
  1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
  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/microsoft-edge.list 
  1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
  2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
  Active apt repos in: /etc/apt/sources.list.d/opera-stable.list 
  1: deb https://deb.opera.com/opera-stable/ stable non-free
Info:
  Processes: 265 Uptime: 12m wakeups: 8 Memory: 23.51 GiB 
  used: 2.1 GiB (8.9%) Init: systemd v: 247 runlevel: 5 default: 5 
  tool: systemctl Compilers: gcc: 10.2.1 alt: 10 Shell: bash 
  default: Bash v: 5.1.4 running-in: quick-system-info-mx inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

Here is my card (Nvidia Quadro K2000d). Results of nvidia-detect

nvidia-detect
Detected NVIDIA GPUs:
0f:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GL [Quadro K2000D] [10de:0ff9] (rev a1)

Checking card: NVIDIA Corporation GK107GL [Quadro K2000D] (rev a1)
Your card is supported by all driver versions.
Your card is also supported by the Tesla 470 drivers series.
Your card is also supported by the Tesla 460 drivers series.
Your card is also supported by the Tesla 450 drivers series.
Your card is also supported by the Tesla 418 drivers series.
It is recommended to install the nvidia-driver package.

Cannot install 470, the script just fails

Candidate is: nvidia-tesla-470-driver 470.57.02-2~mx21+1
Installed is: nvidia-tesla-470-driver (none)

Need driver: nvidia-tesla-470-driver 470.57.02-2~mx21+1
2 ERROR: Unknown argument: nvidia

This is for both 5.10 and 5.16, using both main and debian backports. 450 does go through the install, but after a reboot noveau is still the default (can't use nvidia-smi or the gui settings program).

MX Linux Forum

MX-21 Need help getting nvidia drivers to install

MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install [Solved]

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install

Re: MX-21 Need help getting nvidia drivers to install