Public bug reported:

I am using Jaunty, with the 180.44-0ubuntu1 version of the nvidia-
glx-180 package.

I discovered that when activating the proprietary driver for nvidia on
my SLI system, that after restart gdm would not start and I was greeted
by the terminal.  After further investigation I discovered that xorg was
spitting out an error similar to this:

(EE)No devices detected

fatal server error:
no screens found

After searching the internet for a few hours I discovered that the error
could be remedied by explicitly defining the Busid of the primary video
card in the Device section of xorg.conf.  This is how my now working
xorg.conf looks:

Section "Device"
    Identifier      "Configured Video Device"
    Driver          "nvidia"
    Busid               "PCI:5:0:0"
    Option         "AllowGLXWithComposite" "1" 
    Option         "AddARGBGLXVisuals" "1"
    Option         "Coolbits" "1"
    Option         "TripleBuffer" "1"
    Option         "DamageEvents" "1"
    Option         "BackingStore" "1"
    Option         "InitialPixmapPlacement" "2"
EndSection

The only important line is the "Busid" line, this is what solved the
problem for me.  I feel as though this should be automatically set up,
as it can be jarring for some users to think they are improving their
graphics to suddenly be greeted with a text only command line after
restart.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: nvidia-glx-180 180.44-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (bui...@palmer) (gcc version 4.3.3 
(Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
SourcePackage: nvidia-graphics-drivers-180
Uname: Linux 2.6.28-11-generic i686

** Affects: nvidia-graphics-drivers-180 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386

-- 
nvidia proprietary driver causes xorg failure on SLI systems
https://bugs.launchpad.net/bugs/379546
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to