Bug#685617: Allow co-installation of nvidia-kernel-dkms and nvidia-kernel-legacy-173xx-dkms

[Andreas Beckmann]

On 2012-08-23 00:18, Gaudenz Steinlin wrote:
> Andreas Beckmann <debian at abeckmann.de> writes:
>> Switching between current and legacy is done by reconfiguring the nvidia
>> alternative (/usr/lib/nvidia/nvidia) - can't that be used by the module
>> load script to select the "right" module?

> In theory yes. But there are several problems:
> - plain alternatives are not possible because the files (the compiled
>   kernel modules) don't necesserily exist even if the package is

No, I didn't want to install alternatives for the kernel module, just
get the status of the alternative (update-alternatives --query nvidia)
to do the correct selection.

> (why not just select the best module if
>   we can).

because the module must match the xorg driver and libGL

> To be honest I did not look at the -source packages too closely. I'm not
> sure if they are still relevant.
They are not going away :-)

> Dkms is IMHO the far superior and easier alternative.
But not suitable for all applications ...

> But anyway the -source packages are already
> co-installable AFAICS.
The -source packages are co-installable, but the generated module
packages are not.

> I don't know if there is a good way to modify the
> build system so that the module is renamed. As I think the -source
> packages are mostly relevant for manual builds I'm not even sure if it's
> a good idea to do such a modification there.
Having the -dkms and -source package building different modules (or
naming them differently) is a bad idea.

> Agreed. Backports to wheezy would be cool though.

Planned.


Andreas