On 4/27/25 07:54, Russell Coker via pkg-nvidia-devel wrote:
Package: nvidia-kernel-dkms
Version: 535.216.03-3

-rw-r--r--. 1 root root 44804808 Apr 27 15:09 
/var/lib/dkms/nvidia-current/535.216.03/6.12.22-amd64/x86_64/module//nvidia-current.ko.xz

I'm getting the following errors from the postinst.  The above ls output shows
that the files in question exist.  The entire process produces modules that
can be loaded and which work, but fails the postinst.

The error about the module version not being newer would be because the
postinst has been run many times (every time I install packages) and compiles
the same files.  Maybe there should be a --force to address that case.

dkms fails to get the version from the module because of that weird modinfo 
failure
and then uses an empty version string (notice the double space in the error 
message
where the version should have been printed)

Building module(s).................... done.
Signing module /var/lib/dkms/nvidia-current/535.216.03/build/nvidia.ko
Signing module /var/lib/dkms/nvidia-current/535.216.03/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia-current/535.216.03/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia-current/535.216.03/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia-current/535.216.03/build/nvidia-peermem.ko
modinfo: ERROR: Module 
/var/lib/dkms/nvidia-current/535.216.03/6.12.22-amd64/x86_64/module//nvidia-current.ko.xz
 not found.
modinfo: ERROR: Module 
/var/lib/dkms/nvidia-current/535.216.03/6.12.22-amd64/x86_64/module//nvidia-current.ko.xz
 not found.

Haven't seen that one so far ...

Error! Module version  for nvidia-current.ko.xz
is not newer than what is already found in kernel 6.12.22-amd64 (535.216.03).
You may override by specifying --force.

Does
  modinfo 
/var/lib/dkms/nvidia-current/535.216.03/6.12.22-amd64/x86_64/module//nvidia-current.ko.xz
return sensible output?

What does
  dkms status -k 6.12.22-amd64 nvidia-current/535.216.03
report about the module?

Does
  dkms install -k 6.12.22-amd64 nvidia-current/535.216.03
work if the module has already been built in an earlier dkms run?
Maybe add --force


Andreas

Reply via email to