<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>gHacks Technology News &#124; Latest Tech News, Software And Tutorials &#187; linux resolution</title> <atom:link href="http://www.ghacks.net/tag/linux-resolution/feed/" rel="self" type="application/rss+xml" /><link>http://www.ghacks.net</link> <description>A technology news blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description> <lastBuildDate>Sat, 11 Feb 2012 09:52:46 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/> <item><title>Get To Know Linux: Understanding xorg.conf</title><link>http://www.ghacks.net/2009/02/04/get-to-know-linux-understanding-xorgconf/</link> <comments>http://www.ghacks.net/2009/02/04/get-to-know-linux-understanding-xorgconf/#comments</comments> <pubDate>Wed, 04 Feb 2009 18:29:50 +0000</pubDate> <dc:creator>Jack Wallen</dc:creator> <category><![CDATA[Advice]]></category> <category><![CDATA[Linux]]></category> <category><![CDATA[Open Source]]></category> <category><![CDATA[Tutorials Advanced]]></category> <category><![CDATA[Tutorials Basic]]></category> <category><![CDATA[linux resolution]]></category> <category><![CDATA[linux video configuration]]></category> <category><![CDATA[X Windows configuration]]></category> <category><![CDATA[Xorg]]></category> <category><![CDATA[xorg.conf]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=9651</guid> <description><![CDATA[For most Linux users the xorg.conf file is one of those files that makes many Linux users cringe with fear upon the threat of having to configure. There is a reason for that, it&#8217;s complex. But when you have an understanding of the pieces that make up the whole puzzle, configuring X Windows becomes much, [...]]]></description> <content:encoded><![CDATA[<p>For most Linux users the <strong>xorg.conf</strong> file is one of those files that makes many Linux users cringe with fear upon the threat of having to configure. There is a reason for that, it&#8217;s complex. But when you have an understanding of the pieces that make up the whole puzzle, configuring X Windows becomes much, much easier.</p><p>But now the Linux community has distributions, such as Fedora 10, that do not default to using  an xorg.conf file. This is great news for many users. However, it&#8217;s bad news when, for some reason, X isn&#8217;t working or you have specific needs that the default isn&#8217;t meeting. With that in mind we&#8217;re going to break down the xorg.conf file so that you will be able to troubleshoot your X Windows configuration when something is wrong.</p><p><span
id="more-9651"></span><strong>The Basics</strong></p><p>The first thing you need to know is that xorg.conf (located typically in <strong>/etc/X11</strong>) is broken up into sections. Each section starts with the tag <strong>Section </strong>and ends with the tag <strong>EndSection</strong>. Each section can be broken into subsections as well. A subsections starts with the tag <strong>SubSection</strong> and ends with the tag <strong>EndSubSection</strong>. So a typical section with subsections contains the tags:<code><br
/> Section Name<br
/> Section Information<br
/> SubSection Name<br
/> SubSection information<br
/> EndSubSection<br
/> EndSection<br
/> </code><br
/> Of course you can&#8217;t just use random sections. There are specific sections to use. Those sections are:</p><ul><li>Files &#8211; pathnames for files such as fontpath</li><li>ServerFlags &#8211; global Xorg server options</li><li>Module &#8211; which modules to load</li><li>InputDevice &#8211; keyboard and pointer (mouse)</li><li>Device &#8211; video card description/information</li><li>Monitor &#8211; display device description</li><li>Modes &#8211; define video modes outside of Monitor section</li><li>Screen &#8211; binds a video adapter to a monitor</li><li>ServerLayout &#8211; binds one or more screens with one or more input devices</li><li>DRI &#8211; optional direct rendering infrastructure information</li><li>Vendor &#8211; vendor specific information</li></ul><p>Each section will have different information/options and is set up:</p><p><strong>Option Variable</strong></p><p>Let&#8217;s take a look at a sample section. We&#8217;ll examine a <strong>Device<em> </em></strong>section from a laptop. The section looks like:</p><p><code>Section "Device"<br
/> Identifier "device1"<br
/> VendorName "VIA Technologies, Inc."<br
/> BoardName "VIA Chrome9-based cards"<br
/> Driver "openchrome"<br
/> Option "DPMS"<br
/> Option "SWcursor"<br
/> Option "VBERestore" "true"<br
/> EndSection<br
/> </code><br
/> The above section configures a Via Chrome video card (often a tricky one to get running) using the <em>openchrome</em> driver. Here&#8217;s how this section breaks down:</p><ul><li>The identifier (labled &#8220;device1&#8243;) connects this section to Screen section with the <em>Device &#8220;device1&#8243; </em>option.</li><li>The VendorName and BoardName both come from the make and model of the video adapter.</li><li>The Driver is the driver the video card will use.</li><li>Option &#8220;DPMS&#8221; &#8211; this enables the Display Power Management System.</li><li>Option &#8220;SWcursor&#8221; &#8211; this enables the cursor to be drawn by software (as opposed to the HWcursor drawing by hard ware).</li><li>Option &#8220;VBERestore&#8221; &#8220;true&#8221; &#8211; allows a laptop screen to restore from suspend or hibernate.</li></ul><p>The lengthiest section of your xorg.conf file will most likely be your Screen section. This section will contain all of the subsections that contain the modes (resolutions) for your monitor. This section will start off like this:</p><p><code>Section "Screen"<br
/> Identifier "screen1"<br
/> Device "device1"<br
/> Monitor "monitor1"<br
/> DefaultColorDepth 24<br
/> </code><br
/> Notice how the above section references both a device and a monitor. These will refer to other sections in the xorg.conf file. This section also contains the <em>DefaultColorDepth</em> which will define the default color depth for your machine. In the case above the default is 24. Now, take a look below at the SubSections of this section:</p><p><code>Subsection "Display"<br
/> Depth 8<br
/> Modes "1440x900" "1280x800"<br
/> EndSubsection<br
/> Subsection "Display"<br
/> Depth 15<br
/> Modes "1440x900" "1280x800"<br
/> EndSubsection<br
/> Subsection "Display"<br
/> Depth 16<br
/> Modes "1440x900" "1280x800"<br
/> EndSubsection<br
/> Subsection "Display"<br
/> Depth 24<br
/> Modes "1440x900" "1280x800"<br
/> EndSubsection<br
/> EndSection<br
/> </code><br
/> As you can see there is a SubSection for four different color depths. Included in those subsections is the default 24. So when X reads the DefaultColorDepth option it will automatically attempt to set the modes configured in the <em>Depth 24</em> subsection. Also notice that each subsection contains two resolutions. X will attempt to set the first resolution (in the case above our first default is 1440&#215;900) and move on to the next if it can not set the first. Most likely X will be able to set the first.</p><p><strong>Final Thoughts</strong></p><p>This is only meant to be an introduction to the xorg.conf configuration file. As you might guess, xorg.conf, can get fairly complex. Add to the complexity numerous options available for each section and you have a valid case to make sure you RTFM (read the fine man page.) And the man page is an outstanding resource to find information on all of the available options. To read the man page issue the command <em>man xorg.conf</em> from the command line.</p><p>By having a solid understanding of the xorg.conf file you won&#8217;t have any problems fixing a fubar&#8217;d X installation or tweaking your xorg.conf file to get the most from your new video card.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2009/02/04/get-to-know-linux-understanding-xorgconf/feed/</wfw:commentRss> <slash:comments>9</slash:comments> </item> </channel> </rss>
