> Given that bug #1130057 (nvidia-kernel-dkms) seems to have been resolved, if > the already applied fix will solve the nvidia-open-kernel-dkms package it > might > be worth tagging it in this bug as well. If not, but applying the same > approach to address the issue would work, I am not sure if the fix could be > applied to nvidia-open-kernel-dkms as well.
The fix doesn't solve the build error for open-kernel unfortunately: Building initial module nvidia-current-open/550.163.01 for 6.19.8+deb14-amd64 Sign command: /lib/modules/6.19.8+deb14-amd64/build/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module(s)......(bad exit status: 2) Failed command: env NV_VERBOSE=1 make -j24 modules KERNEL_UNAME=6.19.8+deb14-amd64 Error! Bad return status for module build on kernel: 6.19.8+deb14-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current-open/550.163.01/build/make.log for more information. Errors are still the same: $ grep "error:" /var/lib/dkms/nvidia-current-open/550.163.01/build/make.log | sort -k 2 | uniq -f2 -c 1 nvidia/nv-dma.c:799:16: error: ‘const struct dma_map_ops’ has no member named ‘map_resource’ 24 ././common/inc/nv-time.h:145:9: error: implicit declaration of function ‘in_irq’ [-Wimplicit-function-declaration] 48 ././common/inc/nv-mm.h:315:25: error: ‘struct vm_area_struct’ has no member named ‘__vm_flags’; did you mean ‘vm_flags’? 1 nvidia/nv-pci.c:237:9: error: too few arguments to function ‘pci_resize_resource’; expected 4, have 3 -- Nicolas Le Cam
