Bug#688567: nvidia-kernel-dkms: no dkms build or install - fails to link correct kernel header directory

Andreas Beckmann debian at abeckmann.de
Sun Sep 23 18:23:44 UTC 2012


Control: tag -1 moreinfo unreproducible

Hi Jeff,

On 2012-09-23 19:56, jeff godden wrote:
> Following a routine dpkg update/dist-upgrade the updated nvidia/304.48
> package was 'added' via dkms, but neither was "build" or "installed".
> This was apparently because the symbolic link from the active
> /lib/modules/<active-kernel-name>/build to
> /usr/src/linux-headers-<current-kernel> was replaced (by the install
> script?) to point to a previously installed *non-custom* kernel.  This
[...]
> The only consideration that I'm suggesting here is to correct whatever
> script might have replaced the correct symbolic link from the build
> target to the currently active kernel.

The nvidia packages don't touch anything in /lib/modules, so this bug
report ended at the wrong address ... Either some kernel package or dkms
is at fault here.

Is the link "owned" by the distribution-kernel-header package?
(dpkg -S /lib/modules/<active-kernel-name>/build)
In that case you might have a file conflict ...

For further investigation, try to reinstall the non-custom kernel header
package and see if the link is "updated".

If you find some culprit (and that's not the custom kernel, but some
package from Debian), please reassign the bug there. Otherwise I'll
close it in about a week.


Andreas

PS: I have no experience with custom kernels ...



More information about the pkg-nvidia-devel mailing list