[ubuntu-x] (Update) Re: -nvidia upgrade issues

Martin Pitt martin.pitt at ubuntu.com
Sun Nov 8 16:03:04 GMT 2009

Alberto Milone [2009-11-07 13:18 +0100]:
> For this reason I think it makes sense to make sure that, when we install 
> nvidia (or any other driver which relies on DKMS), the module is built for the 
> current kernel (e.g. 2.6.28) and for the most recent one (e.g. 2.6.31). If the 
> current kernel and the most recent one are the same, then nothing changes and 
> we build only 1 module.

It could also be built for all kernels which already have an older
version of the same module built?

> I think I can fix this by making Jockey test the existence of the target 
> kernel module in 
> /var/lib/dkms/$DRIVER_NAME/$KERNEL_NAME-$ARCH/module/$KERNEL_MODULE.ko
> e.g. /var/lib/dkms/nvidia/kernel-2.6.31-14-generic-pae-i686/module/nvidia.ko
> This can be done either in each handler (e.g. nvidia, fglrx, etc.) or in a 
> more generic way (maybe in the KernelModuleHandler class?) so that each 
> handler can benefit from this check.

We could implement this in jockey, sure. I think it would be more
robust to do it in DKMS itself, since then people installing with
aptitude or another tool will benefit from this as well. But if it's
easier to do this from Jockey, it should cover a large majority of use
cases indeed.


Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

More information about the ubuntu-devel mailing list