Generate basic xorg.conf
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 12 of 12
  1. #1
    Join Date
    Aug 2012
    Location
    Israel
    Posts
    77
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Generate basic xorg.conf

    Hello,
    I'm trying to get a basic xorg.conf using
    Code:
    # Xorg -configure
    This results in:
    Code:
    X.Org X Server 1.12.0
    Release Date: 2012-03-04
    X Protocol Version 11, Revision 0
    Build Operating System: x86-01 2.6.32-220.4.1.el6.x86_64 
    Current Operating System: Linux wvxvw-desktop 3.5.2-3.fc17.x86_64 #1 SMP Tue Aug 21 19:06:52 UTC 2012 x86_64
    Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.5.2-3.fc17.x86_64 root=UUID=4ed248f4-6c97-4487-a339-b4f13b2df555 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
    Build Date: 14 March 2012  03:02:21PM
    Build ID: xorg-x11-server 1.12.0-2.fc17 
    Current version of pixman: 0.24.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: Sun Aug 26 21:23:29 2012
    List of video drivers:
    	intel
    	nouveau
    	ati
    	qxl
    	fglrx
    	cirrus
    	dummy
    	radeon
    	vmware
    	openchrome
    	ast
    	mga
    	fbdev
    	vesa
    (++) Using config file: "/root/xorg.conf.new"
    (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    Number of created screens does not match number of detected devices.
      Configuration failed.
    Server terminated with error (2). Closing log file.
    The error is kind of strange, but it is actually reasonable regarding the outistic nonsense that it writes to the xorg.conf.new...
    Is there any realiable way to obtain a simple basic xorg.conf other then the one mentioned above?

    Note, I'm running the configure command while X is not running, otherwise the configuration fails (why?).
    If you could just post here a most basic xorg.conf which would be suitable for a generic distro, that would be good enough too.

    Thanks in advance.

  2. #2
    Join Date
    Sep 2005
    Location
    Redneck Riviera
    Posts
    397
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    Try using
    Code:
    Xorg  :1 -configure
    as described in http://fedoraproject.org/wiki/How_to_create_xorg.conf

  3. #3
    Join Date
    Aug 2009
    Location
    Waldorf, Maryland
    Posts
    7,345
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    It fails while X is running because it has to access the video interface to determine what it is, the clock rates it supports, and the resolutions it supports - not to mention what the monitor definitions are. Doing this can cause the video board to reset some internal values or simultaneous access to the control registers will cause really strange errors to occur to the display.

    Current X servers do not need, nor should they have, an xorg.conf file. In extreme situations (usually caused by monitor errors) it cannot determine supported resolutions and will choose something basic. In these situations you can override that part of the default by putting sections in /etc/X11/xorg.conf.d.
    Last edited by jpollard; 26th August 2012 at 08:03 PM.

  4. #4
    Join Date
    Aug 2012
    Location
    Israel
    Posts
    77
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    @cazo Thanks, but it gives the exact same output, unfortunately, both the configuration file and the error message.

    @jpollard well, it's said to generate a basic configuration file - there's no knowledge of video card or anything like that is required... and, yes, that's exactly my case, Xorg is using wrong drivers (I want it to use mesa drivers for AMD card, but it uses something generic instead). Unfortunately, with AMD video cards just any situation seems to be an extreme case :/ Other than that, it's sad that instead of one indecypherable file of Xorg settings there's now more of the same kind spread around the PC... by the way, it actually wants the conf.d to be in /usr/share/X11, not /etc/X11, but that doesn't make it easier / any difference.
    Still, I reckon it will prefer the xorg.conf if it will exist in it's traditional location because the previous driver put it there and it worked. So, if you just happen to have one generic xorg.conf - that would be of a great help.

  5. #5
    Join Date
    Aug 2009
    Location
    Waldorf, Maryland
    Posts
    7,345
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    It looks in several places first (including the users home directory).

    It is actually simpler as the only thing needed in the file is that part used. I only have a definition for the keyboard (Section "InputClass") and that is mostly to enable the ctrl-alt-backspace to abort the X server.

    The xorg.conf.new that you got written should have all the sections in it. Just pick the section you want to change and put the file in /etc/X11/xorg.conf.d/nn-section-name.conf, where nn is a number (likely 01 as I expect you too only have a keyboard defined by default).

    You can test modifications with a "startx -- -config <file>" where the <file> is the xorg.conf.new file as modified.

    I suggest trying the unmodified file first just so you can see what it does.

  6. #6
    Join Date
    Aug 2012
    Location
    Israel
    Posts
    77
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    The xorg.conf.new belives that my monitor is some sort of a hypercube with most of its surfaces placed in the dimensions mere mortals cannot see... it is really weird what it has written there, unless there was some cardinal change in the settings style I'm not aware of (most likely), below is the complete text of that beast:

    Code:
    Section "ServerLayout"
    	Identifier     "X.org Configured"
    	Screen      0  "Screen0" 0 0
    	Screen      1  "Screen1" RightOf "Screen0"
    	InputDevice    "Mouse0" "CorePointer"
    	InputDevice    "Keyboard0" "CoreKeyboard"
    EndSection
    
    Section "Files"
    	ModulePath   "/usr/lib64/xorg/modules"
    	FontPath     "catalogue:/etc/X11/fontpath.d"
    	FontPath     "built-ins"
    EndSection
    
    Section "Module"
    	Load  "glx"
    	Load  "dbe"
    	Load  "record"
    	Load  "extmod"
    	Load  "dri2"
    	Load  "dri"
    EndSection
    
    Section "InputDevice"
    	Identifier  "Keyboard0"
    	Driver      "kbd"
    EndSection
    
    Section "InputDevice"
    	Identifier  "Mouse0"
    	Driver      "mouse"
    	Option	    "Protocol" "auto"
    	Option	    "Device" "/dev/input/mice"
    	Option	    "ZAxisMapping" "4 5 6 7"
    EndSection
    
    Section "Monitor"
    	Identifier   "Monitor0"
    	VendorName   "Monitor Vendor"
    	ModelName    "Monitor Model"
    EndSection
    
    Section "Monitor"
    	Identifier   "Monitor1"
    	VendorName   "Monitor Vendor"
    	ModelName    "Monitor Model"
    EndSection
    
    Section "Device"
            ### Available Driver options are:-
            ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
            ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
            ### <percent>: "<f>%"
            ### [arg]: arg optional
            #Option     "ShadowFB"           	# [<bool>]
            #Option     "Rotate"             	# <str>
            #Option     "fbdev"              	# <str>
            #Option     "debug"              	# [<bool>]
    	Identifier  "Card0"
    	Driver      "fbdev"
    	BusID       "PCI:3:0:0"
    EndSection
    
    Section "Device"
            ### Available Driver options are:-
            ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
            ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
            ### <percent>: "<f>%"
            ### [arg]: arg optional
            #Option     "ShadowFB"           	# [<bool>]
            #Option     "DefaultRefresh"     	# [<bool>]
            #Option     "ModeSetClearScreen" 	# [<bool>]
    	Identifier  "Card1"
    	Driver      "vesa"
    	BusID       "PCI:3:0:0"
    EndSection
    
    Section "Screen"
    	Identifier "Screen0"
    	Device     "Card0"
    	Monitor    "Monitor0"
    	SubSection "Display"
    		Viewport   0 0
    		Depth     1
    	EndSubSection
    	SubSection "Display"
    		Viewport   0 0
    		Depth     4
    	EndSubSection
    	SubSection "Display"
    		Viewport   0 0
    		Depth     8
    	EndSubSection
    	SubSection "Display"
    		Viewport   0 0
    		Depth     15
    	EndSubSection
    	SubSection "Display"
    		Viewport   0 0
    		Depth     16
    	EndSubSection
    	SubSection "Display"
    		Viewport   0 0
    		Depth     24
    	EndSubSection
    EndSection
    
    Section "Screen"
    	Identifier "Screen1"
    	Device     "Card1"
    	Monitor    "Monitor1"
    	SubSection "Display"
    		Viewport   0 0
    		Depth     1
    	EndSubSection
    	SubSection "Display"
    		Viewport   0 0
    		Depth     4
    	EndSubSection
    	SubSection "Display"
    		Viewport   0 0
    		Depth     8
    	EndSubSection
    	SubSection "Display"
    		Viewport   0 0
    		Depth     15
    	EndSubSection
    	SubSection "Display"
    		Viewport   0 0
    		Depth     16
    	EndSubSection
    	SubSection "Display"
    		Viewport   0 0
    		Depth     24
    	EndSubSection
    EndSection
    I don't have an unmodified file (i.e. the old xorg.conf has the fglrx-related info, which I don't need, but i'm not sure how much of it I need to remove or replace, and what would be the replacement. But, really, the one above looks even worse to me.

    By the way, I have more intput devices, then listed in the generated config (I also have a nostromo), but, for the obvious reason, I only have one card inserted in the third PCI slot :/ I only have one screen and one display by the way (or is this some sort of X-logic that requires the single display to be two displays at the time?)
    Last edited by wvxvw; 26th August 2012 at 09:34 PM.

  7. #7
    Join Date
    Aug 2009
    Location
    Waldorf, Maryland
    Posts
    7,345
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    The different displays are created because the videocard supports them. Only one will be active at a time, and that one is the 24 bit color. I think the others can be deleted without any problems.

    I believe (not sure) you are going to be trying to replace the "fbdev" driver...

    It has been a very long time since I've been that deep into the configuration file. The most I've really needed (in the last 10 years) was to specify the resolution because the laptop monitor didn't identify itself with an EDID string.

    Using putting the sections in /etc/X11/xorg.conf.d allows the system to dynamically add/remove devices (various pointers and such) without having to modify the configuration file. The specified configuration overrides what the Xserver will try to do - so specifying one prevents it from doing dynamic reconfiguration.

  8. #8
    Join Date
    Aug 2012
    Location
    Israel
    Posts
    77
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    Oook, below is what I've tried, and it didn't work, the error is this:
    Code:
    [    22.166] (II) LoadModule: "vesa"
    [    22.166] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
    [    22.196] (II) Module vesa: vendor="X.Org Foundation"
    [    22.196] 	compiled for 1.11.99.901, module version = 2.3.0
    [    22.196] 	Module class: X.Org Video Driver
    [    22.196] 	ABI class: X.Org Video Driver, version 12.0
    [    22.196] (II) VESA: driver for VESA chipsets: vesa
    [    22.196] (++) using VT number 1
    
    [    22.197] vesa: Ignoring device with a bound kernel driver
    [    22.197] (WW) Falling back to old probe method for vesa
    [    22.197] (II) UnloadModule: "vesa"
    [    22.197] (EE) Screen(s) found, but none have a usable configuration.
    [    22.197] 
    Fatal server error:
    [    22.197] no screens found
    The xorg.conf looks like this:
    Code:
    Section "ServerLayout"
    	Identifier     "X.org Configured"
    	Screen      0  "Screen0" 0 0
    	InputDevice    "Mouse0" "CorePointer"
    	InputDevice    "Keyboard0" "CoreKeyboard"
    EndSection
    
    Section "Files"
    	ModulePath   "/usr/lib64/xorg/modules"
    	FontPath     "catalogue:/etc/X11/fontpath.d"
    	FontPath     "built-ins"
    EndSection
    
    Section "Module"
    	Load  "glx"
    	Load  "dbe"
    	Load  "record"
    	Load  "extmod"
    	Load  "dri2"
    	Load  "dri"
    EndSection
    
    Section "InputDevice"
    	Identifier  "Keyboard0"
    	Driver      "kbd"
    EndSection
    
    Section "InputDevice"
    	Identifier  "Mouse0"
    	Driver      "mouse"
    	Option	    "Protocol" "auto"
    	Option	    "Device" "/dev/input/mice"
    	Option	    "ZAxisMapping" "4 5 6 7"
    EndSection
    
    Section "Monitor"
    	Identifier   "Monitor0"
    	VendorName   "Monitor Vendor"
    	ModelName    "Monitor Model"
    EndSection
    
    Section "Device"
            ### Available Driver options are:-
            ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
            ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
            ### <percent>: "<f>%"
            ### [arg]: arg optional
            #Option     "ShadowFB"           	# [<bool>]
            #Option     "DefaultRefresh"     	# [<bool>]
            #Option     "ModeSetClearScreen" 	# [<bool>]
    	Identifier  "Card1"
    	Driver      "vesa"
    	BusID       "PCI:3:0:0"
    EndSection
    
    Section "Screen"
    	Identifier "Screen0"
    	Device     "Card1"
    	Monitor    "Monitor0"
    	SubSection "Display"
    		Viewport   0 0
    		Depth     24
    	EndSubSection
    EndSection
    Why / what is wrong with the screen configuration?

  9. #9
    Join Date
    Aug 2009
    Location
    Waldorf, Maryland
    Posts
    7,345
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    Not screen - the vesa driver got disabled. Since that got disabled, the screen had no device associated (hence, unusable).

    It chains from the screen section via "Card1", which is defined in the device section.

    I'm not sure why it doesn't work, but you might try commenting out the BusID line.

  10. #10
    Join Date
    Aug 2012
    Location
    Israel
    Posts
    77
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    BusID is certainly correct, I inserted that card just a day ago, and it is indeed the third PCI slot on the mobo... but I'll try commenting it and we'll see.
    Actually, wait, vesa's drivers aren't in the /usr/lib64/xorg/modules ... interesting where are they :S ah, no, sorry, they are there.

    Nah, same exact error.

    OK, completely uninstalled mesa drivers, installed them again, and it worked, but now I have software GL rendering... why it should be me?!

    Code:
    [    24.668] (II) Loading sub module "fb"
    [    24.668] (II) LoadModule: "fb"
    [    24.668] (II) Loading /usr/lib64/xorg/modules/libfb.so
    [    24.668] (II) Module fb: vendor="X.Org Foundation"
    [    24.668] 	compiled for 1.12.0, module version = 1.0.0
    [    24.668] 	ABI class: X.Org ANSI C Emulation, version 0.4
    [    24.668] (**) FBDEV(1): using shadow framebuffer
    [    24.668] (II) Loading sub module "shadow"
    [    24.668] (II) LoadModule: "shadow"
    [    24.668] (II) Loading /usr/lib64/xorg/modules/libshadow.so
    [    24.668] (II) Module shadow: vendor="X.Org Foundation"
    [    24.668] 	compiled for 1.12.0, module version = 1.1.0
    [    24.668] 	ABI class: X.Org ANSI C Emulation, version 0.4
    [    24.668] (II) UnloadModule: "vesa"
    [    24.668] (II) UnloadModule: "radeon"
    [    24.668] (II) Unloading radeon
    [    24.668] (==) Depth 24 pixmap format is 32 bpp
    [    24.694] (==) FBDEV(0): Backing store disabled
    [    24.698] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
    repepeatet couple hunderds of times...
    [    24.698] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
    [    24.698] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
    [    24.698] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
    [    24.698] (==) FBDEV(0): DPMS enabled
    [    24.698] (==) RandR enabled
    [    24.698] (II) Initializing built-in extension Generic Event Extension
    [    24.698] (II) Initializing built-in extension SHAPE
    [    24.698] (II) Initializing built-in extension MIT-SHM
    [    24.698] (II) Initializing built-in extension XInputExtension
    [    24.698] (II) Initializing built-in extension XTEST
    [    24.698] (II) Initializing built-in extension BIG-REQUESTS
    [    24.698] (II) Initializing built-in extension SYNC
    [    24.698] (II) Initializing built-in extension XKEYBOARD
    [    24.698] (II) Initializing built-in extension XC-MISC
    [    24.698] (II) Initializing built-in extension XINERAMA
    [    24.698] (II) Initializing built-in extension XFIXES
    [    24.698] (II) Initializing built-in extension RENDER
    [    24.698] (II) Initializing built-in extension RANDR
    [    24.698] (II) Initializing built-in extension COMPOSITE
    [    24.698] (II) Initializing built-in extension DAMAGE
    [    24.700] (II) SELinux: Disabled by boolean
    [    24.705] (II) AIGLX: Screen 0 is not DRI2 capable
    [    24.705] (II) AIGLX: Screen 0 is not DRI capable
    Why is it even loading FBDEV? That repeating error seems to be related to font rendering, but I'm not sure, in any way, I just don't know what to do next
    Last edited by wvxvw; 26th August 2012 at 11:21 PM.

  11. #11
    Join Date
    May 2012
    Location
    Portland, Oregon
    Posts
    14
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    I dunno if this has been said, but reboot into text-only mode (append a 1 or "single" to your kernel options) try xorg-mkconfig

  12. #12
    Join Date
    Aug 2012
    Location
    Israel
    Posts
    77
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Generate basic xorg.conf

    I think that my problem is now more of a sort: "Why is X loading the framebuffer driver when it has Mesa drivers installed and the video card that supports hardware rendering / composing?" It doesn't look like any configuration file I would come up with will affect that (but if I'm wrong here - I'd be happy to be wrong).
    Is this some misconfiguration, or is this driver and the card are incompatible / the driver cannot handle the card well, or the driver and X are incompatible, and how to find that out.

    The relevant section of the log is this:
    Code:
    [    17.774] (II) LoadModule: "vesa"
    [    17.774] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
    [    17.783] (II) Module vesa: vendor="X.Org Foundation"
    [    17.783] 	compiled for 1.12.0, module version = 2.3.1
    [    17.783] 	Module class: X.Org Video Driver
    [    17.783] 	ABI class: X.Org Video Driver, version 12.0
    [    17.783] (II) LoadModule: "modesetting"
    [    17.784] (WW) Warning, couldn't open module modesetting
    [    17.784] (II) UnloadModule: "modesetting"
    [    17.784] (II) Unloading modesetting
    [    17.784] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [    17.784] (II) LoadModule: "fbdev"
    [    17.784] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
    [    17.796] (II) Module fbdev: vendor="X.Org Foundation"
    [    17.796] 	compiled for 1.11.99.901, module version = 0.4.2
    [    17.796] 	ABI class: X.Org Video Driver, version 12.0
    [    17.796] (II) RADEON: Driver for ATI Radeon chipsets:
    	ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
    	. . . a very long list of supported video cards . . .
    	CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, ARUBA, ARUBA, ARUBA,
    	ARUBA, ARUBA, ARUBA, ARUBA
    [    17.799] (II) VESA: driver for VESA chipsets: vesa
    [    17.799] (II) FBDEV: driver for framebuffer: fbdev
    [    17.799] (++) using VT number 1
    
    [    17.800] vesa: Ignoring device with a bound kernel driver
    [    17.800] (WW) Falling back to old probe method for vesa
    [    17.800] (II) Loading sub module "fbdevhw"
    [    17.800] (II) LoadModule: "fbdevhw"
    [    17.801] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
    What is modesetting and why is it needed, and why is it searched for is above me :/
    Last edited by wvxvw; 27th August 2012 at 11:23 AM.

Similar Threads

  1. Generate grub.conf file automatically
    By fred_m in forum Using Fedora
    Replies: 3
    Last Post: 17th November 2009, 12:55 AM
  2. Replies: 2
    Last Post: 19th April 2008, 01:02 PM
  3. Replies: 1
    Last Post: 8th January 2007, 07:02 AM
  4. Yikes no Xorg, .. need an xorg.conf
    By steve941 in forum Using Fedora
    Replies: 1
    Last Post: 14th April 2006, 05:27 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •