ubuntu-x-swat team mailing list archive

[Daniel Quinlan <daniel@xxxxxxxxxxxxxxx>]

On Thu, Nov 5, 2009 at 6:10 PM, Bryce Harrington
<bryce@xxxxxxxxxxxxxxxxxxx> wrote:
> manjul, ok thanks for getting back to us.  We can focus this bug report
> on Daniel's version of the issue.
>
> Daniel, looking at your make.log it seems to be working successfully and
> it mentions it's building against 2.6.31, so it doesn't quite indicate
> where things failed...  Was that make.log what was there before, or was
> that from after when you ran dpkg-reconfigure?

it was after the dpkg-reconfigure.  looking at the output of
dkpkg-reconfigure it looks like it cleaned up whatever was there
previously. ie. there isn't a directory for the previous kernel

> It is starting to sound like perhaps there is a race condition.  I.e.,
> at time of install while you're upgrading to 2.6.31, the 2.6.28 kernel
> is installed so DKMS builds against that.  You reboot into 2.6.31 and X
> can't find an nvidia.ko for this version of the kernel.

yup, that's sounds right

> So, I think this might be a dupe of bug #438398.  Does that sound
> accurate?

no, because in that bug the build failed.  in my case the build
succeeded but for the 2.6.28 kernel.

if I'd booted into 2.6.28 things would've been fine.  but when 2.6.31
installed it became the default kernel.

is there a way for a new kernel install to trigger a rebuild or a
reconfigure of another package?

-- 
regards,
Daniel Quinlan

-- 
nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update from jaunty to karmic
https://bugs.launchpad.net/bugs/474917
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu.