Incorrect Nvidia driver installed by checking 3rd party box

[Quackers]

During 11-10 install on checking the 3rd party programs box the Nvidia 173 driver is installed.
However my graphics card uses the nvidia-current driver

Nov 21 19:42:19 ubuntu ubiquity: WARNING:root:Could not open DriverDB cache /var/cache/jockey/driverdb-OpenPrintingDriverDB.cache: [Errno 2] No such file or directory: '/var/cache/jockey/driverdb-OpenPrintingDriverDB.cache'
...
Nov 21 19:42:20 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_96 failed: ERROR: modinfo: could not find module nvidia_96
Nov 21 19:42:20 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_current failed: ERROR: modinfo: could not find module nvidia_current
Nov 21 19:42:20 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_173_updates failed: ERROR: modinfo: could not find module nvidia_173_updates
Nov 21 19:42:20 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_current_updates failed: ERROR: modinfo: could not find module nvidia_current_updates
Nov 21 19:42:20 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_173 failed: ERROR: modinfo: could not find module nvidia_173
Nov 21 19:42:20 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_96_updates failed: ERROR: modinfo: could not find module nvidia_96_updates
...
Nov 21 19:42:21 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_current failed: ERROR: modinfo: could not find module nvidia_current
Nov 21 19:42:21 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_173_updates failed: ERROR: modinfo: could not find module nvidia_173_updates
Nov 21 19:42:21 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_173 failed: ERROR: modinfo: could not find module nvidia_173
Nov 21 19:42:21 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_current_updates failed: ERROR: modinfo: could not find module nvidia_current_updates
Nov 21 19:42:21 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_current failed: ERROR: modinfo: could not find module nvidia_current
Nov 21 19:42:21 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_173_updates failed: ERROR: modinfo: could not find module nvidia_173_updates
Nov 21 19:42:21 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_173 failed: ERROR: modinfo: could not find module nvidia_173
Nov 21 19:42:21 ubuntu ubiquity: WARNING:root:modinfo for module nvidia_current_updates failed: ERROR: modinfo: could not find module nvidia_current_updates
Nov 21 19:42:30 ubuntu ubiquity: Selecting previously unselected package patch.
Nov 21 19:42:30 ubuntu ubiquity: (Reading database ...
Nov 21 19:42:30 ubuntu ubiquity: 138193 files and directories currently installed.)
...
Nov 21 19:42:32 ubuntu ubiquity: Selecting previously unselected package nvidia-173.
Nov 21 19:42:32 ubuntu ubiquity: Unpacking nvidia-173 (from .../nvidia-173_173.14.30-0ubuntu8_i386.deb) ...

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Mon Oct 17 14:05:44 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Quackers (quackers)]

This is not a 12-04 bug, it's a 11-10 installer bug

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[sojourner (itsmealso2)]

while the 173 driver is what is installed during installation , after install nvidia-current shows as recommended by additional drivers .

[oldfred (oldfred)]

The additional drivers now shows three entries. The installed 173, current and an updated which I gather is the current but will be updated?

Is this left over from alpha or beta as it seemed then the only driver was the 173 as there were issues with everything else?

[Quackers (quackers)]

Nothing yet?

[oldfred (oldfred)]

Just installed 12.04. Same issue but worse. Could not get to graphical screens at all. Alt-f2 gave me command line. Did updates Nov 10, 2011 and still would not fully boot.
Uninstalled 173, installed nvidia-current , finally got to gui, but it used default video as it then popped up saying I could install proprietary drivers.
fred@fred-Precise:~$ dpkg-query -l | grep nvidia
rc nvidia-173 173.14.30-0ubuntu8 NVIDIA binary Xorg driver, kernel module and VDPAU library
ii nvidia-common 1:0.2.35 Find obsolete NVIDIA drivers
ii nvidia-current 285.05.09-0ubuntu1 NVIDIA binary Xorg driver, kernel module and VDPAU library
ii nvidia-current-updates 285.05.09-0ubuntu1 NVIDIA binary Xorg driver, kernel module and VDPAU library
ii nvidia-settings 280.13-0ubuntu4 Tool of configuring the NVIDIA graphics driver
ii nvidia-settings-updates 280.13-0ubuntu1 Tool of configuring the NVIDIA graphics driver

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bryce Harrington (bryce)]

