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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1663876

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

Status in dkms package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1663876/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to