PCI:XX:YY:Z Requred In Intrepid xorg.conf

Bug #263768 reported by Jeremy LaCroix
2
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: xorg

I installed Kubuntu Intrepid a few days ago. I did not install gnome or any other packages that weren't required. After installing, I did not have an xserver. After a few days of fighting with it, I finally got it to work. I had to put the PCI:XX:YY:Z line in xorg.conf in order for my xserver to start working.

PCI:XX:YY:Z has NEVER been required in my xorg.conf in ANY version of Ubuntu ever released. In fact, until now, I had to remove that line in order for anything to work at all. Before adding that line, I tried "sudo dpkg-reconfigure xserver-xorg" and that did not fix it. I also tried vesa and nv for the driver and neither worked. Putting PCI:XX:YY:Z in my xorg.conf is the only thing that worked. Just to note I have an SLI system.

Here is my xorg.conf:
------------------------------------
Section "Module"
 Load "glx"
EndSection

Section "Device"
 Identifier "Device0"
 Driver "nvidia"
 VendorName "NVIDIA"
 BusID "PCI:03:00:0"
 Option "NoLogo" "True"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 Defaultdepth 24
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 screen 0 "Default Screen" 0 0
EndSection
----------------------------------------------------

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

don't paste stuff inline, use attachments.

description: updated
Revision history for this message
Alberto Milone (albertomilone) wrote :

The problem must affect Xorg rather than just the nvidia driver since the problem can be reproduced with vesa and nv too.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

ok then. Please _attach_ the full logfile _without_ the line in xorg.conf.

Changed in xorg:
status: New → Incomplete
Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote : Re: [Bug 263768] Re: PCI:XX:YY:Z Requred In Intrepid xorg.conf

Which log file?

Timo Aaltonen wrote:
> ok then. Please _attach_ the full logfile _without_ the line in
> xorg.conf.
>
> ** Changed in: xorg-server (Ubuntu)
> Sourcepackagename: xorg => xorg-server
> Status: New => Incomplete
>
>

Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote :

I'm going to assume you're referring to the Xorg.0.log file. I attached
it, if that's what you're looking for. The log file attached is when I
do not have the PCI:XX:YY:Z option enabled.

Timo Aaltonen wrote:
> ok then. Please _attach_ the full logfile _without_ the line in
> xorg.conf.
>
> ** Changed in: xorg-server (Ubuntu)
> Sourcepackagename: xorg => xorg-server
> Status: New => Incomplete
>
>

William Grant (wgrant)
Changed in xorg-server:
status: Incomplete → New
Revision history for this message
Lonnie Blansett (lonnie) wrote :

I have a system with 2 NVIDIA 8800s SLI'd and I got the same problem when I installed the kubuntu ibex amd64 release candidate. But when I added the "BusID" line X would start again. I have not had time to test out any of the SLI directives in the xorg.conf file yet but when I do I'll post the results of that too.

Revision history for this message
Jeremy LaCroix (jlacroix82-deactivatedaccount) wrote :

Thanks for the input. The problem is that it should at least work enough
to let X start. I hope this problem is fixed for the final release.
Unfortunately, I don't have SLI anymore to test it further, but I still
hope you keep me in the loop.

Lonnie Blansett wrote:
> I have a system with 2 NVIDIA 8800s SLI'd and I got the same problem
> when I installed the kubuntu ibex amd64 release candidate. But when I
> added the "BusID" line X would start again. I have not had time to test
> out any of the SLI directives in the xorg.conf file yet but when I do
> I'll post the results of that too.
>
>

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

Other bug subscribers

Bug attachments

Remote bug watches

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