Repository/Build Issue: NVIDIA Drivers missing from Trixie (Testing) on PVE 6.17.9

C

Crashies

New Member
Feb 11, 2026
2
0
1
Hi all,

I'm running a Proxmox host on a Debian Trixie (Testing) base with kernel 6.17.9-1-pve. I am trying to set up an NVIDIA GTX 950/RTX 3070 for LXC passthrough, but I've hit a wall.

The Problem:

  1. Repository Visibility: Despite adding contrib non-free non-free-firmware to my debian.sources file (DEB822 format), apt install nvidia-driver returns "no installation candidate."
  2. Kernel Compatibility: Previous attempts to install manual .deb packages failed with DKMS build errors (exit status 2) on the 6.17 kernel.
Current setup:

Has the nvidia-driver package been temporarily pulled from the Trixie branch due to the 6.17 kernel changes, or is there a specific Proxmox-compatible repository I should be using for newer kernels?
 
not super sure about the 'no installation candidate' issue, what does
Code: 
apt-cache policy nvidia-driver
show?
here it's like this:
Code: 
nvidia-driver:
  Installed: (none)
  Candidate: 550.163.01-2
  Version table:
     550.163.01-2 500
        500 http://deb.debian.org/debian trixie/non-free amd64 Packages

so it is available in the non-free section...

aside from that, it won't work anyway since it's not compatible with our 6.17 kernel as you already wrote
so normally i'd recommend checking the 'backports' repository, but AFAICS there is no newer one available.

Without that, the only way left is to use the generic linux '.run' file from nvidias homepage (which should cope with the newer kernel)
 
Thanks, Dominik. I fixed my DEB822 sources and now see the candidate 550.163.01-2.

However, I've seen reports that version 550.163.01-4 contains a backported fix specifically for the 6.17 kernel build errors. You mentioned backports doesn't have a newer one, but 550.163.01-4~bpo13+1 seems to be showing up in some Trixie-backports lists.

Should I try to pull that specific version? Also, I'm swapping to an RTX 3070 soon will it still be shareable across multiple LXCs even if I have to use a workaround for the host driver?"
 
Crashies said:
However, I've seen reports that version 550.163.01-4 contains a backported fix specifically for the 6.17 kernel build errors. You mentioned backports doesn't have a newer one, but 550.163.01-4~bpo13+1 seems to be showing up in some Trixie-backports lists.

Should I try to pull that specific version?
Click to expand...
ah ok, i only saw that just the package version was bumped and assumed it didn't contain any relevant changes for this, but yeah go ahead and try, the worst that can happen is that the module won't compile and you have to remove the package again wit apt remove

Crashies said:
Also, I'm swapping to an RTX 3070 soon will it still be shareable across multiple LXCs even if I have to use a workaround for the host driver?"
Click to expand...
if the driver you installed also works with a 3070, i don't see how it would behave differently, but since i don't know exactly what you want to configure/do it's hard to say ;)
 
You must log in or register to reply here.
Top Bottom
Back