Was able to reproduce this bug myself (#893760) after a fresh install of Precise.

[Bryce Harrington (bryce)]

I'm setting the priority of the -nvidia bug task to High, although I think this isn't a fault in the driver itself, but rather an error in the algorithm selecting the binary package to be installed. (Ubiquity presumably??)

[Bryce Harrington (bryce)]

Here's the installer logs

[Bryce Harrington (bryce)]

Quackers, can you explain what you mean by "This is not a 12-04 bug, it's a 11-10 installer bug"? Are you reproducing this fresh installing Oneiric onto a system? I'm definitely seeing this on Precise but don't recall running into it for Oneiric install testing.

[Quackers (quackers)]

Yes, at the time I was doing a fresh install of 11-10 which was to be upgraded to 12-04 for testing.
I checked the box for the 3rd party drivers and after installation and rebooting I found that the 173 driver had been installed rather than the nvidia-current driver, which is the correct driver for my card.

[Bryce Harrington (bryce)]

Alright, well it definitely affects precise. I'll add an oneiric tag so once the issue is discovered it can be evaluated for possible SRU.

[Bryce Harrington (bryce)]

In digging through ubiquity, it looks like ubiquity hands off control to jockey via dbus, and it seems jockey runs into trouble. In the log it seems jockey is unable to find (or create?) it's cache, and so I wonder if that may be what's steering it off the cliff.

[Bryce Harrington (bryce)]

Bug #888273 has the same warning (against 11.10), although description is ambiguous if it was encountered under same conditions as this.

[Bryce Harrington (bryce)]

I have a sense that it is selecting -173 because it's the last thing in the list. However I'm not spotting in the code where exactly that list might be.

The error message is from get_modinfo() in detection.py.

[Quackers (quackers)]

Thanks for all the info Bryce, and the extra bugs. The problem seems to have gone largely un-noticed previously, possibly because most people don't check that box during installation? I know I don't usually.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Pitt (pitti)]

There seem to be two different issues here:

The -173 version does not build:
--------------------------------------------

Nov 21 19:42:40 ubuntu ubiquity: First Installation: checking all kernels...
Nov 21 19:42:40 ubuntu ubiquity: Building only for 3.1.0-2-generic
Nov 21 19:42:40 ubuntu ubiquity: Building for architecture i686
Nov 21 19:42:40 ubuntu ubiquity: Building initial module for 3.1.0-2-generic
Nov 21 19:42:49 ubuntu ubiquity: Error!
Nov 21 19:42:49 ubuntu ubiquity: Bad return status for module build on kernel: 3.1.0-2-generic (i686)
Nov 21 19:42:49 ubuntu ubiquity: Consult /var/lib/dkms/nvidia-173/173.14.30/build/make.log for more information.

This is most likely due to the new kernel, and shouldn't affect oneiric.

[Martin Pitt (pitti)]

As for the wrongly detected driver version, can someone with an affected NVidia system please attach /var/log/jockey.log after the failed install? It should be in the target system, i. e. after reboot, not in the live environment. It would also be helpful if you could give me the output of

  jockey-text --list

on that system. Thanks!

[Quackers (quackers)]

My oneiric install has now been upgraded to precise so presumably my logs won't help. In fact /var/log/jockey.log is empty.
I could install oneiric again and then post the outputs you request if you think that might help.

[Martin Pitt (pitti)]

Quackers [2011-11-25 16:49 -0000]:
> I could install oneiric again and then post the outputs you request
> if you think that might help.

Either from oneiric or a precise install would be fine. It should tell
me more about why it selects the 173 driver. Thanks!

[Quackers (quackers)]

Ok, re-installed OO again and the Nvidia 173 driver was installed again.
Output of jockey-text --list is [code]ootest@ootest-VGN-AR51SU:~$ jockey-text --list
xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
xorg:nvidia_173_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use)
xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
ootest@ootest-VGN-AR51SU:~$
[/code]
/var/log/jockey.log is [code]2011-11-25 17:26:38,073 DEBUG: updating <jockey.detection.LocalKernelModulesDriverDB instance at 0x2733b00>
2011-11-25 17:26:40,338 DEBUG: reading modalias file /lib/modules/3.0.0-12-generic/modules.alias
2011-11-25 17:26:40,585 DEBUG: reading modalias file /usr/share/jockey/modaliases/b43
2011-11-25 17:26:40,599 DEBUG: reading modalias file /usr/share/jockey/modaliases/disable-upstream-nvidia
2011-11-25 17:26:40,638 WARNING: Could not open DriverDB cache /var/cache/jockey/driverdb-OpenPrintingDriverDB.cache: [Errno 2] No such file or directory: '/var/cache/jockey/driverdb-OpenPrintingDriverDB.cache'
2011-11-25 17:26:40,680 DEBUG: loading custom handler /usr/share/jockey/handlers/fglrx.py
2011-11-25 17:26:40,780 WARNING: modinfo for module fglrx_updates failed: ERROR: modinfo: could not find module fglrx_updates

