[zesty] dkms nvidia error with linux-headers-4.10.0-7

Bug #1663876 reported by brochard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dkms (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On Zesty, x64, I can't install the nvidia-378 driver with the new kernel 4.10.0-7 due to a dkms error.

...
ERROR (dkms apport): kernel package linux-headers-4.10.0-7-generic is not supported
Error! Bad return status for module build on kernel: 4.10.0-7-generic (x86_64)
Consult /var/lib/dkms/nvidia-378/378.09/build/make.log for more information.
...

And make.log as attachement

Regards

Revision history for this message
brochard (brochignac) wrote :
Revision history for this message
brochard (brochignac) wrote :

It was the same error with the kernel 4.10.0-6.
It works with the kernel 4.9.0-15

Revision history for this message
Leon (lehjr) wrote :

I tried 4.10.0-7 (4.10.0-7-generic #9~16.04.1-Ubuntu SMP Mon Feb 6 20:38:53 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux) a couple days ago, but but almost every symlink in in the source dir was broken, which will caused dkms modules to fail to build.

Revision history for this message
Leon (lehjr) wrote :

To clarify my above comment, the symlinks all point to "../linux-lts-zesty-headers-4.10.0-7/" locations that do not exist, so each and every symlink is in fact broken. :

 /usr/src/linux-headers-4.10.0-7-generic $ ls -l
total 1436
drwxr-xr-x 3 root root 4096 Feb 12 12:15 arch
lrwxrwxrwx 1 root root 41 Feb 6 17:14 block -> ../linux-lts-zesty-headers-4.10.0-7/block
lrwxrwxrwx 1 root root 41 Feb 6 17:14 certs -> ../linux-lts-zesty-headers-4.10.0-7/certs
lrwxrwxrwx 1 root root 42 Feb 6 17:14 crypto -> ../linux-lts-zesty-headers-4.10.0-7/crypto
lrwxrwxrwx 1 root root 49 Feb 6 17:14 Documentation -> ../linux-lts-zesty-headers-4.10.0-7/Documentation
lrwxrwxrwx 1 root root 43 Feb 6 17:14 drivers -> ../linux-lts-zesty-headers-4.10.0-7/drivers
lrwxrwxrwx 1 root root 44 Feb 6 17:14 firmware -> ../linux-lts-zesty-headers-4.10.0-7/firmware
lrwxrwxrwx 1 root root 38 Feb 6 17:14 fs -> ../linux-lts-zesty-headers-4.10.0-7/fs
drwxr-xr-x 4 root root 4096 Feb 12 12:15 include
lrwxrwxrwx 1 root root 40 Feb 6 17:14 init -> ../linux-lts-zesty-headers-4.10.0-7/init
lrwxrwxrwx 1 root root 39 Feb 6 17:14 ipc -> ../linux-lts-zesty-headers-4.10.0-7/ipc
lrwxrwxrwx 1 root root 42 Feb 6 17:14 Kbuild -> ../linux-lts-zesty-headers-4.10.0-7/Kbuild
lrwxrwxrwx 1 root root 43 Feb 6 17:14 Kconfig -> ../linux-lts-zesty-headers-4.10.0-7/Kconfig
drwxr-xr-x 2 root root 4096 Feb 12 12:15 kernel
lrwxrwxrwx 1 root root 39 Feb 6 17:14 lib -> ../linux-lts-zesty-headers-4.10.0-7/lib
lrwxrwxrwx 1 root root 44 Feb 6 17:14 Makefile -> ../linux-lts-zesty-headers-4.10.0-7/Makefile
lrwxrwxrwx 1 root root 38 Feb 6 17:14 mm -> ../linux-lts-zesty-headers-4.10.0-7/mm
-rw-r--r-- 1 root root 1442017 Feb 6 17:14 Module.symvers
lrwxrwxrwx 1 root root 39 Feb 6 17:14 net -> ../linux-lts-zesty-headers-4.10.0-7/net
lrwxrwxrwx 1 root root 43 Feb 6 17:14 samples -> ../linux-lts-zesty-headers-4.10.0-7/samples
drwxr-xr-x 6 root root 12288 Feb 12 12:15 scripts
lrwxrwxrwx 1 root root 44 Feb 6 17:14 security -> ../linux-lts-zesty-headers-4.10.0-7/security
lrwxrwxrwx 1 root root 41 Feb 6 17:14 sound -> ../linux-lts-zesty-headers-4.10.0-7/sound
lrwxrwxrwx 1 root root 39 Feb 6 17:14 spl -> ../linux-lts-zesty-headers-4.10.0-7/spl
lrwxrwxrwx 1 root root 41 Feb 6 17:14 tools -> ../linux-lts-zesty-headers-4.10.0-7/tools
lrwxrwxrwx 1 root root 42 Feb 6 17:14 ubuntu -> ../linux-lts-zesty-headers-4.10.0-7/ubuntu
lrwxrwxrwx 1 root root 39 Feb 6 17:14 usr -> ../linux-lts-zesty-headers-4.10.0-7/usr
lrwxrwxrwx 1 root root 40 Feb 6 17:14 virt -> ../linux-lts-zesty-headers-4.10.0-7/virt
lrwxrwxrwx 1 root root 39 Feb 6 17:14 zfs -> ../linux-lts-zesty-headers-4.10.0-7/zfs

Revision history for this message
brochard (brochignac) wrote :

I haven't this problem. I have the two directories :

/usr/src/linux-headers-4.10.0-7-generic/
/usr/src/linux-headers-4.10.0-7/

All the syslinks in /usr/src/linux-headers-4.10.0-7-generic/ point to /usr/src/linux-headers-4.10.0-7/

And the /var/lib/dkms/nvidia-378/378.09/build/make.log talks about :

/var/lib/dkms/nvidia-378/378.09/build/nvidia/nv-pat.c:213:14: error: ‘CPU_DOWN_FAILED’ undeclared (first use in this function)
         case CPU_DOWN_FAILED:
              ^~~~~~~~~~~~~~~
/var/lib/dkms/nvidia-378/378.09/build/nvidia/nv-pat.c:213:14: note: each undeclared identifier is reported only once for each function it appears in
/var/lib/dkms/nvidia-378/378.09/build/nvidia/nv-pat.c:220:14: error: ‘CPU_DOWN_PREPARE’ undeclared (first use in this function)
         case CPU_DOWN_PREPARE:
              ^~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/nvidia-378/378.09/build/nvidia/nv-pat.c:15:0:
/var/lib/dkms/nvidia-378/378.09/build/nvidia/nv-pat.c: In function ‘nv_init_pat_support’:
/var/lib/dkms/nvidia-378/378.09/build/common/inc/nv-linux.h:391:34: error: implicit declaration of function ‘register_cpu_notifier’ [-Werror=implicit-function-declaration]
 #define register_hotcpu_notifier register_cpu_notifier
                                  ^
/var/lib/dkms/nvidia-378/378.09/build/nvidia/nv-pat.c:258:17: note: in expansion of macro ‘register_hotcpu_notifier’
             if (register_hotcpu_notifier(&nv_hotcpu_nfb) != 0)
                 ^~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia-378/378.09/build/nvidia/nv-pat.c: In function ‘nv_teardown_pat_support’:
/var/lib/dkms/nvidia-378/378.09/build/common/inc/nv-linux.h:388:36: error: implicit declaration of function ‘unregister_cpu_notifier’ [-Werror=implicit-function-declaration]
 #define unregister_hotcpu_notifier unregister_cpu_notifier
                                    ^
/var/lib/dkms/nvidia-378/378.09/build/nvidia/nv-pat.c:283:9: note: in expansion of macro ‘unregister_hotcpu_notifier’
         unregister_hotcpu_notifier(&nv_hotcpu_nfb);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
scripts/Makefile.build:294 : la recette pour la cible « /var/lib/dkms/nvidia-378/378.09/build/nvidia/nv-pat.o » a échouée
make[2]: *** [/var/lib/dkms/nvidia-378/378.09/build/nvidia/nv-pat.o] Erreur 1
make[2]: *** Attente des tâches non terminées....
Makefile:1524 : la recette pour la cible « _module_/var/lib/dkms/nvidia-378/378.09/build » a échouée
make[1]: *** [_module_/var/lib/dkms/nvidia-378/378.09/build] Erreur 2
make[1] : on quitte le répertoire « /usr/src/linux-headers-4.10.0-7-generic »
Makefile:81 : la recette pour la cible « modules » a échouée
make: *** [modules] Erreur 2

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :

Feedback

zesty 64 bit with kernel 4.10.0-8 + nvidia-378.13

kernel installation was good, and next cold boot was normal: journalctl is clean (mostly)

Changed in dkms (Ubuntu):
status: New → Incomplete
Revision history for this message
brochard (brochignac) wrote :

I've just updated and I confirm, with the new kernel 4.10.0-8 + the update nvidia-378.13, it works.

Solved bug ?

dino99 (9d9)
Changed in dkms (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.