xfree86/man/xorg.conf.man

10 run-time parameters: command line options, environment variables, the
12 and fallback defaults. When the same information is supplied in more
13 than one way, the highest precedence mechanism is used. The list of
15 all parameters can be supplied via all methods. The available command
17 described in the Xserver(@appmansuffix@) and
20 specific configuration parameters are described in the relevant driver
26 and files ending in the suffix
28 from the directory
33 configuration file is searched for in the following places when the
53 is a relative path (with no \(lq..\(rq components) specified with the
57 is the relative path (with no \(lq..\(rq components) specified by that
60 is the machine's hostname as reported by
63 When the Xorg server is started by the \(lqroot\(rq user, the config file
85 is the path specified with the
89 is the path specified by that
92 is the path specified by that environment variable (usually the home
95 is the machine's hostname as reported by
98 Additional configuration files are searched for in the following
99 directories when the server is started as a normal user:
112 is a relative path (with no \(lq..\(rq components) specified with the
116 When the Xorg server is started by the \(lqroot\(rq user, the
131 is the path specified with the
137 This is to separate configuration files from the vendor or 3rd party packages
139 These files are found in the following directory:
153 Each section has the form:
188 In new config files, the
205 sections are at the highest level.
206 They bind together the input and output devices that will be used in a session.
207 The input devices are described in the
212 These multiple components are bound together in the
214 sections, and it is these that are referenced by the
220 The graphics boards are described in the
222 sections, and the monitors are described in the
233 Each config file entry usually takes up a single line in the file.  They
235 with the number and types of the arguments depending on the keyword.
251 may be used to provide free\-form data to various components of the server.
255 The first is the option name, and the optional second argument is the
275 When no value is specified, the option's value is
287 and the following boolean option values are recognised as
299 then the option value is negated.
301 Example: the following option entries are equivalent:
314 followed by one of the following frequency units:
324 When the unit name is omitted, the correct units will be determined from
325 the value and the expectations of the appropriate range of the value.
326 It is recommended that the units always be specified when using frequency
327 option values to avoid any errors in determining the value.
331 section is used to specify some path names required by the server.
332 Some of these paths can also be set from the command line (see
336 The command line settings override the values specified in the config
340 section is optional, as are all of the entries that may appear in it.
345 sets the search path for fonts.
346 This path is a comma separated list of font path elements which the Xorg
350 entries may be specified, and they will be concatenated to build up the
351 fontpath used by the server.  Font path elements can be absolute
352 directory paths, catalogue directories or a font server identifier. The
353 formats of the later two are explained below:
359 Catalogue directories can be specified using the prefix \fBcatalogue:\fR
360 before the directory name. The directory can then be populated with
361 symlinks pointing to the real font directories, using the following
362 syntax in the symlink name:
372 is an attribute which will be passed to the underlying FPE and
374 is a number used to order the fontfile FPEs. Examples:
391 Font server identifiers have the form:
399 is the transport type to use to connect to the font server (e.g.,
405 is the hostname of the machine running the font server, and
407 is the port number that the font server is listening on (usually 7100).
410 When this entry is not specified in the config file, the server falls back
411 to the compiled\-in default font path, which contains the following
425 Font path elements that are found to be invalid are removed from the
426 font path when the server starts up.
430 sets the search path for loadable Xorg server modules.
431 This path is a comma separated list of directories which the Xorg server
432 searches for loadable modules loading in the order specified.
435 entries may be specified, and they will be concatenated to build the
436 module search path used by the server.  The default module path is
441 .\" The LogFile keyword is not currently implemented
445 sets the name of the Xorg server log file.
459 is the display number for the Xorg server.
463 sets the base directory for keyboard layout files.  The
465 command line option can be used to override this.  The default directory is
471 In addition to options specific to this section (described below), the
475 All of the entries in this section are
477 although for compatibility purposes some of the old style entries are
483 section is optional, as are the entries that may be specified in it.
486 specified in this section (with the exception of the
491 specified in the active
500 from the config file.
501 At the moment the only defined value is
506 This specifies the default
508 section to use in the absence of the
513 This prevents the Xorg server from trapping a range of unexpected fatal
515 Instead, the Xorg server will die and drop core where the fault occurred.
516 The default behaviour is for the Xorg server to exit cleanly, but still drop a
519 server problem and know how to deal with the consequences.
522 This disallows the use of the
526 refers to one of the numbered function keys).
534 This disallows the use of the
537 This action is normally used to terminate the Xorg server.
538 When this option is enabled, the action has no effect.
542 This disallows the use of the
553 This disables the parts of the VidMode extension used by the xvidtune client
554 that can be used to change the video modes.
555 Default: the VidMode extension is enabled.
558 This allows the xvidtune client (and other clients that use the VidMode
563 This tells the mousedrv(@drivermansuffix@) and vmmouse(@drivermansuffix@)
564 drivers to not report failure if the mouse device can't be opened/initialised.
565 It has no effect on the evdev(@drivermansuffix@) or other drivers.
569 sets the inactivity timeout for the
571 phase of the screensaver.
574 This is equivalent to the Xorg server's
576 flag, and the value can be changed at run\-time with
581 sets the inactivity timeout for the
585 is in minutes, and the value can be changed at run\-time with
590 It is only enabled for screens that have the
592 option set (see the MONITOR section below).
595 sets the inactivity timeout for the
599 is in minutes, and the value can be changed at run\-time with
604 It is only enabled for screens that have the
606 option set (see the MONITOR section below).
609 sets the inactivity timeout for the
613 is in minutes, and the value can be changed at run\-time with
618 It is only enabled for screens that have the
620 option set (see the MONITOR section below).
623 Set the maximum number of clients allowed to connect to the X server.
642 This option controls how many GLX visuals the GLX modules sets up.
646 the GLXFBConfigs provided by the driver as GLX visuals.  Other options are
648 which will set up the minimal set allowed by the GLX specification and
653 Include the default font path even if other paths are specified in
662 If this option is disabled, then no devices will be added from the HAL or
666 If this option is disabled, then the devices will be added (and the
668 to the client.
672 If this option is disabled, then no GPU devices will be added from the udev
676 This option controls whether the log is flushed and/or synced to disk after
687 This section is ignored when the Xorg server is built in static form.
694 section is optional, as are all of the entries that may be specified in
698 The first and most commonly used form is an entry that uses the
703 This instructs the server to load the module called
705 The module name given should be the module's standard name, not the
707 The standard name is case\-sensitive, and does not include the \(lqlib\(rq
708 or \(lqcyg\(rq prefixes, or the \(lq.so\(rq or \(lq.dll\(rq suffixes.
711 Example: the DRI extension module can be loaded with the following entry:
719 This instructs the server to not load the module called
721 Some modules are loaded by default in the server, and this overrides that
724 instruction is given for the same module, it overrides the
726 instruction and the module is loaded. The module name given should be the
727 module's standard name, not the module file name. As with the
729 instruction, the standard name is case-sensitive, and does not include the
730 "lib" prefix, or the ".a", ".o", or ".so" suffixes.
734 with the subsection name being the module name, and the contents of the
738 that are passed to the module when it is loaded.
740 Example: the extmod module (which contains a miscellaneous group of
741 server extensions) can be loaded, with the XFree86\-DGA extension
742 disabled by using the following entry:
752 Modules are searched for in each directory specified in the
754 search path, and in the drivers, extensions, input, internal, and
759 To see what extension modules are available, check the extensions
772 that at very least the \(lqextmod\(rq extension module be loaded.
773 If it isn't, some commonly used server extensions (like the SHAPE
782 section is optional, as are all of the entries that may be specified in
785 Entries in this section are listed as Option statements with the name of
786 the extension as the first argument, and a boolean value as the second.
787 The extension name is case\-sensitive, and matches the form shown in the output
791 Example: the MIT-SHM extension can be disabled with the following entry:
809 sections in the xorg.conf if hotplugging is in use (i.e. AutoAddDevices is
812 sections using the
819 be at least two: one for the core (primary) keyboard
820 and one for the core pointer.
821 If either of these two is missing, a default configuration for the missing
822 ones will be used. In the absence of an explicitly specified core input
823 device, the first
830 If there is no match there, the first
832 that uses the \(lqmouse\(rq (or \(lqkbd\(rq) driver is used.
834 Currently the default configuration may not work as expected on all platforms.
837 sections have the following format:
861 entry specifies the unique name for this input device.
864 entry specifies the name of the driver to use for this input device.
865 When using the loadable server, the input driver module
874 section, if it is referenced by the
878 command line options, or if it is selected implicitly as the core pointer
879 or keyboard device in the absence of such explicit references.
893 See the individual input driver manual pages for a description of the
897 Always add the device to the ServerLayout section used by this instance of
899 specified in the configuration and/or on the command line.
919 When enabled, the input device is set up floating and does not
920 report events through any master device or control a cursor. The device is
921 only available to clients using the X Input Extension API. This option is
929 are the inverse of option
937 This option controls the startup behavior only, a device
941 Specifies the 3x3 transformation matrix for absolute input devices. The
942 input device will be bound to the area given in the matrix.  In most
943 configurations, "a" and "e" specify the width and height of the area the
944 device is bound to, and "c" and "f" specify the x and y offset of the area.
945 The value range is 0 to 1, where 1 represents the width or height of all
946 root windows together, 0.5 represents half the area, etc. The values
947 represent a 3x3 matrix, with the first, second and third group of three
948 values representing the first, second and third row of the matrix,
949 respectively.  The identity matrix is "1 0 0 0 1 0 0 0 1".
951 For pointing devices, the following options control how the pointer
953 these can be adjusted at runtime, see the xinput(1) man page for details. Only
957 Select the profile. In layman's terms, the profile constitutes the "feeling" of
958 the acceleration. More formally, it defines how the transfer function (actual
977 Makes the pointer go
980 between 0 and 1 will speed up the pointer.
983 Allows to actually decelerate the pointer when going slow. At most, it will be
988 Selects the scheme, which is the underlying algorithm.
993 .B  "lightweight   old acceleration code (as specified in the X protocol spec)"
1001 Set numerator and denominator of the acceleration factor. The acceleration
1003 profiles to suit the users needs. The
1007 profiles use it directly (i.e. they accelerate by the factor), for other
1012 Set the threshold, which is roughly the velocity (usually device units per 10
1013 ms) required for acceleration to become effective. The precise effect varies
1014 with the profile however.
1025 best to arrange the sections with the most generic matches first.
1028 sections have the following format:
1051 entry specifies the unique name for this input class.
1054 entry specifies the name of the driver to use for this input device.
1055 After all classes have been examined, the
1057 module from the first
1059 entry will be enabled when using the loadable server.
1064 sections. Each section can contain optional entries to narrow the match
1065 of the class. If none of the optional entries appear, the
1068 these entries appear, they all must match for the configuration to apply.
1072 sections. The first allows various tokens to be matched against attributes
1073 of the device. An entry can be constructed to match attributes from different
1074 devices by separating arguments with a '|' character. Multiple entries of the
1075 same type may be supplied to add multiple matching conditions on the same
1093 This entry can be used to check if the substring
1095 occurs in the device's product name.
1098 This entry can be used to check if the substring
1100 occurs in the device's vendor name.
1103 This entry can be used to check if the device file matches the
1108 This entry can be used to check if the operating system matches the
1111 string. This entry is only supported on platforms providing the
1116 The device's Plug and Play (PnP) ID can be checked against the
1121 The device's USB ID can be checked against the
1123 shell wildcard pattern. The ID is constructed as lowercase hexadecimal numbers
1124 separated by a ':'. This is the same format as the
1129 Check the case-sensitive string
1131 against the currently configured driver of the device. Ordering of sections
1132 using this entry is important since it will not match unless the driver has
1133 been set by the config backend or a previous
1138 This entry can be used to check if tags assigned by the config backend
1139 matches the
1141 pattern. A match is found if at least one of the tags given in
1143 matches at least one of the tags assigned by the backend.
1146 Check the case-sensitive string
1148 against the currently active
1150 section. The empty string "" matches an implicit layout which appears
1155 The above directives have equivalents for negative matching with the
1166 directives. These NoMatch directives match if the subsequent match is not
1167 met by the device.
1188 When an input device has been matched to the
1192 entries are applied to the device. One
1196 is recognized. See the
1198 section above for a description of the remaining
1203 This optional entry specifies that the device should be ignored entirely,
1204 and not added to the server. This can be useful when the device is handled
1216 arrange the sections with the most generic matches first.
1219 sections have the following format:
1240 entry specifies the unique name for this output class.
1243 entry specifies the name of the driver to use for this output device.
1244 After all classes have been examined, the
1246 module from the first
1248 entry will be enabled when using the loadable server.
1254 Each section can contain optional entries to narrow the match of the class.
1255 If none of the optional entries appear, the
1258 If more than one of these entries appear, they all must match for the
1261 The following list of tokens can be matched against attributes of the device.
1279 Check the case-sensitive string
1281 against the kernel driver of the device.
1283 When an output device has been matched to the
1287 entries are applied to the device. One
1291 is recognized. See the
1293 section below for a description of the remaining
1298 This option specifies that the matched device should be treated as the
1299 primary GPU, replacing the selection of the GPU used as output by the
1301 the PrimaryGPU option set, the first one enumerated becomes the primary GPU.
1313 are pre-pended to the search path for loadable Xorg server modules. See
1315 in the
1322 There must be at least one, for the video card being used.
1325 sections have the following format:
1348 entry specifies the unique name for this graphics device.
1351 entry specifies the name of the driver to use for this graphics device.
1352 When using the loadable server, the driver module
1369 to be specified because the information is auto\-detected.
1370 See the individual graphics driver manual pages for further information
1371 about this, and for a description of the device\-specific options.
1372 Note that most of the
1374 listed here (but not the other entries) may be specified in the
1376 section instead of here in the
1381 This specifies the bus location of the graphics card.
1385 string has the form
1387 (e.g., \(lqPCI:1@0:0:0\(rq might be appropriate for an AGP card). The
1389 optional in single-head configurations when using the primary graphics card.
1392 Its main purpose is to make an unambiguous connection between the device
1393 section and the hardware it is representing.
1394 This information can usually be found by running the pciaccess tool
1404 parameter determines which head each of the
1409 range from 0 to one less than the total number of heads per entity.
1410 Most drivers require that the primary screen (0) be present.
1413 This usually optional entry specifies the chipset used on the graphics
1415 In most cases this entry is not required because the drivers will probe the
1416 hardware to determine the chipset type.
1417 Don't specify it unless the driver-specific documentation recommends that you
1421 This optional entry specifies the type of RAMDAC used on the graphics
1423 This is only used by a few of the drivers, and in most cases it is not
1424 required because the drivers will probe the hardware to determine the
1426 Don't specify it unless the driver-specific documentation recommends that you
1432 This optional entry specifies the RAMDAC speed rating (which is usually
1433 printed on the RAMDAC chip).
1436 When multiple values are given, they apply to the framebuffer pixel sizes
1438 This is not used by many drivers, and only needs to be specified when the
1439 speed rating of the RAMDAC is different from the defaults built in to
1440 driver, or when the driver can't auto-detect the correct defaults.
1441 Don't specify it unless the driver-specific documentation recommends that you
1445 specifies the pixel that are on your graphics board.
1447 The value is stored internally to the nearest kHz.
1448 The ordering of the clocks is important.
1449 It must match the order in which they are selected on the graphics board.
1452 lines may be specified, and each is concatenated to form the list.
1455 Don't specify this entry unless the driver-specific documentation explicitly
1459 This optional entry is used to specify the clock chip type on graphics
1462 For details, see the appropriate driver manual page.
1465 This optional entry specifies the amount of video ram that is installed
1466 on the graphics board.
1468 In most cases this is not required because the Xorg server probes
1473 This optional entry specifies the memory base address of a graphics
1479 This optional entry specifies the IO base address.
1484 This optional entry specifies a numerical ID representing the chip type.
1485 For PCI cards, it is usually the device ID.
1486 This can be used to override the auto-detection, but that should only be done
1487 when the driver-specific documentation recommends it.
1490 This optional entry specifies the chip revision number.
1491 This can be used to override the auto-detection, but that should only be done
1492 when the driver-specific documentation recommends it.
1508 extended layout by default. (Defaults to off; the video driver can change the
1516 Option flags may be specified in the
1520 The former are described in the driver\-specific documentation.
1521 Some of the latter are described below in the section about the
1533 There should normally be at least one, for the monitor being used,
1537 sections have the following format:
1551 section is the
1557 entry specifies the unique name for this monitor.
1560 section may be used to provide information about the specifications of the
1563 and information about the video modes to use with the monitor.
1566 outputs of the video card.  Using the name of the output defined by the video
1567 driver plus the identifier of a monitor section, one associates a monitor
1568 section with an output by adding an option to the Device section in the
1577 In the absence of specific association of monitor sections to outputs, if a
1578 monitor section is present the server will associate it with an output to
1581 Specifying video modes is optional because the server will use the DDC or other
1582 information provided by the monitor to automatically configure the list of
1584 When modes are specified explicitly in the
1586 section (with the
1591 keywords), built-in modes with the same names are not included.
1593 when they meet the requirements of the monitor.
1600 This optional entry specifies the monitor's manufacturer.
1603 This optional entry specifies the monitor's model.
1606 gives the range(s) of horizontal sync frequencies supported by the
1612 By default the values are in units of kHz.
1618 is added to the end of the line.
1619 The data given here is used by the Xorg server to determine if video
1620 modes are within the specifications of the monitor.
1621 This information should be available in the monitor's handbook.
1625 gives the range(s) of vertical refresh frequencies supported by the
1631 By default the values are in units of Hz.
1637 is added to the end of the line.
1638 The data given here is used by the Xorg server to determine if video
1639 modes are within the specifications of the monitor.
1640 This information should be available in the monitor's handbook.
1644 This optional entry gives the width and height, in millimetres, of the
1645 picture area of the monitor.
1646 If given this is used to calculate the horizontal and vertical pitch (DPI) of
1652 This is an optional entry that can be used to specify the gamma correction
1653 for the monitor.
1655 The values should be in the range 0.1 to 10.0, and the default is 1.0.
1659 Include the set of modes listed in the
1663 This makes all of the modes defined in that section available for use by
1668 definitions for video modes for the monitor.
1669 In most cases this isn't necessary because the built-in set of VESA standard
1673 keyword indicates the start of a multi-line video mode description.
1674 The mode description is terminated with the
1677 The mode description consists of the following entries:
1681 is the dot (pixel) clock rate to be used for the mode.
1684 specifies the horizontal timings for the mode.
1687 specifies the vertical timings for the mode.
1693 indicates that the mode is interlaced.
1699 can be used to select the polarity of the HSync signal.
1703 can be used to select the polarity of the VSync signal.
1710 may be used to select the composite sync polarity.
1713 specifies the number of pixels (towards the right edge of the screen) by
1714 which the display enable signal is to be skewed.
1716 This option might become necessary to override the default value supplied
1717 by the server (if any).
1719 If the last few pixels on a scan line appear on the left of the screen,
1723 specifies the number of times each scanline is painted on the screen.
1725 Values less than 1 are treated as 1, which is the default.
1726 Generally, the
1733 This entry is a more compact version of the
1735 entry, and it also can be used to specify video modes for the monitor.
1737 In most cases this isn't necessary because the built\-in set of VESA
1743 is in four sections, the first three of which are mandatory.
1744 The first is the dot (pixel) clock.
1745 This is a single number specifying the pixel clock rate for the mode in
1747 The second section is a list of four numbers specifying the horizontal
1749 These numbers are the
1756 The third section is a list of four numbers specifying the vertical
1758 These numbers are the
1768 indicates that the mode is interlaced.
1774 can be used to select the polarity of the HSync signal.
1778 can be used to select the polarity of the VSync signal.
1785 may be used to select the composite sync polarity.
1790 options mentioned above in the
1796 This option controls whether the server should enable the DPMS extension
1797 for power management for this screen.  The default is to enable the
1801 This option controls whether the video card should drive the sync signal
1802 on the green color pin.  Not all cards support this option, and most
1803 monitors do not require it.  The default is off.
1806 This optional entry specifies that the monitor should be treated as the primary
1810 This optional entry specifies a mode to be marked as the preferred initial mode
1811 of the monitor.
1816 It is possible to switch to the next and previous mode via
1818 All these keypad available modes are selected from the screen mode list.
1819 This list is a copy of the compatibility output monitor mode list.
1820 Since this output is the output connected to the lowest
1822 monitor defines the available zoom modes.
1826 This optional entry specifies the position of the monitor within the X
1831 This optional entry specifies that the monitor should be positioned to the
1832 left of the output (not monitor) of the given name.
1836 This optional entry specifies that the monitor should be positioned to the
1837 right of the output (not monitor) of the given name.
1841 This optional entry specifies that the monitor should be positioned above the
1842 output (not monitor) of the given name.
1846 This optional entry specifies that the monitor should be positioned below the
1847 output (not monitor) of the given name.
1851 This optional entry specifies whether the monitor should be turned on
1852 at startup.  By default, the server will attempt to enable all connected
1857 This optional entry specifies whether the server should add supported default
1858 modes to the list of modes offered on this monitor. By default, the server
1861 which the server can use.
1865 This optional entry specifies the minimum dot clock, in kHz, that is supported
1866 by the monitor.
1869 This optional entry specifies the maximum dot clock, in kHz, that is supported
1870 by the monitor.
1873 This optional entry specifies that the monitor should be ignored entirely,
1874 and not reported through RandR.  This is useful if the hardware reports the
1879 This optional entry specifies the initial rotation of the given monitor.
1889 of the
1893 sections may include the definitions provided in these sections by
1894 using the
1897 In most cases the
1899 sections are not necessary because the built\-in set of VESA standard modes
1903 sections have the following format:
1917 entry specifies the unique name for this set of mode descriptions.
1920 sections are the
1924 entries that are described above in the
1931 There must be at least one, for the \(lqscreen\(rq being used.
1932 A \(lqscreen\(rq represents the binding of a graphics device
1941 section or by the
1944 If neither of those is present, the first
1946 section found in the config file is considered the active one.
1949 sections have the following format:
1976 entry specifies the unique name for this screen.
1979 section provides information specific to the whole screen, including
1989 This entry specifies the
1992 present, this is what ties a specific card to a screen.  The
1994 must match the
1998 section in the config file.
2001 This entry specifies the
2004 present, this is what ties a specific secondary card to a screen.  The
2006 must match the
2010 section in the config file. This can be specified up to 4 times for a single screen.
2017 Currently the default configuration may not function as expected on all
2025 specifies which color depth the server should use by default.
2029 If neither is specified, the default depth is driver\-specific, but in most
2037 In most cases the driver will chose the best default value for this.
2053 flags may be specified in the
2056 Some are driver\-specific and are described in the driver documentation.
2063 there are bugs in the driver.
2066 Note that disabling an operation will have no effect if the operation is
2067 not accelerated (whether due to lack of support in the hardware or in the
2072 use for the screen. This may be used to select an alternate implementation
2077 Use the Int10 module to initialize the primary graphics card.
2078 Normally, only secondary cards are soft-booted using the Int10 module, as the
2079 primary card has already been initialized by the BIOS at boot time.
2083 Disables the Int10 module, a module that uses the int10 call to the BIOS
2084 of the graphics card to initialize it.
2093 and the one chosen depends on the depth and/or fbbpp that is being used for
2097 subsection format is described in the section below.
2107 subsection is the first that matches the depth and/or fbbpp values being
2108 used, or failing that, the first that has neither a depth or fbbpp value
2113 When there isn't one that matches the depth and/or fbbpp values being used,
2114 all the parameters that can be specified here fall back to their defaults.
2117 subsections have the following format:
2130 This entry specifies what colour depth the
2135 subsection or when wishing to match only against the
2140 values that are allowed depends on the driver.
2145 means the number of bits in a pixel that are actually used to determine
2150 Most hardware that uses 32 bits per pixel only uses 24 of them to hold the
2151 colour information, which means that the colour depth is 24, not 32.
2154 This entry specifies the framebuffer format this
2163 This optional entry specifies the relative RGB weighting to be used
2166 This may also be specified from the command line with the
2172 This optional entry specifies the virtual screen resolution to be used.
2176 The given value will be rounded down if this is not the case.
2177 Video modes which are too large for the specified virtual size will be
2179 If this entry is not present, the virtual screen resolution will be set to
2180 accommodate all the valid video modes given in the
2184 Refer to the appropriate driver\-specific documentation for details.
2187 This optional entry sets the upper left corner of the initial display.
2188 This is only relevant when the virtual screen resolution is different
2189 from the resolution of the initial video mode.
2190 If this entry is not given, then the initial display will be centered in
2194 This optional entry specifies the list of video modes to use.
2198 They must correspond to those specified or referenced in the appropriate
2203 The first valid mode in this list will be the default display mode for
2206 It is possible to switch to the next mode with
2208 and to the previous mode with
2210 When this entry is omitted, the valid modes referenced by the appropriate
2212 section will be used.  If the
2214 section contains no modes, then the selection will be taken from the
2218 This optional entry sets the default root visual type.
2219 This may also be specified from the command line (see the
2237 The visual type available for the depths 15, 16 and 24 are (default is
2251 The visual types available for the depth 4 are (default is
2263 The visual type available for the depth 1 (monochrome) is
2268 This optional entry allows the \(lqblack\(rq colour to be specified.
2273 This optional entry allows the \(lqwhite\(rq colour to be specified.
2278 Option flags may be specified in the
2282 The former are described in the driver\-specific documentation.
2283 Some of the latter are described above in the section about the
2290 A \(lqserver layout\(rq represents the binding of one or more screens
2295 In multi\-head configurations, it also specifies the relative layout of the
2299 section is considered \(lqactive\(rq if it is referenced by the
2303 entry in the
2305 section (the former takes precedence over the latter).
2306 If those options are not used, the first
2308 section found in the config file is considered the active one.
2311 sections are present, the single active screen and two active (core)
2312 input devices are selected as described in the relevant sections above.
2315 sections have the following format:
2341 entry specifies the unique name for this server layout.
2344 section provides information specific to the whole session, including
2350 override those given in the
2361 field is mandatory, and specifies the
2366 field is optional, and may be used to specify the screen number
2368 When this field is omitted, the screens will be numbered in the order that
2373 field describes the way multiple screens are positioned.
2380 These both specify that the upper left corner's coordinates are
2385 Some older versions of XFree86 (4.2 and earlier) don't recognise the
2387 keyword, so it's safest to just specify the coordinates without it.
2398 These give the screen's location relative to another screen.
2399 The first four position the screen immediately to the right, left, above or
2400 below the other screen.
2401 When positioning to the right or left, the top edges are aligned.
2402 When positioning above or below, the left edges are aligned.
2405 form specifies the offset of the screen's origin (upper left corner)
2406 relative to the origin of another screen.
2412 Normally at least two are required, one each for the core pointer and
2416 entries are searched for using the method described above in the
2418 section.  The
2420 field is mandatory, and specifies the name of the
2426 The options permitted here are any that may also be given in the
2441 and the first two should normally be used to indicate the core pointer
2454 In addition to the following, any option permitted in the
2457 When the same option appears in both places, the value given here overrides
2458 the one given in the
2463 Restrict device resets to the specified
2465 See the
2469 above) for the format of the
2480 except that the bus ID of the first device in the layout is used.
2500 This optional section is used to provide some information for the
2502 Details about the format of this section can be found on-line at