1xorg.conf(5)                  File Formats Manual                 xorg.conf(5)
2
3
4

NAME

6       xorg.conf, xorg.conf.d - configuration files for Xorg X server
7

INTRODUCTION

9       Xorg  supports several mechanisms for supplying/obtaining configuration
10       and run-time parameters: command line options,  environment  variables,
11       the  xorg.conf and xorg.conf.d configuration files, auto-detection, and
12       fallback defaults. When the same information is supplied in  more  than
13       one  way,  the highest precedence mechanism is used. The list of mecha‐
14       nisms is ordered from highest precedence to lowest. Note that  not  all
15       parameters  can be supplied via all methods. The available command line
16       options and environment variables (and some defaults) are described  in
17       the Xserver(1) and Xorg(1) manual pages. Most configuration file param‐
18       eters, with their defaults, are described below. Driver and module spe‐
19       cific  configuration parameters are described in the relevant driver or
20       module manual page.
21

DESCRIPTION

23       Xorg uses a configuration file called xorg.conf and files ending in the
24       suffix .conf from the directory xorg.conf.d for its initial setup.  The
25       xorg.conf configuration file is searched for in  the  following  places
26       when the server is started as a normal user:
27
28           /etc/X11/<cmdline>
29           /usr/etc/X11/<cmdline>
30           /etc/X11/$XORGCONFIG
31           /usr/etc/X11/$XORGCONFIG
32           /etc/X11/xorg.conf
33           /etc/xorg.conf
34           /usr/etc/X11/xorg.conf.<hostname>
35           /usr/etc/X11/xorg.conf
36           /usr/lib/X11/xorg.conf.<hostname>
37           /usr/lib/X11/xorg.conf
38
39       where  <cmdline> is a relative path (with no “..” components) specified
40       with the -config command line option, $XORGCONFIG is the relative  path
41       (with  no  “..” components) specified by that environment variable, and
42       <hostname> is the machine's hostname as reported by gethostname(3).
43
44       When the Xorg server is started by the “root”  user,  the  config  file
45       search locations are as follows:
46
47           <cmdline>
48           /etc/X11/<cmdline>
49           /usr/etc/X11/<cmdline>
50           $XORGCONFIG
51           /etc/X11/$XORGCONFIG
52           /usr/etc/X11/$XORGCONFIG
53           /etc/X11/xorg.conf
54           /etc/xorg.conf
55           /usr/etc/X11/xorg.conf.<hostname>
56           /usr/etc/X11/xorg.conf
57           /usr/lib/X11/xorg.conf.<hostname>
58           /usr/lib/X11/xorg.conf
59
60       where  <cmdline>  is  the  path specified with the -config command line
61       option (which may be absolute or relative),  $XORGCONFIG  is  the  path
62       specified by that environment variable (absolute or relative), $HOME is
63       the path specified by  that  environment  variable  (usually  the  home
64       directory),  and  <hostname>  is  the machine's hostname as reported by
65       gethostname(3).
66
67       Additional configuration files are searched for in the following direc‐
68       tories when the server is started as a normal user:
69
70           /etc/X11/<cmdline>
71           /etc/X11/<cmdline>
72           /etc/X11/xorg.conf.d
73           /etc/X11/xorg.conf.d
74
75       where  <cmdline> is a relative path (with no “..” components) specified
76       with the -configdir command line option.
77
78       When the Xorg server is started by the “root” user, the  config  direc‐
79       tory search locations are as follows:
80
81           <cmdline>
82           /etc/X11/<cmdline>
83           /etc/X11/<cmdline>
84           /etc/X11/xorg.conf.d
85           /etc/X11/xorg.conf.d
86
87       where  <cmdline> is the path specified with the -configdir command line
88       option (which may be absolute or relative).
89
90       Finally, configuration files will also be searched for in  a  directory
91       reserved  for system use.  This is to separate configuration files from
92       the vendor or 3rd party packages from those  of  local  administration.
93       These files are found in the following directory:
94
95           /usr/share/X11/xorg.conf.d
96
97       The  xorg.conf  and  xorg.conf.d files are composed of a number of sec‐
98       tions which may be present in any order, or omitted to use default con‐
99       figuration values.  Each section has the form:
100
101           Section  "SectionName"
102               SectionEntry
103               ...
104           EndSection
105
106       The section names are:
107
108           Files          File pathnames
109           ServerFlags    Server flags
110           Module         Dynamic module loading
111           Extensions     Extension enabling
112           InputDevice    Input device description
113           InputClass     Input class description
114           OutputClass    Output class description
115           Device         Graphics device description
116           VideoAdaptor   Xv video adaptor description
117           Monitor        Monitor description
118           Modes          Video modes descriptions
119           Screen         Screen configuration
120           ServerLayout   Overall layout
121           DRI            DRI-specific configuration
122           Vendor         Vendor-specific configuration
123
124       The  following obsolete section names are still recognised for compati‐
125       bility purposes.  In new config files, the InputDevice  section  should
126       be used instead.
127
128           Keyboard       Keyboard configuration
129           Pointer        Pointer/mouse configuration
130
131       The old XInput section is no longer recognised.
132
133       The ServerLayout sections are at the highest level.  They bind together
134       the input and output devices that will be used in a session.  The input
135       devices are described in the InputDevice sections.  Output devices usu‐
136       ally consist of multiple independent components (e.g., a graphics board
137       and  a  monitor).   These multiple components are bound together in the
138       Screen sections, and it is these that are referenced by the  ServerLay‐
139       out section.  Each Screen section binds together a graphics board and a
140       monitor.  The graphics boards are described in the Device sections, and
141       the monitors are described in the Monitor sections.
142
143       Config  file  keywords  are  case-insensitive,  and  “_” characters are
144       ignored.  Most strings (including Option names) are also  case-insensi‐
145       tive, and insensitive to white space and “_” characters.
146
147       Each  config  file  entry  usually  takes up a single line in the file.
148       They consist of a keyword, which is possibly followed by  one  or  more
149       arguments,  with the number and types of the arguments depending on the
150       keyword.  The argument types are:
151
152           Integer     an integer number in decimal, hex or octal
153           Real        a floating point number
154           String      a string enclosed in double quote marks (")
155
156       Note: hex integer values must be prefixed with “0x”, and  octal  values
157       with “0”.
158
159       A  special  keyword called Option may be used to provide free-form data
160       to various components of the server.  The Option keyword  takes  either
161       one  or  two  string  arguments.  The first is the option name, and the
162       optional second argument is  the  option  value.   Some  commonly  used
163       option value types include:
164
165           Integer     an integer number in decimal, hex or octal
166           Real        a floating point number
167           String      a sequence of characters
168           Boolean     a boolean value (see below)
169           Frequency   a frequency value (see below)
170
171       Note  that  all  Option  values,  not just strings, must be enclosed in
172       quotes.
173
174       Boolean options may optionally have a value specified.  When  no  value
175       is specified, the option's value is TRUE.  The following boolean option
176       values are recognised as TRUE:
177
178           1, on, true, yes
179
180       and the following boolean option values are recognised as FALSE:
181
182           0, off, false, no
183
184       If an option name is prefixed with  "No",  then  the  option  value  is
185       negated.
186
187       Example: the following option entries are equivalent:
188
189           Option "Accel"   "Off"
190           Option "NoAccel"
191           Option "NoAccel" "On"
192           Option "Accel"   "false"
193           Option "Accel"   "no"
194
195       Frequency  option  values  consist  of a real number that is optionally
196       followed by one of the following frequency units:
197
198           Hz, k, kHz, M, MHz
199
200       When the unit name is omitted, the correct  units  will  be  determined
201       from  the  value  and  the expectations of the appropriate range of the
202       value.  It is recommended that the units always be specified when using
203       frequency option values to avoid any errors in determining the value.
204

FILES SECTION

206       The  Files  section  is used to specify some path names required by the
207       server.  Some of these paths can also be set from the command line (see
208       Xserver(1) and Xorg(1)).  The command line settings override the values
209       specified in the config file.  The Files section is  optional,  as  are
210       all of the entries that may appear in it.
211
212       The entries that can appear in this section are:
213
214       FontPath "path"
215              sets  the search path for fonts.  This path is a comma separated
216              list of font path elements which the Xorg  server  searches  for
217              font databases.  Multiple FontPath entries may be specified, and
218              they will be concatenated to build up the fontpath used  by  the
219              server.   Font  path  elements  can be absolute directory paths,
220              catalogue directories or a font server identifier.  The  formats
221              of the later two are explained below:
222
223              Catalogue directories:
224
225                  Catalogue directories can be specified using the prefix cat‐
226                  alogue: before the directory name. The directory can then be
227                  populated  with  symlinks pointing to the real font directo‐
228                  ries, using the following syntax in the symlink name:
229
230                      <identifier>:[attribute]:pri=<priority>
231
232                  where   <identifier>   is   an   alphanumeric    identifier,
233                  [attribute]  is  an  attribute  which  will be passed to the
234                  underlying FPE and <priority> is a number used to order  the
235                  fontfile FPEs. Examples:
236
237                      75dpi:unscaled:pri=20 -> /usr/share/X11/fonts/75dpi
238                      gscript:pri=60 -> /usr/share/fonts/default/ghostscript
239                      misc:unscaled:pri=10 -> /usr/share/X11/fonts/misc
240
241              Font server identifiers:
242
243                  Font server identifiers have the form:
244
245                      <trans>/<hostname>:<port-number>
246
247                  where <trans> is the transport type to use to connect to the
248                  font server (e.g., unix for UNIX-domain sockets or tcp for a
249                  TCP/IP  connection),  <hostname>  is  the  hostname  of  the
250                  machine running the font server, and  <port-number>  is  the
251                  port  number  that  the font server is listening on (usually
252                  7100).
253
254              When this entry is not specified in the config file, the  server
255              falls  back to the compiled-in default font path, which contains
256              the following font path elements (which can be set inside a cat‐
257              alogue directory):
258
259                  /usr/share/fonts/X11/misc/
260                  /usr/share/fonts/X11/TTF/
261                  /usr/share/fonts/X11/OTF/
262                  /usr/share/fonts/X11/Type1/
263                  /usr/share/fonts/X11/100dpi/
264                  /usr/share/fonts/X11/75dpi/
265
266              Font path elements that are found to be invalid are removed from
267              the font path when the server starts up.
268
269       ModulePath "path"
270              sets the search path for loadable  Xorg  server  modules.   This
271              path  is  a  comma  separated list of directories which the Xorg
272              server searches for loadable modules loading in the order speci‐
273              fied.   Multiple  ModulePath  entries may be specified, and they
274              will be concatenated to build the module search path used by the
275              server.  The default module path is
276
277                  /usr/lib64/xorg/modules
278
279       XkbDir "path"
280              sets  the base directory for keyboard layout files.  The -xkbdir
281              command line option can be used to override this.   The  default
282              directory is
283
284                  /usr/share/X11/xkb
285

SERVERFLAGS SECTION

287       In  addition to options specific to this section (described below), the
288       ServerFlags section is used to specify some global Xorg server options.
289       All  of  the entries in this section are Options, although for compati‐
290       bility purposes some of the old style  entries  are  still  recognised.
291       Those old style entries are not documented here, and using them is dis‐
292       couraged.  The ServerFlags section is optional, as are the entries that
293       may be specified in it.
294
295       Options  specified in this section (with the exception of the "Default‐
296       ServerLayout" Option) may be overridden by  Options  specified  in  the
297       active ServerLayout section.  Options with command line equivalents are
298       overridden when their command line equivalent  is  used.   The  options
299       recognised by this section are:
300
301       Option "Debug"  "string"
302              This  comma-separated  list  provides  a  way to control various
303              debugging switches from the config file.  At the moment the only
304              defined value is dmabuf_capable which instructs glamor to enable
305              some unstable buffer management code.
306
307       Option "DefaultServerLayout"  "layout-id"
308              This specifies the default ServerLayout section to  use  in  the
309              absence of the -layout command line option.
310
311       Option "NoTrapSignals"  "boolean"
312              This  prevents  the  Xorg  server from trapping a range of unex‐
313              pected fatal signals and exiting  cleanly.   Instead,  the  Xorg
314              server  will  die  and  drop core where the fault occurred.  The
315              default behaviour is for the Xorg server to  exit  cleanly,  but
316              still  drop  a core file.  In general you never want to use this
317              option unless you are debugging an Xorg server problem and  know
318              how to deal with the consequences.
319
320       Option "DontVTSwitch"  "boolean"
321              This  disallows  the  use  of the Ctrl+Alt+Fn sequence (where Fn
322              refers to one of the numbered function keys).  That sequence  is
323              normally used to switch to another "virtual terminal" on operat‐
324              ing systems  that  have  this  feature.   When  this  option  is
325              enabled,  that key sequence has no special meaning and is passed
326              to clients.  Default: off.
327
328       Option "DontZap"  "boolean"
329              This disallows the use of the Terminate_Server XKB action  (usu‐
330              ally  on  Ctrl+Alt+Backspace,  depending  on XKB options).  This
331              action is normally used to terminate the Xorg server.  When this
332              option is enabled, the action has no effect.  Default: off.
333
334       Option "DontZoom"  "boolean"
335              This   disallows   the   use  of  the  Ctrl+Alt+Keypad-Plus  and
336              Ctrl+Alt+Keypad-Minus sequences.  These sequences allows you  to
337              switch  between video modes.  When this option is enabled, those
338              key sequences have no special meaning and are passed to clients.
339              Default: off.
340
341       Option "DisableVidModeExtension"  "boolean"
342              This  disables  the  parts  of the VidMode extension used by the
343              xvidtune client that can be used  to  change  the  video  modes.
344              Default: the VidMode extension is enabled.
345
346       Option "AllowNonLocalXvidtune"  "boolean"
347              This  allows the xvidtune client (and other clients that use the
348              VidMode extension) to connect from another host.  Default: off.
349
350       Option "AllowMouseOpenFail"  "boolean"
351              This tells the mousedrv(4) and vmmouse(4) drivers to not  report
352              failure if the mouse device can't be opened/initialised.  It has
353              no effect on the evdev(4) or other drivers.  Default: false.
354
355       Option "BlankTime"  "time"
356              sets the inactivity timeout for the blank phase of  the  screen‐
357              saver.   time  is  in  minutes.   This is equivalent to the Xorg
358              server's -s flag, and the value can be changed at run-time  with
359              xset(1).  Default: 10 minutes.
360
361       Option "StandbyTime"  "time"
362              sets  the inactivity timeout for the standby phase of DPMS mode.
363              time is in minutes, and the value can  be  changed  at  run-time
364              with  xset(1).   Default: 10 minutes.  This is only suitable for
365              VESA DPMS compatible monitors, and may not be supported  by  all
366              video  drivers.   It  is  only enabled for screens that have the
367              "DPMS" option set (see the MONITOR section below).
368
369       Option "SuspendTime"  "time"
370              sets the inactivity timeout for the suspend phase of DPMS  mode.
371              time  is  in  minutes,  and the value can be changed at run-time
372              with xset(1).  Default: 10 minutes.  This is only  suitable  for
373              VESA  DPMS  compatible monitors, and may not be supported by all
374              video drivers.  It is only enabled for  screens  that  have  the
375              "DPMS" option set (see the MONITOR section below).
376
377       Option "OffTime"  "time"
378              sets  the  inactivity  timeout  for  the off phase of DPMS mode.
379              time is in minutes, and the value can  be  changed  at  run-time
380              with  xset(1).   Default: 10 minutes.  This is only suitable for
381              VESA DPMS compatible monitors, and may not be supported  by  all
382              video  drivers.   It  is  only enabled for screens that have the
383              "DPMS" option set (see the MONITOR section below).
384
385       Option "MaxClients"  "integer"
386              Set the maximum number of clients allowed to connect  to  the  X
387              server.  Acceptable values are 64, 128, 256 or 512.
388
389       Option "NoPM"  "boolean"
390              Disables something to do with power management events.  Default:
391              PM enabled on platforms that support it.
392
393       Option "Xinerama"  "boolean"
394              enable or disable XINERAMA extension.  Default is disabled.
395
396       Option "IndirectGLX" "boolean"
397              enable or disable indirect GLX contexts. Indirect  GLX  contexts
398              are disabled by default.
399
400       Option "DRI2" "boolean"
401              enable or disable DRI2. DRI2 is disabled by default.
402
403       Option "GlxVisuals" "string"
404              This  option  controls how many GLX visuals the GLX modules sets
405              up.  The default value is typical, which will setup up a typical
406              subset  of  the GLXFBConfigs provided by the driver as GLX visu‐
407              als.  Other options are minimal, which will set up  the  minimal
408              set  allowed  by  the GLX specification and all which will setup
409              GLX visuals for all GLXFBConfigs.
410
411       Option "UseDefaultFontPath" "boolean"
412              Include the default font path even if other paths are  specified
413              in xorg.conf. If enabled, other font paths are included as well.
414              Enabled by default.
415
416       Option "IgnoreABI" "boolean"
417              Allow modules built for a  different,  potentially  incompatible
418              version of the X server to load. Disabled by default.
419
420       Option "AutoAddDevices" "boolean"
421              If  this  option is disabled, then no devices will be added from
422              the HAL or udev backends. Enabled by default.
423
424       Option "AutoEnableDevices" "boolean"
425              If this option is disabled, then the devices will be added  (and
426              the  DevicePresenceNotify  event  sent),  but  not enabled, thus
427              leaving policy up to the client.  Enabled by default.
428
429       Option "AutoAddGPU" "boolean"
430              If this option is disabled, then no GPU devices  will  be  added
431              from  the udev backend. Enabled by default. (May need to be dis‐
432              abled to setup Xinerama).
433
434       Option "AutoBindGPU"  "boolean"
435              If enabled then secondary GPUs will be automatically set  up  as
436              output-sinks  and  offload-sources.  Making  e.g. laptop outputs
437              connected only to the secondary GPU directly available  for  use
438              without   needing  to  run  "xrandr  --setprovideroutputsource".
439              Enabled by default.
440
441       Option "Log" "string"
442              This option controls whether the log is flushed and/or synced to
443              disk  after  each  message.   Possible values are flush or sync.
444              Unset by default.
445

MODULE SECTION

447       The Module section is used to specify which Xorg server modules  should
448       be  loaded.   This  section is ignored when the Xorg server is built in
449       static form.  The type of modules normally loaded in this  section  are
450       Xorg  server  extension  modules.   Most  other module types are loaded
451       automatically when they are needed via other  mechanisms.   The  Module
452       section is optional, as are all of the entries that may be specified in
453       it.
454
455       Entries in this section may be in two forms.  The first and  most  com‐
456       monly  used  form  is an entry that uses the Load keyword, as described
457       here:
458
459       Load  "modulename"
460              This instructs the server to load the module called  modulename.
461              The  module name given should be the module's standard name, not
462              the module file name.  The standard name is case-sensitive,  and
463              does  not  include  the “lib” or “cyg” prefixes, or the “.so” or
464              “.dll” suffixes.
465
466              Example: the DRI extension module can be loaded with the follow‐
467              ing entry:
468
469                  Load "dri"
470
471       Disable  "modulename"
472              This  instructs the server to not load the module called module‐
473              name.  Some modules are loaded by default  in  the  server,  and
474              this  overrides that default. If a Load instruction is given for
475              the same module, it overrides the Disable  instruction  and  the
476              module  is  loaded. The module name given should be the module's
477              standard name, not the  module  file  name.  As  with  the  Load
478              instruction,  the  standard name is case-sensitive, and does not
479              include the "lib" prefix, or the ".a", ".o", or ".so" suffixes.
480
481       The second form of entry is a  SubSection,  with  the  subsection  name
482       being the module name, and the contents of the SubSection being Options
483       that are passed to the module when it is loaded.
484
485       Example: the extmod module (which contains  a  miscellaneous  group  of
486       server  extensions)  can be loaded, with the XFree86-DGA extension dis‐
487       abled by using the following entry:
488
489           SubSection "extmod"
490              Option  "omit XFree86-DGA"
491           EndSubSection
492
493       Modules are searched for in each directory specified in the  ModulePath
494       search  path, and in the drivers, extensions, input, internal, and mul‐
495       timedia subdirectories of each of those directories.   In  addition  to
496       this,  operating  system  specific  subdirectories of all the above are
497       searched first if they exist.
498
499       To see what extension modules are available, check the extensions  sub‐
500       directory under:
501
502           /usr/lib64/xorg/modules
503
504       The  “extmod”, “dbe”, “dri”, “dri2”, “glx”, and “record” extension mod‐
505       ules are loaded automatically, if they  are  present,  unless  disabled
506       with  "Disable"  entries.   It  is  recommended  that at very least the
507       “extmod” extension module be loaded.  If it isn't, some  commonly  used
508       server extensions (like the SHAPE extension) will not be available.
509

EXTENSIONS SECTION

511       The Extensions section is used to specify which X11 protocol extensions
512       should be enabled or disabled.  The Extensions section is optional,  as
513       are all of the entries that may be specified in it.
514
515       Entries  in  this section are listed as Option statements with the name
516       of the extension as the first argument, and a boolean value as the sec‐
517       ond.   The extension name is case-sensitive, and matches the form shown
518       in the output of "Xorg -extension ?".
519
520              Example: the MIT-SHM extension can be disabled with the  follow‐
521              ing entry:
522
523                  Section "Extensions"
524                      Option "MIT-SHM" "Disable"
525                  EndSection
526

INPUTDEVICE SECTION

528       The  config  file  may  have  multiple  InputDevice sections.  Recent X
529       servers employ HAL or udev backends for input  device  enumeration  and
530       input  hotplugging.  It is usually not necessary to provide InputDevice
531       sections in the xorg.conf if hotplugging is in use (i.e. AutoAddDevices
532       is  enabled). If hotplugging is enabled, InputDevice sections using the
533       mouse, kbd and vmmouse driver will be ignored.
534
535       If hotplugging is disabled, there will normally be at  least  two:  one
536       for  the  core  (primary)  keyboard  and  one for the core pointer.  If
537       either of these two is missing, a default configuration for the missing
538       ones will be used. In the absence of an explicitly specified core input
539       device, the first InputDevice marked as CorePointer  (or  CoreKeyboard)
540       is  used.   If there is no match there, the first InputDevice that uses
541       the “mouse” (or “kbd”) driver is used.  The final fallback  is  to  use
542       built-in  default  configurations.  Currently the default configuration
543       may not work as expected on all platforms.
544
545       InputDevice sections have the following format:
546
547           Section "InputDevice"
548               Identifier "name"
549               Driver     "inputdriver"
550               options
551               ...
552           EndSection
553
554       The Identifier and Driver entries are required in all InputDevice  sec‐
555       tions.  All other entries are optional.
556
557       The  Identifier  entry specifies the unique name for this input device.
558       The Driver entry specifies the name of the driver to use for this input
559       device.   When  using  the  loadable  server,  the  input driver module
560       "inputdriver" will be loaded for each active InputDevice  section.   An
561       InputDevice  section  is  considered  active  if it is referenced by an
562       active ServerLayout section, if it is referenced by  the  -keyboard  or
563       -pointer  command  line options, or if it is selected implicitly as the
564       core pointer or keyboard device in the absence of such explicit  refer‐
565       ences.  The most commonly used input drivers are evdev(4) on Linux sys‐
566       tems, and kbd(4) and mousedrv(4) on other platforms.
567
568       InputDevice sections recognise some driver-independent  Options,  which
569       are described here.  See the individual input driver manual pages for a
570       description of the device-specific options.
571
572       Option "AutoServerLayout"  "boolean"
573              Always add the device to the ServerLayout section used  by  this
574              instance  of the server. This affects implied layouts as well as
575              explicit layouts specified in the configuration  and/or  on  the
576              command line.
577
578       Option "CorePointer"
579              Deprecated, see Floating
580
581       Option "CoreKeyboard"
582              Deprecated, see Floating
583
584       Option "AlwaysCore"  "boolean"
585              Deprecated, see Floating
586
587       Option "SendCoreEvents"  "boolean"
588              Deprecated, see Floating
589
590
591       Option "Floating"  "boolean"
592              When  enabled,  the input device is set up floating and does not
593              report events through any master device or control a cursor. The
594              device  is only available to clients using the X Input Extension
595              API. This option is disabled  by  default.   The  options  Core‐
596              Pointer,  CoreKeyboard,  AlwaysCore, and SendCoreEvents, are the
597              inverse of option Floating (i.e.  SendCoreEvents "on" is equiva‐
598              lent to Floating "off" ).
599
600              This  option controls the startup behavior only, a device may be
601              reattached or set floating at runtime.
602
603       Option "TransformationMatrix" "a b c d e f g h i"
604              Specifies the  3x3  transformation  matrix  for  absolute  input
605              devices. The input device will be bound to the area given in the
606              matrix.  In most configurations, "a" and "e" specify  the  width
607              and  height  of the area the device is bound to, and "c" and "f"
608              specify the x and y offset of the area.  The value range is 0 to
609              1,  where  1  represents the width or height of all root windows
610              together, 0.5 represents half the area, etc. The  values  repre‐
611              sent  a  3x3  matrix,  with the first, second and third group of
612              three values representing the first, second and third row of the
613              matrix,  respectively.   The identity matrix is "1 0 0 0 1 0 0 0
614              1".
615
616   POINTER ACCELERATION
617       For pointing devices, the following options control how the pointer  is
618       accelerated or decelerated with respect to physical device motion. Most
619       of these can be adjusted at runtime, see the  xinput(1)  man  page  for
620       details.  Only  the  most  important acceleration options are discussed
621       here.
622
623       Option "AccelerationProfile"  "integer"
624              Select the profile. In layman's terms, the  profile  constitutes
625              the "feeling" of the acceleration. More formally, it defines how
626              the transfer function (actual acceleration as a function of cur‐
627              rent  device velocity and acceleration controls) is constructed.
628              This is mainly a matter of personal preference.
629
630              0      classic (mostly compatible)
631             -1      none (only constant deceleration is applied)
632              1      device-dependent
633              2      polynomial (polynomial function)
634              3      smooth linear (soft knee, then linear)
635              4      simple (normal when slow, otherwise accelerated)
636              5      power (power function)
637              6      linear (more speed, more acceleration)
638              7      limited (like linear, but maxes out at threshold)
639
640       Option "ConstantDeceleration"  "real"
641              Makes the pointer go deceleration times slower than normal. Most
642              useful for high-resolution devices. A value between 0 and 1 will
643              speed up the pointer.
644
645       Option "AdaptiveDeceleration"  "real"
646              Allows to actually decelerate the pointer when  going  slow.  At
647              most,  it  will  be  adaptive deceleration times slower. Enables
648              precise pointer placement without sacrificing speed.
649
650       Option "AccelerationScheme"  "string"
651              Selects the scheme, which is the underlying algorithm.
652
653              predictable   default algorithm (behaving more predictable)
654              lightweight   old acceleration code (as specified in the X protocol spec)
655              none          no acceleration or deceleration
656
657       Option "AccelerationNumerator"  "integer"
658
659       Option "AccelerationDenominator"  "integer"
660              Set numerator and denominator of the  acceleration  factor.  The
661              acceleration  factor  is a rational which, together with thresh‐
662              old, can be used to tweak profiles to suit the users needs.  The
663              simple  and limited profiles use it directly (i.e. they acceler‐
664              ate by the factor), for other profiles it  should  hold  that  a
665              higher acceleration factor leads to a faster pointer. Typically,
666              1 is unaccelerated and values up to 5 are sensible.
667
668       Option "AccelerationThreshold"  "integer"
669              Set the threshold, which is roughly the velocity (usually device
670              units  per 10 ms) required for acceleration to become effective.
671              The precise effect varies with the profile however.
672
673

INPUTCLASS SECTION

675       The config file may have multiple InputClass sections.  These  sections
676       are optional and are used to provide configuration for a class of input
677       devices as they are automatically added. An input device can match more
678       than  one  InputClass  section. Each class can override settings from a
679       previous class, so it is best to arrange the  sections  with  the  most
680       generic matches first.
681
682       InputClass sections have the following format:
683
684           Section "InputClass"
685               Identifier  "name"
686               entries
687               ...
688               options
689               ...
690           EndSection
691
692       The Identifier entry is required in all InputClass sections.  All other
693       entries are optional.
694
695       The Identifier entry specifies the unique name for  this  input  class.
696       The Driver entry specifies the name of the driver to use for this input
697       device.  After all classes have been examined, the "inputdriver" module
698       from  the  first  Driver  entry will be enabled when using the loadable
699       server.
700
701       When an input device is automatically added,  its  characteristics  are
702       checked  against  all  InputClass  sections.  Each  section can contain
703       optional entries to narrow the match of  the  class.  If  none  of  the
704       optional  entries  appear,  the  InputClass section is generic and will
705       match any input device. If more than one of these entries appear,  they
706       all must match for the configuration to apply.
707
708       There  are  two types of match entries used in InputClass sections. The
709       first allows various tokens to be matched  against  attributes  of  the
710       device.  An entry can be constructed to match attributes from different
711       devices by separating arguments with a '|' character. Multiple  entries
712       of the same type may be supplied to add multiple matching conditions on
713       the same attribute. For example:
714
715           Section "InputClass"
716               Identifier   "My Class"
717               # product string must contain example and
718               # either gizmo or gadget
719               MatchProduct "example"
720               MatchProduct "gizmo|gadget"
721               NoMatchDriver "drivername"
722               ...
723           EndSection
724
725       MatchProduct  "matchproduct"
726              This entry can be used to check if the substring  "matchproduct"
727              occurs in the device's product name.
728
729       MatchVendor  "matchvendor"
730              This  entry  can be used to check if the substring "matchvendor"
731              occurs in the device's vendor name.
732
733       MatchDevicePath "matchdevice"
734              This entry can be used to check if the device file  matches  the
735              "matchdevice" pathname pattern.
736
737       MatchOS "matchos"
738              This  entry can be used to check if the operating system matches
739              the case-insensitive "matchos" string. This entry is  only  sup‐
740              ported on platforms providing the uname(2) system call.
741
742       MatchPnPID "matchpnp"
743              The  device's  Plug and Play (PnP) ID can be checked against the
744              "matchpnp" shell wildcard pattern.
745
746       MatchUSBID "matchusb"
747              The device's USB ID can be checked against the "matchusb"  shell
748              wildcard pattern. The ID is constructed as lowercase hexadecimal
749              numbers separated by a ':'. This  is  the  same  format  as  the
750              lsusb(8) program.
751
752       MatchDriver "matchdriver"
753              Check  the  case-sensitive string "matchdriver" against the cur‐
754              rently configured driver of the  device.  Ordering  of  sections
755              using this entry is important since it will not match unless the
756              driver has been set by the config backend or a  previous  Input‐
757              Class section.
758
759       MatchTag "matchtag"
760              This  entry  can be used to check if tags assigned by the config
761              backend matches the "matchtag" pattern. A match is found  if  at
762              least  one  of the tags given in "matchtag" matches at least one
763              of the tags assigned by the backend.
764
765       MatchLayout "matchlayout"
766              Check the case-sensitive string "matchlayout" against  the  cur‐
767              rently  active ServerLayout section. The empty string "" matches
768              an implicit layout which appears if no named  ServerLayout  sec‐
769              tions have been found.
770
771       The  above  directives  have equivalents for negative matching with the
772       NoMatchProduct, NoMatchVendor, NoMatchDevicePath, NoMatchOS, NoMatchPn‐
773       PID,  NoMatchUSBID, NoMatchDriver, NoMatchTag, and NoMatchLayout direc‐
774       tives. These NoMatch directives match if the subsequent  match  is  not
775       met by the device.
776
777       The  second  type of entry is used to match device types. These entries
778       take a boolean argument similar to Option entries.
779
780       MatchIsKeyboard     "bool"
781
782       MatchIsPointer      "bool"
783
784       MatchIsJoystick     "bool"
785
786       MatchIsTablet       "bool"
787
788       MatchIsTabletPad    "bool"
789
790       MatchIsTouchpad     "bool"
791
792       MatchIsTouchscreen  "bool"
793
794       When an input device has been matched to the  InputClass  section,  any
795       Option  entries  are  applied  to  the  device. One InputClass specific
796       Option is recognized. See the InputDevice section above for a  descrip‐
797       tion of the remaining Option entries.
798
799       Option "Ignore" "boolean"
800              This  optional entry specifies that the device should be ignored
801              entirely, and not added to the server. This can be  useful  when
802              the  device is handled by another program and no X events should
803              be generated.
804

OUTPUTCLASS SECTION

806       The config file may have multiple OutputClass sections.  These sections
807       are  optional and are used to provide configuration for a class of out‐
808       put devices as they are automatically  added.   An  output  device  can
809       match  more than one OutputClass section.  Each class can override set‐
810       tings from a previous class, so it is best to arrange the sections with
811       the most generic matches first.
812
813       OutputClass sections have the following format:
814
815           Section "OutputClass"
816               Identifier  "name"
817               entries
818               ...
819           EndSection
820
821       The  Identifier  entry  is  required  in all OutputClass sections.  All
822       other entries are optional.
823
824       The Identifier entry specifies the unique name for this  output  class.
825       The  Driver entry specifies the name of the driver to use for this out‐
826       put device.  After all classes have been examined,  the  "outputdriver"
827       module from the first Driver entry will be enabled when using the load‐
828       able server.
829
830       When an output device is automatically added, its  characteristics  are
831       checked  against  all  OutputClass  sections.  Each section can contain
832       optional entries to narrow the match of the  class.   If  none  of  the
833       optional  entries  appear,  the OutputClass section is generic and will
834       match any output device.  If more than one  of  these  entries  appear,
835       they all must match for the configuration to apply.
836
837       The  following  list of tokens can be matched against attributes of the
838       device.  An entry can be constructed to match attributes from different
839       devices by separating arguments with a '|' character.
840
841       For example:
842
843           Section "OutputClass"
844               Identifier   "My Class"
845               # kernel driver must be either foo or bar
846               MatchDriver "foo|bar"
847               ...
848           EndSection
849
850       MatchDriver "matchdriver"
851              Check the case-sensitive string "matchdriver" against the kernel
852              driver of the device.
853
854       When an output device has been matched to the OutputClass section,  any
855       Option  entries  are  applied  to  the device. One OutputClass specific
856       Option is recognized. See the Device section below for a description of
857       the remaining Option entries.
858
859       Option "PrimaryGPU" "boolean"
860              This  option specifies that the matched device should be treated
861              as the primary GPU, replacing the selection of the GPU  used  as
862              output by the firmware. If multiple output devices match an Out‐
863              putClass section with the PrimaryGPU option set, the  first  one
864              enumerated becomes the primary GPU.
865
866       A  OutputClass  Section  may contain ModulePath entries. When an output
867       device matches an OutputClass section, any ModulePath entries  in  that
868       OutputClass  are pre-pended to the search path for loadable Xorg server
869       modules. See ModulePath in the Files section for more info.
870

DEVICE SECTION

872       The config file may have multiple Device sections.  There  must  be  at
873       least one, for the video card being used.
874
875       Device sections have the following format:
876
877           Section "Device"
878               Identifier "name"
879               Driver     "driver"
880               entries
881               ...
882           EndSection
883
884       The  Identifier and Driver entries are required in all Device sections.
885       All other entries are optional.
886
887       The Identifier entry  specifies  the  unique  name  for  this  graphics
888       device.   The  Driver entry specifies the name of the driver to use for
889       this graphics device.  When using the loadable server, the driver  mod‐
890       ule  "driver"  will be loaded for each active Device section.  A Device
891       section is considered active if it is referenced by  an  active  Screen
892       section.
893
894       Device  sections recognise some driver-independent entries and Options,
895       which  are  described  here.   Not  all  drivers  make  use  of   these
896       driver-independent  entries,  and  many  of those that do don't require
897       them to be specified because the information is auto-detected.  See the
898       individual  graphics  driver manual pages for further information about
899       this, and for a description of the device-specific options.  Note  that
900       most  of  the  Options  listed  here (but not the other entries) may be
901       specified in the Screen section instead of here in the Device section.
902
903       BusID  "bus-id"
904              This specifies the bus  location  of  the  graphics  card.   For
905              PCI/AGP    cards,    the    bus-id    string    has   the   form
906              PCI:bus@domain:device:function  (e.g.,  “PCI:1@0:0:0”  might  be
907              appropriate for an AGP card). The "@domain" part can be left out
908              for PCI domain 0. This field is usually optional in  single-head
909              configurations  when using the primary graphics card.  In multi-
910              head configurations, or when using a secondary graphics card  in
911              a  single-head configuration, this entry is mandatory.  Its main
912              purpose is to make an unambiguous connection between the  device
913              section  and  the hardware it is representing.  This information
914              can usually be found by running the pciaccess tool scanpci.
915
916       Screen  number
917              This option is mandatory for cards where a single PCI entity can
918              drive more than one display (i.e., multiple CRTCs sharing a sin‐
919              gle graphics accelerator and video memory).  One Device  section
920              is  required  for each head, and this parameter determines which
921              head each of the Device sections applies to.  The  legal  values
922              of  number  range  from  0  to one less than the total number of
923              heads per entity.  Most drivers require that the primary  screen
924              (0) be present.
925
926       Chipset  "chipset"
927              This  usually  optional  entry specifies the chipset used on the
928              graphics board.  In  most  cases  this  entry  is  not  required
929              because  the  drivers  will  probe the hardware to determine the
930              chipset type.  Don't specify it unless the driver-specific docu‐
931              mentation recommends that you do.
932
933       Ramdac  "ramdac-type"
934              This  optional  entry  specifies  the type of RAMDAC used on the
935              graphics board.  This is only used by a few of the drivers,  and
936              in  most cases it is not required because the drivers will probe
937              the hardware to determine the RAMDAC type where possible.  Don't
938              specify  it  unless the driver-specific documentation recommends
939              that you do.
940
941       DacSpeed  speed
942
943       DacSpeed  speed-8 speed-16 speed-24 speed-32
944              This optional entry specifies the RAMDAC speed rating (which  is
945              usually printed on the RAMDAC chip).  The speed is in MHz.  When
946              one value is given, it applies to all framebuffer  pixel  sizes.
947              When  multiple  values  are given, they apply to the framebuffer
948              pixel sizes 8, 16, 24 and 32 respectively.  This is not used  by
949              many drivers, and only needs to be specified when the speed rat‐
950              ing of the RAMDAC is different from the  defaults  built  in  to
951              driver,  or  when  the  driver  can't  auto-detect  the  correct
952              defaults.  Don't specify it unless the driver-specific  documen‐
953              tation recommends that you do.
954
955       Clocks  clock ...
956              specifies the pixel that are on your graphics board.  The clocks
957              are in MHz, and may be specified as  a  floating  point  number.
958              The value is stored internally to the nearest kHz.  The ordering
959              of the clocks is important.  It must match the  order  in  which
960              they  are selected on the graphics board.  Multiple Clocks lines
961              may be specified, and each is concatenated  to  form  the  list.
962              Most  drivers do not use this entry, and it is only required for
963              some older boards with non-programmable clocks.   Don't  specify
964              this  entry  unless the driver-specific documentation explicitly
965              recommends that you do.
966
967       ClockChip  "clockchip-type"
968              This optional entry is used to specify the clock  chip  type  on
969              graphics boards which have a programmable clock generator.  Only
970              a few  Xorg  drivers  support  programmable  clock  chips.   For
971              details, see the appropriate driver manual page.
972
973       VideoRam  mem
974              This  optional  entry  specifies the amount of video ram that is
975              installed on the graphics board.  This is  measured  in  kBytes.
976              In  most  cases  this  is  not  required because the Xorg server
977              probes the graphics  board  to  determine  this  quantity.   The
978              driver-specific  documentation  should indicate when it might be
979              needed.
980
981       MemBase  baseaddress
982              This optional entry specifies  the  memory  base  address  of  a
983              graphics board's linear frame buffer.  This entry is not used by
984              many drivers, and it should only be specified if the driver-spe‐
985              cific documentation recommends it.
986
987       IOBase  baseaddress
988              This  optional  entry specifies the IO base address.  This entry
989              is not used by many drivers, and it should only be specified  if
990              the driver-specific documentation recommends it.
991
992       ChipID  id
993              This  optional  entry  specifies a numerical ID representing the
994              chip type.  For PCI cards, it is usually the  device  ID.   This
995              can be used to override the auto-detection, but that should only
996              be done when the driver-specific documentation recommends it.
997
998       ChipRev  rev
999              This optional entry specifies the chip  revision  number.   This
1000              can be used to override the auto-detection, but that should only
1001              be done when the driver-specific documentation recommends it.
1002
1003       MatchSeat  seat-id
1004              Only apply this Device section if  X  server  was  started  with
1005              -seat seat-id option.
1006
1007       Option "ModeDebug" "boolean"
1008              Enable  printing of additional debugging information about mode‐
1009              setting to the server log.
1010
1011       Option "PreferCloneMode" "boolean"
1012              If enabled, bring up monitors of a screen in clone mode  instead
1013              of  horizontal extended layout by default. (Defaults to off; the
1014              video driver can change the default value, but this  option  can
1015              always override it)
1016
1017       Options
1018              Option  flags  may  be  specified in the Device sections.  These
1019              include driver-specific options and driver-independent  options.
1020              The  former  are described in the driver-specific documentation.
1021              Some of the latter are described below in the section about  the
1022              Screen section, and they may also be included here.
1023
1024

VIDEOADAPTOR SECTION

1026       Nobody wants to say how this works.  Maybe nobody knows ...
1027
1028

MONITOR SECTION

1030       The  config file may have multiple Monitor sections.  There should nor‐
1031       mally be at least one, for the monitor being used, but a  default  con‐
1032       figuration will be created when one isn't specified.
1033
1034       Monitor sections have the following format:
1035
1036           Section "Monitor"
1037               Identifier "name"
1038               entries
1039               ...
1040           EndSection
1041
1042       The only mandatory entry in a Monitor section is the Identifier entry.
1043
1044       The  Identifier  entry specifies the unique name for this monitor.  The
1045       Monitor section may be used to provide information about the specifica‐
1046       tions  of  the monitor, monitor-specific Options, and information about
1047       the video modes to use with the monitor.
1048
1049       With RandR 1.2-enabled drivers, monitor sections may be  tied  to  spe‐
1050       cific  outputs of the video card.  Using the name of the output defined
1051       by the video driver plus the identifier of a monitor section, one asso‐
1052       ciates  a  monitor  section  with  an output by adding an option to the
1053       Device section in the following format:
1054
1055       Option "Monitor-outputname" "monitorsection"
1056
1057       (for example, Option "Monitor-VGA" "VGA monitor" for a VGA output)
1058
1059       In the absence of specific association of monitor sections to  outputs,
1060       if  a  monitor  section is present the server will associate it with an
1061       output to preserve compatibility for  previous  single-head  configura‐
1062       tions.
1063
1064       Specifying  video modes is optional because the server will use the DDC
1065       or other information provided by the monitor to automatically configure
1066       the  list  of  modes available.  When modes are specified explicitly in
1067       the Monitor section (with the Mode, ModeLine,  or  UseModes  keywords),
1068       built-in  modes  with  the same names are not included.  Built-in modes
1069       with different names are, however, still implicitly included, when they
1070       meet the requirements of the monitor.
1071
1072       The entries that may be used in Monitor sections are described below.
1073
1074       VendorName  "vendor"
1075              This optional entry specifies the monitor's manufacturer.
1076
1077       ModelName  "model"
1078              This optional entry specifies the monitor's model.
1079
1080       HorizSync  horizsync-range
1081              gives  the  range(s) of horizontal sync frequencies supported by
1082              the monitor.  horizsync-range may be a comma separated  list  of
1083              either  discrete  values or ranges of values.  A range of values
1084              is two values separated by a dash.  By default the values are in
1085              units  of  kHz.  They may be specified in MHz or Hz if MHz or Hz
1086              is added to the end of the line.  The data given here is used by
1087              the Xorg server to determine if video modes are within the spec‐
1088              ifications of the monitor.  This information should be available
1089              in  the monitor's handbook.  If this entry is omitted, a default
1090              range of 28-33kHz is used.
1091
1092       VertRefresh  vertrefresh-range
1093              gives the range(s) of vertical refresh frequencies supported  by
1094              the monitor.  vertrefresh-range may be a comma separated list of
1095              either discrete values or ranges of values.  A range  of  values
1096              is two values separated by a dash.  By default the values are in
1097              units of Hz.  They may be specified in MHz or kHz if MHz or  kHz
1098              is added to the end of the line.  The data given here is used by
1099              the Xorg server to determine if video modes are within the spec‐
1100              ifications of the monitor.  This information should be available
1101              in the monitor's handbook.  If this entry is omitted, a  default
1102              range of 43-72Hz is used.
1103
1104       DisplaySize  width height
1105              This  optional entry gives the width and height, in millimetres,
1106              of the picture area of the monitor.  If given this  is  used  to
1107              calculate the horizontal and vertical pitch (DPI) of the screen.
1108
1109       Gamma  gamma-value
1110
1111       Gamma  red-gamma green-gamma blue-gamma
1112              This  is an optional entry that can be used to specify the gamma
1113              correction for the monitor.  It may be  specified  as  either  a
1114              single value or as three separate RGB values.  The values should
1115              be in the range 0.1 to 10.0, and the default is  1.0.   Not  all
1116              drivers are capable of using this information.
1117
1118       UseModes  "modesection-id"
1119              Include the set of modes listed in the Modes section called mod‐
1120              esection-id.  This makes all of the modes defined in  that  sec‐
1121              tion available for use by this monitor.
1122
1123       Mode  "name"
1124              This is an optional multi-line entry that can be used to provide
1125              definitions for video modes for the monitor.  In most cases this
1126              isn't  necessary because the built-in set of VESA standard modes
1127              will be sufficient.  The Mode keyword indicates the start  of  a
1128              multi-line video mode description.  The mode description is ter‐
1129              minated with the EndMode keyword.  The mode description consists
1130              of the following entries:
1131
1132              DotClock  clock
1133                  is the dot (pixel) clock rate to be used for the mode.
1134
1135              HTimings  hdisp hsyncstart hsyncend htotal
1136                  specifies the horizontal timings for the mode.
1137
1138              VTimings  vdisp vsyncstart vsyncend vtotal
1139                  specifies the vertical timings for the mode.
1140
1141              Flags  "flag" ...
1142                  specifies  an optional set of mode flags, each of which is a
1143                  separate string in  double  quotes.   "Interlace"  indicates
1144                  that  the mode is interlaced.  "DoubleScan" indicates a mode
1145                  where each scanline is doubled.  "+HSync" and  "-HSync"  can
1146                  be  used  to  select  the  polarity  of  the  HSync  signal.
1147                  "+VSync" and "-VSync" can be used to select the polarity  of
1148                  the  VSync  signal.  "Composite" can be used to specify com‐
1149                  posite sync on hardware where this is supported.   Addition‐
1150                  ally, on some hardware, "+CSync" and "-CSync" may be used to
1151                  select the composite sync polarity.
1152
1153              HSkew  hskew
1154                  specifies the number of pixels (towards the  right  edge  of
1155                  the  screen)  by  which  the  display enable signal is to be
1156                  skewed.  Not all drivers use this information.  This  option
1157                  might  become  necessary  to override the default value sup‐
1158                  plied by the server (if  any).   “Roving”  horizontal  lines
1159                  indicate  this value needs to be increased.  If the last few
1160                  pixels on a scan line appear on the left of the screen, this
1161                  value should be decreased.
1162
1163              VScan  vscan
1164                  specifies  the  number  of times each scanline is painted on
1165                  the screen.  Not all drivers use this  information.   Values
1166                  less  than 1 are treated as 1, which is the default.  Gener‐
1167                  ally, the "DoubleScan" Flag  mentioned  above  doubles  this
1168                  value.
1169
1170       ModeLine  "name" mode-description
1171              This  entry  is a more compact version of the Mode entry, and it
1172              also can be used to specify video modes for the  monitor.   This
1173              is  a  single  line  format for specifying video modes.  In most
1174              cases this isn't necessary because  the  built-in  set  of  VESA
1175              standard modes will be sufficient.
1176
1177              The  mode-description  is  in  four sections, the first three of
1178              which are mandatory.  The first is the dot (pixel) clock.   This
1179              is  a single number specifying the pixel clock rate for the mode
1180              in MHz.  The second section is a list of four numbers specifying
1181              the  horizontal  timings.   These  numbers are the hdisp, hsync‐
1182              start, hsyncend, and htotal values.  The third section is a list
1183              of  four numbers specifying the vertical timings.  These numbers
1184              are the vdisp, vsyncstart, vsyncend,  and  vtotal  values.   The
1185              final  section  is a list of flags specifying other characteris‐
1186              tics of the mode.  Interlace indicates that the mode  is  inter‐
1187              laced.   DoubleScan indicates a mode where each scanline is dou‐
1188              bled.  +HSync and -HSync can be used to select the  polarity  of
1189              the  HSync  signal.  +VSync and -VSync can be used to select the
1190              polarity of the VSync signal.  Composite can be used to  specify
1191              composite  sync  on hardware where this is supported.  Addition‐
1192              ally, on some hardware, +CSync and -CSync may be used to  select
1193              the  composite  sync polarity.  The HSkew and VScan options men‐
1194              tioned above in the Mode entry  description  can  also  be  used
1195              here.
1196
1197       Option "DPMS" "bool"
1198              This  option  controls whether the server should enable the DPMS
1199              extension for power management for this screen.  The default  is
1200              to enable the extension.
1201
1202       Option "SyncOnGreen" "bool"
1203              This  option  controls  whether  the video card should drive the
1204              sync signal on the green color pin.  Not all cards support  this
1205              option,  and  most  monitors  do not require it.  The default is
1206              off.
1207
1208       Option "Primary" "bool"
1209              This optional entry specifies that the monitor should be treated
1210              as the primary monitor. (RandR 1.2-supporting drivers only)
1211
1212       Option "PreferredMode" "name"
1213              This  optional  entry  specifies a mode to be marked as the pre‐
1214              ferred initial mode of the monitor.  (RandR 1.2-supporting driv‐
1215              ers only)
1216
1217       Option "ZoomModes" "name name ..."
1218              This  optional entry specifies modes to be marked as zoom modes.
1219              It is possible to switch to  the  next  and  previous  mode  via
1220              Ctrl+Alt+Keypad-Plus  and Ctrl+Alt+Keypad-Minus.  All these key‐
1221              pad available modes are selected  from  the  screen  mode  list.
1222              This  list  is  a  copy of the compatibility output monitor mode
1223              list.  Since this output is the output connected to  the  lowest
1224              dot-area monitor, as determined from its largest size mode, that
1225              monitor defines the available zoom modes.  (RandR 1.2-supporting
1226              drivers only)
1227
1228       Option "Position" "x y"
1229              This optional entry specifies the position of the monitor within
1230              the X screen.  (RandR 1.2-supporting drivers only)
1231
1232       Option "LeftOf" "output"
1233              This optional entry specifies that the monitor should  be  posi‐
1234              tioned  to  the  left  of  the output (not monitor) of the given
1235              name.  (RandR 1.2-supporting drivers only)
1236
1237       Option "RightOf" "output"
1238              This optional entry specifies that the monitor should  be  posi‐
1239              tioned  to  the  right  of the output (not monitor) of the given
1240              name.  (RandR 1.2-supporting drivers only)
1241
1242       Option "Above" "output"
1243              This optional entry specifies that the monitor should  be  posi‐
1244              tioned above the output (not monitor) of the given name.  (RandR
1245              1.2-supporting drivers only)
1246
1247       Option "Below" "output"
1248              This optional entry specifies that the monitor should  be  posi‐
1249              tioned below the output (not monitor) of the given name.  (RandR
1250              1.2-supporting drivers only)
1251
1252       Option "Enable" "bool"
1253              This optional entry specifies  whether  the  monitor  should  be
1254              turned  on  at  startup.  By default, the server will attempt to
1255              enable all connected monitors.   (RandR  1.2-supporting  drivers
1256              only)
1257
1258       Option "DefaultModes" "bool"
1259              This optional entry specifies whether the server should add sup‐
1260              ported default modes to the list of modes offered on this  moni‐
1261              tor.  By  default, the server will add default modes; you should
1262              only disable this if you can guarantee that EDID will be  avail‐
1263              able  at  all times, or if you have added custom modelines which
1264              the server can use.  (RandR 1.2-supporting drivers only)
1265
1266       Option "MinClock" "frequency"
1267              This optional entry specifies the minimum  dot  clock,  in  kHz,
1268              that is supported by the monitor.
1269
1270       Option "MaxClock" "frequency"
1271              This  optional  entry  specifies  the maximum dot clock, in kHz,
1272              that is supported by the monitor.
1273
1274       Option "Ignore" "bool"
1275              This optional entry specifies that the monitor should be ignored
1276              entirely, and not reported through RandR.  This is useful if the
1277              hardware reports the  presence  of  outputs  that  don't  exist.
1278              (RandR 1.2-supporting drivers only)
1279
1280       Option "Rotate" "rotation"
1281              This  optional entry specifies the initial rotation of the given
1282              monitor.   Valid  values  for  rotation  are  "normal",  "left",
1283              "right", and "inverted".  (RandR 1.2-supporting drivers only)
1284
1285

MODES SECTION

1287       The  config file may have multiple Modes sections, or none.  These sec‐
1288       tions provide a way of defining sets of video  modes  independently  of
1289       the  Monitor  sections.   Monitor  sections may include the definitions
1290       provided in these sections by using  the  UseModes  keyword.   In  most
1291       cases  the Modes sections are not necessary because the built-in set of
1292       VESA standard modes will be sufficient.
1293
1294       Modes sections have the following format:
1295
1296           Section "Modes"
1297               Identifier "name"
1298               entries
1299               ...
1300           EndSection
1301
1302       The Identifier entry specifies the unique name for  this  set  of  mode
1303       descriptions.   The  other  entries permitted in Modes sections are the
1304       Mode and ModeLine entries that are described above in the Monitor  sec‐
1305       tion.
1306

SCREEN SECTION

1308       The  config  file  may have multiple Screen sections.  There must be at
1309       least one, for the “screen” being  used.   A  “screen”  represents  the
1310       binding  of  a  graphics device (Device section) and a monitor (Monitor
1311       section).  A Screen section is considered “active” if it is  referenced
1312       by  an  active  ServerLayout  section  or  by  the -screen command line
1313       option.  If neither of those is present, the first Screen section found
1314       in the config file is considered the active one.
1315
1316       Screen sections have the following format:
1317
1318           Section "Screen"
1319               Identifier "name"
1320               Device     "devid"
1321               GPUDevice  "devid"
1322               Monitor    "monid"
1323               entries
1324               ...
1325               SubSection "Display"
1326                  entries
1327                  ...
1328               EndSubSection
1329               ...
1330           EndSection
1331
1332       The Identifier entry is mandatory.  All others are optional.
1333
1334       The  Identifier  entry  specifies the unique name for this screen.  The
1335       Screen section provides  information  specific  to  the  whole  screen,
1336       including screen-specific Options.  In multi-head configurations, there
1337       will be multiple active  Screen  sections,  one  for  each  head.   The
1338       entries available for this section are:
1339
1340       Device  "device-id"
1341              This  entry  specifies  the  Device  section to be used for this
1342              screen.  When multiple graphics cards are present, this is  what
1343              ties  a specific card to a screen.  The device-id must match the
1344              Identifier of a Device section in the config file.
1345
1346       GPUDevice  "device-id"
1347              This entry specifies the Device section to be  used  as  a  sec‐
1348              ondary GPU device for this screen.  When multiple graphics cards
1349              are present, this is what ties a specific secondary  card  to  a
1350              screen.   The  device-id  must  match the Identifier of a Device
1351              section in the config file. This can be specified up to 4  times
1352              for a single screen.
1353
1354       Monitor  "monitor-id"
1355              specifies  which  monitor  description  is  to  be used for this
1356              screen.  If a Monitor name is not specified, a default  configu‐
1357              ration  is  used.   Currently  the default configuration may not
1358              function as expected on all platforms.
1359
1360       VideoAdaptor  "xv-id"
1361              specifies an optional Xv video adaptor description  to  be  used
1362              with this screen.
1363
1364       DefaultDepth  depth
1365              specifies  which  color  depth the server should use by default.
1366              The -depth command line option can be used to override this.  If
1367              neither  is specified, the default depth is driver-specific, but
1368              in most cases is 8.
1369
1370       DefaultFbBpp  bpp
1371              specifies which framebuffer  layout  to  use  by  default.   The
1372              -fbbpp  command  line  option  can be used to override this.  In
1373              most cases the driver will chose  the  best  default  value  for
1374              this.   The only case where there is even a choice in this value
1375              is for depth 24, where some hardware supports both a  packed  24
1376              bit framebuffer layout and a sparse 32 bit framebuffer layout.
1377
1378       MatchSeat  seat-id
1379              Only  apply  this  Screen  section  if X server was started with
1380              -seat seat-id option.
1381
1382       Options
1383              Various Option flags may be specified  in  the  Screen  section.
1384              Some  are  driver-specific and are described in the driver docu‐
1385              mentation.  Others are driver-independent, and  will  eventually
1386              be described here.
1387
1388       Option "Accel"
1389              Enables 2D hardware acceleration.  This option is on by default,
1390              but it may be necessary to turn it off if there are bugs in  the
1391              driver.   There are many options to disable specific accelerated
1392              operations, listed below.  Note that disabling an operation will
1393              have  no effect if the operation is not accelerated (whether due
1394              to lack of support in the hardware or in the driver).
1395
1396       Option "GlxVendorLibrary" "string"
1397              This option specifies a space-separated list  of  OpenGL  vendor
1398              libraries  to  use for the screen. This may be used to select an
1399              alternate implementation for development, debugging,  or  alter‐
1400              nate feature sets.  Default: mesa.
1401
1402       Option "InitPrimary" "boolean"
1403              Use  the  Int10  module to initialize the primary graphics card.
1404              Normally, only secondary cards are soft-booted using  the  Int10
1405              module,  as the primary card has already been initialized by the
1406              BIOS at boot time.  Default: false.
1407
1408       Option "NoInt10" "boolean"
1409              Disables the Int10 module, a module that uses the int10 call  to
1410              the BIOS of the graphics card to initialize it.  Default: false.
1411
1412       Each  Screen section may optionally contain one or more Display subsec‐
1413       tions.  Those subsections provide  depth/fbbpp  specific  configuration
1414       information,  and the one chosen depends on the depth and/or fbbpp that
1415       is being used  for  the  screen.   The  Display  subsection  format  is
1416       described in the section below.
1417
1418

DISPLAY SUBSECTION

1420       Each  Screen  section  may  have  multiple  Display  subsections.   The
1421       “active” Display subsection is the first that matches the depth  and/or
1422       fbbpp  values being used, or failing that, the first that has neither a
1423       depth or fbbpp value specified.  The Display subsections are  optional.
1424       When  there  isn't one that matches the depth and/or fbbpp values being
1425       used, all the parameters that can be specified here fall back to  their
1426       defaults.
1427
1428       Display subsections have the following format:
1429
1430               SubSection "Display"
1431                   Depth  depth
1432                   entries
1433                   ...
1434               EndSubSection
1435
1436       Depth  depth
1437              This entry specifies what colour depth the Display subsection is
1438              to be used for.  This entry is usually specified, but it may  be
1439              omitted to create a match-all Display subsection or when wishing
1440              to match only against the FbBpp parameter.  The range  of  depth
1441              values  that  are  allowed  depends on the driver.  Most drivers
1442              support 8, 15, 16 and 24.  Some also support  1  and/or  4,  and
1443              some  may support other values (like 30).  Note: depth means the
1444              number of bits in a pixel that are actually  used  to  determine
1445              the pixel colour.  32 is not a valid depth value.  Most hardware
1446              that uses 32 bits per pixel only uses 24 of  them  to  hold  the
1447              colour information, which means that the colour depth is 24, not
1448              32.
1449
1450       FbBpp  bpp
1451              This entry specifies the framebuffer format this Display subsec‐
1452              tion  is to be used for.  This entry is only needed when provid‐
1453              ing depth 24 configurations that allow a choice between a 24 bpp
1454              packed framebuffer format and a 32bpp sparse framebuffer format.
1455              In most cases this entry should not be used.
1456
1457       Weight  red-weight green-weight blue-weight
1458              This optional entry specifies the relative RGB weighting  to  be
1459              used  for  a  screen  is being used at depth 16 for drivers that
1460              allow multiple formats.  This may also  be  specified  from  the
1461              command line with the -weight option (see Xorg(1)).
1462
1463       Virtual  xdim ydim
1464              This  optional  entry specifies the virtual screen resolution to
1465              be used.  xdim must be a multiple of either 8  or  16  for  most
1466              drivers,  and  a multiple of 32 when running in monochrome mode.
1467              The given value will be rounded down if this is  not  the  case.
1468              Video  modes  which are too large for the specified virtual size
1469              will be rejected.  If this entry is  not  present,  the  virtual
1470              screen resolution will be set to accommodate all the valid video
1471              modes given in the Modes entry.  Some drivers/hardware  combina‐
1472              tions  do not support virtual screens.  Refer to the appropriate
1473              driver-specific documentation for details.
1474
1475       ViewPort  x0 y0
1476              This optional entry sets the upper left corner  of  the  initial
1477              display.   This is only relevant when the virtual screen resolu‐
1478              tion is different from the resolution of the initial video mode.
1479              If  this  entry  is  not given, then the initial display will be
1480              centered in the virtual display area.
1481
1482       Modes  "mode-name" ...
1483              This optional entry specifies the list of video  modes  to  use.
1484              Each  mode-name  specified  must be in double quotes.  They must
1485              correspond to those specified or referenced in  the  appropriate
1486              Monitor  section  (including implicitly referenced built-in VESA
1487              standard modes).  The server will delete modes  from  this  list
1488              which  don't satisfy various requirements.  The first valid mode
1489              in this list will be the default display mode for startup.   The
1490              list  of  valid  modes  is  converted internally into a circular
1491              list.   It  is  possible  to  switch  to  the  next  mode   with
1492              Ctrl+Alt+Keypad-Plus and to the previous mode with Ctrl+Alt+Key‐
1493              pad-Minus.  When this entry is omitted, the valid  modes  refer‐
1494              enced  by  the appropriate Monitor section will be used.  If the
1495              Monitor section contains no modes, then the  selection  will  be
1496              taken from the built-in VESA standard modes.
1497
1498       Visual  "visual-name"
1499              This optional entry sets the default root visual type.  This may
1500              also be specified from the command line (see the Xserver(1)  man
1501              page).   The  visual types available for depth 8 are (default is
1502              PseudoColor):
1503
1504                  StaticGray
1505                  GrayScale
1506                  StaticColor
1507                  PseudoColor
1508                  TrueColor
1509                  DirectColor
1510
1511              The visual type available for the  depths  15,  16  and  24  are
1512              (default is TrueColor):
1513
1514                  TrueColor
1515                  DirectColor
1516
1517              Not all drivers support DirectColor at these depths.
1518
1519              The visual types available for the depth 4 are (default is Stat‐
1520              icColor):
1521
1522                  StaticGray
1523                  GrayScale
1524                  StaticColor
1525                  PseudoColor
1526
1527              The visual type available for the depth 1 (monochrome) is  Stat‐
1528              icGray.
1529
1530       Black  red green blue
1531              This  optional  entry allows the “black” colour to be specified.
1532              This is only supported at depth 1.  The default is black.
1533
1534       White  red green blue
1535              This optional entry allows the “white” colour to  be  specified.
1536              This is only supported at depth 1.  The default is white.
1537
1538       Options
1539              Option flags may be specified in the Display subsections.  These
1540              may  include  driver-specific  options  and   driver-independent
1541              options.   The former are described in the driver-specific docu‐
1542              mentation.  Some of the latter are described above in  the  sec‐
1543              tion  about  the  Screen  section, and they may also be included
1544              here.
1545

SERVERLAYOUT SECTION

1547       The config file may have multiple  ServerLayout  sections.   A  “server
1548       layout” represents the binding of one or more screens (Screen sections)
1549       and one or more input devices (InputDevice sections) to form a complete
1550       configuration.   In  multi-head  configurations,  it also specifies the
1551       relative layout of the heads.  A  ServerLayout  section  is  considered
1552       “active”  if  it is referenced by the -layout command line option or by
1553       an Option "DefaultServerLayout" entry in the ServerFlags  section  (the
1554       former  takes  precedence  over  the latter).  If those options are not
1555       used, the first ServerLayout section found in the config file  is  con‐
1556       sidered  the  active one.  If no ServerLayout sections are present, the
1557       single active screen and two active (core) input devices  are  selected
1558       as described in the relevant sections above.
1559
1560       ServerLayout sections have the following format:
1561
1562           Section "ServerLayout"
1563               Identifier   "name"
1564               Screen       "screen-id"
1565               ...
1566               InputDevice  "idev-id"
1567               ...
1568               options
1569               ...
1570           EndSection
1571
1572       Each  ServerLayout  section  must have an Identifier entry and at least
1573       one Screen entry.
1574
1575       The Identifier entry specifies the unique name for this server  layout.
1576       The  ServerLayout  section  provides  information specific to the whole
1577       session, including session-specific Options.  The  ServerFlags  options
1578       (described  above)  may be specified here, and ones given here override
1579       those given in the ServerFlags section.
1580
1581       The entries that may be used in this section are described here.
1582
1583       Screen  screen-num "screen-id" position-information
1584              One of these entries must be given for each screen being used in
1585              a  session.  The screen-id field is mandatory, and specifies the
1586              Screen  section  being  referenced.   The  screen-num  field  is
1587              optional,  and  may  be  used  to  specify  the screen number in
1588              multi-head configurations.  When  this  field  is  omitted,  the
1589              screens  will  be numbered in the order that they are listed in.
1590              The numbering starts from 0, and must be consecutive.  The posi‐
1591              tion-information  field  describes  the way multiple screens are
1592              positioned.  There are a number  of  different  ways  that  this
1593              information can be provided:
1594
1595              x y
1596
1597              Absolute  x y
1598                  These  both specify that the upper left corner's coordinates
1599                  are (x,y).  The Absolute keyword is  optional.   Some  older
1600                  versions  of  XFree86  (4.2 and earlier) don't recognise the
1601                  Absolute keyword, so it's safest to just specify the coordi‐
1602                  nates without it.
1603
1604              RightOf   "screen-id"
1605
1606              LeftOf    "screen-id"
1607
1608              Above     "screen-id"
1609
1610              Below     "screen-id"
1611
1612              Relative  "screen-id" x y
1613                  These give the screen's location relative to another screen.
1614                  The first four position the screen immediately to the right,
1615                  left,  above or below the other screen.  When positioning to
1616                  the right or left, the top edges are  aligned.   When  posi‐
1617                  tioning  above  or  below,  the left edges are aligned.  The
1618                  Relative form specifies the offset of  the  screen's  origin
1619                  (upper  left  corner)  relative  to  the  origin  of another
1620                  screen.
1621
1622       InputDevice  "idev-id" "option" ...
1623              One of these entries should be given for each input device being
1624              used in a session.  Normally at least two are required, one each
1625              for the core pointer and keyboard devices.  If either  of  those
1626              is  missing, suitable InputDevice entries are searched for using
1627              the method described above  in  the  INPUTDEVICE  section.   The
1628              idev-id field is mandatory, and specifies the name of the Input‐
1629              Device section being referenced.  Multiple option fields may  be
1630              specified,  each  in  double quotes.  The options permitted here
1631              are any that may also be  given  in  the  InputDevice  sections.
1632              Normally  only  session-specific  input  device options would be
1633              used here.  The most commonly used options are:
1634
1635                  "CorePointer"
1636                  "CoreKeyboard"
1637                  "SendCoreEvents"
1638
1639              and the first two should normally be used to indicate  the  core
1640              pointer and core keyboard devices respectively.
1641
1642       MatchSeat  seat-id
1643              Only  apply  this  ServerLayout  section if X server was started
1644              with -seat seat-id option.
1645
1646       Options
1647              In addition to  the  following,  any  option  permitted  in  the
1648              ServerFlags  section  may also be specified here.  When the same
1649              option appears in both places, the value  given  here  overrides
1650              the one given in the ServerFlags section.
1651
1652       Option "IsolateDevice"  "bus-id"
1653              Restrict  device  resets to the specified bus-id.  See the BusID
1654              option (described in DEVICE SECTION, above) for  the  format  of
1655              the  bus-id  parameter.   This  option  overrides SingleCard, if
1656              specified.  At present, only PCI devices can be isolated in this
1657              manner.
1658
1659       Option "SingleCard"  "boolean"
1660              As  IsolateDevice, except that the bus ID of the first device in
1661              the layout is used.
1662
1663       Here is an example of a ServerLayout section for a dual headed configu‐
1664       ration with two mice:
1665
1666           Section "ServerLayout"
1667               Identifier  "Layout 1"
1668               Screen      "MGA 1"
1669               Screen      "MGA 2" RightOf "MGA 1"
1670               InputDevice "Keyboard 1" "CoreKeyboard"
1671               InputDevice "Mouse 1"    "CorePointer"
1672               InputDevice "Mouse 2"    "SendCoreEvents"
1673               Option      "BlankTime"  "5"
1674           EndSection
1675

DRI SECTION

1677       This  optional  section  is  used  to  provide some information for the
1678       Direct Rendering Infrastructure.  Details about the format of this sec‐
1679       tion can be found on-line at <http://dri.freedesktop.org/>.
1680

VENDOR SECTION

1682       The optional Vendor section may be used to provide vendor-specific con‐
1683       figuration information.  Multiple Vendor sections may be  present,  and
1684       they  may  contain  an Identifier entry and multiple Option flags.  The
1685       data therein is not used in this release.
1686

SEE ALSO

1688       General: X(7), Xserver(1), Xorg(1), cvt(1), gtf(1).
1689
1690       Not all modules or interfaces are available on all platforms.
1691
1692       Display  drivers:  apm(4),  ati(4),  chips(4),   cirrus(4),   cyrix(4),
1693       fbdev(4),  glide(4),  glint(4),  i128(4),  i740(4), imstt(4), intel(4),
1694       mga(4), neomagic(4), nv(4), openchrome(4), r128(4),  radeon(4),  rendi‐
1695       tion(4),  savage(4),  s3virge(4),  siliconmotion(4), sis(4), sisusb(4),
1696       sunbw2(4),  suncg14(4),  suncg3(4),  suncg6(4),  sunffb(4),  sunleo(4),
1697       suntcx(4),   tdfx(4),   trident(4),   tseng(4),   vesa(4),   vmware(4),
1698       voodoo(4), wsfb(4), xgi(4), xgixp(4).
1699
1700       Input drivers: acecad(4), citron(4), elographics(4), evdev(4), fpit(4),
1701       joystick(4), kbd(4), libinput(4), mousedrv(4), mutouch(4), penmount(4),
1702       synaptics(4), vmmouse(4), void(4), wacom(4).
1703
1704       Other modules and interfaces: exa(4), fbdevhw(4), v4l(4).
1705

AUTHORS

1707       This   manual   page   was   largely   rewritten   by    David    Dawes
1708       <dawes@xfree86.org>.
1709
1710
1711
1712X Version 11                  xorg-server 1.20.1                  xorg.conf(5)
Impressum