XFree86(1) XFree86(1) 1mNAME0m XFree86 - X11R6 X server 1mSYNOPSIS0m 1mXFree86 22m[1m:4m22mdisplay24m] [4moption24m 4m...24m] 1mDESCRIPTION0m 1mXFree86 22mis a full featured X server that was originally designed for UNIX and UNIX-like operating systems running on Intel x86 hardware. It now runs on a wider range of hardware and OS platforms. This work was originally derived from 4mX38624m 4m1.224m by Thomas Roell which was contributed to X11R5 by Snitily Graphics Consulting Service. The 1mXFree86 22mserver architecture was redesigned for the 4.0 release, and it includes among many other things a loadable module system derived from code donated by Metro Link, Inc. The current XFree86 release is com- patible with X11R6.6. 1mPLATFORMS0m 1mXFree86 22moperates under a wide range of operating systems and hardware platforms. The Intel x86 (IA32) architecture is the most widely sup- ported hardware platform. Other hardware platforms include Compaq Alpha, Intel IA64, SPARC and PowerPC. The most widely supported oper- ating systems are the free/OpenSource UNIX-like systems such as Linux, FreeBSD, NetBSD and OpenBSD. Commercial UNIX operating systems such as Solaris (x86) and UnixWare are also supported. Other supported operat- ing systems include LynxOS, and GNU Hurd. Darwin and Mac OS X are sup- ported with the XDarwin(1) X server. Win32/Cygwin is supported with the XWin X server. 1mNETWORK CONNECTIONS0m 1mXFree86 22msupports connections made using the following reliable byte- streams: 4mLocal0m On most platforms, the "Local" connection type is a UNIX-domain socket. On some System V platforms, the "local" connection types also include STREAMS pipes, named pipes, and some other mechanisms. 4mTCPIP0m 1mXFree86 22mlistens on port 6000+4mn24m, where 4mn24m is the display number. This connection type can be disabled with the 1m-nolisten 22moption (see the Xserver(1) man page for details). 1mENVIRONMENT VARIABLES0m For operating systems that support local connections other than Unix Domain sockets (SVR3 and SVR4), there is a compiled-in list specifying the order in which local connections should be attempted. This list can be overridden by the 4mXLOCAL24m environment variable described below. If the display name indicates a best-choice connection should be made (e.g. 1m:0.022m), each connection mechanism is tried until a connection succeeds or no more mechanisms are available. Note: for these OSs, the Unix Domain socket connection is treated differently from the other local connection types. To use it the connection must be made to 1munix:0.022m. The 4mXLOCAL24m environment variable should contain a list of one more more of the following: NAMED PTS SCO ISC which represent SVR4 Named Streams pipe, Old-style USL Streams pipe, SCO XSight Streams pipe, and ISC Streams pipe, respectively. You can select a single mechanism (e.g. 4mXLOCAL=NAMED24m), or an ordered list (e.g. 4mXLOCAL="NAMED:PTS:SCO"24m). his variable overrides the compiled-in defaults. For SVR4 it is recommended that 4mNAMED24m be the first prefer- ence connection. The default setting is 4mPTS:NAMED:ISC:SCO24m. To globally override the compiled-in defaults, you should define (and export if using 1msh 22mor 1mksh22m) 4mXLOCAL24m globally. If you use startx(1) or xinit(1), the definition should be at the top of your 4m.xinitrc24m file. If you use xdm(1), the definitions should be early on in the 4m/usr/X11R6/lib/X11/xdm/Xsession24m script. 1mOPTIONS0m 1mXFree86 22msupports several mechanisms for supplying/obtaining configura- tion and run-time parameters: command line options, environment vari- ables, the XF86Config(5) configuration file, auto-detection, and fall- back 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 param- eters can be supplied via all methods. The available command line options and environment variables (and some defaults) are described here and in the Xserver(1) manual page. Most configuration file param- eters, with their defaults, are described in the XF86Config(5) manual page. Driver and module specific configuration parameters are described in the relevant driver or module manual page. Starting with version 4.4, 1mXFree86 22mhas support for generating a usable configuration at run-time when no XF86Config(5) configuration file is provided. The initial version of this automatic configuration support is targeted at the most popular hardware and software platforms sup- ported by XFree86. Some details about how this works can be found in the 1mCONFIGURATION 22msection below and in the getconfig(1) manual page. In addition to the normal server options described in the Xserver(1) manual page, 1mXFree86 22maccepts the following command line switches: 1mvt4m22mXX24m 4mXX24m specifies the Virtual Terminal device number which 1mXFree860m will use. Without this option, 1mXFree86 22mwill pick the first available Virtual Terminal that it can locate. This option applies only to platforms such as Linux, BSD, SVR3 and SVR4, that have virtual terminal support. 1m-allowMouseOpenFail0m Allow the server to start up even if the mouse device can't be opened or initialised. This is equivalent to the 1mAllow-0m 1mMouseOpenFail 22mXF86Config(5) file option. 1m-allowNonLocalModInDev0m Allow changes to keyboard and mouse settings from non-local clients. By default, connections from non-local clients are not allowed to do this. This is equivalent to the 1mAllowNonLo-0m 1mcalModInDev 22mXF86Config(5) file option. 1m-allowNonLocalXvidtune0m Make the VidMode extension available to remote clients. This allows the xvidtune client to connect from another host. This is equivalent to the 1mAllowNonLocalXvidtune 22mXF86Config(5) file option. By default non-local connections are not allowed. 1m-appendauto0m Append the automatic XFree86 server configuration data to an existing configuration file. By default this is only done when an existing configuration file does not contain any 1mServerLay-0m 1mout 22msections or any 1mScreen 22msections. This can be useful for providing configuration details for things not currently han- dled by the automatic configuration mechanism, such as input devices, font paths, etc. 1m-autoconfig0m Use automatic XFree86 server configuration, even if a configu- ration file is available. By default automatic configuration is only used when a configuration file cannot be found. 1m-bgamma 4m22mvalue0m Set the blue gamma correction. 4mvalue24m must be between 0.1 and 10. The default is 1.0. Not all drivers support this. See also the 1m-gamma22m, 1m-rgamma22m, and 1m-ggamma 22moptions. 1m-bpp 4m22mn24m No longer supported. Use 1m-depth 22mto set the color depth, and use 1m-fbbpp 22mif you really need to force a non-default frame- buffer (hardware) pixel format. 1m-configure0m When this option is specified, the 1mXFree86 22mserver loads all video driver modules, probes for available hardware, and writes out an initial XF86Config(5) file based on what was detected. This option currently has some problems on some platforms, but in most cases it is a good way to bootstrap the configuration process. This option is only available when the server is run as root (i.e, with real-uid 0). 1m-crt /dev/tty4m22mXX0m SCO only. This is the same as the 1mvt 22moption, and is provided for compatibility with the native SCO X server. 1m-depth 4m22mn0m Sets the default color depth. Legal values are 1, 4, 8, 15, 16, and 24. Not all drivers support all values. 1m-disableModInDev0m Disable dynamic modification of input device settings. This is equivalent to the 1mDisableModInDev 22mXF86Config(5) file option. 1m-disableVidMode0m Disable the the parts of the VidMode extension (used by the xvidtune client) that can be used to change the video modes. This is equivalent to the 1mDisableVidModeExtension 22mXF86Config(5) file option. 1m-fbbpp 4m22mn0m Sets the number of framebuffer bits per pixel. You should only set this if you're sure it's necessary; normally the server can deduce the correct value from 1m-depth 22mabove. Useful if you want to run a depth 24 configuration with a 24 bpp framebuffer rather than the (possibly default) 32 bpp framebuffer (or vice versa). Legal values are 1, 8, 16, 24, 32. Not all drivers support all values. 1m-flipPixels0m Swap the default values for the black and white pixels. 1m-gamma 4m22mvalue0m Set the gamma correction. 4mvalue24m must be between 0.1 and 10. The default is 1.0. This value is applied equally to the R, G and B values. Those values can be set independently with the 1m-rgamma22m, 1m-bgamma22m, and 1m-ggamma 22moptions. Not all drivers support this. 1m-ggamma 4m22mvalue0m Set the green gamma correction. 4mvalue24m must be between 0.1 and 10. The default is 1.0. Not all drivers support this. See also the 1m-gamma22m, 1m-rgamma22m, and 1m-bgamma 22moptions. 1m-ignoreABI0m The 1mXFree86 22mserver checks the ABI revision levels of each mod- ule that it loads. It will normally refuse to load modules with ABI revisions that are newer than the server's. This is because such modules might use interfaces that the server does not have. When this option is specified, mismatches like this are downgraded from fatal errors to warnings. This option should be used with care. 1m-keeptty0m Prevent the server from detaching its initial controlling ter- minal. This option is only useful when debugging the server. Not all platforms support (or can use) this option. 1m-keyboard 4m22mkeyboard-name0m Use the XF86Config(5) file 1mInputDevice 22msection called 4mkeyboard-0m 4mname24m as the core keyboard. This option is ignored when the 1mServerLayout 22msection specifies a core keyboard. In the absence of both a ServerLayout section and this option, the first rele- vant 1mInputDevice 22msection is used for the core keyboard. 1m-layout 4m22mlayout-name0m Use the XF86Config(5) file 1mServerLayout 22msection called 4mlayout-0m 4mname24m. By default the first 1mServerLayout 22msection is used. 1m-logfile 4m22mfilename0m Use the file called 4mfilename24m as the 1mXFree86 22mserver log file. The default log file is 1m/var/log/XFree86.4m22mn24m1m.log 22mon most plat- forms, where 4mn24m is the display number of the 1mXFree86 22mserver. The default may be in a different directory on some platforms. This option is only available when the server is run as root (i.e, with real-uid 0). 1m-logverbose 22m[4mn24m] Sets the verbosity level for information printed to the 1mXFree860m server log file. If the 4mn24m value isn't supplied, each occur- rence of this option increments the log file verbosity level. When the 4mn24m value is supplied, the log file verbosity level is set to that value. The default log file verbosity level is 3. 1m-modulepath 4m22msearchpath0m Set the module search path to 4msearchpath24m. 4msearchpath24m is a comma separated list of directories to search for 1mXFree860m server modules. This option is only available when the server is run as root (i.e, with real-uid 0). 1m-noappendauto0m Disable appending the automatic XFree86 server configuration to a partial static configuration. 1m-nosilk 22mDisable Silken Mouse support. 1m-pixmap240m Set the internal pixmap format for depth 24 pixmaps to 24 bits per pixel. The default is usually 32 bits per pixel. There is normally little reason to use this option. Some client appli- cations don't like this pixmap format, even though it is a per- fectly legal format. This is equivalent to the 1mPixmap 22mXF86Con- fig(5) file option. 1m-pixmap320m Set the internal pixmap format for depth 24 pixmaps to 32 bits per pixel. This is usually the default. This is equivalent to the 1mPixmap 22mXF86Config(5) file option. 1m-pointer 4m22mpointer-name0m Use the XF86Config(5) file 1mInputDevice 22msection called 4mpointer-0m 4mname24m as the core pointer. This option is ignored when the 1mServerLayout 22msection specifies a core pointer. In the absence of both a ServerLayout section and this option, the first rele- vant 1mInputDevice 22msection is used for the core pointer. 1m-probeonly0m Causes the server to exit after the device probing stage. The XF86Config(5) file is still used when this option is given, so information that can be auto-detected should be commented out. 1m-quiet 22mSuppress most informational messages at startup. The verbosity level is set to zero. 1m-rgamma 4m22mvalue0m Set the red gamma correction. 4mvalue24m must be between 0.1 and 10. The default is 1.0. Not all drivers support this. See also the 1m-gamma22m, 1m-bgamma22m, and 1m-ggamma 22moptions. 1m-scanpci0m When this option is specified, the 1mXFree86 22mserver scans the PCI bus, and prints out some information about each device that was detected. See also scanpci(1) and pcitweak(1). 1m-screen 4m22mscreen-name0m Use the XF86Config(5) file 1mScreen 22msection called 4mscreen-name24m. By default the screens referenced by the default 1mServerLayout0m section are used, or the first 1mScreen 22msection when there are no 1mServerLayout 22msections. 1m-showconfig0m This is the same as the 1m-version 22moption, and is included for compatibility reasons. It may be removed in a future release, so the 1m-version 22moption should be used instead. 1m-weight 4m22mnnn0m Set RGB weighting at 16 bpp. The default is 565. This applies only to those drivers which support 16 bpp. 1m-verbose 22m[4mn24m] Sets the verbosity level for information printed on stderr. If the 4mn24m value isn't supplied, each occurrence of this option increments the verbosity level. When the 4mn24m value is supplied, the verbosity level is set to that value. The default ver- bosity level is 0. 1m-version0m Print out the server version, patchlevel, release date, the operating system/platform it was built on, and whether it includes module loader support. 1m-xf86config 4m22mfile0m Read the server configuration from 4mfile24m. This option will work for any file when the server is run as root (i.e, with real-uid 0), or for files relative to a directory in the config search path for all other users. 1mKEYBOARD0m The 1mXFree86 22mserver is normally configured to recognize various special combinations of key presses that instruct the server to perform some action, rather than just sending the key press event to a client appli- cation. The default XKEYBOARD keymap defines the key combinations listed below. The server also has these key combinations builtin to its event handler for cases where the XKEYBOARD extension is not being used. When using the XKEYBOARD extension, which key combinations per- form which actions is completely configurable. For more information about when the builtin event handler is used to recognize the special key combinations, see the documentation on the 1mHandleSpecialKeys 22moption in the XF86Config(5) man page. The special combinations of key presses recognized directly by 1mXFree860m are: 1mCtrl+Alt+Backspace0m Immediately kills the server -- no questions asked. This can be disabled with the 1mDontZap 22mXF86Config(5) file option. 1mCtrl+Alt+Keypad-Plus0m Change video mode to next one specified in the configuration file. This can be disabled with the 1mDontZoom 22mXF86Config(5) file option. 1mCtrl+Alt+Keypad-Minus0m Change video mode to previous one specified in the configura- tion file. This can be disabled with the 1mDontZoom 22mXF86Con- fig(5) file option. 1mCtrl+Alt+Keypad-Multiply0m Not treated specially by default. If the 1mAllowClosedownGrabs0m XF86Config(5) file option is specified, this key sequence kills clients with an active keyboard or mouse grab as well as killing any application that may have locked the server, nor- mally using the XGrabServer(3) Xlib function. 1mCtrl+Alt+Keypad-Divide0m Not treated specially by default. If the 1mAllowDeactivateGrabs0m XF86Config(5) file option is specified, this key sequence deac- tivates any active keyboard and mouse grabs. 1mCtrl+Alt+F1...F120m For BSD and Linux systems with virtual terminal support, these keystroke combinations are used to switch to virtual terminals 1 through 12, respectively. This can be disabled with the 1mDontVTSwitch 22mXF86Config(5) file option. 1mCONFIGURATION0m 1mXFree86 22mtypically uses a configuration file called 1mXF86Config 22mfor its initial setup. Refer to the XF86Config(5) manual page for information about the format of this file. Starting with version 4.4, 1mXFree86 22mhas a mechanism for automatically generating a built-in configuration at run-time when no 1mXF86Config 22mfile is present. The current version of this automatic configuration mecha- nism works in three ways. The first is via enhancements that have made many components of the 1mXF86Config 22mfile optional. This means that information that can be probed or reasonably deduced doesn't need to be specified explicitly, greatly reducing the amount of built-in configuration information that needs to be generated at run-time. The second is to use an external utility called getconfig(1), when available, to use meta-configuration information to generate a suitable configuration for the primary video device. The meta-configuration information can be updated to allow an existing installation to get the best out of new hardware or to work around bugs that are found post- release. The third is to have "safe" fallbacks for most configuration informa- tion. This maximises the likelihood that the 1mXFree86 22mserver will start up in some usable configuration even when information about the spe- cific hardware is not available. The automatic configuration support for XFree86 is work in progress. It is currently aimed at the most popular hardware and software plat- forms supported by XFree86. Enhancements are planned for future releases. 1mFILES0m The 1mXFree86 22mserver config file can be found in a range of locations. These are documented fully in the XF86Config(5) manual page. The most commonly used locations are shown here. 1m/etc/X11/XF86Config 22mServer configuration file. 1m/etc/X11/XF86Config-4 22mServer configuration file. 1m/etc/XF86Config 22mServer configuration file. 1m/usr/X11R6/etc/XF86Config 22mServer configuration file. 1m/usr/X11R6/lib/X11/XF86Config 22mServer configuration file. 1m/var/log/XFree86.4m22mn24m1m.log 22mServer log file for display 4mn24m. 1m/usr/X11R6/bin/* 22mClient binaries. 1m/usr/X11R6/include/* 22mHeader files. 1m/usr/X11R6/lib/* 22mLibraries. 1m/usr/X11R6/lib/X11/fonts/* 22mFonts. 1m/usr/X11R6/lib/X11/rgb.txt 22mColor names to RGB mapping. 1m/usr/X11R6/lib/X11/XErrorDB 22mClient error message database. 1m/usr/X11R6/lib/X11/app-defaults/*0m Client resource specifications. 1m/usr/X11R6/man/man?/* 22mManual pages. 1m/etc/X4m22mn24m1m.hosts 22mInitial access control list for display 4mn24m. 1mSEE ALSO0m X(7), Xserver(1), xdm(1), xinit(1), XF86Config(5), xf86config(1), xf86cfg(1), xvidtune(1), apm(4), ati(4), chips(4), cirrus(4), cyrix(4), fbdev(4), glide(4), glint(4), i128(4), i740(4), i810(4), imstt(4), mga(4), neomagic(4), nsc(4), nv(4), r128(4), rendition(4), s3virge(4), siliconmotion(4), sis(4), sunbw2(4), suncg14(4), suncg3(4), suncg6(4), sunffb(4), sunleo(4), suntcx(4), tdfx(4), tga(4), trident(4), tseng(4), v4l(4), vesa(4), vga(4), vmware(4), README 4m24m, RELNOTES 4m24m, README.mouse 4m24m, README.DRI 4m24m, Install 4m24m. 1mAUTHORS0m XFree86 has many contributors world wide. The names of most of them can be found in the documentation, CHANGELOG files in the source tree, and in the actual source code. The names of the contributors to the current release can be found in the release notes 4m24m. XFree86 was originally based on 4mX38624m 4m1.224m by Thomas Roell, which was contributed to the then X Consortium's X11R5 distribution by SGCS. The project that became XFree86 was originally founded in 1992 by David Dawes, Glenn Lai, Jim Tsillas and David Wexelblat. XFree86 was later integrated in the then X Consortium's X11R6 release by a group of dedicated XFree86 developers, including the following: Stuart Anderson, Doug Anson, Gertjan Akkerman, Mike Bernson, Robin Cutshaw, David Dawes, Marc Evans, Pascal Haible, Matthieu Herrb, Dirk Hohndel, David Holland, Alan Hourihane, Jeffrey Hsu, Glenn Lai, Ted Lemon, Rich Murphey, Hans Nasten, Mark Snitily, Randy Ter- bush, Jon Tombs, Kees Verstoep, Paul Vixie, Mark Weaver, David Wex- elblat, Philip Wheatley, Thomas Wolfram, Orest Zborowski. Contributors to XFree86 4.4.0 include: Roi a Torkilsheyggi, Dave Airlie, Andrew Aitchison, Marco Antonio Alvarez, Alexandr Andreev, Jack Angel, Eric Anholt, Ani, Juuso Ĺberg, Sergey Babkin, Alexey Baj, Bang Jun-Young, Uberto Barbini, Kyle Bateman, Matthew W. S. Bell, Vano Beridze, Hiroyuki Bessho, Andrew Bevitt, Christian Biere, Martin Birgmeier, Jakub Bogusz, Le Hong Boi, Paul Bolle, Charl Botha, Stanislav Brabec, Eric Branlund, Rob Braun, Peter Breitenlohner, Michael Breuer, Kevin Brosius, Frederick Bruckman, Oswald Buddenhagen, Nilgün Belma Bugüner, Julian Cable, Yukun Chen, Ping Cheng, Juliusz Chroboczek, Fred Clift, Alan Coopersmith, Martin Costabel, Alan Cox, Michel Dänzer, David Dawes, Leif Delgass, Richard Dengler, John Dennis, Thomas Dickey, Randy Dunlap, Chris Edgington, Paul Eggert, Paul Elliott, Emmanuel, Visanu Euarchukiati, Mike Fabian, Rik Faith, Brian Feld- man, Wu Jian Feng, Kevin P. Fleming, Jose Fonseca, Hugues Fournier, Miguel Freitas, Quentin Garnier, Břrre Gaup, Michael Geddes, Frank Giessler, Hansruedi Glauser, Wolfram Gloger, Alexander Gottwald, Guido Guenther, Ralf Habacker, Bruno Haible, Lindsay Haigh, John Harper, James Harris, Mike A. Harris, Bryan W. Headley, John Heasley, Thomas Hellström, Matthieu Herrb, Jonathan Hough, Alan Hourihane, Joel Ray Holveck, Harold L Hunt II, Ricardo Y. Igarashi, Mutsumi ISHIKAWA , Tsuyoshi ITO, Kean Johnston, Nicolas JOLY, Phil Jones, Roman Kagan, Theppitak Karoonboonyanan, Etsushi Kato, Koike Kazuhiko, Aidan Kehoe, Juergen Keil, Andreas Kies, Thomas Klausner, Mario Klebsch, Egmont Koblinger, Vlatko Kosturjak, Kusanagi Kouichi, Mel Kravitz, Peter Kunzmann, Nick Kurshev, Mashrab Kuva- tov, Marc La France, Radics Laszlo, Zarick Lau, Nolan Leake, Michel Lespinasse, Noah Levitt, Dave Love, H.J. Lu, Lubos Lunak, Sven Luther, Torrey T. Lyons, Calum Mackay, Paul Mackerras, Roland Mainz, Kevin Martin, Michal Maruska, Kensuke Matsuzaki, maxim, Stephen McCamant, Ferris McCormick, Luke Mewburn, Nicholas Miell, Robert Millan, Hisashi MIYASHITA, Gregory Mokhin, Patrik Mont- gomery, Joe Moss, Josselin Mouette, Frank Murphy, Reiko Nakajima, Paul Nasrat, Dan Nelson, Bastien Nocera, Alexandre Oliva, Hideki ONO, Peter Osterlund, Sergey V. Oudaltsov, Séamus Ó Ciardhuáin, Bob Paauwe, Paul Pacheco, Tom Pala, Ivan Pascal, T. M. Pederson, Earle F. Philhower III, Nils Philippsen, Manfred Pohler, Alexander Pohoyda, Alain Poirier, Arnaud Quette, Jim Radford, Dale Rahn, Lucas Correia Villa Real, René Rebe, Tyler Retzlaff, Sebastian Rit- tau, Tim Roberts, Alastair M. Robinson, Branden Robinson, Daniel Rock, Ian Romanick, Bernhard Rosenkraenzer, Mĺns Rullgĺrd, Andriy Rysin, Supphachoke Santiwichaya, Pablo Saratxaga, Matthias Scheler, Jens Schweikhardt, Danilo Segan, Shantonu Sen, Stas Sergeev, Jung- shik Shin, Nikola Smolenski, Andreas Stenglein, Paul Stewart, Alexander Stohr, Alan Strohm, Will Styles, James Su, Mike Sulivan, Ville Syrjala, Slava Sysoltsev, Akira TAGOH, Toshimitsu Tanaka, Akira Taniguchi, Owen Taylor, Neil Terry, Jonathan Thambidurai, John Tillman, Adam Tlalka, Linus Torvalds, Christian Tosta, Warren Turkal, Stephen J. Turnbull, Ted Unangst, Mike Urban, Simon Vallet, Thuraiappah Vaseeharan, Luc Verhaegen, Yann Vernier, Michail Vidi- assov, Sebastiano Vigna, Mark Vojkovich, Stephane Voltz, Boris Weissman, Keith Whitwell, Thomas Winischhofer, Eric Wittry, Kim Woelders, Roy Wood, Jason L. Wright, Joerg Wunsch, Chisato Yamauchi, Hui Yu. Contributors to XFree86 4.5.0 include: Szilveszter Adam, Tim Adye, Taneem Ahmed, Andrew Aitchison, Raoul Arranz, Zaeem Arshad, Dwayne Bailey, Ilyas Bakirov, Denis Barbier, Kyle Bateman, J. Scott Berg, Thomas Biege, Dmitry Bolkhovityanov, H Merijn Brand, Peter Breitenlohner, Benjamin Burke, Dale L Busacker, busmanus, Julian Cable, Mike Castle, David M. Clay, Philip Clayton, Alan Coopersmith, Ricardo Cruz, Michel Dänzer, J. D. Darling, David Dawes, Michael Dawes, Rafael Ávila de Espíndola, Rick De Laet, Josip Deanovic, Angelus Dei, Laurent Deniel, Thomas Dickey, Stefan Dirsch, Charles Dobson, DRI Project, Emmanuel Dreyfus, Boris Dusek, Georgina O. Economou, Egbert Eich, Bernd Ernesti, Chris Evans, Rik Faith, Adrian Fiechter, Matthew Fischer, FreeType Team, Terry R. Frienrichsen, Christopher Fynn, Hubert Gburzynski, Nicolas George, Frank Giessler, Fred Gleason, Dmitry Golubev, Alexander Gottwald, Herbert Graeber, Miroslav Halas, John Harper, Harshula, John Heasley, Matthieu Herrb, David Holl, Alex Holland, Peng Hongbo, Alan Hourihane, Harold L Hunt II, Alan Iwi, Timur Jamakeev, Paul Jarc, Kean Johnston, Nicolas Joly, Mark Kandianis, Kaleb Keithley, Chamath Keppitiyagama, Jung-uk Kim, Satoshi Kimura, Michael Knud- sen, Vlatko Kosturjak, Alexei Kosut, Anton Kovalenko, Joachim Kue- bart, Marc La France, David Laight, Zarick Lau, Pierre Lalet, Michael Lampe, Lanka Linux User Group, Nolan Leake, Werner Lemberg, Dejan Lesjak, Noah Levitt, Greg Lewis, Bernhard R Link, Jonas Lund, S. Lussos, Torrey T. Lyons, Roland Mainz, N Marci, Kevin Martin, Stephen McCamant, Mesa Developers, Luke Mewburn, Petr Mladek, Bram Moolenaar, Steve Murphy, Ishikawa MUTSUMI, Radu Octavian, Lee Olsen, Greg Parker, Ivan Pascal, Alexander E. Patrakov, Mike Pechkin, Soós Péter, Zvezdan Petkovic, Alexander Pohoyda, Xie Qian, Bill Randle, Adam J. Richter, Tim Roberts, Bernhard Rosenkraenzer, Andreas Rüden, Steve Rumble, Oleg Safiullin, Ty Sarna, Leo Sav- ernik, Barry Scott, Shantonu Sen, Yu Shao, Andreas Schwab, Matthias Scheler, Dan Shearer, Michael Shell, Paul Shupak, Alexander Stohr, Marius Strobl, Mikko Markus Torni, Jess Thrysoee, Izumi Tsutsui, Tungsten Graphics, Ryan Underwood, Tristan Van Berkom, Michael van Elst, Phillip Vandry, Roman Vasylyev, Luc Verhaegen, Rodion Vshevtsov, Mark Vojkovich, Edi Werner, Keith Whitwell, Scot Wilcoxon, Dave Williss, Thomas Winischhofer, Kuang-che Wu, X-Oz Technologies, Chisato Yamauchi, Michael Yaroslavtsev, David Yerger, Su Yong, Hui Yu, Sagi Zeevi, Christian Zietz. Contributors to XFree86 4.6.0 include: ASPEED Technologies, Andrew Aitchison, James Ascroft-Leigh, Étienne Bersac, Peter Breitenlohner, Terry Chang, Y. C. Chen, Jeff Chua, James Cloos, Alan Coopersmith, Miguel González Cuadrado, David Dawes, Thomas Dickey, Stefan Dirsch, Bernd Ernesti, Jordan Frank, Will L G, Frank Giessler, Thorsten Glaser, Damian Janusz Gruszka, Lukas Hejtmanek, Evil Mr Henry, Jens Herden, Alan Hourihane, Nico- las Joly, Bang Jun-Young, Alexander Kabaev, Satoshi Kimura, Milos Komarcevic, Marc La France, Dejan Lesjak, Khong Jye Liew, Jong Lin, Michael Lorenz, Michael Macallan, Michal Maruska, Luke Mewburn, Timothy Musson, Newsh, Takaaki Nomura, Ivan Pascal, Bob Peterson, Pierre, Aaron Plattner, Alexander Pohoyda, Jeremy C. Reed, Conrad Schuler, Bruno Schwander, Olaf Seibert, Aaron Solochek, Helmar Spangenberg, Ken Stailey, Tobias Stoeckmann, Tungsten Graphics, James Richard Tyrer, Staffan Ulfberg, Denis Vlasenko, Mark Vojkovich, Tom Williams, Dave Williss, X-Oz Technologies, XGI, Christos Zoulas. XFree86 source is available from the FTP server 4m24m, and from the XFree86 CVS server 4m24m. Documentation and other information can be found from the XFree86 web site 4m24m. 1mLEGAL0m 1mXFree86 22mis copyright software, provided under licenses that permit mod- ification and redistribution in source and binary form without fee. Portions of 1mXFree86 22mare copyright by The XFree86 Project, Inc. and numerous authors and contributors from around the world. Licensing information can be found at 4m24m. Refer to the source code for specific copyright notices. 1mXFree86(R) 22mis a registered trademark of The XFree86 Project, Inc. XF86Config(5) XF86Config(5) 1mNAME0m XF86Config - Configuration File for XFree86 1mINTRODUCTION0m 1mXFree86 22msupports several mechanisms for supplying/obtaining configura- tion and run-time parameters: command line options, environment vari- ables, the XF86Config 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 parame- ters can be supplied via all methods. The available command line options and environment variables (and some defaults) are described in the Xserver(1) and XFree86(1) manual pages. Most configuration file parameters, with their defaults, are described below. Driver and mod- ule specific configuration parameters are described in the relevant driver or module manual page. Starting with version 4.4, 1mXFree86 22mhas support for generating a usable configuration at run-time when no 1mXF86Config 22mfile is provided. The initial version of this automatic configuration support is targeted at the most popular hardware and software platforms supported by XFree86. Some details about how this works can be found in the XFree86(1) and getconfig(1) manual pages. Starting with version 4.5, it is possible for this automatically gener- ated configuration to supplement a partial static configuration. The partial static configuration can be used to provide non-default config- uration details for things that are not currently handled by the auto- matic configuration mechanism. 1mDESCRIPTION0m 1mXFree86 22muses a configuration file called 1mXF86Config 22mfor its initial setup. This configuration file is searched for in the following places when the server is started as a normal user: 4m/etc/X11/24m 4m/usr/X11R6/etc/X11/24m 4m/etc/X11/24m1m$XF86CONFIG0m 4m/usr/X11R6/etc/X11/24m1m$XF86CONFIG0m 4m/etc/X11/XF86Config-40m 4m/etc/X11/XF86Config0m 4m/etc/XF86Config0m 4m/usr/X11R6/etc/X11/XF86Config.24m 4m/usr/X11R6/etc/X11/XF86Config-40m 4m/usr/X11R6/etc/X11/XF86Config0m 4m/usr/X11R6/lib/X11/XF86Config.24m 4m/usr/X11R6/lib/X11/XF86Config-40m 4m/usr/X11R6/lib/X11/XF86Config0m where 4m24m is a relative path (with no ".." components) specified with the 1m-xf86config 22mcommand line option, 1m$XF86CONFIG 22mis the relative path (with no ".." components) specified by that environment variable, and 4m24m is the machine's hostname as reported by gethostname(3). When the XFree86 server is started by the "root" user, the config file search locations are as follows: 4m/etc/X11/24m 4m/usr/X11R6/etc/X11/24m 1m$XF86CONFIG0m 4m/etc/X11/24m1m$XF86CONFIG0m 4m/usr/X11R6/etc/X11/24m1m$XF86CONFIG0m 1m$HOME4m22m/XF86Config0m 4m/etc/X11/XF86Config-40m 4m/etc/X11/XF86Config0m 4m/etc/XF86Config0m 4m/usr/X11R6/etc/X11/XF86Config.24m 4m/usr/X11R6/etc/X11/XF86Config-40m 4m/usr/X11R6/etc/X11/XF86Config0m 4m/usr/X11R6/lib/X11/XF86Config.24m 4m/usr/X11R6/lib/X11/XF86Config-40m 4m/usr/X11R6/lib/X11/XF86Config0m where 4m24m is the path specified with the 1m-xf86config 22mcommand line option (which may be absolute or relative), 1m$XF86CONFIG 22mis the path specified by that environment variable (absolute or relative), 1m$HOME 22mis the path specified by that environment variable (usually the home directory), and 4m24m is the machine's hostname as reported by gethostname(3). The 1mXF86Config 22mfile is composed of a number of sections which may be present in any order. Each section has the form: 1mSection "4m22mSectionName24m1m"0m 4mSectionEntry0m ... 1mEndSection0m The section names are: 1mFiles 22mFile pathnames 1mServerFlags 22mServer flags 1mModule 22mDynamic module loading 1mInputDevice 22mInput device description 1mDevice 22mGraphics device description 1mVideoAdaptor 22mXv video adaptor description 1mMonitor 22mMonitor description 1mModes 22mVideo modes descriptions 1mScreen 22mScreen configuration 1mServerLayout 22mOverall layout 1mDRI 22mDRI-specific configuration 1mVendor 22mVendor-specific configuration The following obsolete section names are still recognised for compati- bility purposes. In new config files, the 1mInputDevice 22msection should be used instead. 1mKeyboard 22mKeyboard configuration 1mPointer 22mPointer/mouse configuration The old 1mXInput 22msection is no longer recognised. The 1mServerLayout 22msections 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 1mInputDevice 22msections. Output devices usu- ally consist of multiple independent components (e.g., and graphics board and a monitor). These multiple components are bound together in the 1mScreen 22msections, and it is these that are referenced by the 1mServer-0m 1mLayout 22msection. Each 1mScreen 22msection binds together a graphics board and a monitor. The graphics boards are described in the 1mDevice 22msec- tions, and the monitors are described in the 1mMonitor 22msections. Config file keywords are case-insensitive, and "_" characters are ignored. Most strings (including 1mOption 22mnames) are also case-insensi- tive, and insensitive to white space and "_" 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: 1mInteger 22man integer number in decimal, hex or octal 1mReal 22ma floating point number 1mString 22ma string enclosed in double quote marks (") Note: hex integer values must be prefixed with "0x", and octal values with "0". A special keyword called 1mOption 22mmay be used to provide free-form data to various components of the server. The 1mOption 22mkeyword 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: 1mInteger 22man integer number in decimal, hex or octal 1mReal 22ma floating point number 1mString 22ma sequence of characters 1mBoolean 22ma boolean value (see below) 1mFrequency 22ma frequency value (see below) Note that 4mall24m 1mOption 22mvalues, 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 1mTRUE22m. The following boolean option values are recognised as 1mTRUE22m: 1m122m, 1mon22m, 1mtrue22m, 1myes0m and the following boolean option values are recognised as 1mFALSE22m: 1m022m, 1moff22m, 1mfalse22m, 1mno0m If an option name is prefixed with "1mNo22m", then the option value is negated. Example: the following option entries are equivalent: 1mOption "Accel" "Off"0m 1mOption "NoAccel"0m 1mOption "NoAccel" "On"0m 1mOption "Accel" "false"0m 1mOption "Accel" "no"0m Frequency option values consist of a real number that is optionally followed by one of the following frequency units: 1mHz22m, 1mk22m, 1mkHz22m, 1mM22m, 1mMHz0m 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. 1mFILES SECTION0m The config file may have multiple 1mFiles 22msections. These are used to specify some path names required by the server. Earlier 1mFiles 22msections have priority over later sections. This means that a path name speci- fied in a 1mFiles 22msection cannot be overridden by a later 1mFiles 22msection (this behaviour may change in the future). Some of these paths can also be set from the command line (see Xserver(1) and XFree86(1)). The command line settings override the values specified in the config file. The 1mFiles 22msection is optional, as are all of the entries that may appear in it. The entries that can appear in this section are: 1mIdentifier "4m22mname24m1m"0m specifies an optional identifying name for the 1mFiles 22msection. 1mFontPath "4m22mpath24m1m"0m sets the search path for fonts. This path is a comma separated list of font path elements which the XFree86 server searches for font databases. Multiple 1mFontPath 22mentries 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: 4m24m/4m24m:4m0m where 4m24m is the transport type to use to connect to the font server (e.g., 1munix 22mfor UNIX-domain sockets or 1mtcp 22mfor a TCP/IP connection), 4m24m is the hostname of the machine running the font server, and 4m24m 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: 4m/usr/X11R6/lib/X11/fonts/misc/0m 4m/usr/X11R6/lib/X11/fonts/Speedo/0m 4m/usr/X11R6/lib/X11/fonts/Type1/0m 4m/usr/X11R6/lib/X11/fonts/CID/0m 4m/usr/X11R6/lib/X11/fonts/75dpi/0m 4m/usr/X11R6/lib/X11/fonts/100dpi/0m The recommended font path contains the following font path ele- ments: 4m/usr/X11R6/lib/X11/fonts/local/0m 4m/usr/X11R6/lib/X11/fonts/misc/0m 4m/usr/X11R6/lib/X11/fonts/75dpi/:unscaled0m 4m/usr/X11R6/lib/X11/fonts/100dpi/:unscaled0m 4m/usr/X11R6/lib/X11/fonts/Type1/0m 4m/usr/X11R6/lib/X11/fonts/CID/0m 4m/usr/X11R6/lib/X11/fonts/Speedo/0m 4m/usr/X11R6/lib/X11/fonts/75dpi/0m 4m/usr/X11R6/lib/X11/fonts/100dpi/0m Font path elements that are found to be invalid are removed from the font path when the server starts up. 1mRGBPath "4m22mpath24m1m"0m 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: 4m/usr/X11R6/lib/X11/rgb0m Note that an implicit 4m.txt24m is added to this path if the server was com- piled to use text rather than binary format RGB color databases. 1mModulePath "4m22mpath24m1m"0m sets the search path for loadable XFree86 server modules. This path is a comma separated list of directories which the XFree86 server searches for loadable modules loading in the order speci- fied. Multiple 1mModulePath 22mentries may be specified, and they will be concatenated to build the module search path used by the server. 1mOptions0m Option flags may be specified in 1mFiles 22msections. 1mSERVERFLAGS SECTION0m The config file may have multiple 1mServerFlags 22msections. These are used to specify some global XFree86 server options. Earlier 1mServerFlags0m sections have priority over later sections. This means that an option specified in a 1mServerFlags 22msection cannot be overridden by a later 1mServerFlags 22msection. Except for the 1mIdentifier 22mentry, all of the entries in this section are 1mOptions22m, although for compatibility pur- poses some of the old style entries are still recognised. Those old style entries are not documented here, and using them is discouraged. The 1mServerFlags 22msection is optional, as are the entries that may be specified in it. 1mOptions 22mspecified in this section (with the exception of the 1m"Default-0m 1mServerLayout" Option22m) may be overridden by 1mOptions 22mspecified in the active 1mServerLayout 22msection. Options with command line equivalents are overridden when their command line equivalent is used. Entries recog- nised by this section are: 1mIdentifier "4m22mname24m1m"0m specifies an optional identifying name for the 1mServerFlags 22msec- tion. 1mOption "DefaultServerLayout" "4m22mlayout-id24m1m"0m This specifies the default 1mServerLayout 22msection to use in the absence of the 1m-layout 22mcommand line option. 1mOption "NoTrapSignals" "4m22mboolean24m1m"0m This prevents the XFree86 server from trapping a range of unex- pected fatal signals and exiting cleanly. Instead, the XFree86 server will die and drop core where the fault occurred. The default behaviour is for the XFree86 server to exit cleanly, but still drop a core file. In general you never want to use this option unless you are debugging an XFree86 server problem and know how to deal with the consequences. 1mOption "DontVTSwitch" "4m22mboolean24m1m"0m This disallows the use of the 1mCtrl+Alt+F4m22mn24m sequence (where F4mn0m refers to one of the numbered function keys). That sequence is normally used to switch to another "virtual terminal" on operat- ing systems that have this feature. When this option is enabled, that key sequence has no special meaning and is passed to clients. Default: off. 1mOption "DontZap" "4m22mboolean24m1m"0m This disallows the use of the 1mCtrl+Alt+Backspace 22msequence. That sequence is normally used to terminate the XFree86 server. When this option is enabled, that key sequence has no special meaning and is passed to clients. Default: off. 1mOption "DontZoom" "4m22mboolean24m1m"0m This disallows the use of the 1mCtrl+Alt+Keypad-Plus 22mand 1mCtrl+Alt+Keypad-Minus 22msequences. 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. 1mOption "DisableVidModeExtension" "4m22mboolean24m1m"0m 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. 1mOption "AllowNonLocalXvidtune" "4m22mboolean24m1m"0m This allows the xvidtune client (and other clients that use the VidMode extension) to connect from another host. Default: off. 1mOption "DisableModInDev" "4m22mboolean24m1m"0m This disables the parts of the XFree86-Misc extension that can be used to modify the input device settings dynamically. Default: that functionality is enabled. 1mOption "AllowNonLocalModInDev" "4m22mboolean24m1m"0m This allows a client to connect from another host and change keyboard and mouse settings in the running server. Default: off. 1mOption "AllowMouseOpenFail" "4m22mboolean24m1m"0m This allows the server to start up even if the mouse device can't be opened/initialised. Default: false. 1mOption "VTInit" "4m22mcommand24m1m"0m Runs 4mcommand24m after the VT used by the server has been opened. The command string is passed to "/bin/sh -c", 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 initiali- sation commands to be run. This option should rarely be needed. Default: not set. 1mOption "VTSysReq" "4m22mboolean24m1m"0m enables the SYSV-style VT switch sequence for non-SYSV systems which support VT switching. This sequence is 1mAlt-SysRq 22mfollowed by a function key (1mFn22m). This prevents the XFree86 server trap- ping the keys used for the default VT switch sequence, which means that clients can access them. Default: off. 1mOption "XkbDisable" "4m22mboolean24m1m"0m disable/enable the XKEYBOARD extension. The -kb command line option overrides this config file option. Default: XKB is enabled. 1mOption "BlankTime" "4m22mtime24m1m"0m sets the inactivity timeout for the blanking phase of the screensaver. 4mtime24m is in minutes. This is equivalent to the XFree86 server's `-s' flag, and the value can be changed at run- time with xset(1). Default: 10 minutes. 1mOption "StandbyTime" "4m22mtime24m1m"0m sets the inactivity timeout for the "standby" phase of DPMS mode. 4mtime24m 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 1m"DPMS" 22moption set (see the MONITOR section below). 1mOption "SuspendTime" "4m22mtime24m1m"0m sets the inactivity timeout for the "suspend" phase of DPMS mode. 4mtime24m 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 1m"DPMS" 22moption set (see the MONITOR section below). 1mOption "OffTime" "4m22mtime24m1m"0m sets the inactivity timeout for the "off" phase of DPMS mode. 4mtime24m 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 1m"DPMS" 22moption set (see the MONITOR section below). 1mOption "Pixmap" "4m22mbpp24m1m"0m This sets the pixmap format to use for depth 24. Allowed values for 4mbpp24m 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. 1mOption "PC98" "4m22mboolean24m1m"0m Specify that the machine is a Japanese PC-98 machine. This should not be enabled for anything other than the Japanese-spe- cific PC-98 architecture. Default: auto-detected. 1mOption "Log" "4m22mlogflag24m1m"0m This option enables special handling for log files that may be useful when debugging certain types of problems. The values for 4mlogflag24m are 1mFlush 22mand 1mSync22m. 1mFlush 22mcauses the log file buffer to be flushed after each write. 1mSync 22mcauses the log file buffer to be flushed and the file data to be written to the disk after each write. The default is for neither of these flags to be enabled. Enabling these flags during normal operation may degrade performance and/or lengthen startup time. 1mOption "NoPM" "4m22mboolean24m1m"0m Disables something to do with power management events. Default: PM enabled on platforms that support it. 1mOption "Xinerama" "4m22mboolean24m1m"0m enable or disable XINERAMA extension. Default is disabled. 1mOption "AllowDeactivateGrabs" "4m22mboolean24m1m"0m This option enables the use of the 1mCtrl+Alt+Keypad-Divide 22mkey sequence to deactivate any active keyboard and mouse grabs. Default: off. 1mOption "AllowClosedownGrabs" "4m22mboolean24m1m"0m This option enables the use of the 1mCtrl+Alt+Keypad-Multiply 22mkey 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 1mAllowDeactivateGrabs 22mand 1mAllowClosedown-0m 1mGrabs 22mwill 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. 1mOption "HandleSpecialKeys" "4m22mwhen24m1m"0m This option controls when the server uses the builtin handler to process special key combinations (such as 1mCtrl+Alt+Backspace22m). 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 4mwhen24m can be 1mAlways22m, 1mNever22m, or 1mWhenNeeded22m. Default: Use the builtin handler only if needed. The server will scan the keymap for a mapping to the 1mTerminate 22maction and, if found, use XKEYBOARD for processing actions, otherwise the builtin handler will be used. 1mMODULE SECTION0m The config file may have multiple 1mModule 22msection. They are used to specify additional XFree86 server modules to be loaded. This section is ignored when the XFree86 server is built in static form. The types of modules normally loaded in this section are XFree86 server extension modules, and font rasteriser modules. Most other module types are loaded automatically when they are needed via other mechanisms. The 1mModule 22msection is optional, as are all of the entries that may be spec- ified in it. 1mIdentifier "4m22mname24m1m"0m specifies an optional identifying name for the 1mModule 22msection. 1mOptions0m Option flags may be specified in 1mModule 22msections. Entries that identify which modules to pre-load may be in two forms. The first and most commonly used form is an entry that uses the 1mLoad0m keyword, as described here: 1mLoad "4m22mmodulename24m1m"0m This instructs the server to load the module called 4mmodulename24m. 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 fol- lowing entry: 1mLoad "type1"0m The second form of entry is a 1mSubSection, 22mwith the subsection name being the module name, and the contents of the 1mSubSection 22mbeing 1mOptions0m 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 dis- abled by using the following entry: 1mSubSection "extmod"0m 1mOption "omit XFree86-DGA"0m 1mEndSubSection0m Modules are searched for in each directory specified in the 1mModulePath0m 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 con- tents of the following directories: /usr/X11R6/lib/modules/fonts /usr/X11R6/lib/modules/extensions The "bitmap" font modules is loaded automatically. It is recommended that at very least the "extmod" extension module be loaded. If it isn't some commonly used server extensions (like the SHAPE extension) will not be available. 1mINPUTDEVICE SECTION0m The config file may have multiple 1mInputDevice 22msections. 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 con- figuration for the missing ones will be used. Currently the default configuration may not work as expected on all platforms. 1mInputDevice 22msections have the following format: 1mSection "InputDevice"0m 1mIdentifier "4m22mname24m1m"0m 1mDriver "4m22minputdriver24m1m"0m 4moptions0m 4m...0m 1mEndSection0m The 1mIdentifier 22mand 1mDriver 22mentries are required in all 1mInputDevice 22msec- tions. All other entries are optional. The 1mIdentifier 22mentry specifies the unique name for this input device. The 1mDriver 22mentry specifies the name of the driver to use for this input device. When using the loadable server, the input driver module "4minputdriver24m" will be loaded for each active 1mInputDevice 22msection. An 1mInputDevice 22msection is considered active if it is referenced by an active 1mServerLayout 22msection, if it is referenced by the 1m-keyboard 22mor 1m-pointer 22mcommand line options, or if it is selected implicitly as the core pointer or keyboard device in the absence of such explicit refer- ences. The most commonly used input drivers are "keyboard" and "mouse". In the absence of an explicitly specified core input device, the first 1mInputDevice 22mmarked as 1mCorePointer 22m(or 1mCoreKeyboard22m) is used. If there is no match there, the first 1mInputDevice 22mthat uses the "mouse" (or "keyboard" or "kbd") driver is used. The final fallback is to use built-in default configurations. 1mInputDevice 22msections recognise some driver-independent 1mOptions22m, which are described here. See the individual input driver manual pages for a description of the device-specific options. 1mOption "CorePointer"0m 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 1mServerLayout0m section, or from the 1m-pointer 22mcommand 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 1mPointer 22msection is used. 1mOption "CoreKeyboard"0m 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 1mServerLayout0m section, or from the 1m-keyboard 22mcommand line option, then the first input device that is capable of being used as a core key- board will be selected as the core keyboard. This option is implicitly set when the obsolete 1mKeyboard 22msection is used. 1mOption "AlwaysCore" "4m22mboolean24m1m"0m 1mOption "SendCoreEvents" "4m22mboolean24m1m"0m 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). 1mOption "HistorySize" "4m22mnumber24m1m"0m Sets the motion history size. Default: 0. 1mOption "SendDragEvents" "4m22mboolean24m1m"0m ??? 1mDEVICE SECTION0m The config file may have multiple 1mDevice 22msections. There must be at least one, for the video card being used. 1mDevice 22msections have the following format: 1mSection "Device"0m 1mIdentifier "4m22mname24m1m"0m 1mDriver "4m22mdriver24m1m"0m 4mentries0m 4m...0m 1mEndSection0m The 1mIdentifier 22mand 1mDriver 22mentries are required in all 1mDevice 22msections. All other entries are optional. The 1mIdentifier 22mentry specifies the unique name for this graphics device. The 1mDriver 22mentry specifies the name of the driver to use for this graphics device. When using the loadable server, the driver mod- ule "4mdriver24m" will be loaded for each active 1mDevice 22msection. A 1mDevice0m section is considered active if it is referenced by an active 1mScreen0m section. 1mDevice 22msections recognise some driver-independent entries and 1mOptions22m, 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 1mOptions 22mlisted here (but not the other entries) may be specified in the 1mScreen 22msection instead of here in the 1mDevice 22msection. 1mBusID "4m22mbus-id24m1m"0m This specifies the bus location of the graphics card. For PCI/AGP cards, the 4mbus-id24m string has the form 1mPCI:4m22mbus24m1m:4m22mdevice24m1m:4m22mfunction24m (e.g., "PCI:1:0:0" 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 XFree86 server with the 1m-scanpci 22mcommand line option. 1mScreen 4m22mnumber0m This option is mandatory for cards where a single PCI entity can drive more than one display (i.e., multiple CRTCs sharing a sin- gle graphics accelerator and video memory). One 1mDevice 22msection is required for each head, and this parameter determines which head each of the 1mDevice 22msections applies to. The legal values of 4mnumber24m range from 0 to one less than the total number of heads per entity. Most drivers require that the primary screen (0) be present. 1mChipset "4m22mchipset24m1m"0m 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 docu- mentation recommends that you do. 1mRamdac "4m22mramdac-type24m1m"0m 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. 1mDacSpeed 4m22mspeed0m 1mDacSpeed 4m22mspeed-824m 4mspeed-1624m 4mspeed-2424m 4mspeed-320m 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 give, 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 rat- ing 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 documen- tation recommends that you do. 1mClocks 4m22mclock24m 4m...0m 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 1mClocks 22mlines 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. 1mClockChip "4m22mclockchip-type24m1m"0m This optional entry is used to specify the clock chip type on graphics boards which have a programmable clock generator. Only a few XFree86 drivers support programmable clock chips. For details, see the appropriate driver manual page. 1mVideoRam 4m22mmem0m 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 XFree86 server probes the graphics board to determine this quantity. The driver-specific documentation should indicate when it might be needed. 1mBiosBase 4m22mbaseaddress0m 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. 1mMemBase 4m22mbaseaddress0m 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-spe- cific documentation recommends it. 1mIOBase 4m22mbaseaddress0m 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. 1mChipID 4m22mid0m 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. 1mChipRev 4m22mrev0m 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. 1mTextClockFreq 4m22mfreq0m 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. 1mIRQ 4m22minterrupt-number0m This optional entry allows an interrupt number to be specified. 1mOptions0m Option flags may be specified in the 1mDevice 22msections. 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 1mScreen 22msection, and they may also be included here. 1mVIDEOADAPTOR SECTION0m The config file may have multiple 1mVideoAdaptor 22msections, which may be referenced from 1mScreen 22msections. 1mVideoAdaptor 22msections have the following format: 1mSection "VideoAdaptor"0m 1mIdentifier "4m22mname24m1m"0m 4mentries0m 4m...0m 1mSubSection "Port"0m 4mentries0m 4m...0m 1mEndSubSection0m 4m...0m 1mEndSection0m The only mandatory entry in a 1mVideoAdaptor 22msection is the 1mIdentifier22m. Other entries include: 1mVendorName "4m22mvendor24m1m"0m This optional entry specifies the video adaptor's manufacturer. 1mBoardName "4m22mmodel24m1m"0m This optional entry specifies the video adaptor's model name. 1mOptions0m may be specified in the 1mVideoAdaptor 22msection. The 1mPort SubSections 22mprovide information about video adaptor ports. Each of these may contain an 1mIdentifier 22mentry and 1mOptions22m. 1mMONITOR SECTION0m The config file may have multiple 1mMonitor 22msections. There should nor- mally be at least one, for the monitor being used, but a default con- figuration will be created when one isn't specified. 1mMonitor 22msections have the following format: 1mSection "Monitor"0m 1mIdentifier "4m22mname24m1m"0m 4mentries0m 4m...0m 1mEndSection0m The only mandatory entry in a 1mMonitor 22msection is the 1mIdentifier 22mentry. The 1mIdentifier 22mentry specifies the unique name for this monitor. The 1mMonitor 22msection provides information about the specifications of the monitor, monitor-specific 1mOptions22m, 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 1mMonitor 22msection (with the 1mModes22m, 1mModeLine22m, or 1mUseModes 22mkeywords), built-in modes with the same names are not included. Built-in modes with different names are, how- ever, still implicitly included. The entries that may be used in 1mMonitor 22msections are described below. 1mVendorName "4m22mvendor24m1m"0m This optional entry specifies the monitor's manufacturer. 1mModelName "4m22mmodel24m1m"0m This optional entry specifies the monitor's model. 1mHorizSync 4m22mhorizsync-range0m gives the range(s) of horizontal sync frequencies supported by the monitor. 4mhorizsync-range24m may be a comma separated list of either discrete values or ranges of values. A range of values is two values separated by a dash. By default the values are in units of kHz. They may be specified in MHz or Hz if 1mMHz 22mor 1mHz0m is added to the end of the line. The data given here is used by the XFree86 server to determine if video modes are within the specifications of the monitor. This information should be available in the monitor's handbook. If this entry is omitted, a default range of 28-33kHz is used. 1mVertRefresh 4m22mvertrefresh-range0m gives the range(s) of vertical refresh frequencies supported by the monitor. 4mvertrefresh-range24m may be a comma separated list of either discrete values or ranges of values. A range of values is two values separated by a dash. By default the values are in units of Hz. They may be specified in MHz or kHz if 1mMHz 22mor 1mkHz0m is added to the end of the line. The data given here is used by the XFree86 server to determine if video modes are within the specifications of the monitor. This information should be available in the monitor's handbook. If this entry is omitted, a default range of 43-72Hz is used. 1mDisplaySize 4m22mwidth24m 4mheight0m This optional entry gives the width and height, in millimetres, of the picture area of the monitor. If given this is used to calculate the horizontal and vertical pitch (DPI) of the screen. 1mGamma 4m22mgamma-value0m 1mGamma 4m22mred-gamma24m 4mgreen-gamma24m 4mblue-gamma0m This is an optional entry that can be used to specify the gamma correction for the monitor. It may be specified as either a single value or as three separate RGB values. The values should be in the range 0.1 to 10.0, and the default is 1.0. Not all drivers are capable of using this information. 1mUseModes "4m22mmodesection-id24m1m"0m Include the set of modes listed in the 1mModes 22msection called 4mmod-0m 4mesection-id.24m This make all of the modes defined in that section available for use by this monitor. 1mMode "4m22mname24m1m"0m This is an optional multi-line entry that can be used to provide definitions for video modes for the monitor. In most cases this isn't necessary because the built-in set of VESA standard modes will be sufficient. The 1mMode 22mkeyword indicates the start of a multi-line video mode description. The mode description is ter- minated with the 1mEndMode 22mkeyword. The mode description consists of the following entries: 1mDotClock 4m22mclock0m is the dot (pixel) clock rate to be used for the mode. 1mHTimings 4m22mhdisp24m 4mhsyncstart24m 4mhsyncend24m 4mhtotal0m specifies the horizontal timings for the mode. 1mVTimings 4m22mvdisp24m 4mvsyncstart24m 4mvsyncend24m 4mvtotal0m specifies the vertical timings for the mode. 1mFlags "4m22mflag24m1m" 4m22m...0m specifies an optional set of mode flags, each of which is a separate string in double quotes. 1m"Interlace" 22mindicates that the mode is interlaced. 1m"DoubleScan" 22mindicates a mode where each scanline is doubled. 1m"+HSync" 22mand 1m"-HSync" 22mcan be used to select the polarity of the HSync signal. 1m"+VSync" 22mand 1m"-VSync" 22mcan be used to select the polarity of the VSync signal. 1m"Composite" 22mcan be used to specify com- posite sync on hardware where this is supported. Addition- ally, on some hardware, 1m"+CSync" 22mand 1m"-CSync" 22mmay be used to select the composite sync polarity. 1mHSkew 4m22mhskew0m 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 sup- plied 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. 1mVScan 4m22mvscan0m 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. Gener- ally, the 1m"DoubleScan" Flag 22mmentioned above doubles this value. 1mModeLine "4m22mname24m1m" 4m22mmode-description0m This entry is a more compact version of the 1mMode 22mentry, 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 4mmode-description24m 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 4mhdisp24m, 4mhsync-0m 4mstart24m, 4mhsyncend24m, and 4mhtotal24m values. The third section is a list of four numbers specifying the vertical timings. These numbers are the 4mvdisp24m, 4mvsyncstart24m, 4mvsyncend24m, and 4mvtotal24m values. The final section is a list of flags specifying other characteris- tics of the mode. 1mInterlace 22mindicates that the mode is inter- laced. 1mDoubleScan 22mindicates a mode where each scanline is dou- bled. 1m+HSync 22mand 1m-HSync 22mcan be used to select the polarity of the HSync signal. 1m+VSync 22mand 1m-VSync 22mcan be used to select the polarity of the VSync signal. 1mComposite 22mcan be used to specify composite sync on hardware where this is supported. Addition- ally, on some hardware, 1m+CSync 22mand 1m-CSync 22mmay be used to select the composite sync polarity. The 1mHSkew 22mand 1mVScan 22moptions men- tioned above in the 1mModes 22mentry description can also be used here. 1mOption "DPMS" "4m22mboolean24m1m"0m Set whether DPMS is enabled for the monitor. The default is taken from the monitor's DDC/EDID information if available, or false if not. 1mOption "TargetRefresh" "4m22mrefresh24m1m"0m Sets a target refresh rate to use for the monitor. If the moni- tor has valid modes with a refresh rate greater or equal to this value, those with a lower refresh rate will not be considered when determining the default resolution to use. This is improves the default resolution selection when none is specified explicitly. Default: 1mTargetRefresh 22mnot used. 1mOption "SyncOnGreen" "4m22mboolean24m1m"0m Set whether sync-on-green should be enabled. The availability of this option is driver-specific. Default: false. 1mOption "PreferredMode" "4m22mXres24m1mx4m22mYres24m1m"0m Sets a preferred resolution to use for the default mode. By default the preferred mode resolution is taken from the DDC/EDID data if it is available and if it is provides a default mode preference. This is typically true for flat panel displays, which have a native/preferred resolution. This option is not used if the 1mUsePreferredMode 22moption is false. 1mOption "UsePreferredMode" "4m22mboolean24m1m"0m Controls whether or not a preferred mode, either detected from the monitor's DDC/EDID data or provided explicitly with the 1mPre-0m 1mferredMode 22moption, is used. Default: true. 1mOptions0m Additional 1mOption 22mflags, including driver-specific options, may be included in 1mMonitor 22msections. 1mMODES SECTION0m The config file may have multiple 1mModes 22msections, or none. These sec- tions provide a way of defining sets of video modes independently of the 1mMonitor 22msections. 1mMonitor 22msections may include the definitions provided in these sections by using the 1mUseModes 22mkeyword. In most cases the 1mModes 22msections are not necessary because the built-in set of VESA standard modes will be sufficient. 1mModes 22msections have the following format: 1mSection "Modes"0m 1mIdentifier "4m22mname24m1m"0m 4mentries0m 4m...0m 1mEndSection0m The 1mIdentifier 22mentry specifies the unique name for this set of mode descriptions. The other entries permitted in 1mModes 22msections are the 1mMode 22mand 1mModeLine 22mentries that are described above in the 1mMonitor 22msec- tion, as well as 1mOptions22m. 1mSCREEN SECTION0m The config file may have multiple 1mScreen 22msections. There must be at least one, for the "screen" being used. A "screen" represents the binding of a graphics device (1mDevice 22msection) and one or more monitors (1mMonitor 22msections). A 1mScreen 22msection is considered "active" if it is referenced by an active 1mServerLayout 22msection or by the 1m-screen 22mcommand line option. If neither of those is present, the first 1mScreen 22msection found in the config file is considered the active one. 1mScreen 22msections have the following format: 1mSection "Screen"0m 1mIdentifier "4m22mname24m1m"0m 1mDevice "4m22mdevid24m1m"0m 1mMonitor "4m22mmonid24m1m"0m 4mentries0m 4m...0m 1mSubSection "Display"0m 4mentries0m 4m...0m 1mEndSubSection0m 4m...0m 1mEndSection0m The 1mIdentifier 22mand 1mDevice 22mentries are mandatory. All others are optional. The 1mIdentifier 22mentry specifies the unique name for this screen. The 1mScreen 22msection provides information specific to the whole screen, including screen-specific 1mOptions22m. In multi-head configurations, there will be multiple active 1mScreen 22msections, one for each head. The entries available for this section are: 1mDevice "4m22mdevice-id24m1m"0m This mandatory entry specifies the 1mDevice 22msection to be used for this screen. This is what ties a specific graphics card to a screen. The 4mdevice-id24m must match the 1mIdentifier 22mof a 1mDevice0m section in the config file. 1mMonitor 4m22mmonitor-num24m 1m"4m22mmonitor-id24m1m"0m One of these entries may be given for each monitor associated with this screen. In the absence of these entries, at least one default monitor will be created for the screen. The 4mmonitor-id0m field is mandatory, and specifies the 1mMonitor 22msection being ref- erenced. The 4mmonitor-num24m field is required when more than one monitor is being associated with the screen. Each referenced monitor should be given a unique monitor number. This monitor number may be given special significance by the driver, and it is also used to identify which 1mDisplay 22msubsection(s) are associ- ated with the screen/monitor. If this field is omitted in a multiple-monitor configuration, default values will be assigned. This is not recommended, and this behaviour may change in future revisions. If a 1mMonitor 22mname is not specified, a default configuration is used. Currently the default configuration may not function as expected on all platforms. 1mVideoAdaptor "4m22mxv-id24m1m"0m specifies an optional Xv video adaptor description to be used with this screen. 1mDefaultDepth 4m22mdepth0m specifies which color depth the server should use by default. The 1m-depth 22mcommand line option can be used to override this. If neither is specified, the default depth is driver-specific, but in most cases is 8. 1mDefaultFbBpp 4m22mbpp0m specifies which framebuffer layout to use by default. The 1m-fbbpp 22mcommand line option can be used to override this. In most cases the driver will chose the best default value for this. The only case where there is even a choice in this value is for depth 24, where some hardware supports both a packed 24 bit framebuffer layout and a sparse 32 bit framebuffer layout. 1mOptions0m Various 1mOption 22mflags may be specified in the 1mScreen 22msection. Some are driver-specific and are described in the driver docu- mentation. Others are driver-independent, and will eventually be described here. 1mOption "Accel"0m Enables XAA (X Acceleration Architecture), a mechanism that makes video cards' 2D hardware acceleration available to the XFree86 server. This option is on by default, but it may be necessary to turn it off if there are bugs in the driver. There are many options to disable specific accelerated operations, listed below. Note that disabling an operation will have no effect if the operation is not accelerated (whether due to lack of support in the hardware or in the driver). 1mOption "BiosLocation" "4m22maddress24m1m"0m Set the location of the BIOS for the Int10 module. One may select a BIOS of another card for posting or the legacy V_BIOS range located at 0xc0000 or an alternative address (BUS_ISA). This is only useful under very special circumstances and should be used with extreme care. 1mOption "InitPrimary" "4m22mboolean24m1m"0m Use the Int10 module to initialize the primary graphics card. Normally, only secondary cards are soft-booted using the Int10 module, as the primary card has already been initialized by the BIOS at boot time. Default: false. 1mOption "NoInt10" "4m22mboolean24m1m"0m Disables the Int10 module, a module that uses the int10 call to the BIOS of the graphics card to initialize it. Default: false. 1mOption "NoMTRR"0m Disables MTRR (Memory Type Range Register) support, a feature of modern processors which can improve video performance by a fac- tor of up to 2.5. Some hardware has buggy MTRR support, and some video drivers have been known to exhibit problems when MTRR's are used. 1mOption "XaaNoCPUToScreenColorExpandFill"0m Disables accelerated rectangular expansion blits from source patterns stored in system memory (using a memory-mapped aper- ture). 1mOption "XaaNoColor8x8PatternFillRect"0m Disables accelerated fills of a rectangular region with a full- color pattern. 1mOption "XaaNoColor8x8PatternFillTrap"0m Disables accelerated fills of a trapezoidal region with a full- color pattern. 1mOption "XaaNoDashedBresenhamLine"0m Disables accelerated dashed Bresenham line draws. 1mOption "XaaNoDashedTwoPointLine"0m Disables accelerated dashed line draws between two arbitrary points. 1mOption "XaaNoImageWriteRect"0m Disables accelerated transfers of full-color rectangular pat- terns from system memory to video memory (using a memory-mapped aperture). 1mOption "XaaNoMono8x8PatternFillRect"0m Disables accelerated fills of a rectangular region with a mono- chrome pattern. 1mOption "XaaNoMono8x8PatternFillTrap"0m Disables accelerated fills of a trapezoidal region with a mono- chrome pattern. 1mOption "XaaNoOffscreenPixmaps"0m Disables accelerated draws into pixmaps stored in offscreen video memory. 1mOption "XaaNoPixmapCache"0m Disables caching of patterns in offscreen video memory. 1mOption "XaaNoScanlineCPUToScreenColorExpandFill"0m Disables accelerated rectangular expansion blits from source patterns stored in system memory (one scan line at a time). 1mOption "XaaNoScanlineImageWriteRect"0m Disables accelerated transfers of full-color rectangular pat- terns from system memory to video memory (one scan line at a time). 1mOption "XaaNoScreenToScreenColorExpandFill"0m Disables accelerated rectangular expansion blits from source patterns stored in offscreen video memory. 1mOption "XaaNoScreenToScreenCopy"0m Disables accelerated copies of rectangular regions from one part of video memory to another part of video memory. 1mOption "XaaNoSolidBresenhamLine"0m Disables accelerated solid Bresenham line draws. 1mOption "XaaNoSolidFillRect"0m Disables accelerated solid-color fills of rectangles. 1mOption "XaaNoSolidFillTrap"0m Disables accelerated solid-color fills of Bresenham trapezoids. 1mOption "XaaNoSolidHorVertLine"0m Disables accelerated solid horizontal and vertical line draws. 1mOption "XaaNoSolidTwoPointLine"0m Disables accelerated solid line draws between two arbitrary points. Each 1mScreen 22msection may optionally contain one or more 1mDisplay 22msubsec- tions. Those subsections provide depth, fbbpp and monitor specific configuration information, and the ones chosen depend on the depth and/or fbbpp that is being used for the screen, as well as the monitor number(s) in multi-monitor configurations. The 1mDisplay 22msubsection for- mat is described in the section below. 1mDISPLAY SUBSECTION0m Each 1mScreen 22msection may have multiple 1mDisplay 22msubsections. The "active" 1mDisplay 22msubsections are the first for each monitor number that match the depth and/or fbbpp values being used, or failing that, the first for each monitor number that has neither a depth or fbbpp value specified. Display subsections with no monitor number specified are used for single monitor per screen configurations. The 1mDisplay 22msubsec- tions are optional. When there isn't one that matches the monitor num- ber and/or depth and/or fbbpp values being used, all the parameters that can be specified here fall back to their defaults. 1mDisplay 22msubsections have the following format: 1mSubSection "Display"0m 1mMonitor 4m22mmonitor-num0m 1mDepth 4m22mdepth0m 4mentries0m 4m...0m 1mEndSubSection0m None of the entries in a 1mDisplay 22msubsection are mandatory. 1mMonitor 4m22mmonitor-num0m This entry specifies which 1mMonitor 22mentry of the 1mScreen 22msection that this 1mDisplay 22msubsection applies to. This number should match the monitor number of one of the 1mMonitor 22mreferences in the 1mScreen 22mscreen. If it doesn't match, then this 1mDisplay 22msubsec- tion will be ignored. If this entry is omitted, it is applied to single-monitor configurations. For multi-monitor configura- tions, the driver may also use information in this subsection for screen-wide parameters. Not all of the parameters in this subsection make sense on a per-monitor basis. Which get used and how they get used is currently up to the driver. Entries that are relevant to multi-monitor configurations include 1mModes22m, 1mVirtual22m, 1mViewPort22m, and 1mOptions22m. 1mDepth 4m22mdepth0m This entry specifies what colour depth the 1mDisplay 22msubsection is to be used for. This entry is usually specified, but it may be omitted to create a match-all 1mDisplay 22msubsection or when wishing to match only against the 1mFbBpp 22mparameter. The range of 4mdepth0m values that are allowed depends on the driver. Most driver sup- port 8, 15, 16 and 24. Some also support 1 and/or 4, and some may support other values (like 30). Note: 4mdepth24m means the num- ber of bits in a pixel that are actually used to determine the pixel colour. 32 is not a valid 4mdepth24m value. Most hardware that uses 32 bits per pixel only uses 24 of them to hold the colour information, which means that the colour depth is 24, not 32. 1mFbBpp 4m22mbpp0m This entry specifies the framebuffer format this 1mDisplay 22msubsec- tion is to be used for. This entry is only needed when provid- ing depth 24 configurations that allow a choice between a 24 bpp packed framebuffer format and a 32bpp sparse framebuffer format. In most cases this entry should not be used. 1mWeight 4m22mred-weight24m 4mgreen-weight24m 4mblue-weight0m This optional entry specifies the relative RGB weighting to be used for a screen is being used at depth 16 for drivers that allow multiple formats. This may also be specified from the command line with the 1m-weight 22moption (see XFree86(1)). 1mVirtual 4m22mxdim24m 4mydim0m This optional entry specifies the virtual screen resolution to be used. 4mxdim24m must be a multiple of either 8 or 16 for most drivers, and a multiple of 32 when running in monochrome mode. The given value will be rounded down if this is not the case. Video modes which are too large for the specified virtual size will be rejected. If this entry is not present, the virtual screen resolution will be set to accommodate all the valid video modes given in the 1mModes 22mentry. Some drivers/hardware combina- tions do not support virtual screens. Refer to the appropriate driver-specific documentation for details. 1mViewPort 4m22mx024m 4my00m This optional entry sets the upper left corner of the initial display. This is only relevant when the virtual screen resolu- tion 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. 1mModes "4m22mmode-name24m1m" 4m22m...0m This optional entry specifies the list of video modes to use. Each 4mmode-name24m specified must be in double quotes. They must correspond to those specified or referenced in the appropriate 1mMonitor 22msection (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 1mCtrl+Alt+Keypad-Plus 22mand to the previous mode with 1mCtrl+Alt+Key-0m 1mpad-Minus22m. When this entry is omitted, the valid modes refer- enced by the appropriate 1mMonitor 22msection will be used. If the 1mMonitor 22msection contains no modes, then the selection will be taken from the built-in VESA standard modes. 1mVisual "4m22mvisual-name24m1m"0m 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 1mPseudoColor22m): 1mStaticGray0m 1mGrayScale0m 1mStaticColor0m 1mPseudoColor0m 1mTrueColor0m 1mDirectColor0m The visual type available for the depths 15, 16 and 24 are (default is 1mTrueColor22m): 1mTrueColor0m 1mDirectColor0m Not all drivers support 1mDirectColor 22mat these depths. The visual types available for the depth 4 are (default is 1mStat-0m 1micColor22m): 1mStaticGray0m 1mGrayScale0m 1mStaticColor0m 1mPseudoColor0m The visual type available for the depth 1 (monochrome) is 1mStat-0m 1micGray22m. 1mBlack 4m22mred24m 4mgreen24m 4mblue0m This optional entry allows the "black" colour to be specified. This is only supported at depth 1. The default is black. 1mWhite 4m22mred24m 4mgreen24m 4mblue0m This optional entry allows the "white" colour to be specified. This is only supported at depth 1. The default is white. 1mOptions0m Option flags may be specified in the 1mDisplay 22msubsections. These may include driver-specific options and driver-independent options. The former are described in the driver-specific docu- mentation. Some of the latter are described above in the sec- tion about the 1mScreen 22msection, and they may also be included here. 1mSERVERLAYOUT SECTION0m The config file may have multiple 1mServerLayout 22msections. A "server layout" represents the binding of one or more screens (1mScreen 22msections) and one or more input devices (1mInputDevice 22msections) to form a complete configuration. In multi-head configurations, it also specifies the relative layout of the heads. A 1mServerLayout 22msection is considered "active" if it is referenced by the 1m-layout 22mcommand line option or by an 1mOption "DefaultServerLayout" 22mentry in the 1mServerFlags 22msection (the former takes precedence over the latter). If those options are not used, the first 1mServerLayout 22msection found in the config file is con- sidered the active one. If no 1mServerLayout 22msections are present, the single active screen and two active (core) input devices are selected as described in the relevant sections above. 1mServerLayout 22msections have the following format: 1mSection "ServerLayout"0m 1mIdentifier "4m22mname24m1m"0m 1mScreen "4m22mscreen-id24m1m"0m 4m...0m 1mInputDevice "4m22midev-id24m1m"0m 4m...0m 4moptions0m 4m...0m 1mEndSection0m Each 1mServerLayout 22msection must have an 1mIdentifier 22mentry and at least one 1mScreen 22mentry. The 1mIdentifier 22mentry specifies the unique name for this server layout. The 1mServerLayout 22msection provides information specific to the whole session, including session-specific 1mOptions22m. The 1mServerFlags 22moptions (described above) may be specified here, and ones given here override those given in the 1mServerFlags 22msection. The entries that may be used in this section are described here. 1mScreen 4m22mscreen-num24m 1m"4m22mscreen-id24m1m" 4m22mposition-information0m One of these entries must be given for each screen being used in a session. The 4mscreen-id24m field is mandatory, and specifies the 1mScreen 22msection being referenced. The 4mscreen-num24m field is optional, and may be used to specify the screen number in multi- head configurations. When this field is omitted, the screens will be numbered in the order that they are listed in. The num- bering starts from 0, and must be consecutive. The optional 4mposition-information24m field describes the way multiple screens are positioned. When this information is not provided, the positioning of the screen defaults to 1mAbsolute 4m22m024m 4m024m. There are a number of different ways that this information can be provided: 4mx24m 4my0m 1mAbsolute 4m22mx24m 4my0m These both specify that the upper left corner's coordinates are (4mx24m,4my24m). The 1mAbsolute 22mkeyword is optional. Some older versions of XFree86 (4.2 and earlier) don't recognise the 1mAbsolute 22mkeyword, so it's safest to just specify the coordi- nates without it. 1mRightOf "4m22mscreen-id24m1m"0m 1mLeftOf "4m22mscreen-id24m1m"0m 1mAbove "4m22mscreen-id24m1m"0m 1mBelow "4m22mscreen-id24m1m"0m 1mRelative "4m22mscreen-id24m1m" 4m22mx24m 4my0m These give the screen's location relative to another screen. The first four position the screen immediately to the right, left, above or below the other screen. When positioning to the right or left, the top edges are aligned. When posi- tioning above or below, the left edges are aligned. The 1mRelative 22mform specifies the offset of the screen's origin (upper left corner) relative to the origin of another screen. 1mInputDevice "4m22midev-id24m1m" "4m22moption24m1m" 4m22m...0m One of these entries should 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. If either of those is missing, suitable 1mInputDevice 22mentries are searched for using the method described above in the 1mINPUTDEVICE 22msection. The 4midev-id24m field is mandatory, and specifies the name of the 1mInput-0m 1mDevice 22msection being referenced. Multiple 4moption24m fields may be specified, each in double quotes. The options permitted here are any that may also be given in the 1mInputDevice 22msections. Normally only session-specific input device options would be used here. The most commonly used options are: 1m"CorePointer"0m 1m"CoreKeyboard"0m 1m"SendCoreEvents"0m and the first two should normally be used to indicate the core pointer and core keyboard devices respectively. 1mOptions0m Any option permitted in the 1mServerFlags 22msection may also be specified here. When the same option appears in both places, the value given here overrides the one given in the 1mServerFlags0m section. Here is an example of a 1mServerLayout 22msection for a dual headed configu- ration with two mice: 1mSection "ServerLayout"0m 1mIdentifier "Layout 1"0m 1mScreen "MGA 1"0m 1mScreen "MGA 2" RightOf "MGA 1"0m 1mInputDevice "Keyboard 1" "CoreKeyboard"0m 1mInputDevice "Mouse 1" "CorePointer"0m 1mInputDevice "Mouse 2" "SendCoreEvents"0m 1mOption "BlankTime" "5"0m 1mEndSection0m 1mDRI SECTION0m This optional section is used to provide some information for the Direct Rendering Infrastructure. 1mIdentifier "4m22mname24m1m"0m specifies an optional identifying name for the 1mDRI 22msection. 1mGroup "4m22mgroup-name24m1m"0m 1mGroup 4m22mgroup-id0m specifies the group ownership for the DRI device nodes. It may be specified as a group name or as a numerical group ID. 1mMode 4m22mmode0m specifies the numerical permissions for the DRI device nodes. 1mBuffers 4m22mcount24m 4msize0m specifies buffers. 1mOptions0m Option flags may be specified in 1mDRI 22msections. 1mVENDOR SECTION0m The optional 1mVendor 22msection may be used to provide vendor-specific con- figuration information. Multiple 1mVendor 22msections may be present, and they may contain the following entries: 1mIdentifier "4m22mname24m1m"0m specifies an identifying name for the 1mVendor 22msection. 1mVendorName "4m22mvendor-name24m1m"0m specifies the vendor name. 1mOptions0m may be specified in the 1mVendor 22msections. In addition to these entries, there may be named 1mSubSections22m, each of which may contain an 1mIdentifier 22mentry and 1mOption 22mentries. 1mFILES0m For an example of an XF86Config file, see the file installed as /usr/X11R6/lib/X11/XF86Config.eg. 1mSEE ALSO0m X(7), Xserver(1), XFree86(1), apm(4), chips(4), cirrus(4), cyrix(4), fbdev(4), glide(4), glint(4), i128(4), i740(4), i810(4), imstt(4), mga(4), neomagic(4), nv(4), r128(4), rendition(4), savage(4), s3virge(4), siliconmotion(4), sis(4), sunbw2(4), suncg14(4), suncg3(4), suncg6(4), sunffb(4), sunleo(4), suntcx(4), tdfx(4), tga(4), tri- dent(4), tseng(4), v4l(4), vesa(4), vga(4), vmware(4), README 4m24m, RELNOTES 4m24m, README.mouse 4m24m, README.DRI 4m24m, Install 4m24m. 1mAUTHORS0m This manual page was largely rewritten for XFree86 4.0 by David Dawes 4m24m. xf86config(1) xf86config(1) 1mNAME0m xf86config - generate an XF86Config file 1mSYNOPSIS0m 1mxf86config0m 1mDESCRIPTION0m 4mxf86config24m is an interactive program for generating an XF86Config file for use with XFree86 X servers. Note that the default name used by 4mxf86config24m for the XF86Config file is system-dependent. For instance, on some systems, XF86Config-4 is used, and on OS/2, XConfig is used. 1mFILES0m 4m/usr/X11R6/lib/X11/Cards0m Video cards database 1mSEE ALSO0m XFree86(1), XF86Config(5), reconfig(1) 1mAUTHOR0m Harm Hanemaayer. xf86cfg(1) xf86cfg(1) 1mNAME0m xf86cfg - Graphical configuration tool for XFree86 4.0 1mSYNOPSIS0m 1mxf86cfg 22m[-xf86config 4mXF86Config24m] [-modulepath 4mmoduledir24m] [-fontpath 4mfontsdir24m] [-toolkitoption ...] 1mDESCRIPTION0m 4mXf86cfg24m is a tool to configure 4mXFree8624m 4m4.024m, and can be used to either write the initial configuration file or make customizations to the cur- rent configuration. When the 1mDISPLAY 22menvironment variable is not set, xf86cfg will run the command 4mXFree8624m 4m-configure24m to allow the xserver detect the hardware in the computer, and write an initial 4mXF86Config24m file in the user's home directory. Then, it will start XFree86 and allow customizations. If the 1mDISPLAY 22menvironment variable is set, xf86cfg will read the default 4mXF86Config24m, that may not be the same being used by the current server, and allow customizations. To use an alternative location for modules or fonts the respective search paths may be specified. Unless there is an 1mApply 22mbutton in the current xf86cfg dialog, the changes made will take place the next time 4mXFree8624m is started. Xf86cfg allows addition and configuration of new devices, such as video cards, monitors, keyboards and mouses. Screen layout configuration for xinerama or traditional multi-head is also available. Modelines can be configured or optimized. AccessX basic configurations can be made in the xf86cfg's accessx sec- tion. 1mOPTIONS0m 4m-xf86config0m Specifies an alternate XF86Config file for configuration. 4m-modulepath0m Specifies where xf86cfg, and the server it may start, should look for XFree86 modules. 4m-serverpath0m Specifies the complete path, not including the binary name, of the XFree86 binary. 4m-fontpath0m Specifies the path to the fonts that should be used by the server started by xf86cfg. 4m-rgbpath0m Specifies the path to the rgb.txt file that should be used by the server started by xf86cfg, if any. 4m-textmode0m If xf86cfg was compiled with support to ncurses, this option makes xf86cfg enters a text mode interface. 4m-nomodules0m When built with support for loading modules, this options changes xf86cfg behaviour, so that it will not load any mod- ules, and thus start quicker. 1mENVIRONMENT0m 4mDISPLAY24m Default host and display number 4mXWINHOME0m Directory where XFree86 was installed, defaults to /usr/X11R6. 4mXENVIRONMENT0m Name of a resource file that overrides the global resources stored in the RESOURCE_MANAGER property 1mFILES0m 4m/etc/XF86Config0m Server configuration file 4m/etc/X11/XF86Config0m Server configuration file 4m/usr/X11R6/etc/XF86Config0m Server configuration file 4m/usr/X11R6/lib/X11/XF86Config.24mhostname Server configuration file 4m/usr/X11R6/lib/X11/XF86Config0m Server configuration file 4m/usr/X11R6/lib/X11/app-default/XF86Cfg0m Specifies xf86cfg resources 4m/usr/X11R6/lib/X11/xkb/X0-config.keyboard0m Keyboard specific configuration 1mSEE ALSO0m 4mXFree8624m(1) 4mXF86Config24m(5) 1mCOPYRIGHT0m Copyright 2000, Conectiva Linux S.A. 4mhttp://www.conectiva.com0m Copyright 2000, The XFree86 Project 4mhttp://www.XFree86.org0m 1mAUTHORS0m Paulo César Pereira de Andrade 4m0m The XFree86 Project 1mBUGS0m Probably. getconfig(1) getconfig(1) 1mNAME0m getconfig - get configuration information for the XFree86 server 1mSYNOPSIS0m 1mgetconfig 22m[4moption24m 4m...24m] 1mDESCRIPTION0m 1mgetconfig 22mis a programmatic interface that is used by the 1mXFree860m server to get configuration information about video hardware when oper- ating without an 1mXF86Config 22mfile. This implementation of 1mgetconfig 22mis written in perl. It processes a prioritized and ordered list of rules supplied internally and from meta-configuration files. The rules are in the form of perl expres- sions. 1mgetconfig 22mwrites to standard output the XF86Config-style con- figuration data specified by the last highest priority rule that evalu- ates to true. Information about the format of the meta-configuration files can be found in the getconfig(5) manual page. 1mOPTIONS0m 1m-I 4m22msearch-path0m Specify the search path to use for meta-config files. 4msearch-0m 4mpath24m is a comma-separated list of directories to search. Each directory in the search path is searched for files with a 4m.cfg0m suffix. Each such file is opened and checked for a valid sig- nature string. Rules are read from files with a valid signa- ture string and appended to the list of rules to evaluate. If no search path is specified, only the internally supplied con- figuration rules will be used. 1m-D 22mEnable debugging output. 1m-V 22mPrint out the version information and exit. 1m-X 4m22mXFree86-version0m Specify the XFree86 version in numeric (integer) form. 1m-b 4m22msubsys-id0m Specify the PCI subsystem ID of the video device. 1m-c 4m22mclass0m Specify the PCI class of the video device. 1m-d 4m22mdevice-id0m Specify the PCI device ID of the video device. 1m-r 4m22mrevision0m Specify the PCI revision of the video device. 1m-s 4m22msubsysvendor-id0m Specify the PCI subsystem vendor ID of the video device. 1m-v 4m22mvendor-id0m Specify the PCI vendor ID of the video device. 1m-S 4m22msbus-path0m Specify the SBUS path of the video device. 1mFILES0m 4m.cfg24m files located in the search path. The search path typically spec- ified by the 1mXFree86 22mserver is: 4m/etc/X110m 4m/usr/X11R6/etc/X110m 4m0m 4m/usr/X11R6/lib/X11/getconfig0m where 4m24m is the 1mXFree86 22mserver's module search path. 1mSEE ALSO0m getconfig(5), XFree86(1), XF86Config(5). 1mAUTHORS0m The XFree86 automatic configuration support and the 1mgetconfig 22minterface was written by David H. Dawes, with the support of X-Oz Technologies. getconfig(5) getconfig(5) 1mNAME0m getconfig - meta configuration files for getconfig(1) 1mSYNOPSIS0m 1m*.cfg0m 1mDESCRIPTION0m 1mgetconfig 22mis a programmatic interface that is used by the 1mXFree860m server to get configuration information about video hardware when oper- ating without an 1mXF86Config 22mfile. This implementation of 1mgetconfig 22mis written in perl. It processes rules from meta-configuration files. All meta-configuration files have a 4m.cfg24m suffix. Lines starting with a pound-sign (#) are comments, and are ignored. Blank lines that consist only of white space are also treated as com- ments and ignored. The first non-comment line must be a signature string followed by the file format version number. The signature string is "XFree86 Project getconfig rules file. Version: " The currently defined version is "1.0". Files that do not have the correct signature string are ignored. The remaining non-comment lines define rules. The start of a new rule is indicated by a line with no leading white space. Subsequent lines making up a rule must be indented with white space. Logical lines within a rule may be split over multiple physical lines by using the usual continuation convention ('\' at the end of the line). The first logical line of each rule is a perl expression. It may be any valid perl expression whose evaluated (with 'eval') result may be used as the argument to a perl 'if' statement. The second logical line should be the name of the XFree86 video driver to use when the rule is true, and subsequent logical lines of each rule, if present, are additional con- figuration output for the video device's 1mXF86Config Device 22msection. The driver name and additional lines of configuration information are written to standard output when the rule is chosen as the successful rule. Pseudo rules consisting of perl expressions may be present in the file for the purpose of defining custom perl variables or setting the weight to use for the following rules. Pseudo rules are rules that consist of a single logical line only, and they are never candidates themselves for the successful rule. Several perl variables are pre-defined, and may be used within rules. They include: 1m$vendor 22mPCI vendor ID 1m$device 22mPCI device ID 1m$revision 22mPCI revision ID 1m$subsys 22mPCI subsystem ID 1m$subsysVendor 22mPCI subsystem vendor ID 1m$class 22mPCI class 1m$sbuspath 22mSBUS path 1m$XFree86Version 22mXFree86 version, as a 'v' string 1m$XFree86VersionNumeric 22mXFree86 numeric version 1m$XFree86VersionMajor 22mXFree86 major version 1m$XFree86VersionMinor 22mXFree86 minor version 1m$XFree86VersionPatch 22mXFree86 patch version 1m$XFree86VersionSnap 22mXFree86 snap version 1m$weight 22mcurrent rule weight The 1m$weight 22mvariable determines the weight of the rules as they are processed. The weight for subsequent rules may be set with a pseudo rule that sets or changes the value of 1m$weight22m. The default weight, and the weight used for built-in rules is 500. The meta-configuration files are processed in an unpredictable order. The weighting of the rules is used to determine their relative priority After processing all of the rules, both built-in and those read from the meta-configuration files, the 1mgetconfig 22mprogram chooses as the suc- cessful rule the last and highest weighted rule that evaluates to true. 1mFILES0m 4m.cfg24m files located in the search path. The search path typically spec- ified by the 1mXFree86 22mserver is: 4m/etc/X110m 4m/usr/X11R6/etc/X110m 4m0m 4m/usr/X11R6/lib/X11/getconfig0m where 4m24m is the 1mXFree86 22mserver's module search path. 4m/usr/X11R6/lib/X11/getconfig/xfree86.cfg0m Default rules file that gets installed. This file doesn't contain any rules by default. 4m/usr/X11R6/lib/X11/getconfig/cfg.sample0m A sample rules file that gives some exam- ples of what types of rules can appear in rules files. 1mSEE ALSO0m getconfig(1), XFree86(1), XF86Config(5). 1mAUTHORS0m The XFree86 automatic configuration support and the 1mgetconfig 22minterface was written by David H. Dawes, with the support of X-Oz Technologies. APM(4) APM(4) 1mNAME0m apm - Alliance ProMotion video driver 1mSYNOPSIS0m 1mSection "Device"0m 1mIdentifier "4m22mdevname24m1m"0m 1mDriver "apm"0m ... 1mEndSection0m 1mDESCRIPTION0m 1mapm 22mis an XFree86 driver for Alliance ProMotion video cards. The driver is accelerated for supported hardware/depth combination. It supports framebuffer depths of 8, 15, 16, 24 and 32 bits. For 6420, 6422, AT24, AT3D and AT25, all depths are fully accelerated except 24 bpp for which only screen to screen copy and rectangle filling is accelerated. 1mSUPPORTED HARDWARE0m The 1mapm 22mdriver supports PCI and ISA video cards on the following Alliance ProMotion chipsets 1mProMotion 64200m 1mProMotion 64220m 1mAT240m 1mAT3D0m 1mAT250m 1mCONFIGURATION DETAILS0m Please refer to XF86Config(5) for general configuration details. This section only covers configuration details specific to this driver. The driver auto-detects the chipset type, but the following 1mChipSet0m names may optionally be specified in the config file 1m"Device" 22msection, and will override the auto-detection: "6422", "at24", "at3d". The AT25 is Chipset "at3d" and the 6420 is 6422. The driver will auto-detect the amount of video memory present for all chips. The actual amount of video memory can also be specified with a 1mVideoRam 22mentry in the config file 1m"Device" 22msection. The following driver 1mOptions 22mare supported: 1mOption "HWCursor" "4m22mboolean24m1m"0m Enable or disable the hardware cursor. Default: on. 1mOption "SWCursor" "4m22mboolean24m1m"0m Force the software cursor. Default: off. 1mOption "NoAccel" "4m22mboolean24m1m"0m Disable or enable acceleration. Default: acceleration is enabled. 1mOption "NoLinear" "4m22mboolean24m1m"0m Disable or enable use of linear frame buffer. Default: on. Note: it may or may not work. Tell me if you need it. 1mOption "PciRetry" "4m22mboolean24m1m"0m Enable or disable PCI retries. Default: off. 1mOption "Remap_DPMS_On" "4m22mstring24m1m"0m 1mOption "Remap_DPMS_Standby" "4m22mstring24m1m"0m 1mOption "Remap_DPMS_Suspend" "4m22mstring24m1m"0m 1mOption "Remap_DPMS_Off" "4m22mstring24m1m"0m Remaps the corresponding DPMS events. I've found that my Her- cules 128/3D swaps Off and Suspend events. You can correct that with 1mOption "Remap_DPMS_Suspend" "Off"0m 1mOption "Remap_DPMS_Off" "Suspend"0m in the 1mDevice 22msection of the config file. 1mOption "ShadowFB" "4m22mboolean24m1m"0m Enable or disable use of the shadow framebuffer layer. Default: off. 1mSEE ALSO0m XFree86(1), XF86Config(5), xf86config(1), Xserver(1), X(7) 1mAUTHORS0m Authors include: Kent Hamilton, Henrik Harmsen and Loic Grenie. ATI(4) ATI(4) 1mNAME0m ati - ATI video driver 1mSYNOPSIS0m 1mSection "Device"0m 1mIdentifier "4m22mdevname24m1m"0m 1mDriver "ati"0m ... 1mEndSection0m 1mDESCRIPTION0m 1mati 22mis an XFree86 driver for ATI video cards. THIS MAN PAGE NEEDS TO BE FILLED IN. 1mSUPPORTED HARDWARE0m The 1mati 22mdriver supports... 1mCONFIGURATION DETAILS0m Please refer to XF86Config(5) for general configuration details. This section only covers configuration details specific to this driver. 1mSEE ALSO0m XFree86(1), XF86Config(5), xf86config(1), Xserver(1), X(7) 1mAUTHORS0m Authors include: ... R128(4) R128(4) 1mNAME0m r128 - ATI Rage 128 video driver 1mSYNOPSIS0m 1mSection "Device"0m 1mIdentifier "4m22mdevname24m1m"0m 1mDriver "r128"0m ... 1mEndSection0m 1mDESCRIPTION0m 1mr128 22mis an XFree86 driver for ATI Rage 128 based video cards. It con- tains full support for 8, 15, 16 and 24 bit pixel depths, hardware acceleration of drawing primitives, hardware cursor, video modes up to 1800x1440 @ 70Hz, doublescan modes (e.g., 320x200 and 320x240), gamma correction at all pixel depths, a fully programming dot clock and robust text mode restoration for VT switching. Dualhead is supported on M3/M4 mobile chips. 1mSUPPORTED HARDWARE0m The 1mr128 22mdriver supports all ATI Rage 128 based video cards including the Rage Fury AGP 32MB, the XPERT 128 AGP 16MB and the XPERT 99 AGP 8MB. 1mCONFIGURATION DETAILS0m Please refer to XF86Config(5) for general configuration details. This section only covers configuration details specific to this driver. The driver auto-detects all device information necessary to initialize the card. However, if you have problems with auto-detection, you can specify: VideoRam - in kilobytes MemBase - physical address of the linear framebuffer IOBase - physical address of the MMIO registers ChipID - PCI DEVICE ID In addition, the following driver 1mOptions 22mare supported: 1mOption "SWcursor" "4m22mboolean24m1m"0m Selects software cursor. The default is 1moff.0m 1mOption "NoAccel" "4m22mboolean24m1m"0m Enables or disables all hardware acceleration. The default is to 1menable 22mhardware acceleration. 1mOption "Dac6Bit" "4m22mboolean24m1m"0m Enables or disables the use of 6 bits per color component when in 8 bpp mode (emulates VGA mode). By default, all 8 bits per color component are used. The default is 1moff.0m 1mOption "VideoKey" "4m22minteger24m1m"0m This overrides the default pixel value for the YUV video overlay key. The default value is 1mundefined.0m 1mOption "Display" "4m22mstring24m1m"0m Select display mode for devices which support flat panels. Sup- ported modes are: 1m"FP" 22m- use flat panel; 1m"CRT" 22m- use cathode ray tube; 1m"Mirror" 22m- use both FP and CRT; 1m"BIOS" 22m- use mode as configured in the BIOS. The default is 1mFP.0m The following 1mOptions 22mare mostly important for non-x86 architectures: 1mOption "ProgramFPRegs" "4m22mboolean24m1m"0m Enable or disable programming of the flat panel registers. Beware that this may damage your panel, so use this 1mat your own0m 1mrisk. 22mThe default depends on the device. 1mOption "PanelWidth" "4m22minteger24m1m"0m 1mOption "PanelHeight" "4m22minteger24m1m"0m Override the flat panel dimensions in pixels. They are used to program the flat panel registers and normally determined using the video card BIOS. If the wrong dimensions are used, the sys- tem may hang. 1mOption "UseFBDev" "4m22mboolean24m1m"0m Enable or disable use of an OS-specific framebuffer device interface (which is not supported on all OSs). See fbdevhw(4) for further information. Default: off. 1mOption "DMAForXv" "4m22mboolean24m1m"0m Try or don't try to use DMA for Xv image transfers. This will reduce CPU usage when playing big videos like DVDs, but may cause instabilities. Default: off. The following additional 1mOptions 22mare supported: 1mOption "ShowCache" "4m22mboolean24m1m"0m Enable or disable viewing offscreen cache memory. A development debug option. Default: off. 1mDualhead Note: 22mThe video BIOS on some laptops interacts strangely with dualhead. This can result in flickering and problems changing modes on crtc2. If you experience these problems, try toggling your laptop's video output switch (e.g. fn-f7, etc.) prior to starting X or switch to another VT and back. 1mSEE ALSO0m XFree86(1), XF86Config(5), xf86config(1), Xserver(1), X(7) 1mAUTHORS0m Rickard E. (Rik) Faith 4mfaith@precisioninsight.com0m Kevin E. Martin 4mkevin@precisioninsight.com0m RADEON(4) RADEON(4) 1mNAME0m radeon - ATI RADEON video driver 1mSYNOPSIS0m 1mSection "Device"0m 1mIdentifier "4m22mdevname24m1m"0m 1mDriver "radeon"0m ... 1mEndSection0m 1mDESCRIPTION0m 1mradeon 22mis an XFree86 driver for ATI RADEON based video cards. It con- tains full support for 8, 15, 16 and 24 bit pixel depths, dual-head setup, flat panel, hardware 2D acceleration, hardware 3D acceleration (experimental on R300 and R400 series cards), hardware cursor, XV extension, and the Xinerama extension. 1mSUPPORTED HARDWARE0m The 1mradeon 22mdriver supports PCI and AGP video cards based on the follow- ing ATI chips 1mR100 22mRadeon 7200 1mRV100 22mRadeon 7000(VE), M6 1mRS100 22mRadeon IGP320(M) 1mRV200 22mRadeon 7500, M7, FireGL 7800 1mRS200 22mRadeon IGP330(M)/IGP340(M) 1mRS250 22mRadeon Mobility 7000 IGP 1mR200 22mRadeon 8500, 9100, FireGL 8800/8700 1mRV250 22mRadeon 9000PRO/9000, M9 1mRS300 22mRadeon 9100 IGP 1mRS350 22mRadeon 9200 IGP 1mRS400 22mRadeon XPRESS 200/200M IGP 1mRV280 22mRadeon 9200PRO/9200/9200SE, M9+ 1mR300 22mRadeon 9700PRO/9700/9500PRO/9500/9600TX, FireGL X1/Z1 (2D only) 1mR350 22mRadeon 9800PRO/9800SE/9800, FireGL X2 (2D only) 1mR360 22mRadeon 9800XT (2d only) 1mRV350 22mRadeon 9600PRO/9600SE/9600, M10/M11, FireGL T2 (2D only) 1mRV360 22mRadeon 9600XT (2d only) 1mRV370 22mRadeon X300, M22 (2d only) 1mRV380 22mRadeon X600, M24 (2d only) 1mRV410 22mRadeon X700, M26 PCIE (2d only) 1mR420 22mRadeon X800 AGP (2d only) 1mR423/R430 22mRadeon X800, M28 PCIE (2d only) 1mR480/R481 22mRadeon X850 PCIE/AGP (2d only) 1mCONFIGURATION DETAILS0m Please refer to XF86Config(5) for general configuration details. This section only covers configuration details specific to this driver. The driver auto-detects all device information necessary to initialize the card. However, if you have problems with auto-detection, you can specify: VideoRam - in kilobytes MemBase - physical address of the linear framebuffer IOBase - physical address of the MMIO registers ChipID - PCI DEVICE ID In addition, the following driver 1mOptions 22mare supported: 1mOption "SWcursor" "4m22mboolean24m1m"0m Selects software cursor. The default is 1moff.0m 1mOption "NoAccel" "4m22mboolean24m1m"0m Enables or disables all hardware acceleration. The default is to 1menable 22mhardware acceleration. 1mOption "Dac6Bit" "4m22mboolean24m1m"0m Enables or disables the use of 6 bits per color component when in 8 bpp mode (emulates VGA mode). By default, all 8 bits per color component are used. The default is 1moff.0m 1mOption "VideoKey" "4m22minteger24m1m"0m This overrides the default pixel value for the YUV video overlay key. The default value is 1m0x1E.0m 1mOption "UseFBDev" "4m22mboolean24m1m"0m Enable or disable use of an OS-specific framebuffer device interface (which is not supported on all OSs). MergedFB does not work when this option is in use. See fbdevhw(4) for further information. The default is 1moff.0m 1mOption "AGPMode" "4m22minteger24m1m"0m Set AGP data transfer rate. (used only when DRI is enabled) 1 -- x1 (default) 2 -- x2 4 -- x4 8 -- x8 others -- invalid 1mOption "AGPFastWrite" "4m22mboolean24m1m"0m Enable AGP fast write. Enabling this option is frequently the cause of instability. Used only when the DRI is enabled. The default is 1moff.0m 1mOption "BusType" "4m22mstring24m1m"0m Used to replace previous ForcePCIMode option. Should only be used when driver's bus detection is incorrect or you want to force a AGP card to PCI mode. Should NEVER force a PCI card to AGP bus. PCI -- PCI bus AGP -- AGP bus PCIE -- PCI Express (falls back to PCI at present) (used only when DRI is enabled) The default is 1mauto detect.0m 1mOption "DDCMode" "4m22mboolean24m1m"0m Force to use the modes queried from the connected monitor. The default is 1moff.0m 1mOption "DisplayPriority" "4m22mstring24m1m"0m Used to prevent flickering or tearing problem caused by display buffer underflow. AUTO -- Driver calculated (default). BIOS -- Remain unchanged from BIOS setting. Use this if the calculation is not correct for your card. HIGH -- Force to the highest priority. Use this if you have problem with above options. This might affect performance slightly. The default value is 1mAUTO.0m 1mOption "MonitorLayout" "4m22mstring24m1m"0m This option is used to overwrite the detected monitor types. This is only required when driver makes a false detection. The possible monitor types are: NONE -- Not connected CRT -- Analog CRT monitor TMDS -- Desktop flat panel LVDS -- Laptop flat panel This option can be used in following format: Option "MonitorLayout" "[type on primary], [type on secondary]" For example, Option "MonitorLayout" "CRT, TMDS" Primary/Secondary head for dual-head cards: (when only one port is used, it will be treated as the primary regardless) 1mPrimary head:0m DVI port on DVI+VGA cards LCD output on laptops Internal TMDS port on DVI+DVI cards 1mSecondary head:0m VGA port on DVI+VGA cards VGA port on laptops External TMDS port on DVI+DVI cards The default value is 1mundefined.0m 1mOption "MergedFB" "4m22mboolean24m1m"0m This enables merged framebuffer mode. In this mode you have a single shared framebuffer with two viewports looking into it. It is similar to Xinerama, but has some advantages. It is faster than Xinerama, the DRI works on both he