nvidia module only working after gdm restart

Bug #592032 reported by Fridtjof Busse
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I'm using the nvidia driver on lucid for a GT240. The driver installs fine, but on reboot Xorg complains about an unusable configuration and does not start:

(EE) Jun 10 08:11:08 NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the
(EE) Jun 10 08:11:08 NVIDIA(0): system's kernel log for additional error messages and
(EE) Jun 10 08:11:08 NVIDIA(0): consult the NVIDIA README for details.
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.

After switching to a tty and running "/etc/init.d/gdm restart" (the "restart X" option in the rescue X11 windows does not work), Xorg comes up just fine without any errors and nvidia works.
There are not nvidia-related errors in the kernel-log.
Is there some sort of race-condition between modules or an incomplete blacklist?

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.15-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Jun 10 08:12:41 2010
DkmsStatus:
 vboxdrv, 3.2.4, 2.6.32-22-generic, x86_64: installed
 nvidia-current, 195.36.15, 2.6.32-22-generic, x86_64: installed
 vboxnetflt, 3.2.4, 2.6.32-22-generic, x86_64: installed
 vboxnetadp, 3.2.4, 2.6.32-22-generic, x86_64: installed
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=3307bfc2-9593-47af-b6bc-cace6d2f23e6 ro quiet splash nomodeset
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-graphics-drivers
dmi.bios.date: 05/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.30
dmi.board.name: P55 Pro
dmi.board.vendor: ASRock
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.:bvrP2.30:bd05/11/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55Pro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-22-generic

Revision history for this message
Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount) wrote :

Creating a custom blacklist and updating the initrd solved the problem (I did not yet identify one specific module, so this might be more modules than necessary):

blacklist vga16fb
blacklist rivafb
blacklist nvidiafb

So it seems /etc/modprobe.d/nvidia-graphics-drivers.conf does not blacklist enough modules. My guess is that the framebuffer blocks the nvidia module from loading properly on the first try.

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

That version is no more supported; please open a new bug report if the actual archive found version also has the same issue.

Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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