The OpenNET Project / Index page

[ новости/++ | форум | wiki | теги | ]

Интерактивная система просмотра системных руководств (man-ов)

 ТемаНаборКатегория 
 
 [Cписок руководств | Печать]

xorg.conf (5)
  • >> xorg.conf (5) ( Linux man: Форматы файлов )
  •  

    NAME

    xorg.conf - configuration File for Xorg X server
     
    

    INTRODUCTION

    Xorg supports several mechanisms for supplying/obtaining configuration and run-time parameters: command line options, environment variables, the xorg.conf configuration file, auto-detection, and fallback defaults. When the same information is supplied in more than one way, the highest precedence mechanism is used. The list of mechanisms is ordered from highest precedence to lowest. Note that not all parameters can be supplied via all methods. The available command line options and environment variables (and some defaults) are described in the Xserver(1) and Xorg(1) manual pages. Most configuration file parameters, with their defaults, are described below. Driver and module specific configuration parameters are described in the relevant driver or module manual page.  

    DESCRIPTION

    Xorg uses a configuration file called xorg.conf 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/etc/X11/<cmdline>
    /etc/X11/$XORGCONFIG
    /usr/etc/X11/$XORGCONFIG
    /etc/X11/xorg.conf-4
    /etc/X11/xorg.conf
    /etc/xorg.conf
    /usr/etc/X11/xorg.conf.<hostname>
    /usr/etc/X11/xorg.conf-4
    /usr/etc/X11/xorg.conf
    /usr/lib/X11/xorg.conf.<hostname>
    /usr/lib/X11/xorg.conf-4
    /usr/lib/X11/xorg.conf
    

    where <cmdline> is a relative path (with no lq..rq components) specified with the -config command line option, $XORGCONFIG is the relative path (with no lq..rq components) specified by that environment variable, and <hostname> is the machine's hostname as reported by gethostname(__oslibmansuffix__).

    When the Xorg server is started by the lqrootrq user, the config file search locations are as follows:

    <cmdline>
    /etc/X11/<cmdline>
    /usr/etc/X11/<cmdline>
    $XORGCONFIG
    /etc/X11/$XORGCONFIG
    /usr/etc/X11/$XORGCONFIG
    $HOME/xorg.conf
    /etc/X11/xorg.conf-4
    /etc/X11/xorg.conf
    /etc/xorg.conf
    /usr/etc/X11/xorg.conf.<hostname>
    /usr/etc/X11/xorg.conf-4
    /usr/etc/X11/xorg.conf
    /usr/lib/X11/xorg.conf.<hostname>
    /usr/lib/X11/xorg.conf-4
    /usr/lib/X11/xorg.conf
    

    where <cmdline> is the path specified with the -config command line option (which may be absolute or relative), $XORGCONFIG is the path specified by that environment variable (absolute or relative), $HOME is the path specified by that environment variable (usually the home directory), and <hostname> is the machine's hostname as reported by gethostname(__oslibmansuffix__).

    The xorg.conf file is composed of a number of sections which may be present in any order. Each section has the form:

    Section  N'34'SectionNameN'34'
        SectionEntry
        ...
    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
    

    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
    

    The old XInput section is no longer recognised.

    The ServerLayout sections are at the highest level. They bind together the input and output devices that will be used in a session. The input devices are described in the InputDevice sections. Output devices usually consist of multiple independent components (e.g., a graphics board and a monitor). These multiple components are bound together in the Screen sections, and it is these that are referenced by the ServerLayout section. Each Screen section binds together a graphics board and a monitor. The graphics boards are described in the Device sections, and the monitors are described in the Monitor sections.

    Config file keywords are case-insensitive, and lq_rq characters are ignored. Most strings (including Option names) are also case-insensitive, and insensitive to white space and lq_rq characters.

    Each config file entry usually takes 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 (N'34')
    

    Note: hex integer values must be prefixed with lq0xrq, and octal values with lq0rq.

    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)
    

    Note that all Option values, not just strings, must be enclosed in quotes.

    Boolean options may optionally have a value specified. When no value is specified, the option's value is TRUE. The following boolean option values are recognised as TRUE:

    1, on, true, yes

    and the following boolean option values are recognised as FALSE:

    0, off, false, no

    If an option name is prefixed with N'34'NoN'34', then the option value is negated.

    Example: the following option entries are equivalent:

    Option N'34'AccelN'34'   N'34'OffN'34'
    Option N'34'NoAccelN'34'
    Option N'34'NoAccelN'34' N'34'OnN'34'
    Option N'34'AccelN'34'   N'34'falseN'34'
    Option N'34'AccelN'34'   N'34'noN'34'
    

    Frequency option values consist of a real number that is optionally followed by one of the following frequency units:

    Hz, k, kHz, M, MHz

    When the unit name is omitted, the correct units will be determined from the value and the expectations of the appropriate range of the value. It is recommended that the units always be specified when using frequency option values to avoid any errors in determining the value.  

    FILES SECTION

    The Files section is used to specify some path names required by the server. Some of these paths can also be set from the command line (see Xserver(1) and Xorg(1)). The command line settings override the values specified in the config file. The Files section is optional, as are all of the entries that may appear in it.

    The entries that can appear in this section are:

    FontPath N'34'pathN'34'
    sets the search path for fonts. This path is a comma separated list of font path elements which the Xorg server searches for font databases. Multiple FontPath entries may be specified, and they will be concatenated to build up the fontpath used by the server. Font path elements may be either absolute directory paths, or a font server identifier. Font server identifiers have the form:

    <trans>/<hostname>:<port-number>

    where <trans> is the transport type to use to connect to the font server (e.g., unix for UNIX-domain sockets or tcp for a TCP/IP connection), <hostname> is the hostname of the machine running the font server, and <port-number> is the port number that the font server is listening on (usually 7100).

    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/share/X11/fonts/misc/
    /usr/share/X11/fonts/TTF/
    /usr/share/X11/fonts/Type1/
    /usr/share/X11/fonts/75dpi/
    /usr/share/X11/fonts/100dpi/
    

    The recommended font path contains the following font path elements:

    /usr/share/X11/fonts/local/
    /usr/share/X11/fonts/misc/
    /usr/share/X11/fonts/75dpi/:unscaled
    /usr/share/X11/fonts/100dpi/:unscaled
    /usr/share/X11/fonts/Type1/
    /usr/share/X11/fonts/Speedo/
    /usr/share/X11/fonts/75dpi/
    /usr/share/X11/fonts/100dpi/
    

    Font path elements that are found to be invalid are removed from the font path when the server starts up.

    RGBPath N'34'pathN'34'
    sets the path name for the RGB color database. When this entry is not specified in the config file, the server falls back to the compiled-in default RGB path, which is:

    /usr/share/X11/rgb

    Note that an implicit .txt is added to this path if the server was compiled to use text rather than binary format RGB color databases.

    ModulePath N'34'pathN'34'
    sets the search path for loadable Xorg server modules. This path is a comma separated list of directories which the Xorg server searches for loadable modules loading in the order specified. Multiple ModulePath entries may be specified, and they will be concatenated to build the module search path used by the server.
     

    SERVERFLAGS SECTION

    In addition to options specific to this section (described below), the ServerFlags section is used to specify some global Xorg server options. All of the entries in this section are Options, although for compatibility purposes some of the old style entries are still recognised. Those old style entries are not documented here, and using them is discouraged. The ServerFlags section is optional, as are the entries that may be specified in it.

    Options specified in this section (with the exception of the N'34'DefaultServerLayoutN'34' Option) may be overridden by Options specified in the active ServerLayout section. Options with command line equivalents are overridden when their command line equivalent is used. The options recognised by this section are:

    Option N'34'DefaultServerLayoutN'34' N'34'layout-idN'34'
    This specifies the default ServerLayout section to use in the absence of the -layout command line option.
    Option N'34'NoTrapSignalsN'34' N'34'booleanN'34'
    This prevents the Xorg server from trapping a range of unexpected fatal signals and exiting cleanly. Instead, the Xorg server will die and drop core where the fault occurred. The default behaviour is for the Xorg server to exit cleanly, but still drop a core file. In general you never want to use this option unless you are debugging an Xorg server problem and know how to deal with the consequences.
    Option N'34'DontVTSwitchN'34' N'34'booleanN'34'
    This disallows the use of the Ctrl+Alt+Fn sequence (where Fn refers to one of the numbered function keys). That sequence is normally used to switch to another N'34'virtual terminalN'34' on operating systems that have this feature. When this option is enabled, that key sequence has no special meaning and is passed to clients. Default: off.
    Option N'34'DontZapN'34' N'34'booleanN'34'
    This disallows the use of the Ctrl+Alt+Backspace sequence. That sequence is normally used to terminate the Xorg server. When this option is enabled, that key sequence has no special meaning and is passed to clients. Default: off.
    Option N'34'DontZoomN'34' N'34'booleanN'34'
    This disallows the use of the Ctrl+Alt+Keypad-Plus and Ctrl+Alt+Keypad-Minus sequences. These sequences allows you to switch between video modes. When this option is enabled, those key sequences have no special meaning and are passed to clients. Default: off.
    Option N'34'DisableVidModeExtensionN'34' N'34'booleanN'34'
    This disables the parts of the VidMode extension used by the xvidtune client that can be used to change the video modes. Default: the VidMode extension is enabled.
    Option N'34'AllowNonLocalXvidtuneN'34' N'34'booleanN'34'
    This allows the xvidtune client (and other clients that use the VidMode extension) to connect from another host. Default: off.
    Option N'34'DisableModInDevN'34' N'34'booleanN'34'
    This disables the parts of the Xorg-Misc extension that can be used to modify the input device settings dynamically. Default: that functionality is enabled.
    Option N'34'AllowNonLocalModInDevN'34' N'34'booleanN'34'
    This allows a client to connect from another host and change keyboard and mouse settings in the running server. Default: off.
    Option N'34'AllowMouseOpenFailN'34' N'34'booleanN'34'
    This allows the server to start up even if the mouse device can't be opened/initialised. Default: false.
    Option N'34'VTInitN'34' N'34'commandN'34'
    Runs command after the VT used by the server has been opened. The command string is passed to N'34'/bin/sh -cN'34', and is run with the real user's id with stdin and stdout set to the VT. The purpose of this option is to allow system dependent VT initialisation commands to be run. This option should rarely be needed. Default: not set.
    Option N'34'VTSysReqN'34' N'34'booleanN'34'
    enables the SYSV-style VT switch sequence for non-SYSV systems which support VT switching. This sequence is Alt-SysRq followed by a function key (Fn). This prevents the Xorg server trapping the keys used for the default VT switch sequence, which means that clients can access them. Default: off.
    Option N'34'XkbDisableN'34' N'34'booleanN'34'
    disable/enable the XKEYBOARD extension. The -kb command line option overrides this config file option. Default: XKB is enabled.
    Option N'34'BlankTimeN'34' N'34'timeN'34'
    sets the inactivity timeout for the blank phase of the screensaver. time is in minutes. This is equivalent to the Xorg server's -s flag, and the value can be changed at run-time with xset(1). Default: 10 minutes.
    Option N'34'StandbyTimeN'34' N'34'timeN'34'
    sets the inactivity timeout for the standby phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1). Default: 20 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N'34'DPMSN'34' option set (see the MONITOR section below).
    Option N'34'SuspendTimeN'34' N'34'timeN'34'
    sets the inactivity timeout for the suspend phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1). Default: 30 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N'34'DPMSN'34' option set (see the MONITOR section below).
    Option N'34'OffTimeN'34' N'34'timeN'34'
    sets the inactivity timeout for the off phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1). Default: 40 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the N'34'DPMSN'34' option set (see the MONITOR section below).
    Option N'34'PixmapN'34' N'34'bppN'34'
    This sets the pixmap format to use for depth 24. Allowed values for bpp are 24 and 32. Default: 32 unless driver constraints don't allow this (which is rare). Note: some clients don't behave well when this value is set to 24.
    Option N'34'PC98N'34' N'34'booleanN'34'
    Specify that the machine is a Japanese PC-98 machine. This should not be enabled for anything other than the Japanese-specific PC-98 architecture. Default: auto-detected.
    Option N'34'NoPMN'34' N'34'booleanN'34'
    Disables something to do with power management events. Default: PM enabled on platforms that support it.
    Option N'34'XineramaN'34' N'34'booleanN'34'
    enable or disable XINERAMA extension. Default is disabled.
    Option N'34'AllowDeactivateGrabsN'34' N'34'booleanN'34'
    This option enables the use of the Ctrl+Alt+Keypad-Divide key sequence to deactivate any active keyboard and mouse grabs. Default: off.
    Option N'34'AllowClosedownGrabsN'34' N'34'booleanN'34'
    This option enables the use of the Ctrl+Alt+Keypad-Multiply key sequence to kill clients with an active keyboard or mouse grab as well as killing any application that may have locked the server, normally using the XGrabServer(3) Xlib function. Default: off.
    Note that the options AllowDeactivateGrabs and AllowClosedownGrabs will allow users to remove the grab used by screen saver/locker programs. An API was written to such cases. If you enable this option, make sure your screen saver/locker is updated. Default: off.
    Option N'34'HandleSpecialKeysN'34' N'34'whenN'34'
    This option controls when the server uses the builtin handler to process special key combinations (such as Ctrl+Alt+Backspace). Normally the XKEYBOARD extension keymaps will provide mappings for each of the special key combinations, so the builtin handler is not needed unless the XKEYBOARD extension is disabled. The value of when can be Always, Never, or WhenNeeded. Default: Use the builtin handler only if needed. The server will scan the keymap for a mapping to the Terminate action and, if found, use XKEYBOARD for processing actions, otherwise the builtin handler will be used.
    Option N'34'AIGLXN'34' N'34'booleanN'34'
    enable or disable AIGLX. AIGLX is enabled by default.
    Option N'34'UseDefaultFontPathN'34' N'34'booleanN'34'
    Include the default font path even if other paths are specified in xorg.conf. If enabled, other font paths are included as well. Enabled by default.
    Option N'34'IgnoreABIN'34' N'34'booleanN'34'
    Allow modules built for a different, potentially incompatible version of the X server to load. Disabled by default.
     

    MODULE SECTION

    The Module section is used to specify which Xorg server modules should be loaded. This section is ignored when the Xorg server is built in static form. The types of modules normally loaded in this section are Xorg server extension modules, and font rasteriser modules. Most other module types are loaded automatically when they are needed via other mechanisms. The Module section is optional, as are all of the entries that may be specified in it.

    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 N'34'modulenameN'34'
    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 lqlibrq prefix, or the lq.arq, lq.orq, or lq.sorq suffixes.

    Example: the Type 1 font rasteriser can be loaded with the following entry:

    Load N'34'type1N'34'
    Disable N'34'modulenameN'34'
    This instructs the server to not load the module called modulename. Some modules are loaded by default in the server, and this overrides that default. If a Load instruction is given for the same module, it overrides the Disable instruction and the module is loaded. The module name given should be the module's standard name, not the module file name. As with the Load instruction, the standard name is case-sensitive, and does not include the "lib" prefix, or the ".a", ".o", or ".so" suffixes.

    The second form of entry is a SubSection, with the subsection name being the module name, and the contents of the SubSection being Options that are passed to the module when it is loaded.

    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 N'34'extmodN'34'
       Option  N'34'omit XFree86-DGAN'34'
    EndSubSection
    

    Modules are searched for in each directory specified in the ModulePath search path, and in the drivers, input, extensions, fonts, and internal subdirectories of each of those directories. In addition to this, operating system specific subdirectories of all the above are searched first if they exist.

    To see what font and extension modules are available, check the contents of the following directories:

    /usr/lib/modules/fonts
    /usr/lib/modules/extensions
    

    The lqbitmaprq font module is loaded automatically. It is recommended that at very least the lqextmodrq extension module be loaded. If it isn't, some commonly used server extensions (like the SHAPE extension) will not be available.  

    INPUTDEVICE SECTION

    The config file may have multiple InputDevice sections. There will normally be at least two: one for the core (primary) keyboard, and one of the core pointer. If either of these two is missing, a default configuration for the missing ones will be used. Currently the default configuration may not work as expected on all platforms.

    InputDevice sections have the following format:

    Section N'34'InputDeviceN'34'
        Identifier N'34'nameN'34'
        Driver     N'34'inputdriverN'34'
        options
        ...
    EndSection
    

    The Identifier and Driver entries are required in all InputDevice sections. All other entries are optional.

    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 N'34'inputdriverN'34' will be loaded for each active InputDevice section. An InputDevice section is considered active if it is referenced by an active ServerLayout section, if it is referenced by the -keyboard or -pointer command line options, or if it is selected implicitly as the core pointer or keyboard device in the absence of such explicit references. The most commonly used input drivers are keyboard(4) and mouse(4).

    In the absence of an explicitly specified core input device, the first InputDevice marked as CorePointer (or CoreKeyboard) is used. If there is no match there, the first InputDevice that uses the lqmouserq (or lqkeyboardrq or lqkbdrq) driver is used. The final fallback is to use built-in default configurations.

    InputDevice sections recognise some driver-independent Options, which are described here. See the individual input driver manual pages for a description of the device-specific options.

    Option N'34'CorePointerN'34'
    When this is set, the input device is installed as the core (primary) pointer device. There must be exactly one core pointer. If this option is not set here, or in the ServerLayout section, or from the -pointer command line option, then the first input device that is capable of being used as a core pointer will be selected as the core pointer. This option is implicitly set when the obsolete Pointer section is used.
    Option N'34'CoreKeyboardN'34'
    When this is set, the input device is to be installed as the core (primary) keyboard device. There must be exactly one core keyboard. If this option is not set here, in the ServerLayout section, or from the -keyboard command line option, then the first input device that is capable of being used as a core keyboard will be selected as the core keyboard. This option is implicitly set when the obsolete Keyboard section is used.
    Option N'34'AlwaysCoreN'34' N'34'booleanN'34'
    Option N'34'SendCoreEventsN'34' N'34'booleanN'34'
    Both of these options are equivalent, and when enabled cause the input device to always report core events. This can be used, for example, to allow an additional pointer device to generate core pointer events (like moving the cursor, etc).
    Option N'34'HistorySizeN'34' N'34'numberN'34'
    Sets the motion history size. Default: 0.
    Option N'34'SendDragEventsN'34' N'34'booleanN'34'
    ???
     

    DEVICE SECTION

    The config file may have multiple Device sections. There must be at least one, for the video card being used.

    Device sections have the following format:

    Section N'34'DeviceN'34'
        Identifier N'34'nameN'34'
        Driver     N'34'driverN'34'
        entries
        ...
    EndSection
    

    The Identifier and Driver entries are required in all Device sections. All other entries are optional.

    The Identifier entry specifies the unique name for this graphics device. The Driver entry specifies the name of the driver to use for this graphics device. When using the loadable server, the driver module N'34'driverN'34' will be loaded for each active Device section. A Device section is considered active if it is referenced by an active Screen section.

    Device sections recognise some driver-independent entries and Options, which are described here. Not all drivers make use of these driver-independent entries, and many of those that do don't require them to be specified because the information is auto-detected. See the individual graphics driver manual pages for further information about this, and for a description of the device-specific options. Note that most of the Options listed here (but not the other entries) may be specified in the Screen section instead of here in the Device section.

    BusID N'34'bus-idN'34'
    This specifies the bus location of the graphics card. For PCI/AGP cards, the bus-id string has the form PCI:bus:device:function (e.g., lqPCI:1:0:0rq might be appropriate for an AGP card). This field is usually optional in single-head configurations when using the primary graphics card. In multi-head configurations, or when using a secondary graphics card in a single-head configuration, this entry is mandatory. Its main purpose is to make an unambiguous connection between the device section and the hardware it is representing. This information can usually be found by running the Xorg server with the -scanpci command line option.
    Screen number
    This option is mandatory for cards where a single PCI entity can drive more than one display (i.e., multiple CRTCs sharing a single graphics accelerator and video memory). One Device section is required for each head, and this parameter determines which head each of the Device sections applies to. The legal values of number range from 0 to one less than the total number of heads per entity. Most drivers require that the primary screen (0) be present.
    Chipset N'34'chipsetN'34'
    This usually optional entry specifies the chipset used on the graphics board. In most cases this entry is not required because the drivers will probe the hardware to determine the chipset type. Don't specify it unless the driver-specific documentation recommends that you do.
    Ramdac N'34'ramdac-typeN'34'
    This optional entry specifies the type of RAMDAC used on the graphics board. This is only used by a few of the drivers, and in most cases it is not required because the drivers will probe the hardware to determine the RAMDAC type where possible. Don't specify it unless the driver-specific documentation recommends that you do.
    DacSpeed speed
    DacSpeed speed-8 speed-16 speed-24 speed-32
    This optional entry specifies the RAMDAC speed rating (which is usually printed on the RAMDAC chip). The speed is in MHz. When one value is given, it applies to all framebuffer pixel sizes. When multiple values are given, they apply to the framebuffer pixel sizes 8, 16, 24 and 32 respectively. This is not used by many drivers, and only needs to be specified when the speed rating of the RAMDAC is different from the defaults built in to driver, or when the driver can't auto-detect the correct defaults. Don't specify it unless the driver-specific documentation recommends that you do.
    Clocks clock ...
    specifies the pixel that are on your graphics board. The clocks are in MHz, and may be specified as a floating point number. The value is stored internally to the nearest kHz. The ordering of the clocks is important. It must match the order in which they are selected on the graphics board. Multiple Clocks lines may be specified, and each is concatenated to form the list. Most drivers do not use this entry, and it is only required for some older boards with non-programmable clocks. Don't specify this entry unless the driver-specific documentation explicitly recommends that you do.
    ClockChip N'34'clockchip-typeN'34'
    This optional entry is used to specify the clock chip type on graphics boards which have a programmable clock generator. Only a few Xorg drivers support programmable clock chips. For details, see the appropriate driver manual page.
    VideoRam mem
    This optional entry specifies the amount of video ram that is installed on the graphics board. This is measured in kBytes. In most cases this is not required because the Xorg server probes the graphics board to determine this quantity. The driver-specific documentation should indicate when it might be needed.
    BiosBase baseaddress
    This optional entry specifies the base address of the video BIOS for the VGA board. This address is normally auto-detected, and should only be specified if the driver-specific documentation recommends it.
    MemBase baseaddress
    This optional entry specifies the memory base address of a graphics board's linear frame buffer. This entry is not used by many drivers, and it should only be specified if the driver-specific documentation recommends it.
    IOBase baseaddress
    This optional entry specifies the IO base address. This entry is not used by many drivers, and it should only be specified if the driver-specific documentation recommends it.
    ChipID id
    This optional entry specifies a numerical ID representing the chip type. For PCI cards, it is usually the device ID. This can be used to override the auto-detection, but that should only be done when the driver-specific documentation recommends it.
    ChipRev rev
    This optional entry specifies the chip revision number. This can be used to override the auto-detection, but that should only be done when the driver-specific documentation recommends it.
    TextClockFreq freq
    This optional entry specifies the pixel clock frequency that is used for the regular text mode. The frequency is specified in MHz. This is rarely used.
    Option N'34'ModeDebugN'34' N'34'booleanN'34'
    Enable printing of additional debugging information about modesetting to the server log.
    Options
    Option flags may be specified in the Device sections. These include driver-specific options and driver-independent options. The former are described in the driver-specific documentation. Some of the latter are described below in the section about the Screen section, and they may also be included here.

     

    VIDEOADAPTOR SECTION

    Nobody wants to say how this works. Maybe nobody knows ...

     

    MONITOR SECTION

    The config file may have multiple Monitor sections. There should normally be at least one, for the monitor being used, but a default configuration will be created when one isn't specified.

    Monitor sections have the following format:

    Section N'34'MonitorN'34'
        Identifier N'34'nameN'34'
        entries
        ...
    EndSection
    

    The only mandatory entry in a Monitor section is the Identifier entry.

    The Identifier entry specifies the unique name for this monitor. The Monitor section may be used to provide inform