[EN] kernel 6.10.2-1-siduction-amd64: fails to built nvidia modul for nv470

[michaa7]

Hi towo,

the new kernel fails to built the nvidia modul for nv470. I dont't know how to filter /var/lib/dkms/nvidia-tesla-470/470.256.02/build/make.log for usefull  info as 

Code: [Select]

"cat /var/lib/dkms/nvidia-tesla-470/470.256.02/build/make.log | grep -i error" finds dozens of "-Werror" which seem unrelated.

Please let me know which info you need and how to filter  it.

Thanks for your work.

Code: [Select]

Building module:
Cleaning build area...
Building module(s)............(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=6.10.2-1-siduction-amd64
Error! Bad return status for module build on kernel: 6.10.2-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-tesla-470/470.256.02/build/make.log for more information.
dkms autoinstall on 6.10.2-1-siduction-amd64/x86_64 failed for nvidia-tesla-470(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.10.2-1-siduction-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.10.2-1-siduction-amd64.postinst line 11.

[Pip]

As you have probably done, I had to boot with the older kernel.

Some things that might be relevant are -

Code: [Select]

/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/os-mlock.c: In function ‘nv_follow_pfn’:
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/os-mlock.c:23:12: error: implicit declaration of function ‘follow_pfn’; did you mean ‘follow_pte’? [-Werror=implicit-function-declaration]
with lots of

Code: [Select]

warning: suggest braces around empty body in an ‘if’ statement [-Wempty-body]
Generally when these things have turned up before, it's just a question of staying with the old kernel for a while (for someone like myself who wouldn't have a clue how to fix things).

[ro_sid]

This kernel also fails building the (Siduction's) nvidia-current driver (or the driver with the kernel ).
The previous (6.11) kernel did not!

[towo]

I have uploaded a patched nvidia-470 driver to our fixes repo. Please test it, since i can't without owning nvidia hardware.

[Pip]

Thanks for trying.

As well as the -Wempty-body warnings, there's

Code: [Select]

/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv-mmap.c:300:5: warning: conflicting types for ‘nv_encode_caching’ due to enum/integer mismatch; have ‘int(pgprot_t *, NvU32,  nv_memory_type_t)’ {aka ‘int(struct pgprot *, unsigned int,  nv_memory_type_t)’} [-Wenum-int-mismatch]
  300 | int nv_encode_caching(
      |     ^~~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/nvidia-tesla-470/470.256.02/build/common/inc/nv-linux.h:1793:
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/common/inc/nv-proto.h:40:13: note: previous declaration of ‘nv_encode_caching’ with type ‘int(pgprot_t *, NvU32,  NvU32)’ {aka ‘int(struct pgprot *, unsigned int,  unsigned int)’}
   40 | int         nv_encode_caching           (pgprot_t *, NvU32, NvU32);
      |             ^~~~~~~~~~~~~~~~~

/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv.c:237:5: note: in expansion of macro ‘NV_KMALLOC’
  237 |     NV_KMALLOC(at, sizeof(nv_alloc_t));
      |     ^~~~~~~~~~
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv.c: At top level:
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv.c:739:12: warning: no previous prototype for ‘nvidia_init_module’ [-Wmissing-prototypes]
  739 | int __init nvidia_init_module(void)
      |            ^~~~~~~~~~~~~~~~~~


Code: [Select]

/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv-mmap.c: In function ‘nv_encode_caching’:
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv-mmap.c:349:16: warning: this statement may fall through [-Wimplicit-fallthrough=]
  349 |             if (NV_ALLOW_CACHING(memory_type))
      |                ^
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv-mmap.c:352:9: note: here
  352 |         default:
      |         ^~~~~~~
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv.c:867:6: warning: no previous prototype for ‘nvidia_exit_module’ [-Wmissing-prototypes]
  867 | void nvidia_exit_module(void)
      |      ^~~~~~~~~~~~~~~~~~


Code: [Select]

/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv.c:891:5: note: in expansion of macro ‘NV_KMALLOC’
  891 |     NV_KMALLOC(nvlfp, sizeof(nv_linux_file_private_t));
      |     ^~~~~~~~~~
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv.c: At top level:
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv.c:1270:23: warning: no previous prototype for ‘nv_get_num_dpaux_instances’ [-Wmissing-prototypes]
 1270 | NV_STATUS NV_API_CALL nv_get_num_dpaux_instances(nv_state_t *nv, NvU32 *num_instances)
      |                       ^~~~~~~~~~~~~~~~~~~~~~~~~~


Code: [Select]

/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/os-interface.c:276:7: warning: no previous prototype for ‘os_mem_copy_custom’ [-Wmissing-prototypes]
  276 | void *os_mem_copy_custom(
      |       ^~~~~~~~~~~~~~~~~~


Code: [Select]

/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv.c: At top level:
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv.c:3667:13: warning: no previous prototype for ‘nv_firmware_path’ [-Wmissing-prototypes]
 3667 | const char *nv_firmware_path(
      |             ^~~~~~~~~~~~~~~~


Code: [Select]

/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/os-mlock.c: In function ‘nv_follow_pfn’:
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/os-mlock.c:23:12: error: implicit declaration of function ‘follow_pfn’; did you mean ‘follow_pte’? [-Werror=implicit-function-declaration]
   23 |     return follow_pfn(vma, address, pfn);
      |            ^~~~~~~~~~
      |            follow_pte


Code: [Select]

/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv-procfs.c: At top level:
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia/nv-procfs.c:689:1: warning: no previous prototype for ‘exercise_error_forwarding_va’ [-Wmissing-prototypes]
  689 | exercise_error_forwarding_va(
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hope those mean something to you.

[michaa7]

Hi towo,

danke!

full-upgrade mit gefixtem nvidia-470-driver + modulbau + reboot in Graphikmodus funktionieren!

Super Arbeit, Danke wie immer für deinen Einsatz.

@ pip

did you update the driver? And BTW, I don't have the directory you mention:

Code: [Select]

# ls /var/lib/dkms/nvidia-tesla-470/470.256.02
6.10.2-1-siduction-amd64  6.9.11-amd64  source

[Pip]

I did a full-upgrade after an update. Do I need to get something from elsewhere too?

Code: [Select]

ls /var//lib/dkms/nvidia-tesla-470/470.256.02/
6.9.10-1-siduction-amd64/  build/  source@

[michaa7]

do you have the siduction fixes repo enabled?

Show the apt command and the error in the output

[ro_sid]

The (Siduction-)nvidia-current = nvidia-driver (550.100) driver now compiles with the kernel 6.9.11 as well as 6.10! @towo: Thank you very much.

[Pip]

Code: [Select]

grep fixes /etc/apt/sources.list.d/fixes.list | grep -v "^#"
 deb [ signed-by=/usr/share/keyrings/fixes-archive-keyring.gpg] http://ftp.uni-stuttgart.de/siduction/fixes unstable main contrib non-free non-free-firmware

Code: [Select]

Building module(s)......(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.10.2-1-siduction-amd64
Error! Bad return status for module build on kernel: 6.10.2-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-tesla-470/470.256.02/build/make.log for more information.
The kernel is built without module signing facility, modules won't be signed

Code: [Select]

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.10.2-1-siduction-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.10.2-1-siduction-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.10.2-1-siduction-amd64 (--configure):
 installed linux-headers-6.10.2-1-siduction-amd64 package post-installation script subprocess returned error exit status 11
Setting up network-manager (1.48.6-1) ...
dpkg: dependency problems prevent configuration of linux-image-siduction-amd64:
 linux-image-siduction-amd64 depends on linux-image-6.10.2-1-siduction-amd64 (= 6.10-2); however:
  Package linux-image-6.10.2-1-siduction-amd64 is not configured yet.

dpkg: error processing package linux-image-siduction-amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-headers-siduction-amd64:
 linux-headers-siduction-amd64 depends on linux-headers-6.10.2-1-siduction-amd64 (= 6.10-2); however:
  Package linux-headers-6.10.2-1-siduction-amd64 is not configured yet.

dpkg: error processing package linux-headers-siduction-amd64 (--configure):
 dependency problems - leaving unconfigured

[michaa7]

is the package linux-headers-6.10.2-1-siduction-amd64 installed?

Code: [Select]

# apt policy  linux-headers-6.10.2-1-siduction-amd64


[Pip]

Sure is.

Code: [Select]

apt policy  linux-headers-6.10.2-1-siduction-amd64
linux-headers-6.10.2-1-siduction-amd64:
  Installed: 6.10-2
  Candidate: 6.10-2
  Version table:
 *** 6.10-2 500
        500 http://ftp.uni-stuttgart.de/siduction/extra unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Code: [Select]

apt list --installed | grep linux-headers-6.10
linux-headers-6.10.2-1-siduction-amd64/siduction,now 6.10-2 amd64 [installed]

[towo]

apt policy nvidia-tesla-470-kernel-dkms

[Pip]

Thank you! Lots of nvidia-tesla-470 packages today an it's gone through without errors.