[pkg-nvidia-devel] Bug#524078: Bug#524078: nvidia-glx tries to drag the wrong amd64 kernel in

[Lennart Sorensen]

On Tue, Apr 14, 2009 at 06:44:26PM +0100, Sheridan Hutchinson wrote:
> Package: nvidia-glx
> Version: 173.14.09-5
> Severity: important
> 
> Hello,
> 
> I'm using squeeze with the kernel package linux-image-amd64.  This drags 
> in linux-image-2.6-amd64, which in turn has installed the package 
> linux-image.2.6.26-2-amd64.
> 
> During installation of the 2.6.26-2 kernel a couple of days ago I 
> noticed it had to remove the nvidia-glx package to get it done.  I 
> agreed as I thought I could put it back after the new kernel was in and 
> running away nicely.
> 
> Unfortunately now whenever I try to install the nvidia-glx package 
> synaptic would require that linux-image-2.6.26-1-amd64 be installed in 
> order for the two nvidia-* packages to be able to install.
> 
> Is this intended because I'm back using the VESA driver at the moment?

Probably just means:

nvidia-glx depends on an nvidia-kernel-modules package

nvidia-kernel-modules are provided by the result of building the
nvidia-kernel-source package.  Sometimes this is available premade (as
is usually the case in stable), and sometimes it isn't (usually after
the kernel maintainers release an updated kernel).

I know that the nvidia modules were rebuilt in the last few days against
2.6.26-2 but might not have entered the archive yet, and almost certainly
would not have hit testing yet.

So you can either use module-assistant to build them yourself for your new
kernel, or you can wait for them to enter testing in a couple of weeks.

To use module assistant do:

m-a a-i -t nvidia-kernel -l 2.6.26-2-amd64

You should then have no problem installing nvidia-glx without trying
to pull in the 2.6.26-1-amd64 kernel (which is required by the lenny
prebuilt nvidia modules).

-- 
Len Sorensen