2011-11-25 17:26:40,786 DEBUG: Instantiated Handler subclass __builtin__.FglrxDriverUpdate from name FglrxDriverUpdate
2011-11-25 17:26:40,786 DEBUG: fglrx.available: falling back to default
2011-11-25 17:26:40,955 DEBUG: ATI/AMD proprietary FGLRX graphics driver (post-release updates) availability undetermined, adding to pool
2011-11-25 17:26:40,959 WARNING: modinfo for module fglrx failed: ERROR: modinfo: could not find module fglrx

2011-11-25 17:26:40,963 DEBUG: Instantiated Handler subclass __builtin__.FglrxDriver from name FglrxDriver
2011-11-25 17:26:40,964 DEBUG: fglrx.available: falling back to default
2011-11-25 17:26:41,084 DEBUG: ATI/AMD proprietary FGLRX graphics driver availability undetermined, adding to pool
2011-11-25 17:26:41,084 DEBUG: loading custom handler /usr/share/jockey/handlers/sl_modem.py
2011-11-25 17:26:41,136 DEBUG: Instantiated Handler subclass __builtin__.SlModem from name SlModem
2011-11-25 17:26:41,174 DEBUG: Software modem not available
2011-11-25 17:26:41,174 DEBUG: loading custom handler /usr/share/jockey/handlers/nvidia.py
2011-11-25 17:26:41,199 WARNING: modinfo for module nvidia_96 failed: ERROR: modinfo: could not find module nvidia_96

2011-11-25 17:26:41,210 DEBUG: Instantiated Handler subclass __builtin__.NvidiaDriver96 from name NvidiaDriver96
2011-11-25 17:26:41,210 DEBUG: nvidia.available: falling back to default
2011-11-25 17:26:41,297 DEBUG: NVIDIA accelerated graphics driver availability undetermined, adding to pool
2011-11-25 17:26:41,301 WARNING: modinfo for module nvidia_current failed: ERROR: modinfo: could not find module nvidia_current

2011-11-25 17:26:41,316 DEBUG: Instantiated Handler subclass __builtin__.NvidiaDriverCurrent from name NvidiaDr...

[Quackers (quackers)]

oops, didn't know code tags don't work here!

[Bryce Harrington (bryce)]

I've unduped bug #893760 to focus on the -173 build issue, which appears to be specific to precise. This bug report can focus on the issue with jockey picking -173 instead of -current, which appears to affect oneiric and precise.

[Martin Pitt (pitti)]

Can you please give me the output of this command (from a Terminal):

  python -c 'from NvidiaDetector.nvidiadetector import NvidiaDetection; print NvidiaDetection().selectDriver()'

Thanks!

[Quackers (quackers)]

That's interesting :-)
As requested

ootest@ootest-VGN-AR51SU:~$ python -c 'from NvidiaDetector.nvidiadetector import NvidiaDetection; print NvidiaDetection().selectDriver()'
nvidia-current

As you can see, the output says nvidia-current, even though the nvidia-settings screen clearly shows the 173.14.30 driver as being used.

[Martin Pitt (pitti)]

The logs still say that "/usr/lib/nvidia-173/ld.so.conf" is the current alternative (from NvidiaDetector.alternatives.MultiArchUtils), this seems to be the root cause of it. I'm afraid this requires an actual nvidia system to reproduce and debug. Alberto, can you see what's wrong here?

[Martin Pitt (pitti)]

Dropping rls-p-tracking. We currently only have one working driver anyway (-current), so this should not be a dealbreaker and can also be fixed in an SRU.

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Hi Martin,

you must be the bearer of knowledge, so why does this not get shared with less experienced but interessted users?

bug 948053 Comment #42, 5.5.2012 : Have asked to publish this issue at least in the release-notes.

If I don't find a hint there I've got to think everything will be going fine...

This might be bad for the reputation of Ubuntu itself

[Alberto Milone (albertomilone)]

Is this still a problem is Precise?

[dino99 (9d9)]

Jockey has been superseded by software-properties, which now handles
third-party driver configuration.