[d28b5ef] | 1 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
| 2 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
| 3 | <!ENTITY % general-entities SYSTEM "../../general.ent">
|
---|
| 4 | %general-entities;
|
---|
| 5 | ]>
|
---|
| 6 |
|
---|
[7c472863] | 7 | <sect1 id="xorg-config">
|
---|
| 8 | <?dbhtml filename="xorg-config.html"?>
|
---|
[d28b5ef] | 9 |
|
---|
| 10 |
|
---|
[5287b7c] | 11 | <title>Xorg-&xorg-version; Testing and Configuration</title>
|
---|
[d28b5ef] | 12 |
|
---|
[b960e3ec] | 13 | <indexterm zone="xorg-config">
|
---|
| 14 | <primary sortas="g-configuring-xorg">Configuring Xorg</primary>
|
---|
| 15 | </indexterm>
|
---|
| 16 |
|
---|
[da4b5e0] | 17 | <sect2 id='X11-testing' xreflabel="Testing Xorg">
|
---|
[5930509] | 18 | <title>Testing Xorg</title>
|
---|
[0d7900a] | 19 |
|
---|
[da4b5e0] | 20 | <note>
|
---|
| 21 | <para>
|
---|
| 22 | Before starting Xorg for the first time, is is useful to
|
---|
| 23 | rebuild the library cache by running <userinput>ldconfig</userinput>
|
---|
| 24 | as the <systemitem class="username">root</systemitem> user.
|
---|
| 25 | </para>
|
---|
| 26 | </note>
|
---|
| 27 |
|
---|
[d43c7a12] | 28 | <note>
|
---|
| 29 | <para>
|
---|
| 30 | Before starting Xorg for the first time, is is often needed to
|
---|
| 31 | reboot the system to ensure all appropriate daemons are started
|
---|
[b9c353b] | 32 | and appropriate security issues are properly set.
|
---|
[d43c7a12] | 33 | As an alternative, logging out and logging back in may work, but as
|
---|
| 34 | of this writing has not been tested.
|
---|
| 35 | </para>
|
---|
| 36 | </note>
|
---|
| 37 |
|
---|
[df5c5e0] | 38 | <warning>
|
---|
| 39 | <para>
|
---|
| 40 | If Xorg hangs for some reason (for example, lacking a proper
|
---|
[2c87187] | 41 | input driver), the system may stop responding to any user input.
|
---|
[df5c5e0] | 42 | As a precaution, you can enable a magic <keycap>SysRq</keycap> key
|
---|
| 43 | before testing Xorg. As the
|
---|
| 44 | <systemitem class="username">root</systemitem> user, issue:
|
---|
| 45 | </para>
|
---|
| 46 |
|
---|
| 47 | <screen><userinput>echo 4 > /proc/sys/kernel/sysrq</userinput></screen>
|
---|
| 48 |
|
---|
| 49 | <para>
|
---|
| 50 | Then if Xorg hangs, it's possible to use
|
---|
| 51 | <keycombo>
|
---|
| 52 | <keycap>Alt</keycap>
|
---|
| 53 | <keycap>SysRq</keycap>
|
---|
| 54 | <keycap>R</keycap>
|
---|
| 55 | </keycombo>
|
---|
| 56 | to reset the keyboard mode. Now it should be able to use
|
---|
| 57 | <keycombo>
|
---|
| 58 | <keycap>Ctrl</keycap>
|
---|
| 59 | <keycap>Alt</keycap>
|
---|
| 60 | <keycap>Fx</keycap>
|
---|
| 61 | </keycombo>
|
---|
| 62 | (replace x with a VT number) to switch to another VT.
|
---|
[4e207bb] | 63 | If it works, login and kill Xorg using command line in the new VT.
|
---|
[df5c5e0] | 64 | </para>
|
---|
| 65 | </warning>
|
---|
| 66 |
|
---|
[da4b5e0] | 67 | <para>
|
---|
| 68 | To test the <application>Xorg</application> installation, issue
|
---|
| 69 | <command>startx</command>. This command brings up a rudimentary window
|
---|
| 70 | manager called <emphasis>twm</emphasis> with three xterm windows and one
|
---|
| 71 | xclock window. The xterm window in the upper left is a login terminal and
|
---|
| 72 | running <emphasis>exit</emphasis> from this terminal will exit the
|
---|
| 73 | <application>X Window</application> session. The third xterm window may
|
---|
| 74 | be obscured on your system by the other two xterms.
|
---|
| 75 | </para>
|
---|
| 76 |
|
---|
| 77 | <note>
|
---|
| 78 | <para>
|
---|
| 79 | When testing <application>Xorg</application> with the
|
---|
| 80 | <application>twm</application> window manager, there will be several
|
---|
[82bdecf] | 81 | warnings in the Xorg log file, <!--<filename revision="sysv">
|
---|
| 82 | /var/log/Xorg.0.log</filename><filename revision="systemd">-->
|
---|
| 83 | $HOME/.local/share/xorg/Xorg.0.log<!--</filename>-->, about missing font
|
---|
[da4b5e0] | 84 | files. In addition, there will be several warnings on the text mode
|
---|
| 85 | terminal (usually tty1) about missing fonts. These warnings do not
|
---|
| 86 | affect functionality, but can be removed if desired by installing
|
---|
| 87 | the <xref linkend="xorg7-legacy"/>.
|
---|
| 88 | </para>
|
---|
| 89 | </note>
|
---|
| 90 |
|
---|
| 91 | <para>
|
---|
| 92 | Generally, there is no specific configuration required for
|
---|
| 93 | <application>Xorg</application>, but customization is possible. For
|
---|
| 94 | details, see <xref linkend='xconfig'/> below.
|
---|
| 95 | </para>
|
---|
| 96 |
|
---|
| 97 | </sect2>
|
---|
| 98 |
|
---|
| 99 | <sect2 role="configuration" id="checking-dri" xreflabel="Checking the DRI
|
---|
| 100 | installation">
|
---|
[7612749] | 101 | <title>Checking the Direct Rendering Infrastructure (DRI)
|
---|
| 102 | Installation</title>
|
---|
[2001b3e] | 103 |
|
---|
[f38727d] | 104 | <para>
|
---|
[7612749] | 105 | DRI is a framework for allowing software to access graphics hardware in
|
---|
| 106 | a safe and efficient manner. It is installed in
|
---|
| 107 | <application>X</application> by default (using
|
---|
| 108 | <application>Mesa</application>) if you have a supported video card.
|
---|
[f38727d] | 109 | </para>
|
---|
| 110 |
|
---|
| 111 | <para>
|
---|
| 112 | To check if DRI drivers are installed properly, check the log file
|
---|
[97ee53d] | 113 | <filename>$HOME/.local/share/xorg/Xorg.0.log</filename> (or
|
---|
| 114 | <filename>/var/log/Xorg.0.log</filename> if you have
|
---|
| 115 | built <xref linkend="xorg-server"/> with the suid bit) for
|
---|
[7612749] | 116 | statements such as:
|
---|
[f38727d] | 117 | </para>
|
---|
| 118 |
|
---|
| 119 | <screen><literal>(II) intel(0): direct rendering: DRI2 Enabled</literal></screen>
|
---|
| 120 |
|
---|
[c96921c] | 121 | <para>or</para>
|
---|
| 122 |
|
---|
| 123 | <screen><literal>(II) NOUVEAU(0): Loaded DRI module</literal></screen>
|
---|
| 124 |
|
---|
[f38727d] | 125 | <note>
|
---|
| 126 | <para>
|
---|
| 127 | DRI configuration may differ if you are using alternate drivers, such
|
---|
| 128 | as those from
|
---|
[87fc185] | 129 | <ulink url="https://www.nvidia.com/page/home.html">NVIDIA</ulink> or
|
---|
| 130 | <ulink url="https://www.amd.com/">AMD</ulink>.
|
---|
[f38727d] | 131 | </para>
|
---|
[2001b3e] | 132 | </note>
|
---|
| 133 |
|
---|
[cc405844] | 134 | <!-- With elogind, this is not needed anymore
|
---|
[f38727d] | 135 | <para>
|
---|
[7612749] | 136 | Although all users can use software acceleration, any hardware
|
---|
| 137 | acceleration (DRI2) is only available to <systemitem
|
---|
| 138 | class="username">root</systemitem> and members of the <systemitem
|
---|
| 139 | class="groupname">video</systemitem> group, but
|
---|
| 140 | <phrase revision="sysv"><emphasis>ConsoleKit2</emphasis></phrase>
|
---|
| 141 | <phrase revision="systemd"><emphasis>systemd-logind</emphasis></phrase>
|
---|
| 142 | takes care of adding any logged in user to the user ACL's of
|
---|
| 143 | <filename>/dev/dri/card*</filename>, the special file(s) allowing access
|
---|
| 144 | to hardware acceleration.<phrase revision="systemd"> So, no further
|
---|
| 145 | configuration is needed.</phrase>
|
---|
[f38727d] | 146 | </para>
|
---|
[2001b3e] | 147 |
|
---|
[7612749] | 148 | <para revision="sysv">
|
---|
| 149 | If your driver is supported and <emphasis>ConsoleKit2</emphasis> is not
|
---|
| 150 | installed, add any users that might use X to the <systemitem
|
---|
| 151 | class="groupname">video</systemitem> group:
|
---|
[f38727d] | 152 | </para>
|
---|
[2001b3e] | 153 |
|
---|
[7612749] | 154 | <screen role="root" revision="sysv"><userinput>usermod -a -G video <replaceable><username></replaceable></userinput></screen>
|
---|
[cc405844] | 155 | -->
|
---|
[f38727d] | 156 | <para>
|
---|
[c96921c] | 157 | Another way to determine if DRI is working properly is to use one of the
|
---|
| 158 | two optionally installed OpenGL demo programs in <xref
|
---|
[7a395d1] | 159 | linkend="mesa"/>. From an X terminal, run <command>glxinfo</command>
|
---|
[f38727d] | 160 | and look for the phrase:
|
---|
| 161 | </para>
|
---|
| 162 |
|
---|
| 163 | <screen><computeroutput>name of display: :0
|
---|
| 164 | display: :0 screen: 0
|
---|
| 165 | direct rendering: Yes</computeroutput></screen>
|
---|
| 166 |
|
---|
| 167 | <para>
|
---|
| 168 | If direct rendering is enabled, you can add verbosity by running
|
---|
[7612749] | 169 | <command>LIBGL_DEBUG=verbose glxinfo</command>. This will show the
|
---|
| 170 | drivers, device nodes and files used by the DRI system.
|
---|
[f38727d] | 171 | </para>
|
---|
| 172 |
|
---|
| 173 | <para>
|
---|
[c96921c] | 174 | To confirm that DRI2 hardware acceleration is working, you can (still in
|
---|
[d6b45f7] | 175 | the X terminal) run the command <command>glxinfo | grep -E "(OpenGL
|
---|
[c96921c] | 176 | vendor|OpenGL renderer|OpenGL version)"</command>.
|
---|
| 177 | If that reports something <emphasis>other than</emphasis>
|
---|
| 178 | <literal>Software Rasterizer</literal> then you have working
|
---|
| 179 | acceleration for the user who ran the command.
|
---|
[f38727d] | 180 | </para>
|
---|
| 181 |
|
---|
| 182 | <para>
|
---|
[c96921c] | 183 | If your hardware does not have any DRI2 driver available, it will use a
|
---|
[7612749] | 184 | Software Rasterizer for Direct Rendering. In such cases, you can use a
|
---|
| 185 | new, LLVM-accelerated, Software Rasterizer called LLVMPipe. In order to
|
---|
| 186 | build LLVMPipe just make sure that <xref linkend="llvm"/> is present at
|
---|
| 187 | Mesa build time. Note that all decoding is done on the CPU instead of
|
---|
| 188 | the GPU, so the display will run slower than with hardware acceleration.
|
---|
| 189 | To check if you are using LLVMpipe, review the output of the glxinfo
|
---|
| 190 | command above. An example of the output using the Software Rasterizer
|
---|
| 191 | is shown below:
|
---|
[f38727d] | 192 | </para>
|
---|
| 193 |
|
---|
[c8a70a5] | 194 | <screen><computeroutput>OpenGL vendor string: VMware, Inc.
|
---|
| 195 | OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 256 bits)
|
---|
[9b175e27] | 196 | OpenGL version string: 3.0 Mesa 10.4.5</computeroutput></screen>
|
---|
[f38727d] | 197 |
|
---|
| 198 | <para>
|
---|
[7612749] | 199 | You can also force LLVMPipe by exporting the
|
---|
| 200 | <envar>LIBGL_ALWAYS_SOFTWARE=1</envar> environment variable when
|
---|
| 201 | starting Xorg.
|
---|
[f38727d] | 202 | </para>
|
---|
| 203 |
|
---|
| 204 | <para>
|
---|
[c96921c] | 205 | Again, if you have built the Mesa OpenGL demos, you can also run the test
|
---|
| 206 | program <command>glxgears</command>. This program brings up a window with
|
---|
| 207 | three gears turning. The X terminal will display how many frames were
|
---|
| 208 | drawn every five seconds, so this will give a rough benchmark. The window
|
---|
| 209 | is scalable, and the frames drawn per second is highly dependent on the
|
---|
| 210 | size of the window. On some hardware, <command>glxgears</command> will
|
---|
| 211 | run synchronized with the vertical refresh signal and the frame rate will
|
---|
| 212 | be approximately the same as the monitor refresh rate.
|
---|
[f38727d] | 213 | </para>
|
---|
[2001b3e] | 214 |
|
---|
[da4b5e0] | 215 | </sect2>
|
---|
[2001b3e] | 216 |
|
---|
[147b566] | 217 | <sect2 role="configuration" id="xorg-debug" xreflabel="Debugging Xorg">
|
---|
| 218 | <title>Debugging Xorg</title>
|
---|
| 219 |
|
---|
| 220 | <para>
|
---|
| 221 | When starting xorg, there are a couple of ways to check what any
|
---|
| 222 | issues you may have. If the system comes up, you can see what driver
|
---|
| 223 | is being used by running <command>xdriinfo</command>. If there are
|
---|
| 224 | issues or you just want to check, look at <filename>Xorg.0.log</filename>.
|
---|
| 225 | </para>
|
---|
| 226 |
|
---|
| 227 | <para>
|
---|
| 228 | The location of <filename>Xorg.0.log</filename> depends on how Xorg is
|
---|
[1fe05eb] | 229 | installed. If the instructions in the book are followed closely and
|
---|
| 230 | Xorg is started from the command line, it will be located in the
|
---|
[147b566] | 231 | <filename class="directory">$HOME/.local/share/xorg/</filename> directory.
|
---|
| 232 | If Xorg is started by a display manager (e.g. <xref linkend='lightdm'/>,
|
---|
[1fe05eb] | 233 | <xref linkend='lxdm'/>, or <xref linkend='gdm'/>) or if
|
---|
[8e8dd4f] | 234 | <filename>$XORG_PREFIX/libexec/Xorg</filename> has the suid bit set,
|
---|
[147b566] | 235 | it will be located in the <filename class="directory">/var/log/</filename>
|
---|
| 236 | directory.
|
---|
| 237 | </para>
|
---|
| 238 |
|
---|
| 239 | <bridgehead renderas="sect3">Xorg.0.log Issues</bridgehead>
|
---|
| 240 |
|
---|
| 241 | <para>
|
---|
| 242 | When you look at Xorg.0.log, check for entries like (EE) or (WW).
|
---|
| 243 | Below are some common entries:
|
---|
| 244 | </para>
|
---|
| 245 |
|
---|
| 246 | <bridgehead renderas="sect5">(WW) Open ACPI failed (/var/run/acpid.socket)</bridgehead>
|
---|
| 247 |
|
---|
| 248 | <para>
|
---|
[5f729f8] | 249 | This warning is because <xref linkend='acpid'/> is not installed. If you
|
---|
| 250 | are not on a laptop, it can be safely ignored. On a laptop, install
|
---|
[147b566] | 251 | <xref linkend='acpid'/> to enable actions like recognizing when the lid is
|
---|
| 252 | closed.
|
---|
| 253 | </para>
|
---|
| 254 |
|
---|
| 255 | <bridgehead renderas="sect5">(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support</bridgehead>
|
---|
| 256 |
|
---|
| 257 | <para>
|
---|
| 258 | This warning is displayed when a regular user starts Xorg. The library
|
---|
| 259 | <filename>libpciaccess.so</filename> issues this warning when it
|
---|
[1fe05eb] | 260 | tries to open <filename>/dev/vga_arbiter</filename>. If there is only
|
---|
[147b566] | 261 | one video card in the system, it can safely be ignored. If desired, the
|
---|
[1fe05eb] | 262 | permissions of this device can be changed by adding a udev rule and
|
---|
[147b566] | 263 | adding the local user to the video group. As the &root; user:
|
---|
| 264 | </para>
|
---|
| 265 |
|
---|
| 266 | <screen role="root"><userinput>cat > /etc/udev/rules.d/99-vga-arbiter.rules << EOF
|
---|
| 267 | # /etc/udev/rules.d/99-vga-arbiter.rules: Set vga_arbiter group/mode
|
---|
| 268 |
|
---|
| 269 | ACTION=="add", KERNEL=="vga_arbiter", GROUP="video" MODE="0660"
|
---|
| 270 | EOF
|
---|
| 271 |
|
---|
[9f4aee8] | 272 | usermod -a -G video <user running xorg></userinput></screen>
|
---|
[147b566] | 273 |
|
---|
| 274 | <bridgehead renderas="sect5">(EE) AIGLX error: dlopen of /opt/xorg/lib/dri/i965_dri.so failed</bridgehead>
|
---|
| 275 |
|
---|
| 276 | <para>
|
---|
| 277 | This error, accompanied by (EE) AIGLX error: unable to load driver i965, occurs
|
---|
| 278 | in some systems with Intel based graphics devices. It is caused by a mismatch
|
---|
| 279 | between the current <xref linkend='xorg-server'/> and <xref linkend='mesa'/>. Xorg
|
---|
[9f4aee8] | 280 | no longer uses the i965 driver and uses the crocus or iris mesa drivers as
|
---|
| 281 | indicated by the <command>xdriinfo</command> command. It can safely be ignored.
|
---|
[147b566] | 282 | </para>
|
---|
| 283 |
|
---|
| 284 | <para>
|
---|
[1fe05eb] | 285 | If desired, this warning can be removed by commenting out lines
|
---|
| 286 | 330-331 and 337-338 (LogMessage) of
|
---|
[147b566] | 287 | <filename>glx/glxdricommon.c</filename> in the <xref linkend='xorg-server'/>
|
---|
| 288 | package.
|
---|
| 289 | </para>
|
---|
| 290 |
|
---|
| 291 | </sect2>
|
---|
| 292 |
|
---|
[da4b5e0] | 293 | <sect2 role="configuration" id="hybrid-graphics" xreflabel="Hybrid Graphics">
|
---|
[f38727d] | 294 | <title>Hybrid Graphics</title>
|
---|
| 295 |
|
---|
| 296 | <para>
|
---|
[7612749] | 297 | Hybrid Graphics is still in experimental state for Linux. Xorg Developers
|
---|
| 298 | have developed a technology called PRIME that can be used for switching
|
---|
| 299 | between integrated and muxless discrete GPU at will. Automatic switching
|
---|
| 300 | is not possible at the moment.
|
---|
[f38727d] | 301 | </para>
|
---|
| 302 |
|
---|
| 303 | <para>
|
---|
[7612749] | 304 | In order to use PRIME for GPU switching, make sure that you are using
|
---|
| 305 | Linux Kernel 3.4 or later (recommended). You will need latest DRI and
|
---|
| 306 | DDX drivers for your hardware and <application>Xorg Server</application>
|
---|
[6039a39] | 307 | 1.13 or later.
|
---|
[f38727d] | 308 | </para>
|
---|
| 309 |
|
---|
| 310 | <para>
|
---|
[7612749] | 311 | <application>Xorg Server</application> should load both GPU drivers
|
---|
[5f729f8] | 312 | automatically. You can check that by running:
|
---|
[6039a39] | 313 | </para>
|
---|
| 314 |
|
---|
| 315 | <screen><userinput>xrandr --listproviders</userinput></screen>
|
---|
| 316 |
|
---|
| 317 | <para>
|
---|
| 318 | There should be two (or more) providers listed, for example:
|
---|
| 319 | </para>
|
---|
| 320 |
|
---|
| 321 | <screen><computeroutput>Providers: number : 2
|
---|
| 322 | Provider 0: id: 0x7d cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 4 associated providers: 1 name:Intel
|
---|
| 323 | Provider 1: id: 0x56 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 1 associated providers: 1 name:radeon</computeroutput></screen>
|
---|
| 324 |
|
---|
| 325 | <para>
|
---|
| 326 | In order to be able to run a GLX application on a discrete GPU, you will
|
---|
| 327 | need to run the following command, where <provider> is the more
|
---|
| 328 | powerful discrete card, and <sink> is the card which has a display
|
---|
| 329 | connected:
|
---|
| 330 | </para>
|
---|
| 331 |
|
---|
| 332 | <screen><userinput>xrandr --setprovideroffloadsink <replaceable><provider> <sink></replaceable></userinput></screen>
|
---|
| 333 |
|
---|
| 334 | <note>
|
---|
| 335 | <para>
|
---|
| 336 | With newer <application>Xorg</application> drivers, such as modesetting
|
---|
| 337 | or intel, which are DRI3 capable, the above command is no longer
|
---|
| 338 | necessary. It does no harm however.
|
---|
| 339 | </para>
|
---|
| 340 | </note>
|
---|
| 341 |
|
---|
| 342 | <para>
|
---|
| 343 | Then, you will need to export the <envar>DRI_PRIME=1</envar> environment
|
---|
| 344 | variable each time you want the powerful GPU to be used. For example,
|
---|
[0d7900a] | 345 |
|
---|
[d6b45f7] | 346 | <screen><userinput>DRI_PRIME=1 glxinfo | grep -E "(OpenGL vendor|OpenGL renderer|OpenGL version)"</userinput></screen>
|
---|
[f38727d] | 347 |
|
---|
| 348 | will show OpenGL vendor, renderer and version for the discrete GPU.
|
---|
| 349 | </para>
|
---|
| 350 |
|
---|
| 351 | <para>
|
---|
[c96921c] | 352 | If the last command reports same OpenGL renderer with and without
|
---|
| 353 | <envar>DRI_PRIME=1</envar>, you will need to check your installation.
|
---|
[f38727d] | 354 | </para>
|
---|
[2001b3e] | 355 |
|
---|
[da4b5e0] | 356 | </sect2>
|
---|
[2001b3e] | 357 |
|
---|
[d28b5ef] | 358 | <sect2 role="configuration" id='xconfig'>
|
---|
| 359 | <title>Setting up Xorg Devices</title>
|
---|
[c96921c] | 360 |
|
---|
[da4b5e0] | 361 | <para>
|
---|
| 362 | For most hardware configurations, modern Xorg will automatically
|
---|
| 363 | get the server configuration correct without any user intervention. There
|
---|
| 364 | are, however, some cases where auto-configuration will be incorrect.
|
---|
| 365 | Following are some example manual configuration items that may be of use
|
---|
| 366 | in these instances.
|
---|
| 367 | </para>
|
---|
[d28b5ef] | 368 |
|
---|
| 369 | <sect3 id="xinput">
|
---|
[da4b5e0] | 370 | <title>Setting up X Input Devices</title>
|
---|
| 371 | <para>
|
---|
| 372 | For most input devices, no additional configuration will be
|
---|
| 373 | necessary. This section is provided for informational purposes only.
|
---|
| 374 | </para>
|
---|
[0d7900a] | 375 |
|
---|
[da4b5e0] | 376 | <para>
|
---|
| 377 | A sample default XKB setup could look like the following (executed as
|
---|
| 378 | the <systemitem class="username">root</systemitem> user):
|
---|
| 379 | </para>
|
---|
[c96921c] | 380 |
|
---|
[7612749] | 381 | <screen role="root"><userinput>cat > /etc/X11/xorg.conf.d/xkb-defaults.conf << "EOF"
|
---|
[51dfb3e] | 382 | <literal>Section "InputClass"
|
---|
[d28b5ef] | 383 | Identifier "XKB Defaults"
|
---|
| 384 | MatchIsKeyboard "yes"
|
---|
[7612749] | 385 | Option "XkbLayout" "fr"
|
---|
[d28b5ef] | 386 | Option "XkbOptions" "terminate:ctrl_alt_bksp"
|
---|
[51dfb3e] | 387 | EndSection</literal>
|
---|
[d28b5ef] | 388 | EOF</userinput></screen>
|
---|
| 389 |
|
---|
[da4b5e0] | 390 | <para>
|
---|
| 391 | The <quote>XkbLayout</quote> line is an example for a French (AZERTY)
|
---|
| 392 | keyboard. Change it to your keyboard model. That line is not needed for
|
---|
| 393 | a QWERTY (US) keyboard.
|
---|
| 394 | </para>
|
---|
| 395 | </sect3>
|
---|
[d28b5ef] | 396 |
|
---|
[da4b5e0] | 397 | <sect3 id="xdisplay">
|
---|
| 398 | <title>Fine Tuning Display Settings</title>
|
---|
[f3429309] | 399 |
|
---|
[da4b5e0] | 400 | <para>
|
---|
| 401 | Again, with modern Xorg, little or no additional configuration is
|
---|
| 402 | necessary. If you should need extra options passed to your video driver,
|
---|
| 403 | for instance, you could use something like the following (again,
|
---|
| 404 | executed as the <systemitem class="username">root</systemitem> user):
|
---|
| 405 | </para>
|
---|
[d28b5ef] | 406 |
|
---|
[da4b5e0] | 407 | <screen role="root"><userinput>cat > /etc/X11/xorg.conf.d/videocard-0.conf << "EOF"
|
---|
[51dfb3e] | 408 | <literal>Section "Device"
|
---|
[d28b5ef] | 409 | Identifier "Videocard0"
|
---|
| 410 | Driver "radeon"
|
---|
| 411 | VendorName "Videocard vendor"
|
---|
| 412 | BoardName "ATI Radeon 7500"
|
---|
| 413 | Option "NoAccel" "true"
|
---|
[51dfb3e] | 414 | EndSection</literal>
|
---|
[d28b5ef] | 415 | EOF</userinput></screen>
|
---|
| 416 |
|
---|
[da4b5e0] | 417 | <para>
|
---|
| 418 | Another common setup is having multiple server layouts for use in
|
---|
| 419 | different environments. Though the server will automatically detect the
|
---|
| 420 | presence of another monitor, it may get the order incorrect:
|
---|
| 421 | </para>
|
---|
[d28b5ef] | 422 |
|
---|
[da4b5e0] | 423 | <screen role="root"><userinput>cat > /etc/X11/xorg.conf.d/server-layout.conf << "EOF"
|
---|
[51dfb3e] | 424 | <literal>Section "ServerLayout"
|
---|
[d28b5ef] | 425 | Identifier "DefaultLayout"
|
---|
| 426 | Screen 0 "Screen0" 0 0
|
---|
| 427 | Screen 1 "Screen1" LeftOf "Screen0"
|
---|
| 428 | Option "Xinerama"
|
---|
[51dfb3e] | 429 | EndSection</literal>
|
---|
[d28b5ef] | 430 | EOF</userinput></screen>
|
---|
| 431 |
|
---|
[da4b5e0] | 432 | </sect3>
|
---|
[d28b5ef] | 433 | </sect2>
|
---|
| 434 | </sect1>
|
---|