Bug 11172

Summary: rm /etc/X11/xorg.conf → Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
Product: xorg Reporter: Rafał Miłecki <zajec5>
Component: * OtherAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: low CC: bryce
Version: 7.2 (2007.02)   
Hardware: x86 (IA32)   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Log that shows why Xorg was not able to start.
none
Part of output of lspci -v
none
xorg.conf that makes Xorg start perfectly in case of my hardware none

Description Rafał Miłecki 2007-06-06 04:17:54 UTC
According to http://wiki.x.org/wiki/Releases/7.2?action=show my X.org 7.2 should start even if I have no "xorg.conf". So I removed my "xorg.conf" and tried "init 5". Xorg didn't start with reporting this error:

Fatal server error:
Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
Comment 1 Rafał Miłecki 2007-06-06 04:19:14 UTC
Created attachment 10204 [details]
Log that shows why Xorg was not able to start.
Comment 2 Rafał Miłecki 2007-06-06 04:20:12 UTC
Comment on attachment 10204 [details]
Log that shows why Xorg was not able to start.

Changing MIME Type to text/plain.
Comment 3 Rafał Miłecki 2007-06-06 04:22:54 UTC
Created attachment 10205 [details]
Part of output of lspci -v
Comment 4 Rafał Miłecki 2007-06-06 04:24:00 UTC
Created attachment 10206 [details]
xorg.conf that makes Xorg start perfectly in case of my hardware
Comment 5 Rafał Miłecki 2007-06-06 04:24:26 UTC
Comment on attachment 10206 [details]
xorg.conf that makes Xorg start perfectly in case of my hardware

Changing MIME Type to text/plain.
Comment 6 Michel Dänzer 2009-06-05 00:09:44 UTC
*** Bug 22089 has been marked as a duplicate of this bug. ***
Comment 7 Julien Cristau 2009-06-05 00:43:43 UTC

*** This bug has been marked as a duplicate of bug 21315 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.