nvidia-173 (173.14.28-0ubuntu1) fails to build kernel module with kernels 2.6.35 and 2.6.36

[Dennis New]

Binary package hint: nvidia-173

nvidia-173 fails to build kernel module with kernels 2.6.35 and 2.6.35

With my recently updated Ubuntu 10.10, the nvidia-173 package fails to build the kernel module for the latest 2.6.35-24-generic kernel, and also for the newer 2.6.36-020636-generic. It does, however, build it for the older 2.6.32-24-generic kernel.

It seems to fail because: "the kernel source for this kernel does not seem to be installed."

Here is what it does when it works (w/ 2.6.32):
"
Removing all DKMS Modules
Done.
Unpacking replacement nvidia-173 ...
Processing triggers for man-db ...
Setting up nvidia-173 (173.14.28-0ubuntu1) ...
update-initramfs: deferring update (trigger activated)
update-initramfs: Generating /boot/initrd.img-2.6.32-24-generic
Loading new nvidia-173-173.14.28 DKMS files...
Building for 2.6.32-24-generic and 2.6.36-020636-generic
Building for architecture i686
Building initial module for 2.6.32-24-generic
Done.
nvidia-173.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/2.6.32-24-generic/updates/dkms/

depmod.........
DKMS: install Completed.
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Processing triggers for python-gmenu ...
Rebuilding /usr/share/applications/desktop.en_CA.utf8.cache...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.36-020636-generic
Processing triggers for python-support ...
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
"

Here is what it fails (w/ 2.6.35/6):
"
Removing all DKMS Modules
Done.
Unpacking replacement nvidia-173 ...
Processing triggers for man-db ...
Setting up nvidia-173 (173.14.28-0ubuntu1) ...
update-initramfs: deferring update (trigger activated)
update-initramfs: Generating /boot/initrd.img-2.6.35-24-generic
Loading new nvidia-173-173.14.28 DKMS files...
Building for 2.6.35-24-generic and 2.6.36-020636-generic
Building for architecture i686
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Processing triggers for python-gmenu ...
Rebuilding /usr/share/applications/desktop.en_CA.utf8.cache...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.36-020636-generic
Processing triggers for python-support ...
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
"

With the failed 2.6.35/2.6.36 attempts, this is the output for "find /var/lib/dkms/nvidia-173/": (it should be full of source files, etc. It's not.)
/var/lib/dkms/nvidia-173/
/var/lib/dkms/nvidia-173/173.14.28
/var/lib/dkms/nvidia-173/173.14.28/build
/var/lib/dkms/nvidia-173/173.14.28/source

So, why is the "kernel source" missing?

And, on a somewhat related note, why does each installation/reinstallation attempt of nvidia-173 "remove all DKMS Modules"? This is very annoying, since it doesn't allow us to boot into different kernels, without having to manually reinstall nvidia-173 each time.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 694200
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.