nVidia Driver Must Be Loaded Manually

Bug #474300 reported by wbee on 2009-11-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Undecided
Unassigned

Bug Description

I'm using 9.10,86,32b,updated maybe twenty minutes ago.

My Nvidia driver is 185.18.36.

When I boot up the computer,it does not apply the driver. When I go System/Administration/Nvidia X Server Settings,the gamma that I set load when I enter nVidia Server Settings.

(I know this is not directly firefox related,but the "report a problem" loaded the title.)

If this is a bug,it's not earth shattering but I thought I'd report it so someone can look at it the next time they are in there anyway.

-----------

Thank you.

ProblemType: Bug
Architecture: i386
Date: Wed Nov 4 10:23:37 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.5.4+nobinonly-0ubuntu0.9.10.1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: firefox-3.5
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:1974): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1974): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2086): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2075): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

wbee (ebrid001) wrote :
Philip Muškovac (yofel) on 2009-11-05
affects: ubuntu → nvidia-graphics-drivers-180 (Ubuntu)
Bryce Harrington (bryce) wrote :

Sorry, I am not understanding the problem description exactly, could you clarify about what went wrong? I'm not sure what you mean by "apply the driver".

Also, there aren't the usual X files attached to this bug report which could help in diagnosing it. Please run 'apport-collect 474300' which should provide these files.

As well, my vague guess at this point is that the driver failed to build properly. In case this is true, could you please find and attach your build log that shows this issue? The file will be found someplace like:

 /var/lib/dkms/nvidia/185.18.36/build/make.log

The numbered directory may be different depending on what version you have installed, but if you poke around it should be somewhere like that.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: New → Incomplete

Architecture: i386
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gateway EMACHINES
NonfreeKernelModules: nvidia
Package: nvidia-graphics-drivers-180 (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=2317229f-9cf8-4bdb-b419-fafa4a62c0be ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/23/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080012
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7207G
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: 100
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd12/23/2005:svnGateway:pnEMACHINES:pvr100:rvnTobefilledbyO.E.M.:rnMS-7207G:rvr100:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: EMACHINES
dmi.product.version: 100
dmi.sys.vendor: Gateway
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

wbee (ebrid001) wrote : BootDmesg.txt
wbee (ebrid001) wrote : Lspci.txt
wbee (ebrid001) wrote : UdevDb.txt
wbee (ebrid001) wrote : UdevLog.txt
wbee (ebrid001) wrote : XorgConf.txt
wbee (ebrid001) wrote : XorgLog.txt
wbee (ebrid001) wrote : Xrandr.txt
wbee (ebrid001) wrote : glxinfo.txt
wbee (ebrid001) wrote : xdpyinfo.txt
wbee (ebrid001) wrote : xkbcomp.txt
Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
wbee (ebrid001) wrote :

Bryce,

System>Administration>nVidia X Server Settings. By "apply the driver",I mean left click on NVidia X Server Settings.

I sent the apport-collect 4/4300 with full access permission.

Yes,it IS driver 185.18.36,(the one in your example.). When I entered that in the terminal,it returned,"No such file or directory". The Nvidia X Server Settings shows the Nvidia Driver Version to be 185.18.36.

When I downloaded 9.10,I went to Hardware Drivers and downloaded the 185 driver. Upon reboot,it was shown to be activated,and the Nvidia Driver Version screen showed that 185.18.36 was the driver.

About five minutes ago,I opened Hardward Drivers and the driver was not activated. But the Nvidia X Server Settings showed it as the driver.

I'm going to send this,reboot,see if it is loaded properly,and then try the build log again.

-----

wbee (ebrid001) wrote :

Bryce,

I went to hardware drivers, reinstalled it, rebooted,and the hardware drivers face said it did not load,though the Nvidia X server settings said that it had.

So,I tried it again,and when it completed,before it rebooted,it resolved to a 173 driver(from the 185 setting). I rebooted and it was shown properly in both places,the nvidia x window and the hardware drivers window.

But the same thing happened. The driver did not load(or at least the gamma setting did not load)until I left clicked on nVidia X Server Settings.

Checking twice to make sure I got the driver number reading correct,I put into my terminal:

 /var/lib/dkms/nvidia/173.14.20/build/make.log

-----------

Thanks again.
and again,it returned "no such file or directory".

Bryce Harrington (bryce) wrote :

Try loading /var/lib/dkms/nvidia in your file browser and poke around to see if you can find any log files. Possibly I got the path wrong.

wbee (ebrid001) wrote :

Bryce,

I did as you suggested and there was nothing in my files.

I put a thread on the Ubuntu Forum asking for information to find the load file.

If I don't respond for a while,it will be because the paycheck calls.:-)

------

Thanks Again.

Bryce Harrington (bryce) wrote :

Hmm, that is a shame, it should be there. Well while you look for that can you also attach your /var/log/dpkg.log and /var/log/apt/term.log ?

wbee (ebrid001) wrote :

Bryce,

Let me tell you I'm in completely over my head with this.

I went into the terminal to find and attach the data you requested. Working as "superuser do",the first returned,"command not found" and the second returned, "no such file or directory".

I bumped the (unanswered) request on the Ubuntu Forum.

All that said,when I had the 185.XX.XX driver loaded,the "Hardware Drivers" screen showed it was NOT activated and in use. I'd load it,reboot,and it would be activated----until the next reboot. Curious,after I loaded and activated the 173 driver,I used the computer janitor,which listed the 185 driver---which means it was someplace on the hard drive.

The 173.XX.XX. driver shows to be loaded and when I boot on,when I left click "nVidia X Server Settings",it activates. I can live with that.

-------------

Thanks Again.

Bryce Harrington (bryce) wrote :

Okay, sorry you're having trouble locating the files. For what it's worth I think we have a good enough understanding of the general problem from other bug reports that we don't need to have you keep mucking with your system if you feel it is now at a stable enough point for your own use? If that's true, I guess we can close the bug at this point. I think we'll have things more robust for Lucid.

Brice,

Thank you.

Closing it works for me.

--- On Mon, 11/9/09, Bryce Harrington <email address hidden> wrote:

From: Bryce Harrington <email address hidden>
Subject: [Bug 474300] Re: nVidia Driver Must Be Loaded Manually
To: <email address hidden>
Date: Monday, November 9, 2009, 7:09 PM

Okay, sorry you're having trouble locating the files.  For what it's
worth I think we have a good enough understanding of the general problem
from other bug reports that we don't need to have you keep mucking with
your system if you feel it is now at a stable enough point for your own
use?  If that's true, I guess we can close the bug at this point.  I
think we'll have things more robust for Lucid.

--
nVidia Driver Must Be Loaded Manually
https://bugs.launchpad.net/bugs/474300
You received this bug notification because you are a direct subscriber
of the bug.

Status in “nvidia-graphics-drivers-180” package in Ubuntu: New

Bug description:
I'm using 9.10,86,32b,updated maybe twenty minutes ago.

My Nvidia driver is 185.18.36.

When I boot up the computer,it does not apply the driver. When I go System/Administration/Nvidia X Server Settings,the gamma that I set load when I enter nVidia Server Settings.

(I know this is not directly firefox related,but the "report a problem" loaded the title.)

If this is a bug,it's not earth shattering but I thought I'd report it so someone can look at it the next time they are in there anyway.

-----------

Thank you.

ProblemType: Bug
Architecture: i386
Date: Wed Nov  4 10:23:37 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.5.4+nobinonly-0ubuntu0.9.10.1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: firefox-3.5
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:1974): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1974): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2086): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2075): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

Bryce Harrington (bryce) on 2010-03-18
tags: added: karmic
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers