#1135362 linux-image-7.0.3+deb14-amd64: Fails to build nVidia module

Package:
nvidia-kernel-dkms
Source:
nvidia-kernel-dkms
Submitter:
Nicolas Patrois
Date:
2026-06-26 10:01:01 UTC
Severity:
normal
Tags:
#1135362#5
Date:
2026-05-01 16:12:04 UTC
From:
To:
Dear Maintainer,

I don’t know if it’s the right place to report this bug.
Anyway, this morning, I couldn’t build nVidia module.

Here is apt’s output (a bit filtered):

Paramétrage de linux-headers-7.0.3+deb14-amd64 (7.0.3-1) ...
/etc/kernel/header_postinst.d/dkms:
Sign command: /lib/modules/7.0.3+deb14-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Autoinstall of module nvidia-current/550.163.01 for kernel 7.0.3+deb14-amd64
(x86_64)
Building module(s)..........(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j12 modules KERNEL_UNAME=7.0.3+deb14-amd64

Error! Bad return status for module build on kernel: 7.0.3+deb14-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/550.163.01/build/make.log for more
information.

Autoinstall on 7.0.3+deb14-amd64 failed for module(s) nvidia-current(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 1
dpkg: erreur de traitement du paquet linux-headers-7.0.3+deb14-amd64
(--configure) :
 old linux-headers-7.0.3+deb14-amd64 package postinst maintainer script
subprocess failed with exit status 1
Paramétrage de linux-image-7.0.3+deb14-amd64 (7.0.3-1) ...
I: /initrd.img is now a symlink to boot/initrd.img-7.0.3+deb14-amd64
/etc/kernel/postinst.d/dkms:
Sign command: /lib/modules/7.0.3+deb14-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Autoinstall of module nvidia-current/550.163.01 for kernel 7.0.3+deb14-amd64
(x86_64)
Building module(s)..........(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j12 modules KERNEL_UNAME=7.0.3+deb14-amd64

Error! Bad return status for module build on kernel: 7.0.3+deb14-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/550.163.01/build/make.log for more
information.

Autoinstall on 7.0.3+deb14-amd64 failed for module(s) nvidia-current(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: erreur de traitement du paquet linux-image-7.0.3+deb14-amd64
(--configure) :
 old linux-image-7.0.3+deb14-amd64 package postinst maintainer script
subprocess failed with exit status 1
[…]
dpkg: des problèmes de dépendances empêchent la configuration de linux-headers-
amd64 :
 linux-headers-amd64 dépend de linux-headers-7.0.3+deb14-amd64 (= 7.0.3-1);
cependant :
 Le paquet linux-headers-7.0.3+deb14-amd64 n'est pas encore configuré.

dpkg: erreur de traitement du paquet linux-headers-amd64 (--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de linux-image-
amd64 :
 linux-image-amd64 dépend de linux-image-7.0.3+deb14-amd64 (= 7.0.3-1);
cependant :
 Le paquet linux-image-7.0.3+deb14-amd64 n'est pas encore configuré.

dpkg: erreur de traitement du paquet linux-image-amd64 (--configure) :
 problèmes de dépendances - laissé non configuré
[…]
Traitement des actions différées (« triggers ») pour bamfdaemon
(0.5.6+repack-1.1+b3) ...
Rebuilding /usr/share/applications/bamf-2.index...
Traitement des actions différées (« triggers ») pour desktop-file-utils
(0.28-1) ...
Traitement des actions différées (« triggers ») pour hicolor-icon-theme
(0.18-2) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.42-15) ...
ldconfig: /usr/local/lib/libSDL-1.2.so.0 is not a symbolic link

Traitement des actions différées (« triggers ») pour man-db (2.13.1-1) ...
Traitement des actions différées (« triggers ») pour shared-mime-info
(2.4-5+b3) ...
Traitement des actions différées (« triggers ») pour mailcap (3.76) ...
Des erreurs ont été rencontrées pendant l'exécution :
 linux-headers-7.0.3+deb14-amd64
 linux-image-7.0.3+deb14-amd64
 linux-headers-amd64
 linux-image-amd64
Erreur : Sub-process /usr/bin/dpkg returned an error code (1)

Yours,
nicolas
#1135362#18
Date:
2026-05-03 21:31:39 UTC
From:
To:
Same error here.
The log file /var/lib/dkms/nvidia-current/550.163.01/build/make.log contain
these messages:
----------------------------------
nvidia/nv-mmap.c: In function ‘nv_vma_enter_locked’:
nvidia/nv-mmap.c:844:24: error: ‘VMA_LOCK_OFFSET’ undeclared (first use in this
function); did you mean ‘VGA_CRTC_OFFSET’?
  844 |     NvU32 tgt_refcnt = VMA_LOCK_OFFSET;
      |                        ^~~~~~~~~~~~~~~
      |                        VGA_CRTC_OFFSET
nvidia/nv-mmap.c:844:24: note: each undeclared identifier is reported only once
for each function it appears in
nvidia/nv-mmap.c: In function ‘nv_vma_start_write’:
nvidia/nv-mmap.c:896:9: error: too many arguments to function
‘__is_vma_write_locked’; expected 1, have 2
  896 |     if (__is_vma_write_locked(vma, &mm_lock_seq))
      |         ^~~~~~~~~~~~~~~~~~~~~      ~~~~~~~~~~~~
In file included from /usr/src/linux-
headers-7.0.3+deb14-common/arch/x86/include/asm/uaccess.h:12,
                 from /usr/src/linux-
headers-7.0.3+deb14-common/include/linux/uaccess.h:13,
                 from /usr/src/linux-
headers-7.0.3+deb14-common/include/linux/sched/task.h:13,
                 from /usr/src/linux-
headers-7.0.3+deb14-common/include/linux/sched/signal.h:9,
                 from ././common/inc/nv-lock.h:35,
                 from ././common/inc/nv-linux.h:32,
                 from nvidia/nv-mmap.c:27:
/usr/src/linux-headers-7.0.3+deb14-common/include/linux/mmap_lock.h:282:20:
note: declared here
  282 | static inline bool __is_vma_write_locked(struct vm_area_struct *vma)
      |                    ^~~~~~~~~~~~~~~~~~~~~
# CC [M]  nvidia/i2c_nvswitch.o
-----------------------------------
#1135362#25
Date:
2026-05-07 18:39:28 UTC
From:
To:
I'm hitting this as well:

*****

nvidia/nv-mmap.c:905:42: error: ‘VMA_LOCK_OFFSET’ undeclared (first use in this function); did you mean ‘VGA_CRTC_OFFSET’?
  905 |         detached = refcount_sub_and_test(VMA_LOCK_OFFSET, &vma->vm_refcnt);
      |                                          ^~~~~~~~~~~~~~~
      |                                          VGA_CRTC_OFFSET
make[4]: *** [/usr/src/linux-headers-7.0.3+deb14-common/scripts/Makefile.build:294: nvidia/nv-mmap.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [/usr/src/linux-headers-7.0.3+deb14-common/Makefile:2129: .] Error 2
make[2]: *** [/usr/src/linux-headers-7.0.3+deb14-common/Makefile:260: __sub-make] Error 2
make[2]: Leaving directory '/var/lib/dkms/nvidia-current/550.163.01/build'
make[1]: *** [Makefile:260: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-7.0.3+deb14-common'
make: *** [Makefile:140: modules] Error 2

# exit code: 2

*****

FWIW, I found what appears to be the same problem discussed here:

https://github.com/NVIDIA/open-gpu-kernel-modules/issues/1113
and cf. here:

https://old.reddit.com/r/linuxquestions/comments/1sodpgh/i_cant_build_the_nvidia_580xxdkms_on_linux_kernel/`
#1135362#30
Date:
2026-05-08 06:50:33 UTC
From:
To:
Dear Maintainer,

I am experiencing this as well in my Debian sid system. I had a similar issue a
couple of weeks ago in a Proxmox host (running Debian trixie), as Proxmox
provides its own kernel and it was bumped to version 7.  Leveraging AI (Gemini
and Claude) I managed to obtain patches for the nvidia-kernel-dkms package in
trixie, so that it would compile for Proxmox's kernel 7. These compile and I
get the functionality, so for me it was "good enough" for my homelab, but I
would not be so bold as to presume they are the best patch possible. If these
patches can be useful to see the changes that were needed to make this work,
such as the ones below, I could upload the file under debian/patches that
applied to the trixie package allowed me to built it for Proxmox's kernel 7:

     - conftest.sh: detect NV_VM_AREA_STRUCT_HAS___VM_FLAGS, absence of
dma_map_ops.map_resource, void return of dma_fence_signal, and
drm_mode_config_funcs.fb_create format_info argument
     - nv-mm.h: handle vma->vm_flags cast for kernels without __vm_flags
     - nv-mmap.c: wrap VMA_LOCK_OFFSET and __is_vma_write_locked for 1-arg form
     - nv-time.h: compat shim for removed in_irq() macro
     - nv-dma.c: guard dma_map_ops.map_resource access
     - header-presence-tests.mk: add drm/drm_print.h detection
     - nvidia-drm-priv.h: include drm_print.h for DRM_ERROR/DRM_INFO/DRM_DEBUG
     - nvidia-dma-fence-helper.h: handle void dma_fence_signal return type
     - nvidia-drm-helper.h: use for_each_new_*_in_state iterators
     - nvidia-drm-drv.c, nvidia-drm-fb.c: handle fb_create format_info arg


Thanks,
Jonas.
#1135362#35
Date:
2026-05-10 06:17:17 UTC
From:
To:
Dear Jonas,

Thanks for this tantalising message!

Until the maintainer is able to provide a "proper" patch, would you be
able to share your patch?  The maintainer might well then be able to
check it and either approve or improve on it.

Best wishes,

   Julian
#1135362#40
Date:
2026-05-10 10:40:49 UTC
From:
To:
Dear maintainer.

Here is a hand-made patch which fixed the build problem on Debian testing.
It works for me, so it may be useful to others, but it's a crude work.

The attached patch contains:
- Linux7 changed VMA_LOCK_OFFSET, so I read a more recent release of the
  nvidia driver (v595) and extracted a fix from it.
- 3 changes of function prototypes were obvious.
- There was an error with awk/pahole, so I removed pahole's variables
  from the Makefile (IIRC, this breaks some debugging features).
  That part of the patch is clearly not suitable for a larger audience.

Regards,
--
François Gannaz
#1135362#45
Date:
2026-05-11 17:38:00 UTC
From:
To:
Hi Julian,

Please find attached the "consolidated" patch as "final-patch.patch) (I had
3-4 which I merged into one), in case it is useful. As I mentioned, I used
Claude Code to support this process, and iterated several times until a
working patch was produced.  (I also did the same using Gemini, but
Gemini's patch seems a little bit more messy, although it also "works"
(e.g. the module compiles).  I can share the patch produced with Gemini as
well for reference when I'm back home, although the one with Claude seemed
the cleanest.)

Thanks,
Jonas.


Jonás Andradas

GPG Fingerprint:  678F 7BD0 83C3 28CE 9E8F
                           3F7F 4D87 9996 E0C6 9372
#1135362#50
Date:
2026-05-11 18:30:20 UTC
From:
To:
These patches have some merit, but it would be better to get them from upstream as this is what seems to be done for prior issues, e.g.:

https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers/-/commit/54d4c40a63dad575bc5e907271b47b873c4a87af

Unfortunately README.source doesn't document the procedure to cherry-pick/backport upstream changes, not is there a Repository URL in the upstream metadata.

Kind Regards,

Bas
#1135362#55
Date:
2026-05-11 21:31:29 UTC
From:
To:
Hi Jonás,

Many thanks for this!

Best wishes,

   Julian
#1135362#60
Date:
2026-05-12 12:16:04 UTC
From:
To:
Hi Julian,

please find attached the patch that was created leveraging Gemini instead.
It addresses the same conflicts, but using slightly different approach.
Adding here just in case it's useful, not necesssarily as a
production-ready patch.

Thanks,
Jonas.
#1135362#65
Date:
2026-05-14 08:44:10 UTC
From:
To:
Thanks Jonas!

Best wishes,

   Julian
#1135362#70
Date:
2026-05-17 21:18:59 UTC
From:
To:
Dear Maintainer,

The problem persist even in version 7.0.7.

Thanks,

Valdinilson.
#1135362#75
Date:
2026-05-18 15:24:14 UTC
From:
To:
it appears that the latest git version of at least the open version of the
nvidia kernel module on github (595.71.05) is compatible with 7.0.x kernels.
Since usually the closed version is aligned, at least in terms of kernel
interfaces, this may be the case for that as well. Would it be feasible to
pull these versions (or a somewhat previous one known to be compatible with
new kernels) at least in experimental, even without letting get into sid or
testing? This would provide at least a partial working alternative to keep
kernel updates on hold for people depending on GPU offloading support on
nvidia.

Thanks, best regards
Giacomo
#1135362#80
Date:
2026-05-19 02:45:47 UTC
From:
To:
On Mon, 18 May 2026 17:24:14 +0200 (CEST) Giacomo Mulas <giacomo.mulas@inaf.it> wrote:

...

It turns out that it's actually quite easy to install Debian-packaged
versions of the latest drivers straight from upstream:

https://developer.nvidia.com/cuda-downloads
https://old.reddit.com/r/debian/comments/1jyzgrx/the_correct_way_to_install_newer_nvidia_drivers/

For Debian unstable on amd64, all I had to do was basically:

$ wget https://developer.download.nvidia.com/compute/cuda/repos/debian13/x86_64/cuda-keyring_1.1-1_all.deb
# dpkg -i /path/to/cuda-keyring_1.1-1_all.deb # this installs a keyring and adds a repository
# apt update && apt upgrade

and voila - 595.71.05 built fine against 7.0.7+deb14-amd64. I rebooted, and
now I'm successfully running 595.71.05 (I haven't yet tested extensively).
#1135362#85
Date:
2026-05-21 20:51:35 UTC
From:
To:
Note that this fix won't work for everyone as Nvidia dropped support for a
bunch of older GPUs with version 590. I used to use the Nvidia repo, but I
had to go back to the Debian repo after my GTX-1060 stopped working.

I can't find the official Nvidia notice about this but here's an article
about it:
https://www.tomshardware.com/tech-industry/geforce-590-driver-branch-is-the-first-without-feature-support-for-gtx-9-and-10-series-gpus-linux-release-marks-the-end-of-the-line-for-graphics-cards-that-defined-an-era

I used François Gannaz's patch on my sid system and that fixed my problem.
#1135362#90
Date:
2026-05-23 19:10:08 UTC
From:
To:
Is anbe OK? I can't find any sign of activity from him since March.
#1135362#95
Date:
2026-05-24 17:55:22 UTC
From:
To:
Dear Maintainer,

I followed these steps:
1.ran $ wget
https://developer.download.nvidia.com/compute/cuda/repos/debian13/x86_64/cuda-
keyring_1.1-1_all.deb
2. Then ran  dpkg -i /path/to/cuda-keyring_1.1-1_all.deb
3. Then ran apt update && apt upgrade
and it installed both just fine. HOWEVER the drivers are not recognized, if I
run
nvidia-smi    NVIDIA-SMI has failed because it couldn't communicate with the
NVIDIA driver. Make sure that the latest NVIDIA driver is installed and
running.
dpkg -l
rc  nvidia-alternative                    550.163.01-5
amd64        allows the selection of NVIDIA as GLX provider
ii  nvidia-driver                         595.71.05-1
amd64        NVIDIA metapackage
ii  nvidia-driver-cuda                    595.71.05-1
amd64        NVIDIA driver CUDA integration components
ii  nvidia-driver-libs:amd64              595.71.05-1
amd64        NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
ii  nvidia-egl-icd                        595.71.05-1
amd64        NVIDIA EGL installable client driver (ICD)
rc  nvidia-installer-cleanup              20240109+1
amd64        cleanup after driver installation with the nvidia-installer
rc  nvidia-kernel-common                  20240109+1
amd64        NVIDIA binary kernel module support files
ii  nvidia-kernel-dkms                    595.71.05-1
amd64        NVIDIA binary kernel module DKMS source
ii  nvidia-kernel-support                 595.71.05-1
amd64        NVIDIA binary kernel module support files
ii  nvidia-modprobe                       595.71.05-1
amd64        utility to load NVIDIA kernel modules and create device nodes
ii  nvidia-opencl-icd:amd64               595.71.05-1
amd64        NVIDIA OpenCL installable client driver (ICD)
ii  nvidia-persistenced                   595.71.05-1
amd64        daemon to maintain persistent software state in the NVIDIA driver
ii  nvidia-settings                       595.71.05-1
amd64        Tool for configuring the NVIDIA graphics driver
rc  nvidia-support                        20240109+1
amd64        NVIDIA binary graphics driver support files
ii  nvidia-vdpau-driver:amd64             595.71.05-1
amd64        Video Decode and Presentation API for Unix - NVIDIA driver
ii  nvidia-vulkan-icd:amd64               595.71.05-1
amd64        NVIDIA Vulkan installable client driver (ICD)
ii  nvidia-xconfig

lspci | grep VGA 
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080]
(rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce
GTX 1080] (rev a1)

To ensure DKMS and the nvidia driver installed I ran:
apt install nvidia-kernel-dkms nvidia-driver
nvidia-kernel-dkms is already the newest version (595.71.05-1).
nvidia-driver is already the newest version (595.71.05-1).
Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0

So it appears the driver was installed but isn't being recognised. Is there an
ETA when a working version will be available?
#1135362#100
Date:
2026-05-25 06:50:18 UTC
From:
To:
Hello,

I have an older card [GeForce GTX 1050 Ti] that is no longer supported
with the 590 and 595 drivers as was noted by Forrest Cahoon. The 580
series still does support these older cards (maybe yours is one). The
nVidia repo referenced above no longer has the 580 version drivers
available, but I found them referenced here:

https://developer.nvidia.com/datacenter-driver-580-downloads?target_os=Linux&target_arch=x86_64&Distribution=Debian&target_version=12&target_type=deb_local

This installs a local repo on your machine containing the 580.159.04
series drivers and userspace libraries that can then be
installed/upgraded by apt.

#Installation Instructions:
wget https://developer.download.nvidia.com/compute/nvidia-driver/580.159.04/local_installers/nvidia-driver-local-repo-debian12-580.159.04_1.0-1_amd64.deb
sudo dpkg -i nvidia-driver-local-repo-debian12-580.159.04_1.0-1_amd64.deb
sudo cp /var/nvidia-driver-local-repo-debian12-580.159.04/nvidia-driver-*-keyring.gpg
/usr/share/keyrings/
sudo apt-get update

#NVIDIA Driver Instructions (choose one option)
#To install the open kernel module flavor:
#sudo apt-get install -y nvidia-open-580
#To install the proprietary kernel module flavor:
sudo apt-get install -y cuda-drivers-580
#To switch between NVIDIA Driver kernel module flavors see here:
#https://docs.nvidia.com/datacenter/tesla/driver-installation-guide/#switching-between-driver-module-flavors

I had the main NVIDIA repo added at the time (as you do), I tested
this and needed to pin the nvidia-driver and all relevant dependencies
to 580.159.04-1, which you are probably going to need to do anyway if
your card is no longer supported from 590 onward. I have attached the
pin files for your convenience (the amd64 one I built out by hand, the
i386 version uses wildcards once I knew what all the deps were -
sorry, I was tired).

With the 580 repo package and pins set up, 'sudo apt-get install -y
cuda-drivers-580' ran normally and set up the 580 driver DKMS for all
installed kernels, including the 7.0.x versions I had installed. I saw
somewhere the 580 driver was updated against linux 7.1.x at least.

$ apt list --installed | grep -i nvidia
firmware-nvidia-graphics/unstable,unstable,now 20260410-1 all [installed]
firmware-nvidia-gsp/unknown,now 580.159.04-1 amd64 [installed,automatic]
libegl-nvidia0/unknown,now 580.159.04-1 amd64 [installed,automatic]
libegl-nvidia0/unknown,now 580.159.04-1 i386 [installed,automatic]
libgles-nvidia1/unknown,now 580.159.04-1 amd64 [installed,automatic]
libgles-nvidia1/unknown,now 580.159.04-1 i386 [installed,automatic]
libgles-nvidia2/unknown,now 580.159.04-1 amd64 [installed,automatic]
libgles-nvidia2/unknown,now 580.159.04-1 i386 [installed,automatic]
libglx-nvidia0/unknown,now 580.159.04-1 amd64 [installed,automatic]
libglx-nvidia0/unknown,now 580.159.04-1 i386 [installed,automatic]
libnvidia-allocator1/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-allocator1/unknown,now 580.159.04-1 i386 [installed,automatic]
libnvidia-api1/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-cfg1/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-egl-gbm1/unknown,now 1.1.3-1 amd64 [installed,automatic]
libnvidia-egl-gbm1/unknown,now 1.1.3-1 i386 [installed,automatic]
libnvidia-egl-wayland1/unknown,now 1:1.1.21-1 amd64 [installed,automatic]
libnvidia-egl-wayland1/unknown,now 1:1.1.21-1 i386 [installed,automatic]
libnvidia-egl-xcb1/unknown,now 1:1.0.5-1 amd64 [installed,automatic]
libnvidia-egl-xcb1/unknown,now 1:1.0.5-1 i386 [installed,automatic]
libnvidia-egl-xlib1/unknown,now 1:1.0.5-1 amd64 [installed,automatic]
libnvidia-egl-xlib1/unknown,now 1:1.0.5-1 i386 [installed,automatic]
libnvidia-eglcore/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-eglcore/unknown,now 580.159.04-1 i386 [installed,automatic]
libnvidia-encode1/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-fbc1/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-glcore/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-glcore/unknown,now 580.159.04-1 i386 [installed,automatic]
libnvidia-glvkspirv/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-glvkspirv/unknown,now 580.159.04-1 i386 [installed,automatic]
libnvidia-gpucomp/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-gpucomp/unknown,now 580.159.04-1 i386 [installed,automatic]
libnvidia-ml1/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-ml1/unknown,now 580.159.04-1 i386 [installed,automatic]
libnvidia-ngx1/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-nvvm4/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-nvvm704/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-opticalflow1/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-pkcs11-openssl3/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-present/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-ptxjitcompiler1/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-rtcore/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-sandboxutils/unknown,now 580.159.04-1 amd64 [installed,automatic]
libnvidia-vksc-core/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-driver-cuda/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-driver-libs/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-driver-libs/unknown,now 580.159.04-1 i386 [installed]
nvidia-driver-local-repo-debian12-580.159.04/now 1.0-1 amd64 [installed,local]
nvidia-driver/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-egl-icd/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-kernel-dkms/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-kernel-support/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-modprobe/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-opencl-icd/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-persistenced/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-settings/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-vdpau-driver/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-vulkan-icd/unknown,now 580.159.04-1 amd64 [installed,automatic]
nvidia-vulkan-icd/unknown,now 580.159.04-1 i386 [installed,automatic]
nvidia-xconfig/unknown,now 580.159.04-1 amd64 [installed,automatic]
xserver-xorg-video-nvidia/unknown,now 580.159.04-1 amd64 [installed,automatic]
$

$ uname -r
7.0.9+deb14-amd64

 nvidia-smi
Sun May 24 23:24:21 2026
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.159.04             Driver Version: 580.159.04
CUDA Version: 13.0     |
+-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A |
Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage |
GPU-Util  Compute M. |
|                                         |                        |
            MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce GTX 1050 Ti     On  |   00000000:01:00.0 Off |
               N/A |
| 30%   26C    P8            N/A  /   75W |     751MiB /   4096MiB |
   0%      Default |
|                                         |                        |
               N/A |
+-----------------------------------------+------------------------+----------------------+


Thanks,
Nathan
#1135362#105
Date:
2026-05-25 07:00:33 UTC
From:
To:
I remembered moments after I sent this that the repo contains a couple
of pinning debs you can just install before 'sudo apt-get install -y
cuda-drivers-580' to configure pinning for 580, but I didn't test it
at the time.

Thanks,
Nathan

On Mon, May 25, 2026 at 1:50 AM Nate McKay <natemckay+debianbugs@gmail.com> wrote:
#1135362#110
Date:
2026-05-29 15:33:35 UTC
From:
To:
Hi,

perhaps here is time to create/initialize transitions on new
kernels, as it is not first time when DKMS (not only nvidia) fails to
build with new one. I do not know, where to ask it, thus i add it to
this case.

As no experienced C man, i am mostly not able to selve that by self,
and i have trouble to setting older kernel to boot or to uninstall
new kernel, and many of its dependencies, as old kernel is often fully
removed.

Frmo my point of view, as DKMS modules are part of debian's repos, it
wants some coordination, to leave testing in usable state...

regards
#1135362#115
Date:
2026-06-01 07:28:27 UTC
From:
To:

while i feel your pain (and I'm eagerly waiting for an update of the
nvidia-kernel-dkms package myself), i'm afraid that not all dkms
packages are "part of Debian".
esp, things in the "non-free" and "contrib" sections are *not* part of
Debian.
and i'm pretty sure that packages in "non-free-firmware" are not
considered part of "Debian proper" as well.

as such, proprietary dkms modules *are* somewhat second-class citizens
in the DFSG world, and will probably not get the same amount of QA as
fully free software.
#1135362#122
Date:
2026-06-05 11:03:54 UTC
From:
To:
Dear Maintainer

Having installed kernel 7.0.10+deb14-amd64 on my somewhat old hardware...

Operating System: Debian GNU/Linux forky/sid
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 7.0.10+deb14-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4790 CPU @ 3.60GHz
Memory: 16 GiB of RAM (14.6 GiB usable)
Graphics Processor 1: NVIDIA GeForce GTX 1060 3GB
Graphics Processor 2: Intel® HD Graphics 4600
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B85M-HD3

...I thought I should upload a report with an updated make.log and
terminal output, in the hope that they may prove useful.

<Terminal output starts>

Processing triggers for nvidia-alternative (550.163.01-5)…
update-alternatives: updating alternative /usr/lib/nvidia/current
because link group nvidia has changed slave links
Setting up nvidia-kernel-dkms (550.163.01-5)…
Loading new nvidia-current/550.163.01 DKMS files...
Building for 7.0.10+deb14-amd64

Building initial module nvidia-current/550.163.01 for 7.0.10+deb14-amd64
Sign command: /lib/modules/7.0.10+deb14-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Certificate or key are missing, generating self signed certificate for
MOK...

Building module(s)...........(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j8 modules KERNEL_UNAME=7.0.10+deb14-amd64

Error! Bad return status for module build on kernel: 7.0.10+deb14-amd64
(x86_64)
Consult /var/lib/dkms/nvidia-current/550.163.01/build/make.log for more
information.
dpkg:error processing package nvidia-kernel-dkms (--configure):
old nvidia-kernel-dkms package postinst maintainer script subprocess
failed with exit status 10
dpkg:dependency problems prevent configuration of nvidia-driver:
nvidia-driver depends on nvidia-kernel-dkms (= 550.163.01-5) |
nvidia-kernel-550.163.01 | nvidia-open-kernel-550.163.01; however:
  Package nvidia-kernel-dkms is not configured yet.
  Package nvidia-kernel-550.163.01 is not installed.
  Package nvidia-kernel-dkms which provides nvidia-kernel-550.163.01 is
not configured yet.
  Package nvidia-open-kernel-550.163.01 is not installed.

dpkg:error processing package nvidia-driver (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.42-16)…
Processing triggers for initramfs-tools (0.151)…
update-initramfs: Generating /boot/initrd.img-7.0.10+deb14-amd64
Processing triggers for update-glx (1.2.2)…
Processing triggers for glx-alternative-nvidia (1.2.2)…
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx (glx)
in auto mode
Processing triggers for glx-alternative-mesa (1.2.2)…
Processing triggers for libc-bin (2.42-16)…
Processing triggers for initramfs-tools (0.151)…
update-initramfs: Generating /boot/initrd.img-7.0.10+deb14-amd64
Errors were encountered while processing:
nvidia-kernel-dkms
nvidia-driver
Error: Sub-process /usr/bin/dpkg returned an error code (1)

<Terminal output ends>

Please find attached make.log

Thank you
Gray
#1135362#127
Date:
2026-06-09 09:27:11 UTC
From:
To:
Hi

Firstly thank you very much for these instructions. I now have nvidia
580 installed and can use my nvidia gtx 1060 to game again.

I did have one glitch however. It seems that sddm tries to start before
the display is ready, which did not occur with the Noveau driver, so I
have to assume that the nvidia drivers are just a bit slower to load.

The fix I found is to force the sddm service to wait a bit:

sudo systemctl edit sddm.service

and add this in:

[Service]
ExecStartPre=/usr/bin/sleep 10

While I have no idea what the ramifications are of this, it got me back
into the GUI and I can see how the games run in Steam :)

Best wishes
Gray

On Mon, 25 May 2026 01:50:18 -0500 Nate McKay  <natemckay+debianbugs@gmail.com> wrote:
 > Hello,
 >
 > I have an older card [GeForce GTX 1050 Ti] that is no longer supported
 > with the 590 and 595 drivers as was noted by Forrest Cahoon. The 580
 > series still does support these older cards (maybe yours is one). The
 > nVidia repo referenced above no longer has the 580 version drivers
 > available, but I found them referenced here:
 >
 >
https://developer.nvidia.com/datacenter-driver-580-downloads?target_os=Linux&target_arch=x86_64&Distribution=Debian&target_version=12&target_type=deb_local
 >
 > This installs a local repo on your machine containing the 580.159.04
 > series drivers and userspace libraries that can then be
 > installed/upgraded by apt.
 >
 > #Installation Instructions:
 > wget
https://developer.download.nvidia.com/compute/nvidia-driver/580.159.04/local_installers/nvidia-driver-local-repo-debian12-580.159.04_1.0-1_amd64.deb
 > sudo dpkg -i nvidia-driver-local-repo-debian12-580.159.04_1.0-1_amd64.deb
 > sudo cp
/var/nvidia-driver-local-repo-debian12-580.159.04/nvidia-driver-*-keyring.gpg
 > /usr/share/keyrings/
 > sudo apt-get update
 >
 > #NVIDIA Driver Instructions (choose one option)
 > #To install the open kernel module flavor:
 > #sudo apt-get install -y nvidia-open-580
 > #To install the proprietary kernel module flavor:
 > sudo apt-get install -y cuda-drivers-580
 > #To switch between NVIDIA Driver kernel module flavors see here:
 >
#https://docs.nvidia.com/datacenter/tesla/driver-installation-guide/#switching-between-driver-module-flavors
 >
 > I had the main NVIDIA repo added at the time (as you do), I tested
 > this and needed to pin the nvidia-driver and all relevant dependencies
 > to 580.159.04-1, which you are probably going to need to do anyway if
 > your card is no longer supported from 590 onward. I have attached the
 > pin files for your convenience (the amd64 one I built out by hand, the
 > i386 version uses wildcards once I knew what all the deps were -
 > sorry, I was tired).
 >
 > With the 580 repo package and pins set up, 'sudo apt-get install -y
 > cuda-drivers-580' ran normally and set up the 580 driver DKMS for all
 > installed kernels, including the 7.0.x versions I had installed. I saw
 > somewhere the 580 driver was updated against linux 7.1.x at least.
 >
 > $ apt list --installed | grep -i nvidia
 > firmware-nvidia-graphics/unstable,unstable,now 20260410-1 all [installed]
 > firmware-nvidia-gsp/unknown,now 580.159.04-1 amd64 [installed,automatic]
 > libegl-nvidia0/unknown,now 580.159.04-1 amd64 [installed,automatic]
 > libegl-nvidia0/unknown,now 580.159.04-1 i386 [installed,automatic]
 > libgles-nvidia1/unknown,now 580.159.04-1 amd64 [installed,automatic]
 > libgles-nvidia1/unknown,now 580.159.04-1 i386 [installed,automatic]
 > libgles-nvidia2/unknown,now 580.159.04-1 amd64 [installed,automatic]
 > libgles-nvidia2/unknown,now 580.159.04-1 i386 [installed,automatic]
 > libglx-nvidia0/unknown,now 580.159.04-1 amd64 [installed,automatic]
 > libglx-nvidia0/unknown,now 580.159.04-1 i386 [installed,automatic]
 > libnvidia-allocator1/unknown,now 580.159.04-1 amd64 [installed,automatic]
 > libnvidia-allocator1/unknown,now 580.159.04-1 i386 [installed,automatic]
 > libnvidia-api1/unknown,now 580.159.04-1 amd64 [installed,automatic]
 > libnvidia-cfg1/unknown,now 580.159.04-1 amd64 [installed,automatic]
 > libnvidia-egl-gbm1/unknown,now 1.1.3-1 amd64 [installed,automatic]
 > libnvidia-egl-gbm1/unknown,now 1.1.3-1 i386 [installed,automatic]
 > libnvidia-egl-wayland1/unknown,now 1:1.1.21-1 amd64 [installed,automatic]
#1135362#136
Date:
2026-06-10 18:28:26 UTC
From:
To:
Hi,

I am also affected by this bug, and have backported patches from
upstream branch 595.

https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers/-/merge_requests/13

I would appreciate it if the nvidia-team could review and merge the MR.
Alternatively I could go ahead with an NMU upload to the DELAYED/7
queue if that helps.

Best
-Dominique
#1135362#141
Date:
2026-06-18 14:50:31 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1135362@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominique Belhachemi <domibel@debian.org> (supplier of updated nvidia-graphics-drivers package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 11 Jun 2026 08:33:08 -0400
Source: nvidia-graphics-drivers
Architecture: source
Version: 550.163.01-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers <pkg-nvidia-devel@lists.alioth.debian.org>
Changed-By: Dominique Belhachemi <domibel@debian.org>
Closes: 1135362
Changes:
 nvidia-graphics-drivers (550.163.01-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix kernel module build failures against Linux 7.0. (Closes: #1135362)
   * Backport VMA locking changes from 595.44.03: rename VMA_LOCK_OFFSET to
     VM_REFCNT_EXCLUDE_READERS_FLAG and add nv_is_vma_write_locked wrapper for
     the dropped mm_lock_seq argument.
   * Fix dma_fence_signal() and dma_fence_signal_locked() void return type for
     Linux 7.0.
   * Suppress PAHOLE awk shim when scripts/Makefile.btf is present: kernel 7.0
     replaced pahole-flags.sh with gen-btf.sh, which invokes $PAHOLE in shell
     context where the single-quoted awk program causes a parse error.
   * Backport MODULE_DESCRIPTION additions from 595.44.06, required by
     CONFIG_MODULE_ALLOW_MISSING_MODULE_DESCRIPTION=n in Forky.
Checksums-Sha1:
 4acf67e233dc70cee8c2cdba8b9bab35d26976a3 7310 nvidia-graphics-drivers_550.163.01-5.1.dsc
 c317986d9793d9d2c27ede2cd8d4cb030f8401d1 248320 nvidia-graphics-drivers_550.163.01-5.1.debian.tar.xz
 56bb75f2d4bab944db99c29a9a9699cb9cfd74c7 22976 nvidia-graphics-drivers_550.163.01-5.1_amd64.buildinfo
Checksums-Sha256:
 5514e522944e0eab82beb2ad558ffae3091a15ddecd43d79df4e1f8e0a372aa9 7310 nvidia-graphics-drivers_550.163.01-5.1.dsc
 8c18eec03de7a91247e18b7e846ced6e2c9876a9d948fc902cee387410c78575 248320 nvidia-graphics-drivers_550.163.01-5.1.debian.tar.xz
 402b0ce70de62dfb819ec456eb44f2a8f33a724c143c0750efedb226eab02d68 22976 nvidia-graphics-drivers_550.163.01-5.1_amd64.buildinfo
Files:
 a353860c6578a00b738af6ee049f519d 7310 non-free/libs optional nvidia-graphics-drivers_550.163.01-5.1.dsc
 6c43b7c76e21be0d98afef149dabb6bc 248320 non-free/libs optional nvidia-graphics-drivers_550.163.01-5.1.debian.tar.xz
 4f08d126fa90222d13294a0289d2d11b 22976 non-free/libs optional nvidia-graphics-drivers_550.163.01-5.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJHBAEBCgAxFiEE6kgtUJkuk2zr2l/SGbXmyGIZEAEFAmoqv0ETHGRvbWliZWxA
ZGViaWFuLm9yZwAKCRAZtebIYhkQAR5MEACEHjV6wFaNczuDZ7VW/txNvLA+95W5
NJEei+LotPoaDP3WMNTFUT6a9vra1zZ8aw8ivufyalzYtRAflVAB8BgDTGDLZ9tM
ffdE9TY/tgg52DeP5Il7/54B/WOO9U5uAixFT24Qxct5pnOPcUX1nDL2ir+o+tRc
NjRGkhUWvhqbqUAfEwSC2mUtkHU3dCx6cLCY1Wn/WR4YrlPmg/18VlcD0lhVHTya
P4tZm/JpPPoeXUhZHv+jGA1g3dX3wAxoSemc6Yddyw6M/UndXLGkURNuebcNfPF9
EtRh4Zye3bRlsBMtOkZu4+7esYH9yDpdo4yeKihiYOUqQ+hfW1ik5Sp99H9CDvV3
nVOBKGtNjoP6Kb9G2n/JLsK8TPTNllDb9FAvuUGRHV0LJBzQo7uMZNcPezdDSS31
LPaUMOd5tOl4UTvjWe+z06Sp8pswmxiCz/RX1X4srX2MLR9YraPCxBnJNM9dTLNv
NWQsLQ1RtcH9SeHV8hU4oliXCxKyU+SxyNeRkIdYw7FC1VIcOPwAqMlJrebSR9MB
ImHYklGbGgF547PwSFCZNXQgd/E/IMsfhn/cVNg1ooAShQ6jbjmlZxlh1244r9IL
tlqiVoDq25PTsXukpn4hc5OJSJXy2DN+i9gsT/KLHqxq3C7DioUCgI3DVtkLkvmW
Mpbj1gVnPGas6g==
=bWw5
-----END PGP SIGNATURE-----
#1135362#158
Date:
2026-06-19 11:57:43 UTC
From:
To:
Hi,
Yay, the bug is solved!
Thank you.
n.
#1135362#163
Date:
2026-06-19 19:54:41 UTC
From:
To:
Dear Maintainer,
Just to let you know, I can currently install the package but then if I
reboot then the computer has no GUI.
current information:
lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce
GTX 1080] (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce
GTX 1080] (rev a1)

uname -a
Linux debianTim 7.0.12+deb14.1-amd64 #1 SMP PREEMPT_DYNAMIC Debian
7.0.12-2 (2026-06-12) x86_64 GNU/Linux
#1135362#168
Date:
2026-06-26 09:59:47 UTC
From:
To:
Dear Maintainer

I was able to get nvidia fully installed on my hardware  - however I
found that using the latest kernel 7.0.12 results in a black screen and
no ability to go to change to the command line as my PC seems to lock up
using nvidia with that kernel.

I AM able to boot to a full KDE plasma GUI using the previous kernel.

My hardware - using 7.0.10 (7.0.12 was fine until I installed the nvidia
drivers):

Operating System: Debian GNU/Linux forky/sid
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 7.0.10+deb14-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4790 CPU @ 3.60GHz
Memory: 16 GiB of RAM (14.6 GiB usable)
Graphics Processor 1: NVIDIA GeForce GTX 1060 3GB
Graphics Processor 2: Intel® HD Graphics 4600
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B85M-HD3

Please suggest how I can supply more info to help with this.

Best wishes
Gray