xorg: failed to load module "nvidia"

Bug #450493 reported by inneas
60
This bug affects 11 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

xorg crashes on boot when using nvidia-glx-185.
Nvidia-glx-173 is working fine.
Using an Geforce 8600M GT on a Dell Inspirion 1720.

Maybe the ubuntu-bug logs not useful cause the report was created running nvidia-173 (without problems).

xorg1.log:
(EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
(EE) NVIDIA: system's kernel log for additional error messages.
(II) UnloadModule: "nvidia"
(II) Unloading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(EE) Failed to load module "nvidia" (module-specific error, 0)
(EE) No drivers available.

Fatal server error:
no screens found

ProblemType: Bug
Architecture: i386
CheckboxSubmission: 4d2d0a0a0792a0b9fa942aa82fdaa6d9
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Tue Oct 13 18:07:11 2009
DistroRelease: Ubuntu 9.10
MachineType: Dell Inc. Inspiron 1720
NonfreeKernelModules: nvidia
Package: nvidia-glx-185 (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-13-generic root=UUID=e7d84e81-7c96-4c6c-a44c-ef9d34c7fc0c ro quiet splash
ProcEnviron:
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0-1ubuntu3
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu3
SourcePackage: nvidia-graphics-drivers-180
Uname: Linux 2.6.31-13-generic i686
XsessionErrors:
 (gnome-settings-daemon:2952): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2952): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:3046): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:3064): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:3291): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 02/03/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0UK437
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/03/2008:svnDellInc.:pnInspiron1720:pvr:rvnDellInc.:rn0UK437:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1720
dmi.sys.vendor: Dell Inc.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-13-generic

Revision history for this message
inneas (inneas) wrote :
inneas (inneas)
tags: added: ubuntu-9.10
Revision history for this message
Jack Deslippe (jdeslip) wrote :

I have the exact same problem on two machines I tried to load Karmic on today. After "installing" the 185 drivers in the hardware-drivers utility, I reboot into a blank screen. XOrg.0.log says:

(EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
(EE) NVIDIA: system's kernel log for additional error messages.
(II) UnloadModule: "nvidia"
(II) Unloading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(EE) Failed to load module "nvidia" (module-specific error, 0)
(EE) No drivers available.

The 173 drivers do infact work fine.

Revision history for this message
Jack Deslippe (jdeslip) wrote :

Also, I am still on kernel 2.6.31-11 so I don't think it is a -13 issue. Something else must have broken the nvidia driver.

Revision history for this message
Jack Deslippe (jdeslip) wrote :

One more pied of info: my in jockey.log - write at the end I have the following:

Setting up fakeroot (1.12.4ubuntu1) ...
update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode.

Setting up nvidia-185-kernel-source (185.18.36-0ubuntu5) ...
First Installation: checking all kernels...
Directory for kernel not found in /lib/modules
Adding Module to DKMS build system

Setting up nvidia-185-libvdpau (185.18.36-0ubuntu5) ...

Setting up nvidia-glx-185 (185.18.36-0ubuntu5) ...

Setting up nvidia-settings (180.25-0ubuntu1) ...

Setting up patch (2.5.9-5) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place

2009-10-13 13:37:47,669 ERROR:
Error! Invalid number of arguments passed.
Usage: add -m <module> -v <module-version>

2009-10-13 13:37:47,837 WARNING: modinfo for module nvidia failed: ERROR: modinfo: could not find module nvidia

2009-10-13 13:37:47,914 DEBUG: XorgDriverHandler device sections ({0: ['\tIdentifier\t"Default Device"\n', '\tDriver\t"nvidia"\n']})

It looks like jockey is not finishing correctly maybe?

Jack Deslippe (jdeslip)
Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: New → Confirmed
Revision history for this message
MFeif (matt-feifarek) wrote :

I have a clue (perhaps).

Looking in /lib/modules, there is NO file named nvidia.ko... which is present on my older, Jaunty system.

Surely the nvidia 185 driver deb file should install a kernel module?

Indeed, recovering all of the nvidia-185* files from /var/cache/apt/ and dpkg-deb -x 'ing them reveals no kernel module.

There are build files in the kernel-source, but they don't appear to be installed.

Perhaps a script isn't getting triggered in one of these packages?

Revision history for this message
Jack Deslippe (jdeslip) wrote :

the ko should be built by jockey or at boot by dkms, but I guess it is failing. I have filed a bug in jockey about the failure here: https://bugs.launchpad.net/jockey/+bug/450770 - but it may be a more general compilation problem and jockey is just a victim. The jockey.log I show above may explain why it is failing though:

2009-10-13 13:37:47,669 ERROR:
Error! Invalid number of arguments passed.
Usage: add -m <module> -v <module-version>

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nvidia-graphics-drivers-180 - 185.18.36-0ubuntu6

---------------
nvidia-graphics-drivers-180 (185.18.36-0ubuntu6) karmic; urgency=low

  * debian/nvidia-185-kernel-source.postinst:
    - There were bugs of undefined variables in the smart buildd detection
      scripts. These should be upstream DKMS anyway, so reference them
      from there (LP: #450493)

 -- Mario Limonciello <email address hidden> Tue, 13 Oct 2009 22:24:00 -0500

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
MFeif (matt-feifarek) wrote :

There is no such package called "nvidia-graphics-drivers-180"

Also, I'm experiencing this bug in nvidia-185-*

Trying to get somewhere with Jockey:

$ sudo jockey-text -l
(no output)
$ sudo jockey-text -u
(no output)
$ sudo jockey-text -c
(no output)

The jockey logs are filled with lines like this:

2009-10-13 23:57:31,742 WARNING: Invalid custom handler module /usr/share/jockey/handlers/nvidia.py
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/jockey/detection.py", line 897, in get_handlers
    execfile(mod, symb)
  File "/usr/share/jockey/handlers/nvidia.py", line 11, in <module>
    from NvidiaDetector.nvidiadetector import NvidiaDetection
ImportError: No module named NvidiaDetector.nvidiadetector
2009-10-13 23:57:31,752 WARNING: modinfo for module fglrx failed: ERROR: modinfo: could not find module fglrx

2009-10-13 23:57:31,891 WARNING: modinfo for module nvidia failed: ERROR: modinfo: could not find module nvidia

2009-10-13 23:57:31,892 WARNING: DriverID for module nvidia does not refer to a locally available module and does not specify free/description/package; ignoring

How do I get these packages to build kernel modules?

Revision history for this message
MFeif (matt-feifarek) wrote :

Sorry; I see "nvidia-graphics-drivers-180" is a nomenclature for Launchpad, not an actual package.

This fixed my problem:
dpkg-reconfigure nvidia-185-kernel-source

Now, Jockey can see the nvidia driver.

Revision history for this message
inneas (inneas) wrote :

Fix working.

But I think there is still a bug in jokey or jokey-gtk.
It seems that the installation of the package wasn't done correctly (error in logs from jokey https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/450493/comments/4 ) but there was no error-message when installing the driver with the jokey-gtk.
There should be at least a warning or better a warning and a option to reinstall the used driver.

In case of future bugs in a driver-package there will be the same problem.
I think users with no experience not able to boot to cli and edit xorg.conf to make the system bootable again.

Revision history for this message
inneas (inneas) wrote :

Made new bug-report for the missing warning from jockey-gtk.
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/451305

Revision history for this message
sudhir gaikwad (zissshh) wrote :
Download full text (5.4 KiB)

X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-28-server i686 Ubuntu
Current Operating System: Linux ubuntu 2.6.32-26-generic #47-Ubuntu SMP Wed Nov 17 15:59:05 UTC 2010 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-26-generic root=UUID=8d18815c-0cde-4d66-aa7f-1f8c728269cf ro quiet splash
Build Date: 10 November 2010 11:25:26AM
xorg-server 2:1.7.6-2ubuntu7.4 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.16.4
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Nov 27 08:52:16 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/usr/lib/X11/xorg.conf.d"
(==) No Layout section. Using the first Screen section.
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "<default monitor>"
(==) No device specified for screen "Default Screen".
 Using the first device section listed.
(**) | |-->Device "Default Device"
(==) No monitor specified for screen "Default Screen".
 Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
 Entry deleted from font path.
(==) FontPath set to:
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/100dpi/:unscaled,
 /usr/share/fonts/X11/75dpi/:unscaled,
 /usr/share/fonts/X11/Type1,
 /usr/share/fonts/X11/100dpi,
 /usr/share/fonts/X11/75dpi,
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
 built-ins
(==) ModulePath set to "/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
(II) The server relies on udev to provide the list of input devices.
 If no devices become available, reconfigure udev or disable AutoAddDevices.
(II) Loader magic: 0x81f1b20
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.4
 X.Org Video Driver: 6.0
 X.Org XInput driver : 7.0
 X.Org Server Extension : 2.0
(++) using VT number 7

(--) PCI: (0:0:1:3) 10de:03f4:1043:8234 nVidia Corporation MCP61 SMU rev 162, Mem @ 0x78000000/524288
(--) PCI:*(0:0:13:0) 10de:03d0:1043:8234 nVidia Corporation C61 [GeForce 6150SE nForce 430] rev 162, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xdd000000/16777216, BIOS @ 0x????????/131072
(II) Open ACPI successful (/var/run/acpid.socket)
(II) "extmod" will be loaded by default.
(II) "dbe" will be loaded by default.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/extra-modules/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
 compiled for 4.0.2, module version = 1.0.0
 Module class: X.Org Server Extension
(II) NVIDIA GLX Module 195.36.24 Thu Apr 22 10:38:29 PDT 2010
(II) Loading extension GLX
(II) LoadModule: "extmod"
(II) Loading /usr/lib...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.