Comment 21 for bug 576648

Revision history for this message
dino99 (9d9) wrote :

Cant says that nvidia cant build with actual kernel as the report title says, but my issues are so close:

it's on Precise i386 with 8500gt & 290 driver from edgers ppa:
oem@oem-desktop:~$ dpkg-query -l | grep nvidia
ii nvidia-common 1:0.2.36 Find obsolete NVIDIA drivers
ii nvidia-current 290.10-0ubuntu1~xedgers~precise1 NVIDIA binary Xorg driver, kernel module and VDPAU library
ii nvidia-settings 290.06-0ubuntu1~xedgers~precise1 Tool of configuring the NVIDIA graphics driver

The problem is:
jockey-gtk dont find driver at all (empty list)
purging then reinstalling nvidia*/jockey* dont show warning/error during installation.

but /var/log/jockey.log warn first with:
Could not open DriverDB cache /var/cache/jockey/driverdb-OpenPrintingDriverDB.cache: [Errno 2] No such file or directory: '/var/cache/jockey/driverdb-OpenPrintingDriverDB.cache'

so i've created an empty /var/cache/jockey/driverdb-OpenPrintingDriverDB.cache, then it seems to help (see the log attached)

Trying to find how jockey-gtk works, i'm surprised to find:
- /usr/share/jockey/modaliases/disable-upstream-nvidia:
   # the nvidia modules have catch-all modaliases, which is wrong; kill
  # them off here, and use the linux-restricted-modules overrides files
  # instead (which are evaluated later than this file)
     reset nvidia
     reset nvidia_new
    reset nvidia_legacy
 The first thing to note is: linux-restricted-modules has been removed from archives since kernel 2.6.24 (ubuntuupdates: tim Gardner) and is only found for old distro via ppa (canonical-kernel-team, ...). So what's going on with this outdated settings ?
- some weaks ago jockey-gtk was having nvidia-current "activated & in use" but proposing oldish drivers (173, current-update) as dh-modaliases was not applied. Now its even worst as it dont find driver at all.

This actual missing "linux-restricted-modules" needs jockey/nvidia/dh-modaliases to be cleaned and updated.