Differences between version 2 and predecessor to the previous major change of XF86Config(5x).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Thursday, December 18, 2003 9:36:59 am | by CraigBox | Revert |
| Older page: | version 1 | Last edited on Wednesday, December 17, 2003 1:17:15 pm | by JohnMcPherson | Revert |
@@ -5,21 +5,21 @@
''XFree86'' uses a configuration file called __XF86Config__ for its initial setup. This configuration file is searched for in the following places when the server is started as a normal user:
- /etc/X11/ ''<cmdline>'' %%%
- /usr/X11R6/etc/X11/ ''<cmdline>'' %%%
- /etc/X11/ __$XF86CONFIG__ %%%
- /usr/X11R6/etc/X11/ __$XF86CONFIG__ %%%
- /etc/X11/XF86Config-4 %%%
- /etc/X11/XF86Config %%%
- /etc/XF86Config %%%
- /usr/X11R6/etc/X11/XF86Config. ''<hostname>'' %%%
- /usr/X11R6/etc/X11/XF86Config-4 %%%
- /usr/X11R6/etc/X11/XF86Config %%%
- /usr/X11R6/lib/X11/XF86Config. ''<hostname>'' %%%
- /usr/X11R6/lib/X11/XF86Config-4 %%%
- /usr/X11R6/lib/X11/XF86Config %%%
+ /etc/X11/ ''<cmdline>''
+ /usr/X11R6/etc/X11/ ''<cmdline>''
+ /etc/X11/ __$XF86CONFIG__
+ /usr/X11R6/etc/X11/ __$XF86CONFIG__
+ /etc/X11/XF86Config-4
+ /etc/X11/XF86Config
+ /etc/XF86Config
+ /usr/X11R6/etc/X11/XF86Config. ''<hostname>''
+ /usr/X11R6/etc/X11/XF86Config-4
+ /usr/X11R6/etc/X11/XF86Config
+ /usr/X11R6/lib/X11/XF86Config. ''<hostname>''
+ /usr/X11R6/lib/X11/XF86Config-4
+ /usr/X11R6/lib/X11/XF86Config
@@ -28,24 +28,24 @@
When the X server is started by the "root" user, the config file search locations are as follows:
- ''<cmdline>'' %%%
- /etc/X11/ ''<cmdline>'' %%%
- /usr/X11R6/etc/X11/ ''<cmdline>'' %%%
- __$XF86CONFIG__ %%%
- /etc/X11/ __$XF86CONFIG__ %%%
- /usr/X11R6/etc/X11/ __$XF86CONFIG__ %%%
- __$HOME__ /XF86Config %%%
- /etc/X11/XF86Config-4 %%%
- /etc/X11/XF86Config %%%
- /etc/XF86Config %%%
- /usr/X11R6/etc/X11/XF86Config. ''<hostname>'' %%%
- /usr/X11R6/etc/X11/XF86Config-4 %%%
- /usr/X11R6/etc/X11/XF86Config %%%
- /usr/X11R6/lib/X11/XF86Config. ''<hostname>'' %%%
- /usr/X11R6/lib/X11/XF86Config-4 %%%
- /usr/X11R6/lib/X11/XF86Config %%%
+ ''<cmdline>''
+ /etc/X11/ ''<cmdline>''
+ /usr/X11R6/etc/X11/ ''<cmdline>''
+ __$XF86CONFIG__
+ /etc/X11/ __$XF86CONFIG__
+ /usr/X11R6/etc/X11/ __$XF86CONFIG__
+ __$HOME__ /XF86Config
+ /etc/X11/XF86Config-4
+ /etc/X11/XF86Config
+ /etc/XF86Config
+ /usr/X11R6/etc/X11/XF86Config. ''<hostname>''
+ /usr/X11R6/etc/X11/XF86Config-4
+ /usr/X11R6/etc/X11/XF86Config
+ /usr/X11R6/lib/X11/XF86Config. ''<hostname>''
+ /usr/X11R6/lib/X11/XF86Config-4
+ /usr/X11R6/lib/X11/XF86Config
@@ -54,42 +54,42 @@
The __XF86Config__ file is composed of a number of sections which may be present in any order. Each section has the form:
- __Section "__ ''!SectionName'' __"__ %%%
+ __Section "__ ''!SectionName'' __"__
- ''!SectionEntry'' %%%
+ ''!SectionEntry''
- ... %%%
- __!EndSection__ %%%
+ ...
+ __!EndSection__
The section names are:
- __Files __ File pathnames %%%
- __!ServerFlags __ Server flags %%%
- __Module __ Dynamic module loading %%%
- __!InputDevice __ Input device description %%%
- __Device __ Graphics device description %%%
- __!VideoAdaptor __ Xv video adaptor description %%%
- __Monitor __ Monitor description %%%
- __Modes __ Video modes descriptions %%%
- __Screen __ Screen configuration %%%
- __!ServerLayout __ Overall layout %%%
- __DRI __ DRI-specific configuration %%%
- __Vendor __ Vendor-specific configuration %%%
+ __Files __ File pathnames
+ __!ServerFlags __ Server flags
+ __Module __ Dynamic module loading
+ __!InputDevice __ Input device description
+ __Device __ Graphics device description
+ __!VideoAdaptor __ Xv video adaptor description
+ __Monitor __ Monitor description
+ __Modes __ Video modes descriptions
+ __Screen __ Screen configuration
+ __!ServerLayout __ Overall layout
+ __DRI __ DRI-specific configuration
+ __Vendor __ Vendor-specific configuration
The following obsolete section names are still recognised for compatibility purposes. In new config files, the __!InputDevice__ section should be used instead.
- __Keyboard __ Keyboard configuration %%%
- __Pointer __ Pointer/mouse configuration %%%
+ __Keyboard __ Keyboard configuration
+ __Pointer __ Pointer/mouse configuration
@@ -102,22 +102,22 @@
Each config file entry usually take up a single line in the file. They consist of a keyword, which is possibly followed by one or more arguments, with the number and types of the arguments depending on the keyword. The argument types are:
- __Integer __ an integer number in decimal, hex or octal %%%
- __Real __ a floating point number %%%
- __String __ a string enclosed in double quote marks (") %%%
+ __Integer __ an integer number in decimal, hex or octal
+ __Real __ a floating point number
+ __String __ a string enclosed in double quote marks (")
Note: hex integer values must be prefixed with "0x", and octal values with "0".
A special keyword called __Option__ may be used to provide free-form data to various components of the server. The __Option__ keyword takes either one or two string arguments. The first is the option name, and the optional second argument is the option value. Some commonly used option value types include:
- __Integer __ an integer number in decimal, hex or octal %%%
- __Real __ a floating point number %%%
- __String __ a sequence of characters %%%
- __Boolean __ a boolean value (see below) %%%
- __Frequency __ a frequency value (see below) %%%
+ __Integer __ an integer number in decimal, hex or octal
+ __Real __ a floating point number
+ __String __ a sequence of characters
+ __Boolean __ a boolean value (see below)
+ __Frequency __ a frequency value (see below)
@@ -140,13 +140,13 @@
Example: the following option entries are equivalent:
- __Option "Accel" "Off"__ %%%
- __Option "!NoAccel"__ %%%
- __Option "!NoAccel" "On"__ %%%
- __Option "Accel" "false"__ %%%
- __Option "Accel" "no"__ %%%
+ __Option "Accel" "Off"__
+ __Option "!NoAccel"__
+ __Option "!NoAccel" "On"__
+ __Option "Accel" "false"__
+ __Option "Accel" "no"__
Frequency option values consist of a real number that is optionally followed by one of the following frequency units:
@@ -170,28 +170,28 @@
When this entry is not specified in the config file, the server falls back to the compiled-in default font path, which contains the following font path elements:
- /usr/X11R6/lib/X11/fonts/misc/ %%%
- /usr/X11R6/lib/X11/fonts/Speedo/ %%%
- /usr/X11R6/lib/X11/fonts/Type1/ %%%
- /usr/X11R6/lib/X11/fonts/CID/ %%%
- /usr/X11R6/lib/X11/fonts/75dpi/ %%%
- /usr/X11R6/lib/X11/fonts/100dpi/ %%%
+ /usr/X11R6/lib/X11/fonts/misc/
+ /usr/X11R6/lib/X11/fonts/Speedo/
+ /usr/X11R6/lib/X11/fonts/Type1/
+ /usr/X11R6/lib/X11/fonts/CID/
+ /usr/X11R6/lib/X11/fonts/75dpi/
+ /usr/X11R6/lib/X11/fonts/100dpi/
The recommended font path contains the following font path elements:
- /usr/X11R6/lib/X11/fonts/local/ %%%
- /usr/X11R6/lib/X11/fonts/misc/ %%%
- /usr/X11R6/lib/X11/fonts/75dpi/:unscaled %%%
- /usr/X11R6/lib/X11/fonts/100dpi/:unscaled %%%
- /usr/X11R6/lib/X11/fonts/Type1/ %%%
- /usr/X11R6/lib/X11/fonts/CID/ %%%
- /usr/X11R6/lib/X11/fonts/Speedo/ %%%
- /usr/X11R6/lib/X11/fonts/75dpi/ %%%
- /usr/X11R6/lib/X11/fonts/100dpi/ %%%
+ /usr/X11R6/lib/X11/fonts/local/
+ /usr/X11R6/lib/X11/fonts/misc/
+ /usr/X11R6/lib/X11/fonts/75dpi/:unscaled
+ /usr/X11R6/lib/X11/fonts/100dpi/:unscaled
+ /usr/X11R6/lib/X11/fonts/Type1/
+ /usr/X11R6/lib/X11/fonts/CID/
+ /usr/X11R6/lib/X11/fonts/Speedo/
+ /usr/X11R6/lib/X11/fonts/75dpi/
+ /usr/X11R6/lib/X11/fonts/100dpi/
Font path elements that are found to be invalid are removed from the font path when the server starts up.
@@ -234,9 +234,9 @@
Entries in this section may be in two forms. The first and most commonly used form is an entry that uses the __Load__ keyword, as described here:
;__Load "__ ''modulename'' __"__ : This instructs the server to load the module called ''modulename'' . The module name given should be the module's standard name, not the module file name. The standard name is case-sensitive, and does not include the "lib" prefix, or the ".a", ".o", or ".so" suffixes.
-
Example: the Type 1 font rasteriser can be loaded with the following entry:
+Example: the Type 1 font rasteriser can be loaded with the following entry:
__Load "type1"__
@@ -246,11 +246,11 @@
Example: the extmod module (which contains a miscellaneous group of server extensions) can be loaded, with the XFree86-DGA extension disabled by using the following entry:
- __!SubSection "extmod"__ %%%
- __ Option "omit XFree86-DGA"__ %%%
- __!EndSubSection__ %%%
+ __!SubSection "extmod"__
+ __ Option "omit XFree86-DGA"__
+ __!EndSubSection__
@@ -259,10 +259,10 @@
To see what font and extension modules are available, check the contents of the following directories:
- /usr/X11R6/lib/modules/fonts %%%
- /usr/X11R6/lib/modules/extensions %%%
+ /usr/X11R6/lib/modules/fonts
+ /usr/X11R6/lib/modules/extensions
@@ -274,14 +274,14 @@
__!InputDevice__ sections have the following format:
- __Section "!InputDevice"__ %%%
- __ Identifier "__ ''name'' __"__ %%%
- __ Driver "__ ''inputdriver'' __"__ %%%
- '' options'' %%%
- '' ...'' %%%
- __!EndSection__ %%%
+ __Section "!InputDevice"__
+ __ Identifier "__ ''name'' __"__
+ __ Driver "__ ''inputdriver'' __"__
+ '' options''
+ '' ...''
+ __!EndSection__
The __Identifier__ entry specifies the unique name for this input device. The __Driver__ entry specifies the name of the driver to use for this input device. When using the loadable server, the input driver module " ''inputdriver'' " will be loaded for each active __!InputDevice__ section. An __!InputDevice__ section is considered active if it is referenced by an active __!ServerLayout__ section, or if it is referenced by the __-keyboard__ or __-pointer__ command line options. The most commonly used input drivers are "keyboard" and "mouse".
@@ -300,14 +300,14 @@
__Device__ sections have the following format:
- __Section "Device"__ %%%
- __ Identifier "__ ''name'' __"__ %%%
- __ Driver "__ ''driver'' __"__ %%%
- '' entries'' %%%
- '' ...'' %%%
- __!EndSection__ %%%
+ __Section "Device"__
+ __ Identifier "__ ''name'' __"__
+ __ Driver "__ ''driver'' __"__
+ '' entries''
+ '' ...''
+ __!EndSection__
@@ -343,13 +343,13 @@
__Monitor__ sections have the following format:
- __Section "Monitor"__ %%%
- __ Identifier "__ ''name'' __"__ %%%
- '' entries'' %%%
- '' ...'' %%%
- __!EndSection__ %%%
+ __Section "Monitor"__
+ __ Identifier "__ ''name'' __"__
+ '' entries''
+ '' ...''
+ __!EndSection__
The __Identifier__ entry specifies the unique name for this monitor. The __Monitor__ section provides information about the specifications of the monitor, monitor-specific __Options__ , and information about the video modes to use with the monitor. Specifying video modes is optional because the server now has a built-in list of VESA standard modes. When modes are specified explicitly in the __Monitor__ section (with the __Modes__ , __!ModeLine__ , or __!UseModes__ keywords), built-in modes with the same names are not included. Built-in modes with different names are, however, still implicitly included.
@@ -371,12 +371,9 @@
;__Flags "__ ''flag'' __"__ '' ...'' : specifies an optional set of mode flags, each of which is a separate string in double quotes. __"Interlace"__ indicates that the mode is interlaced. __"!DoubleScan"__ indicates a mode where each scanline is doubled. __"+HSync"__ and __"-HSync"__ can be used to select the polarity of the HSync signal. __"+VSync"__ and __"-VSync"__ can be used to select the polarity of the VSync signal. __"Composite"__ can be used to specify composite sync on hardware where this is supported. Additionally, on some hardware, __"+CSync"__ and __"-CSync"__ may be used to select the composite sync polarity.
;__HSkew __ ''hskew'' : specifies the number of pixels (towards the right edge of the screen) by which the display enable signal is to be skewed. Not all drivers use this information. This option might become necessary to override the default value supplied by the server (if any). "Roving" horizontal lines indicate this value needs to be increased. If the last few pixels on a scan line appear on the left of the screen, this value should be decreased.
;__VScan __ ''vscan'' : specifies the number of times each scanline is painted on the screen. Not all drivers use this information. Values less than 1 are treated as 1, which is the default. Generally, the __"!DoubleScan"__ __Flag__ mentioned above doubles this value.
-;__!ModeLine "__ ''name'' __"__ '' mode-description'' : This entry is a more compact version of the __Mode__ entry, and it also can be used to specify video modes for the monitor. is a single line format for specifying video modes. In most cases this isn't necessary because the built-in set of VESA standard modes will be sufficient.
-
-
-
The ''mode-description'' is in four sections, the first three of which are mandatory. The first is the dot (pixel) clock. This is a single number specifying the pixel clock rate for the mode in MHz. The second section is a list of four numbers specifying the horizontal timings. These numbers are the ''hdisp'' , ''hsyncstart'' , ''hsyncend'' , and ''htotal'' values. The third section is a list of four numbers specifying the vertical timings. These numbers are the ''vdisp'' , ''vsyncstart'' , ''vsyncend'' , and ''vtotal'' values. The final section is a list of flags specifying other characteristics of the mode. __Interlace__ indicates that the mode is interlaced. __!DoubleScan__ indicates a mode where each scanline is doubled. __+HSync__ and __-HSync__ can be used to select the polarity of the HSync signal. __+VSync__ and __-VSync__ can be used to select the polarity of the VSync signal. __Composite__ can be used to specify composite sync on hardware where this is supported. Additionally, on some hardware, __+CSync__ and __-CSync__ may be used to select the composite sync polarity. The __HSkew__ and __VScan__ options mentioned above in the __Modes__ entry description can also be used here.
+;__!ModeLine "__ ''name'' __"__ '' mode-description'' : This entry is a more compact version of the __Mode__ entry, and it also can be used to specify video modes for the monitor. is a single line format for specifying video modes. In most cases this isn't necessary because the built-in set of VESA standard modes will be sufficient. The ''mode-description'' is in four sections, the first three of which are mandatory. The first is the dot (pixel) clock. This is a single number specifying the pixel clock rate for the mode in MHz. The second section is a list of four numbers specifying the horizontal timings. These numbers are the ''hdisp'' , ''hsyncstart'' , ''hsyncend'' , and ''htotal'' values. The third section is a list of four numbers specifying the vertical timings. These numbers are the ''vdisp'' , ''vsyncstart'' , ''vsyncend'' , and ''vtotal'' values. The final section is a list of flags specifying other characteristics of the mode. __Interlace__ indicates that the mode is interlaced. __!DoubleScan__ indicates a mode where each scanline is doubled. __+HSync__ and __-HSync__ can be used to select the polarity of the HSync signal. __+VSync__ and __-VSync__ can be used to select the polarity of the VSync signal. __Composite__ can be used to specify composite sync on hardware where this is supported. Additionally, on some hardware, __+CSync__ and __-CSync__ may be used to select the composite sync polarity. The __HSkew__ and __VScan__ options mentioned above in the __Modes__ entry description can also be used here.
;__Options__ : Some __Option__ flags that may be useful to include in __Monitor__ sections (when needed) include __"DPMS"__ , and __"!SyncOnGreen"__ .
@@ -386,13 +383,13 @@
__Modes__ sections have the following format:
- __Section "Modes"__ %%%
- __ Identifier "__ ''name'' __"__ %%%
- '' entries'' %%%
- '' ...'' %%%
- __!EndSection__ %%%
+ __Section "Modes"__
+ __ Identifier "__ ''name'' __"__
+ '' entries''
+ '' ...''
+ __!EndSection__
@@ -406,20 +403,20 @@
__Screen__ sections have the following format:
- __Section "Screen"__ %%%
- __ Identifier "__ ''name'' __"__ %%%
- __ Device "__ ''devid'' __"__ %%%
- __ Monitor "__ ''monid'' __"__ %%%
- '' entries'' %%%
- '' ...'' %%%
- __ !SubSection "Display"__ %%%
- '' entries'' %%%
- '' ...'' %%%
- __ !EndSubSection__ %%%
- '' ...'' %%%
- __!EndSection__ %%%
+ __Section "Screen"__
+ __ Identifier "__ ''name'' __"__
+ __ Device "__ ''devid'' __"__
+ __ Monitor "__ ''monid'' __"__
+ '' entries''
+ '' ...''
+ __ !SubSection "Display"__
+ '' entries''
+ '' ...''
+ __ !EndSubSection__
+ '' ...''
+ __!EndSection__
@@ -461,13 +458,13 @@
__Display__ subsections have the following format:
- __ !SubSection "Display"__ %%%
- __ Depth __ ''depth'' %%%
- '' entries'' %%%
- '' ...'' %%%
- __ !EndSubSection__ %%%
+ __ !SubSection "Display"__
+ __ Depth __ ''depth''
+ '' entries''
+ '' ...''
+ __ !EndSubSection__
@@ -479,47 +476,36 @@
;__!ViewPort __ ''x0 y0'' : This optional entry sets the upper left corner of the initial display. This is only relevant when the virtual screen resolution is different from the resolution of the initial video mode. If this entry is not given, then the initial display will be centered in the virtual display area.
;__Modes "__ ''mode-name'' __"__ '' ...'' : This entry is highly desirable for most drivers, and it specifies the list of video modes to use. Each ''mode-name'' specified must be in double quotes. They must correspond to those specified or referenced in the appropriate __Monitor__ section (including implicitly referenced built-in VESA standard modes). The server will delete modes from this list which don't satisfy various requirements. The first valid mode in this list will be the default display mode for startup. The list of valid modes is converted internally into a circular list. It is possible to switch to the next mode with __Ctrl+Alt+Keypad-Plus__ and to the previous mode with __Ctrl+Alt+Keypad-Minus__ . When this entry is omitted, the largest valid mode referenced by the appropriate __Monitor__ section will be used.
;__Visual "__ ''visual-name'' __"__ : This optional entry sets the default root visual type. This may also be specified from the command line (see the ''Xserver(1)'' man page). The visual types available for depth 8 are (default is __!PseudoColor__ ):
+ __!StaticGray__
+ __!GrayScale__
+ __!StaticColor__
+ __!PseudoColor__
+ __!TrueColor__
+ __!DirectColor__
+The visual type available for the depths 15, 16 and 24 are (default is __!TrueColor__ ):
-
__!StaticGray
__ %%%
- __!GrayScale__
%%%
- __!StaticColor__ %%%
- __!PseudoColor__ %%%
- __!TrueColor__ %%%
-
__!DirectColor__ %%%
+
__!TrueColor
__
+ __!DirectColor__
+Not all drivers support __!DirectColor__ at these depths.
+The visual types available for the depth 4 are (default is __!StaticColor__ ):
+ __!StaticGray__
+ __!GrayScale__
+ __!StaticColor__
+ __!PseudoColor__
- The visual type available for the depths 15, 16 and 24 are (default is __!TrueColor__ ):
-
- __!TrueColor__ %%%
- __!DirectColor__ %%%
-
-
-
- Not all drivers support __!DirectColor__ at these depths.
- The visual types available for the depth 4 are (default is __!StaticColor__ ):
-
-
- __!StaticGray__ %%%
- __!GrayScale__ %%%
- __!StaticColor__ %%%
- __!PseudoColor__ %%%
-
-
-
-
The visual type available for the depth 1 (monochrome) is __!StaticGray__ .
+The visual type available for the depth 1 (monochrome) is __!StaticGray__ .
;__Black __ ''red green blue'' : This optional entry allows the "black" colour to be specified. This
;__White __ ''red green blue'' : This optional entry allows the "white" colour to be specified. This is only supported at depth 1. The default is white.
;__Options__ : Option flags may be specified in the __Display__ subsections. These may include driver-specific options and driver-independent options. The former are described in the driver-specific documentation. Some of the latter are described above in the section about the __Screen__ section, and they may also be included here.
-
-
!!SERVERLAYOUT SECTION
The config file may have multiple __!ServerLayout__ sections. A "server layout" represents the binding of one or more screens ( __Screen__ sections) and one or more input devices ( __!InputDevice__ sections) to form a complete configuration. In multi-head configurations, it also specifies the relative layout of the heads. A __!ServerLayout__ section is considered "active" if it is referenced by the __-layout__ command line option. If that option is not used, the first __!ServerLayout__ section found in the config file is considered the active one. If no __!ServerLayout__ sections are present, the single active screen and two active (core) input devices are selected as described in the relevant sections above.
@@ -527,17 +513,17 @@
__!ServerLayout__ sections have the following format:
- __Section "!ServerLayout"__ %%%
- __ Identifier "__ ''name'' __"__ %%%
- __ Screen "__ ''screen-id'' __"__ %%%
- '' ...'' %%%
- __ !InputDevice "__ ''idev-id'' __"__ %%%
- '' ...'' %%%
- '' options'' %%%
- '' ...'' %%%
- __!EndSection__ %%%
+ __Section "!ServerLayout"__
+ __ Identifier "__ ''name'' __"__
+ __ Screen "__ ''screen-id'' __"__
+ '' ...''
+ __ !InputDevice "__ ''idev-id'' __"__
+ '' ...''
+ '' options''
+ '' ...''
+ __!EndSection__
@@ -556,11 +542,11 @@
;__!InputDevice "__ ''idev-id'' __" "__ ''option'' __"__ '' ...'' : One of these entries must be given for each input device being used in a session. Normally at least two are required, one each for the core pointer and keyboard devices. The ''idev-id'' field is mandatory, and specifies the name of the __!InputDevice__ section being referenced. Multiple ''option'' fields may be specified, each in double quotes. The options permitted here are any that may also be given in the __!InputDevice__ sections. Normally only session-specific input device options would be used here. The most commonly used options are:
- __"!CorePointer"__ %%%
- __"!CoreKeyboard"__ %%%
- __"!SendCoreEvents"__ %%%
+ __"!CorePointer"__
+ __"!CoreKeyboard"__
+ __"!SendCoreEvents"__
@@ -571,17 +557,17 @@
Here is an example of a __!ServerLayout__ section for a dual headed configuration with two mice:
- __Section "!ServerLayout"__ %%%
- __ Identifier "Layout 1"__ %%%
- __ Screen "MGA 1"__ %%%
- __ Screen "MGA 2" !RightOf "MGA 1"__ %%%
- __ !InputDevice "Keyboard 1" "!CoreKeyboard"__ %%%
- __ !InputDevice "Mouse 1" "!CorePointer"__ %%%
- __ !InputDevice "Mouse 2" "!SendCoreEvents"__ %%%
- __ Option "!BlankTime" "5"__ %%%
- __!EndSection__ %%%
+ __Section "!ServerLayout"__
+ __ Identifier "Layout 1"__
+ __ Screen "MGA 1"__
+ __ Screen "MGA 2" !RightOf "MGA 1"__
+ __ !InputDevice "Keyboard 1" "!CoreKeyboard"__
+ __ !InputDevice "Mouse 1" "!CorePointer"__
+ __ !InputDevice "Mouse 2" "!SendCoreEvents"__
+ __ Option "!BlankTime" "5"__
+ __!EndSection__
