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

[dolphin_oracle]

it would be

Code: Select all

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

[mmikeinsantarosa]

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.

[dolphin_oracle]

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.

[mmikeinsantarosa]

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

[dolphin_oracle]

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.

[mmikeinsantarosa]

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

[dolphin_oracle]

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.

[Stevo]

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.

[mmikeinsantarosa]

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?

[Stevo]

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.