Hello, I'm trying to upgrade my system to 6.19 kernel and keep getting this error:
Setting up linux-headers-6.19.5-1-siduction-amd64 (6.19-5)...
/etc/kernel/header_postinst.d/dkms:
The kernel is built without module signing facility, modules won't be signed
Autoinstall of module nvidia-current/580.95.05 for kernel 6.19.5-1-siduction-amd64 (x86_64)
Building module(s)......(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.19.5-1-siduction-amd64
Error! Bad return status for module build on kernel: 6.19.5-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/580.95.05/build/make.log for more information.
Autoinstall on 6.19.5-1-siduction-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
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.19.5-1-siduction-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.19.5-1-siduction-amd64 (--configure):
old linux-headers-6.19.5-1-siduction-amd64 package postinst maintainer script subprocess failed with exit status 1
Setting up linux-image-6.19.5-1-siduction-amd64 (6.19-5)...
/etc/kernel/postinst.d/dkms:
The kernel is built without module signing facility, modules won't be signed
Autoinstall of module nvidia-current/580.95.05 for kernel 6.19.5-1-siduction-amd64 (x86_64)
Building module(s)......(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.19.5-1-siduction-amd64
Error! Bad return status for module build on kernel: 6.19.5-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/580.95.05/build/make.log for more information.
Autoinstall on 6.19.5-1-siduction-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: error processing package linux-image-6.19.5-1-siduction-amd64 (--configure):
old linux-image-6.19.5-1-siduction-amd64 package postinst maintainer script subprocess failed with exit status 1
dpkg: dependency problems prevent configuration of linux-headers-siduction-amd64:
linux-headers-siduction-amd64 depends on linux-headers-6.19.5-1-siduction-amd64 (= 6.19-5); however:
Package linux-headers-6.19.5-1-siduction-amd64 is not configured yet.
dpkg: error processing package linux-headers-siduction-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-headers-6.19.5-1-siduction-amd64
linux-image-6.19.5-1-siduction-amd64
linux-headers-siduction-amd64
needrestart is being skipped since dpkg has failed
Error: Sub-process /usr/bin/dpkg returned an error code (1)
Could anyone advice me how to proceed?
Thank you.
I had a similar problem with nvidia-tesla-470. Debian put out new packages for it wich solved the problem.
So it seems help is on the way. Look out for new nvidia 580 driver packages with apt.
I wanted to start the update this morning, or rather I did start it, and I'm getting the same error. nVIDIA 580 is installed on my system, and no older packages from nVIDIA.
Same here:
Error! Bad return status for module build on kernel: 6.19.5-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/580.95.05/build/make.log for more information.
For "580"-drivers have a look into the "Software-Support" forum.
Especially at https://forum.siduction.org/index.php?topic=9910.msg78834#msg78834 (https://forum.siduction.org/index.php?topic=9910.msg78834#msg78834).
towo fixed it for us!
With regard to the tesla drivers:
If you replace the usr/src/nvidia-tesla-470-470.256.02/patches directory of siduction package
nvidia-tesla-470-kernel-dkms_470.256.02-8siduction1_amd64.deb
by directory usr/src/nvidia-tesla-470-470.256.02/patches of Debian package
nvidia-tesla-470-kernel-dkms_470.256.02-9_amd64.deb
everything works as expected. I guess this is the only difference between versions
470.256.02-8siduction1 and 470.256.02-9, so no wonder that it works.
Today's upgrade solved the issue. Thank you.