/[gentoo]/xml/htdocs/doc/en/xorg-config.xml
Gentoo

Diff of /xml/htdocs/doc/en/xorg-config.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.28 Revision 1.44
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v 1.28 2009/01/26 08:08:22 nightmorph Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xorg-config.xml,v 1.44 2011/03/02 08:16:43 nightmorph Exp $ -->
4 4
5<guide link="/doc/en/xorg-config.xml"> 5<guide>
6<title>The X Server Configuration HOWTO</title> 6<title>The X Server Configuration HOWTO</title>
7 7
8<author title="Author"> 8<author title="Author">
9 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 9 <mail link="swift"/>
10</author> 10</author>
11<author title="Editor"> 11<author title="Author">
12 <mail link="nightmorph"/> 12 <mail link="nightmorph"/>
13</author> 13</author>
14 14
15<abstract> 15<abstract>
16Xorg is the X Window server which allows users to have a graphical 16Xorg is the X Window server which allows users to have a graphical
20 20
21<!-- The content of this document is licensed under the CC-BY-SA license --> 21<!-- The content of this document is licensed under the CC-BY-SA license -->
22<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 22<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
23<license/> 23<license/>
24 24
25<version>1.19</version> 25<version>6</version>
26<date>2009-01-26</date> 26<date>2011-03-02</date>
27 27
28<chapter> 28<chapter>
29<title>What is the X Window Server?</title> 29<title>What is the X Window Server?</title>
30<section> 30<section>
31<title>Graphical vs Command-Line</title> 31<title>Graphical vs Command-Line</title>
32<body> 32<body>
33 33
34<p> 34<p>
35The average user may be frightened at the thought of having to type in commands. 35The average user may be frightened at the thought of having to type in commands.
36Why wouldn't he be able to point and click his way through the freedom provided 36Why wouldn't he be able to point and click his way through the freedom provided
37by Gentoo (and Linux in general)? Well, *big smile*, of course you are able to 37by Gentoo (and Linux in general)? Well, of course you are able to
38do this. :-) Linux offers a wide variety of flashy user interfaces and 38do this! Linux offers a wide variety of flashy user interfaces and
39environments which you can install on top of your existing installation. 39environments which you can install on top of your existing installation.
40</p> 40</p>
41 41
42<p> 42<p>
43This is one of the biggest surprises new users come across: a graphical user 43This is one of the biggest surprises new users come across: a graphical user
89<title>Installing Xorg</title> 89<title>Installing Xorg</title>
90<section> 90<section>
91<body> 91<body>
92 92
93<p> 93<p>
94Before installing Xorg you have to configure two important variables in the 94Before you can install Xorg, you need to prepare your system for it. First,
95<path>/etc/make.conf</path> file. 95we'll set up the kernel to support input devices and video cards. Then we'll
96</p> 96prepare <path>/etc/make.conf</path> so that the right drivers and Xorg packages
97 97are built and installed.
98<p> 98</p>
99
100</body>
101</section>
102<section>
103<title>Input driver support</title>
104<body>
105
106<p>
107By default, Xorg uses <c>evdev</c>, a generic input driver. You'll need to
108activate support for <c>evdev</c> by making a change to your kernel
109configuration. Read the <uri link="/doc/en/kernel-config.xml">Kernel
110Configuration Guide</uri> if you don't know how to setup your kernel.
111</p>
112
113<pre caption="Enabling evdev in the kernel">
114Device Drivers ---&gt;
115 Input device support ---&gt;
116 &lt;*&gt; Event interface
117</pre>
118
119</body>
120</section>
121<section>
122<title>Kernel modesetting</title>
123<body>
124
125<p>
126Modern open-source video drivers rely on kernel modesetting (KMS). KMS provides
127an improved graphical boot with less flickering, faster user switching, a
128built-in framebuffer console, seamless switching from the console to Xorg, and
129other features. KMS conflicts with legacy framebuffer drivers, which must remain
130<b>disabled</b> in your kernel configuration.
131</p>
132
133<p>
134First, prepare your kernel for KMS. You need to do this step regardless of which
135Xorg video driver you're using.
136</p>
137
138<pre caption="Configuring framebuffers">
139Device Drivers ---&gt;
140 Graphics support ---&gt;
141 Support for frame buffer devices ---&gt;
142 <comment>(Disable all drivers, including VGA, Intel, nVidia, and ATI)</comment>
143
144 <comment>(Further down, enable basic console support. KMS uses this.)</comment>
145 Console display driver support ---&gt;
146 &lt;*&gt; Framebuffer Console Support
147</pre>
148
149<p>
150Next, configure your kernel to use the proper KMS driver for your video card.
151Intel, nVidia, and ATI are the most common cards, so follow code listing for
152your card below.
153</p>
154
155<p>
156For Intel cards:
157</p>
158
159<pre caption="Intel settings">
160Device Drivers ---&gt;
161 Graphics support ---&gt;
162 /dev/agpgart (AGP Support) ---&gt;
163 &lt;*&gt; Intel 440LX/BX/GX, I8xx and E7x05 chipset support
164 Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---&gt;
165 &lt;*&gt; Intel 830M, 845G, 852GM, 855GM, 865G (i915 driver)
166 i915 driver
167 [*] Enable modesetting on intel by default
168</pre>
169
170<p>
171For nVidia cards:
172</p>
173
174<pre caption="nVidia settings">
175<comment>(Enable DRM)</comment>
176Device Drivers ---&gt;
177 Graphics support ---&gt;
178 &lt;*&gt; Direct Rendering Manager ---&gt;
179
180<comment>(Nouveau is currently in the Staging drivers section)</comment>
181Device Drivers ---&gt;
182 Staging drivers ---&gt;
183 [ ] Exclude Staging drivers from being built
184 &lt;*&gt; Nouveau (nVidia) cards
185</pre>
186
187<p>
188For newer ATI cards (<uri link="/doc/en/ati-faq.xml">RadeonHD 2000 and
189up</uri>), you will need to emerge <c>radeon-ucode</c>. Once you have installed
190<c>radeon-ucode</c>, configure your kernel as shown:
191</p>
192
193<pre caption="ATI settings">
194<comment>(Setup the kernel to use the radeon-ucode firmware)</comment>
195Device Drivers ---&gt;
196 Generic Driver Options ---&gt;
197 [*] Include in-kernel firmware blobs in kernel binary
198 <comment># RadeonHD 2000, 3000, and 4000 series cards:</comment>
199 (radeon/R600_rlc.bin radeon/R700_rlc.bin) External firmware blobs
200 <comment># RadeonHD 5000, a.k.a Evergreen, and newer cards:</comment>
201 (radeon/CEDAR_me.bin radeon/CEDAR_pfp.bin radeon/CEDAR_rlc.bin
202 radeon/CYPRESS_me.bin radeon/CYPRESS_pfp.bin radeon/CYPRESS_rlc.bin
203 radeon/JUNIPER_me.bin radeon/JUNIPER_pfp.bin radeon/JUNIPER_rlc.bin
204 radeon/REDWOOD_me.bin radeon/REDWOOD_pfp.bin
205 radeon/REDWOOD_rlc.bin) External firmware blobs
206 <comment># Radeon HD 6200/6300 aka. Ontario/Zacate:</comment>
207 (radeon/PALM_me.bin radeon/PALM_pfp.bin radeon/SUMO_rlc.bin) External
208 firmware blobs
209 <comment># Radeon HD 6400-6900 aka. Northern Islands:</comment>
210 (radeon/BARTS_mc.bin radeon/BARTS_me.bin radeon/BARTS_pfp.bin
211 radeon/BTC_rlc.bin radeon/CAICOS_mc.bin radeon/CAICOS_me.bin
212 radeon/CAICOS_pfp.bin radeon/TURKS_mc.bin radeon/TURKS_me.bin
213 radeon/TURKS_pfp.bin) External firmware blobs
214 (/lib/firmware/) Firmware blobs root directory
215
216<comment>(Enable Radeon KMS support)</comment>
217Device Drivers ---&gt;
218 Graphics support ---&gt;
219 &lt;*&gt; Direct Rendering Manager ---&gt;
220 &lt;*&gt; ATI Radeon
221 [*] Enable modesetting on radeon by default
222</pre>
223
224<note>
225Old Radeon cards (X1900 series and older) don't need the <c>radeon-ucode</c>
226package or any firmware configuration. Just enable the Direct Rendering Manager
227and ATI Radeon modesetting.
228</note>
229
230<p>
231Now that you're done setting up KMS, continue with preparing
232<path>/etc/make.conf</path> in the next section.
233</p>
234
235</body>
236</section>
237<section>
238<title>make.conf configuration</title>
239<body>
240
241<p>
242Now that your kernel is prepared, you have to configure two important variables
243in the <path>/etc/make.conf</path> file before you can install Xorg.
244</p>
245
246<p>
99The first one is <c>VIDEO_CARDS</c>. This is used to set the video drivers that 247The first variable is <c>VIDEO_CARDS</c>. This is used to set the video drivers
100you intend to use and is usually based on the kind and brand of card you have. 248that you intend to use and is usually based on the kind of video card you have.
101The most common settings are <c>nvidia</c> for Nvidia cards or <c>fglrx</c> for 249The most common settings are <c>nouveau</c> for nVidia cards or <c>radeon</c>
102ATI Radeon cards. Those are the proprietary drivers from Nvidia and ATI 250for ATI cards. Both have actively developed, well-supported open-source
103respectively. If you would like to use the open source versions, use <c>nv</c> 251drivers.
104rather than <c>nvidia</c> in the variable, but bear in mind that using this 252</p>
105driver means no 3D acceleration at all. The free <c>radeon</c> and 253
106<c>radeonhd</c> drivers for ATI cards support 3D acceleration on older Radeons 254<note>
107but don't yet support all the features of the newer ones. <c>VIDEO_CARDS</c> may 255You may also try the proprietary drivers from nVidia and ATI, <c>nvidia</c> and
108contain more than one driver, in this case list of them should be separated with 256<c>fglrx</c> respectively. However, setting up the proprietary drivers is
257beyond the scope of this guide. Please read the <uri
258link="/doc/en/nvidia-guide.xml">Gentoo Linux nVidia Guide</uri> and <uri
259link="/doc/en/ati-faq.xml">Gentoo Linux ATI FAQ</uri>. If you don't know which
260drivers you should choose, refer to these guides for more information.
261</note>
262
263<p>
264The <c>intel</c> driver may be used for desktops or laptops with common Intel
265integrated graphics chipsets.
266</p>
267
268<note>
269<c>VIDEO_CARDS</c> may contain more than one driver, each separated with a
109spaces. 270space.
110</p> 271</note>
111 272
112<p> 273<p>
113The second variable is <c>INPUT_DEVICES</c> and is used to determine which 274The second variable is <c>INPUT_DEVICES</c> and is used to determine which
114drivers are to be built for input devices. In most cases setting it to 275drivers are to be built for input devices. In most cases setting it to
115<c>keyboard mouse</c> should work just fine. If you use alternative input 276<c>evdev</c> should work just fine. If you use alternative input
116devices, such as a Synaptics touchpad for a laptop, be sure to add it to 277devices, such as a Synaptics touchpad for a laptop, be sure to add it to
117<c>INPUT_DEVICES</c>. 278<c>INPUT_DEVICES</c>.
118</p> 279</p>
119 280
120<p> 281<p>
121Now you should decide which drivers you will use and add necessary settings to 282Now you should decide which drivers you will use and add necessary settings to
122the <path>/etc/make.conf</path> file: 283the <path>/etc/make.conf</path> file:
123</p> 284</p>
124 285
125<pre caption="Sample make.conf entries"> 286<pre caption="Sample make.conf entries">
126<comment>(For mouse and keyboard support)</comment> 287<comment>(For mouse, keyboard, and Synaptics touchpad support)</comment>
127INPUT_DEVICES="keyboard mouse" 288INPUT_DEVICES="evdev synaptics"
128<comment>(For Nvidia cards)</comment> 289<comment>(For nVidia cards)</comment>
129VIDEO_CARDS="nvidia" 290VIDEO_CARDS="nouveau"
130<comment>(OR, for ATI Radeon cards)</comment> 291<comment>(OR, for ATI Radeon cards)</comment>
131VIDEO_CARDS="fglrx" 292VIDEO_CARDS="radeon"
132</pre> 293</pre>
133 294
134<p>
135More instructions on how to configure nVidia and ATI cards can be found in
136<uri link="/doc/en/nvidia-guide.xml">Gentoo Linux nVidia Guide</uri> and in
137<uri link="/doc/en/ati-faq.xml">Gentoo Linux ATI FAQ</uri>. If you don't know
138which drivers you should choose, refer to these guides for more information.
139</p> 295<p>
296If the suggested settings don't work for you, you should run <c>emerge -pv
297xorg-drivers</c>, check all the options available and choose those which apply to
298your system. This example is for a system with a keyboard, mouse, Synaptics
299touchpad, and a Radeon video card.
300</p>
301
302<pre caption="Displaying all the driver options available">
303# <i>emerge -pv xorg-drivers</i>
304
305These are the packages that would be merged, in order:
306
307Calculating dependencies... done!
308[ebuild R ] x11-base/xorg-drivers-1.9 INPUT_DEVICES="evdev synaptics
309-acecad -aiptek -elographics% -fpit% -joystick -keyboard -mouse -penmount -tslib
310-virtualbox -vmmouse -void -wacom"
311VIDEO_CARDS="radeon -apm -ark -ast -chips -cirrus -dummy -epson -fbdev -fglrx
312(-geode) -glint -i128 (-i740) (-impact) -intel -mach64 -mga -neomagic (-newport)
313-nouveau -nv -nvidia -r128 -rendition -s3 -s3virge -savage -siliconmotion -sis
314-sisusb (-sunbw2) (-suncg14) (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx)
315-tdfx -tga -trident -tseng -v4l -vesa -via -virtualbox -vmware (-voodoo) (-xgi)"
3160 kB
317</pre>
318
319<p>
320After setting all the necessary variables you can install the Xorg package.
321</p>
322
323<pre caption="Installing Xorg">
324# <i>emerge xorg-server</i>
325</pre>
140 326
141<note> 327<note>
142If the suggested settings don't work for you, you should run <c>emerge -pv 328You could install the <c>xorg-x11</c> metapackage instead of the more
143xorg-server</c>, check all the options available and choose those which apply to 329lightweight <c>xorg-server</c>. Functionally, <c>xorg-x11</c> and
144your system. The example is for the amd64 architecture and 330<c>xorg-server</c> are the same. However, <c>xorg-x11</c> brings in many more
145<c>xorg-server-1.2</c>. 331packages that you probably don't need, such as a huge assortment of fonts in
332many different languages. They're not necessary for a working desktop.
146</note> 333</note>
147 334
148<pre caption="Displaying all the driver options available">
149# <i>emerge -pv xorg-server</i>
150
151These are the packages that would be merged, in order:
152
153Calculating dependencies... done!
154[ebuild R ] x11-base/xorg-server-1.2.0-r3 USE="dri nptl xorg (-3dfx) -debug
155-dmx -ipv6 -kdrive -minimal -sdl -xprint" INPUT_DEVICES="keyboard mouse -acecad
156-aiptek -calcomp -citron -digitaledge -dmc -dynapro -elo2300 -elographics -evdev
157-fpit -hyperpen -jamstudio -joystick -magellan -microtouch -mutouch -palmax
158-penmount -spaceorb -summa -synaptics -tek4957 -ur98 -vmmouse -void -wacom"
159VIDEO_CARDS="nvidia -apm -ark -chips -cirrus -cyrix -dummy -epson -fbdev -fglrx
160-glint -i128 (-i740) -i810 (-impact) (-imstt) -mach64 -mga -neomagic (-newport)
161(-nsc) -nv -r128 -radeon -rendition -s3 -s3virge -savage -siliconmotion -sis
162-sisusb (-sunbw2) (-suncg14) (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx)
163-tdfx -tga -trident -tseng -v4l -vesa -vga -via -vmware -voodoo" 0 kB
164</pre>
165
166<p>
167After setting all the necessary variables you can install the Xorg package.
168</p> 335<p>
169
170<pre caption="Installing Xorg">
171# <i>emerge xorg-x11</i>
172</pre>
173
174<p>
175When the installation is finished, you might need to re-initialise some 336When the installation is finished, you will need to re-initialise some
176environment variables before you continue. Just run <c>env-update</c> followed 337environment variables before you continue. Just run <c>env-update</c> followed
177by <c>source /etc/profile</c> and you're all set. 338by <c>source /etc/profile</c> and you're all set.
178</p> 339</p>
179 340
180<pre caption="Re-initialising the environment variables"> 341<pre caption="Re-initialising the environment variables">
181# <i>env-update</i> 342# <i>env-update</i>
182# <i>source /etc/profile</i> 343# <i>source /etc/profile</i>
183</pre> 344</pre>
184 345
346<p>
347Now it's time to start the Hardware Abstraction Layer (HAL) daemon and set it to
348automatically start each time you boot. This is necessary to get a working X
349environment, otherwise your input devices won't be detected and you'll probably
350just get a blank screen. We'll cover HAL more in the <uri
351link="#using_hal">next section</uri>.
352</p>
353
354<pre caption="Starting HAL">
355# <i>/etc/init.d/hald start</i>
356# <i>rc-update add hald default</i>
357</pre>
358
185</body> 359</body>
186</section> 360</section>
187</chapter> 361</chapter>
362
188<chapter> 363<chapter>
189<title>Configuring Xorg</title> 364<title>Configuring Xorg</title>
365<section id="using_hal">
366<title>Using HAL</title>
367<body>
368
369<p>
370The X server is designed to work out-of-the-box, with no need to manually edit
371Xorg's configuration files.
372</p>
373
374<p>
375You should first try <uri link="#using_startx">starting X</uri> without creating
376<path>/etc/X11/xorg.conf</path>.
377</p>
378
379<p>
380If Xorg won't start (if there's something wrong with the screen, or with your
381keyboard/mouse), then you can try fixing problems by using the right
382configuration files.
383</p>
384
385<p>
386By default, Xorg uses HAL (Hardware Abstraction Layer) to detect and configure
387devices such as keyboards and mice.
388</p>
389
390<p>
391HAL comes with many premade device rules, also called policies. These policy
392files are available in <path>/usr/share/hal/fdi/policy/</path>. Just find a few
393that suit your needs most closely and copy them to
394<path>/etc/hal/fdi/policy/</path>.
395</p>
396
397<impo>
398Do not edit the files in <path>/usr/share/hal/fdi/</path>! Just copy the ones
399you need, and edit them once they're placed in the proper <path>/etc</path>
400location.
401</impo>
402
403<p>
404For example, to get a basic working keyboard/mouse combination, you could copy
405the following files to <path>/etc/hal/fdi/policy/</path>:
406</p>
407
408<pre caption="Using HAL policy files">
409# <i>cp /usr/share/hal/fdi/policy/10osvendor/10-input-policy.fdi /etc/hal/fdi/policy</i>
410# <i>cp /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi /etc/hal/fdi/policy</i>
411</pre>
412
413<p>
414There are several other HAL policies in <path>/usr/share/hal/fdi/</path> that
415may interest you, such as laptop configurations, storage device handling, power
416management, and more. Just copy any of the policies to
417<path>/etc/hal/fdi/policy/</path>.
418</p>
419
420<impo>
421Remember, <e>every</e> time you finish making changes to HAL policy files, you
422need to restart the HAL daemon by running <c>/etc/init.d/hald restart</c>.
423</impo>
424
425<p>
426You can edit the policy files in <path>/etc/hal/fdi/policy</path> to your
427liking. You may want to make a few tweaks or to expose additional
428functionality. Let's go through an example of tweaking a HAL policy.
429</p>
430
431<p>
432One very convenient trick is to kill the X server entirely by pressing
433Ctrl-Alt-Backspace. This is useful when your X server is malfunctioning, frozen,
434etc. It's not as extreme as rebooting the whole machine with Ctrl-Alt-Del.
435</p>
436
437<p>
438Recent X server versions disabled this key combination by default. However, you
439can reenable it by copying <path>10-x11-input.fdi</path> to
440<path>/etc/hal/fdi/policy</path> and editing it. You'll need to add just one
441line to the appropriate section, as shown below:
442</p>
443
444<pre caption="Editing 10-x11-input.fdi">
445<comment>(Open the file in your preferred editor)</comment>
446# <i>nano -w /etc/hal/fdi/policy/10-x11-input.fdi</i>
447<comment>(Find the "input.keys" section)</comment>
448&lt;match key="info.capabilities" contains="input.keys"&gt;
449<comment>(Add the "terminate" merge string as shown)</comment>
450&lt;match key="info.capabilities" contains="input.keys"&gt;
451 &lt;merge key="input.x11_driver" type="string"&gt;keyboard&lt;/merge&gt;
452 <i>&lt;merge key="input.xkb.options" type="string"&gt;terminate:ctrl_alt_bksp&lt;/merge&gt;</i>
453 &lt;match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
454 string="Linux"&gt;
455 &lt;merge key="input.x11_driver" type="string"&gt;evdev&lt;merge&gt;
456 &lt;/match&gt;
457 &lt;/match&gt;
458</pre>
459
460<p>
461Once you're done, run <c>/etc/init.d/hald restart</c> so that HAL picks up your
462changes.
463</p>
464
465<p>
466There, now you have a handy way of killing an unresponsive X server. This is
467useful when programs have frozen your display entirely, or when configuring and
468tweaking your Xorg environment. Be careful when killing your desktop with this
469key combination -- most programs really don't like it when you end them this
470way, and you may lose some (or all) of what you were working on.
471</p>
472
473<p>
474Hopefully just working with the HAL policy files results in a working X desktop.
475If Xorg still won't start, or there's some other problem, then you'll need to
476manually configure <path>xorg.conf</path> as shown in the next section.
477</p>
478
479</body>
190<section> 480</section>
481<section>
191<title>The xorg.conf File</title> 482<title>The xorg.conf file</title>
192<body> 483<body>
193 484
485<note>
486Configuring <path>xorg.conf</path> should be seen as a "last resort" option. It
487really desirable to run without one if possible, and to do all your
488configuration via HAL policy files. If you still can't get a working
489configuration, then read on.
490</note>
491
194<p> 492<p>
195The configuration file of Xorg is called <path>xorg.conf</path> and it 493The configuration file of Xorg is called <path>xorg.conf</path> and it resides
196resides in <path>/etc/X11</path>. The Xorg-X11 package provides an example 494in <path>/etc/X11</path>. Xorg provides an example configuration as
197configuration as <path>/etc/X11/xorg.conf.example</path> which you can use to 495<path>/etc/X11/xorg.conf.example</path> which you can use to create your own
198create your own configuration. It is heavily commented, but if you are in need 496configuration. It is heavily commented, but if you are in need of more
199of more documentation regarding the syntax, don't hesitate to read the man page: 497documentation regarding the syntax, don't hesitate to read the man page:
200</p> 498</p>
201 499
202<pre caption="Reading the xorg.conf man page"> 500<pre caption="Reading the xorg.conf man page">
203# <i>man 5 xorg.conf</i> 501$ <i>man 5 xorg.conf</i>
204</pre>
205
206<p>
207Happy reading for those of you willing to. We surely don't so we'll continue
208with checking out how we can create the file automatically.
209</p> 502</pre>
210 503
211</body> 504</body>
212</section>
213<section> 505</section>
506<section>
214<title>Default: Automatic Generation of xorg.conf</title> 507<title>Automatic Generation of xorg.conf</title>
215<body> 508<body>
216 509
217<p> 510<p>
218Xorg itself is able to guess most parameters for you. In most cases, you 511Xorg itself is able to guess most parameters for you. In most cases, you
219will only have to change some lines to get the resolution you want up and 512will only have to change some lines to get the resolution you want up and
233will have told you that it has written <path>/root/xorg.conf.new</path> ready 526will have told you that it has written <path>/root/xorg.conf.new</path> ready
234for you to test. So let's test. :) 527for you to test. So let's test. :)
235</p> 528</p>
236 529
237<pre caption="Testing the xorg.conf.new file"> 530<pre caption="Testing the xorg.conf.new file">
238# <i>X -config /root/xorg.conf.new</i> 531# <i>X -retro -config /root/xorg.conf.new</i>
239</pre> 532</pre>
240 533
241<p> 534<p>
242If all goes well, you should see a simple black and white pattern. Verify if 535If all goes well, you should see a simple black and white pattern. Verify if
243your mouse works correctly and if the resolution is good. If you received errors 536your mouse works correctly and if the resolution is good. You might not be able
244about "/dev/mouse", try changing your mouse device to <c>/dev/input/mice</c> in
245the "InputDevice" section of <path>xorg.conf</path>. You might not be able to
246deduce the exact resolution, but you should be able to see if it's too low. You 537to deduce the exact resolution, but you should be able to see if it's too low.
247can exit any time by pressing Ctrl-Alt-Backspace. 538You can exit any time by pressing Ctrl-Alt-Backspace.
248</p>
249
250</body>
251</section>
252<section>
253<title>Alternative: Semi-Automatic Generation of xorg.conf</title>
254<body>
255
256<p> 539</p>
257Xorg provides a tool called <c>xorgconfig</c> which will ask you for various
258information regarding your system (graphical adapter, keyboard, ...). Based on
259your input it will create a <path>xorg.conf</path> file.
260</p>
261
262<pre caption="Semi-Automatic Generation of xorg.conf">
263# <i>xorgconfig</i>
264</pre>
265
266<p>
267Another tool, also provided by Xorg, is <c>xorgcfg</c>, which will first
268attempt to run <c>Xorg -configure</c> and then start the X server for more
269final tweaking.
270</p>
271
272<pre caption="Using xorgcfg">
273# <i>xorgcfg</i>
274<comment>(In case X crashes or the configuration fails, try:)</comment>
275# <i>xorgcfg -textmode</i>
276</pre>
277 540
278</body> 541</body>
279</section> 542</section>
280<section> 543<section>
281<title>Copying over xorg.conf</title> 544<title>Copying over xorg.conf</title>
282<body> 545<body>
283 546
284<p> 547<p>
285Let us copy over the <path>xorg.conf.new</path> to 548Let us copy over the <path>xorg.conf.new</path> to
286<path>/etc/X11/xorg.conf</path> now, so we won't have to continuously run 549<path>/etc/X11/xorg.conf</path> now, so we won't have to continuously run
287<c>X -config</c> -- typing just <c>X</c> or <c>startx</c> is easier. :) 550<c>X -config</c> -- typing just <c>startx</c> is easier. :)
288</p> 551</p>
289 552
290<pre caption="Copying over xorg.conf"> 553<pre caption="Copying over xorg.conf">
291# <i>cp /root/xorg.conf.new /etc/X11/xorg.conf</i> 554# <i>cp /root/xorg.conf.new /etc/X11/xorg.conf</i>
292</pre> 555</pre>
296<section id="using_startx"> 559<section id="using_startx">
297<title>Using startx</title> 560<title>Using startx</title>
298<body> 561<body>
299 562
300<p> 563<p>
301Now try <c>startx</c> to start up your X server. <c>startx</c> is a script 564Now try <c>startx</c> to start up your X server. <c>startx</c> is a script
302that executes an <e>X session</e>, that is, it starts the X servers and some 565that executes an <e>X session</e>, that is, it starts the X server and some
303graphical applications on top of it. It decides which applications to run 566graphical applications on top of it. It decides which applications to run
304using the following logic: 567using the following logic:
305</p> 568</p>
306 569
307<ul> 570<ul>
308 <li> 571 <li>
310 execute the commands listed there. 573 execute the commands listed there.
311 </li> 574 </li>
312 <li> 575 <li>
313 Otherwise, it will read the value of the XSESSION variable and will execute 576 Otherwise, it will read the value of the XSESSION variable and will execute
314 one of the sessions available in <path>/etc/X11/Sessions/</path> 577 one of the sessions available in <path>/etc/X11/Sessions/</path>
315 accordingly (you can set the value of XSESSION in <path>/etc/rc.conf</path> 578 accordingly. You can set the value of XSESSION in
316 to make it a default for all the users on the system). 579 <path>/etc/env.d/90xsession</path> to make it a default for all the users
317 </li> 580 on the system. For example, as root, run <c>echo XSESSION="Xfce4" >
318 <li> 581 /etc/env.d/90xsession</c>. This will create the <path>90xsession</path> file
319 If all of the above fail, it will fall back to a simple window manager, 582 and set the default X session to <uri
320 usually <c>twm</c>. 583 link="/doc/en/xfce-config.xml">Xfce</uri>. Remember to run <c>env-update</c>
584 after changing <path>90xsession</path>.
321 </li> 585 </li>
322</ul> 586</ul>
323 587
324<pre caption="Starting X"> 588<pre caption="Starting X">
325# <i>startx</i> 589$ <i>startx</i>
326</pre> 590</pre>
327 591
592<p>
593You can kill the X session by using the Ctrl-Alt-Backspace key combination. This
594will, however, make X exit disgracefully -- something that you might not always
595want.
328<p> 596</p>
329If you see an ugly, loathsome, repulsive, deformed window manager, that's 597
330<c>twm</c>. To finish the twm session, type in <c>exit</c> or Ctrl-D in the 598<p>
331upcoming xterms. You can also kill the X session using the Ctrl-Alt-Backspace 599If you haven't yet installed a window manager, all you'll see is a black screen.
332combination. This will however make X exit disgracefully -- something that you 600Since this can also be a sign that something's wrong, you may want to emerge
333might not always want. It doesn't hurt though. :) 601<c>twm</c> and <c>xterm</c> <e>only to test X</e>.
602</p>
603
604<p>
605Once those two programs are installed, run <c>startx</c> again. A few xterm
606windows should appear, making it easier to verify that X is working correctly.
607Once you're satisfied with the results, run <c>emerge --unmerge twm xterm</c> as
608root to get rid of the testing packages. You won't need them once you've setup a
609proper desktop environment.
334</p> 610</p>
335 611
336</body> 612</body>
337</section> 613</section>
338</chapter> 614</chapter>
615
339<chapter> 616<chapter>
340<title>Tweaking xorg.conf</title> 617<title>Tweaking X settings</title>
341<section> 618<section>
342<title>Setting your Resolution</title> 619<title>Setting your Resolution</title>
343<body> 620<body>
344 621
345<p> 622<p>
346If you feel that the screen resolution is wrong, you will need to check two 623If you feel that the screen resolution is wrong, you will need to check two
347sections in your configuration. First of all, you have the <e>Screen</e> section 624sections in your <path>xorg.conf</path> configuration. First of all, you have
348which lists the resolutions, if any that your X server will run at. By 625the <e>Screen</e> section which lists the resolutions, if any that your X server
349default, this section might not list any resolutions at all. If this is the 626will run at. By default, this section might not list any resolutions at all. If
350case, Xorg will estimate the resolutions based on the information in the 627this is the case, Xorg will estimate the resolutions based on the information in
351second section, <e>Monitor</e>. 628the second section, <e>Monitor</e>.
352</p> 629</p>
353 630
354<p> 631<p>
355What happens is that Xorg checks the settings of <c>HorizSync</c> and 632What happens is that Xorg checks the settings of <c>HorizSync</c> and
356<c>VertRefresh</c> in the <e>Monitor</e> section to compute valid resolutions. 633<c>VertRefresh</c> in the <e>Monitor</e> section to compute valid resolutions.
357For now, leave these settings as-is. Only when the changes to the <e>Screen</e> 634For now, leave these settings as-is. Only when the changes to the <e>Screen</e>
358section (which we will describe in a minute) don't work, then you will need to 635section (which we will describe in a minute) don't work, then you will need to
359look up the specs for your monitor and fill in the correct values. You can also 636look up the specs for your monitor and fill in the correct values.
360use a tool that searches for your monitor's specs, such as
361<c>sys-apps/ddcxinfo-knoppix</c>.
362</p> 637</p>
363 638
364<warn> 639<warn>
365Do <b>not</b> "just" change the values of these two monitor related variables 640Do <b>not</b> "just" change the values of these two monitor related variables
366without consulting the technical specifications of your monitor. Setting 641without consulting the technical specifications of your monitor. Setting
367incorrect values lead to out-of-sync errors at best and smoked up screens at 642incorrect values lead to out-of-sync errors at best and smoked up screens at
368worst. 643worst.
369</warn> 644</warn>
370 645
371<p> 646<p>
372Now let us change the resolutions. In the next example from 647Now let us change the resolution. In the next example from
373<path>/etc/X11/xorg.conf</path> we add the <c>Modes</c> lines and the 648<path>/etc/X11/xorg.conf</path> we add the <c>PreferredMode</c> line so that our
374<c>DefaultDepth</c> so that our X server starts with 24 bits at 1024x768 by 649X server starts at 1440x900 by default. Don't mind the given strings -- they are
375default. Don't mind the given strings -- they are examples and will most likely 650examples and will most likely differ from the settings on your system. However,
376differ from the settings on your system. 651the <c>Option</c> in the <c>Device</c> section must match the name of your
652monitor (<c>DVI-0</c>), which can be obtained by running <c>xrandr</c>. You'll
653need to <c>emerge xrandr</c> just long enough to get this information. The
654argument after the monitor name (in the <c>Device</c> section) must match the
655<c>Identifier</c> in the <c>Monitor</c> section.
377</p> 656</p>
378 657
379<pre caption="Changing the Screen section in /etc/X11/xorg.conf"> 658<pre caption="Changing the Monitor section in /etc/X11/xorg.conf">
380Section "Screen" 659Section "Device"
381 Identifier "Default Screen" 660 Identifier "RadeonHD 4550"
382 Device "S3 Inc. ProSavage KN133 [Twister K]" 661 Option "Monitor-DVI-0" "DVI screen"
383 Monitor "Generic Monitor"
384 <i>DefaultDepth 24</i>
385 <comment># Skipping some text to improve readability</comment>
386 SubSection "Display"
387 Depth 24
388 <i>Modes "1024x768"</i>
389 EndSubSection
390EndSection 662EndSection
391</pre> 663Section "Monitor"
392 664 Identifier "DVI screen"
393<p> 665 Option "PreferredMode" "1440x900"
394Run X (<c>startx</c>) to discover it uses the resolution you want. :)
395</p>
396
397</body>
398</section>
399<section>
400<title>Configuring your Keyboard</title>
401<body>
402
403<p>
404To setup X to use an international keyboard, search for the <e>InputDevice</e>
405section that configures the keyboard and add the <c>XkbLayout</c> option to
406point to the keyboard layout you want. As an example, we show you how to apply
407for the Belgian layout. Just substitute the country-keycode with yours:
408</p>
409
410<pre caption="Changing the keyboard layout">
411Section "InputDevice"
412 Identifier "Generic Keyboard"
413 Driver "keyboard"
414 Option "CoreKeyboard"
415 Option "XkbRules" "xorg"
416 Option "XkbModel" "pc105"
417 <i>Option "XkbLayout" "be"</i>
418EndSection 666EndSection
419</pre> 667</pre>
420 668
669<p>
670Run X (<c>startx</c>) to discover it uses the resolution you want.
671</p>
672
421</body> 673</body>
422</section>
423<section> 674</section>
424<title>Configuring your Mouse</title> 675<section>
676<title>Multiple monitors</title>
425<body> 677<body>
426 678
427<p>
428If your mouse isn't working, you will first need to find out if it is detected
429by the kernel at all. Mice are (device-wise) seen as
430<path>/dev/input/mouse0</path> (or <path>/dev/input/mice</path> if you want to
431use several mice). In some cases <path>/dev/psaux</path> is used. In either
432case you can check if the devices do represent
433your mouse by checking the output of those files when you move your mouse. You
434will usually see some junk on your screen. To end the session press
435<c>Ctrl-C</c>.
436</p> 679<p>
437 680You can configure more than one monitor in <path>/etc/X11/xorg.conf</path>. All
438<pre caption="Checking the device files"> 681you have to do is give each monitor an identifer, then list its physical
439# <i>cat /dev/input/mouse0</i> 682position, such as "RightOf" or "Above" another monitor. The following example
440<comment>(Don't forget to press Ctrl-C to end this)</comment> 683shows how to configure a DVI and a VGA monitor, with the VGA monitor as the
441</pre> 684right-hand screen:
442
443<p> 685</p>
444If your mouse isn't detected, verify if all the necessary modules are loaded.
445</p>
446 686
447<p> 687<pre caption="Configuring multiple monitors in xorg.conf">
448If your mouse is detected, fill in the device in the appropriate
449<e>InputDevice</e> section. In the next example you'll see we also set two other
450options: <c>Protocol</c> (which lists the mouse protocol to be used -- most
451users will use PS/2 or IMPS/2) and <c>ZAxisMapping</c> (which allows for the
452mousewheel (if applicable) to be used).
453</p>
454
455<pre caption="Changing the mouse settings in Xorg">
456Section "InputDevice" 688Section "Device"
457 Identifier "TouchPad Mouse" 689 Identifier "RadeonHD 4550"
458 Driver "mouse" 690 Option "Monitor-DVI-0" "DVI screen"
459 Option "CorePointer" 691 Option "Monitor-VGA-0" "VGA screen"
460 <i>Option "Device" "/dev/input/mouse0"</i>
461 <i>Option "Protocol" "IMPS/2"</i>
462 <i>Option "ZAxisMapping" "4 5"</i>
463EndSection 692EndSection
464</pre>
465 693
694Section "Monitor"
695 Identifier "DVI screen"
696EndSection
697
698Section "Monitor"
699 Identifier "VGA screen"
700 Option "RightOf" "DVI screen"
701EndSection
702</pre>
703
704</body>
705</section>
706<section>
707<title>Configuring your keyboard</title>
708<body>
709
710<p>
711To setup X to use an international keyboard, you can copy the content of
712<path>/usr/share/doc/hal-*/*/use-estonian-layout.fdi.bz2</path> to
713<path>/etc/hal/fdi/policy/10-xinput-configuration.fdi</path>:
466<p> 714</p>
715
716<pre caption="Using an existing config file">
717# <i>bzcat /usr/share/doc/hal-*/*/use-estonian-layout.fdi.bz2 > /etc/hal/fdi/policy/10-xinput-configuration.fdi</i>
718</pre>
719
720<p>
721Now you can just edit <path>10-xinput-configuration.fdi</path> and change the
722Estonian keyboard layout (<c>ee</c>) to your own, such as Great Britain
723(<b>gb</b>) or Polish (<b>pl</b>).
724</p>
725
726<p>
727When you're finished, run <c>/etc/init.d/hald restart</c> as root to make sure
728that HAL picks up your configuration file changes.
729</p>
730
731</body>
732</section>
733<section>
734<title>Finishing up</title>
735<body>
736
737<p>
467Run <c>startx</c> and be happy about the result. :) Congratulations, you now 738Run <c>startx</c> and be happy about the result. Congratulations, you now
468(hopefully) have a working Xorg on your system. The next step is to remove this 739(hopefully) have a working Xorg on your system. The next step is to install a
469ugly lightweight window manager and use a high-feature one (or even a desktop 740useful window manager or desktop environment such as KDE, GNOME, or
470environment) such as KDE or GNOME, but that's not part of this guide. :) 741Xfce, but that's not part of this guide.
471</p> 742</p>
472 743
473</body> 744</body>
474</section> 745</section>
475</chapter> 746</chapter>
747
476<chapter> 748<chapter>
477<title>Resources</title> 749<title>Resources</title>
478<section> 750<section>
479<title>Creating and Tweaking xorg.conf</title> 751<title>Creating and Tweaking xorg.conf</title>
480<body> 752<body>
481 753
482<p> 754<p>
483First of all, <c>man xorg.conf</c> provides a quick yet complete reference 755First of all, <c>man xorg.conf</c> and <c>man evdev</c> provide quick yet
484about the syntax used by the configuration file. Be sure to have it open on a 756complete references about the syntax used by these configuration files. Be sure
485terminal near you when you edit your configuration file! 757to have them open on a terminal near you when you edit your configuration
758files!
486</p> 759</p>
487 760
488<p> 761<p>
489Also, be sure to look at <path>/etc/X11/xorg.conf.example</path>; you may wish 762Also, be sure to look at <path>/etc/X11/xorg.conf.example</path>; you may wish
490to copy this and use it as a foundation for writing your own 763to copy this and use it as a foundation for writing your own
497</p> 770</p>
498 771
499<p> 772<p>
500There are also many online resources on editing <path>xorg.conf</path>. We only 773There are also many online resources on editing <path>xorg.conf</path>. We only
501list few of them here, be sure to <uri link="http://www.google.com">Google</uri> 774list few of them here, be sure to <uri link="http://www.google.com">Google</uri>
502for more. :) As <path>xorg.conf</path> and <path>XF86Config</path> (the 775for more.
503configuration file for the XFree86 project) use the
504same syntax for most configuration options and more information about
505<path>XF86Config</path> is available, we'll list those resources as well.
506</p> 776</p>
507
508<ul>
509 <li>
510 <uri link="http://tldp.org/HOWTO/XFree-Local-multi-user-HOWTO/">The XFree
511 Local Multi-User HOWTO</uri>
512 </li>
513 <li>
514 <uri
515 link="http://www-106.ibm.com/developerworks/edu/os-dw-linuxxwin-i.html">An
516 Introduction to XFree 4.x</uri> by Chris Houser
517 </li>
518</ul>
519 777
520</body> 778</body>
521</section> 779</section>
522<section> 780<section>
523<title>Other resources</title> 781<title>Other resources</title>
528environments and applications can be found in the <uri 786environments and applications can be found in the <uri
529link="/doc/en/?catid=desktop">Gentoo Desktop Documentation Resources</uri> 787link="/doc/en/?catid=desktop">Gentoo Desktop Documentation Resources</uri>
530section of our documentation. 788section of our documentation.
531</p> 789</p>
532 790
791<p>
792If you're upgrading to <c>xorg-server</c> 1.8 from an earlier version, then be
793sure to read the <uri
794link="/proj/en/desktop/x/x11/xorg-server-1.8-upgrade-guide.xml">migration
795guide</uri>.
796</p>
797
533</body> 798</body>
534</section> 799</section>
535</chapter> 800</chapter>
536</guide> 801</guide>

Legend:
Removed from v.1.28  
changed lines
  Added in v.1.44

  ViewVC Help
Powered by ViewVC 1.1.20