When multiple graphics cards are present, this is what ties a specific card to a screen. The device-id must match the Identifier of a Device section in the config file. When multiple graphics cards are present, this is what ties a specific secondary card to a screen. This can be specified up to 4 times for a single screen. Monitor "monitor-id" specifies which monitor description is to be used for this screen. If a Monitor name is not specified, a default configu- ration is used.
Currently the default configuration may not function as expected on all platforms. VideoAdaptor "xv-id" specifies an optional Xv video adaptor description to be used with this screen.
DefaultDepth depth specifies which color depth the server should use by default. The -depth command line option can be used to override this. If neither is specified, the default depth is driver-specific, but in most cases is 8. DefaultFbBpp bpp specifies which framebuffer layout to use by default.
The -fbbpp command 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. MatchSeat seat-id Only apply this Screen section if X server was started with -seat seat-id option.
Options Various Option flags may be specified in the Screen section. Some are driver-specific and are described in the driver docu- mentation.
Others are driver-independent, and will eventually be described here. Option "Accel" Enables 2D hardware acceleration. 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. This may be used to select an alternate implementation for development, debugging, or alter- nate feature sets.
Default: mesa. Option "InitPrimary" "boolean" 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. Each Screen section may optionally contain one or more Display subsec- tions. The Display subsection format is described in the section below. The Display subsections are optional.
Display subsections have the following format: SubSection "Display" Depth depth entries EndSubSection Depth depth This entry specifies what colour depth the Display subsection is to be used for. This entry is usually specified, but it may be omitted to create a match-all Display subsection or when wishing to match only against the FbBpp parameter.
The range of depth values that are allowed depends on the driver. Most drivers support 8, 15, 16 and Note: depth means the number of bits in a pixel that are actually used to determine the pixel colour. 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 FbBpp bpp This entry specifies the framebuffer format this Display subsec- 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. Weight red-weight green-weight blue-weight 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 -weight option see Xorg 1.
Virtual xdim ydim This optional entry specifies the virtual screen resolution to be used. 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 Modes entry. Refer to the appropriate driver-specific documentation for details. ViewPort x0 y0 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. Modes "mode-name" This optional entry specifies the list of video modes to use.
Each mode-name specified must be in double quotes. They must correspond to those specified or referenced in the appropriate Monitor section including implicitly referenced built-in VESA standard modes.
The server will delete modes from this list which don't satisfy various requirements. The first valid mode in this list will be the default display mode for startup. The list of valid modes is converted internally into a circular list. When this entry is omitted, the valid modes refer- enced by the appropriate Monitor section will be used. If the Monitor section contains no modes, then the selection will be taken from the built-in VESA standard modes. Visual "visual-name" This optional entry sets the default root visual type.
This may also be specified from the command line see the Xserver 1 man page. Black red green blue This optional entry allows the "black" colour to be specified. This is only supported at depth 1. The default is black. White red green blue This optional entry allows the "white" colour to be specified.
The default is white. Options Option flags may be specified in the Display subsections. These may include driver-specific options and driver-independent options. The former are described in the driver-specific docu- mentation. Some of the latter are described above in the sec- tion about the Screen section, and they may also be included here. A "server layout" represents the binding of one or more screens Screen sections and one or more input devices InputDevice sections to form a complete configuration.
In multi-head configurations, it also specifies the relative layout of the heads. A ServerLayout section is considered "active" if it is referenced by the -layout command line option or by an Option "DefaultServerLayout" entry in the ServerFlags section the former takes precedence over the latter. If those options are not used, the first ServerLayout section found in the config file is con- sidered the active one. If no ServerLayout sections are present, the single active screen and two active core input devices are selected as described in the relevant sections above.
InputDevice "idev-id" The Identifier entry specifies the unique name for this server layout. The ServerLayout section provides information specific to the whole session, including session-specific Options. The ServerFlags options described above may be specified here, and ones given here override those given in the ServerFlags section.
The entries that may be used in this section are described here. Screen screen-num "screen-id" position-information One of these entries must be given for each screen being used in a session. The screen-id field is mandatory, and specifies the Screen section being referenced.
The screen-num 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 numbering starts from 0, and must be consecutive. The posi- tion-information field describes the way multiple screens are positioned. There are a number of different ways that this information can be provided: x y Absolute x y These both specify that the upper left corner's coordinates are x,y.
The Absolute keyword is optional. Some older versions of XFree86 4. RightOf "screen-id" LeftOf "screen-id" Above "screen-id" Below "screen-id" Relative "screen-id" x y 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 Relative form specifies the offset of the screen's origin upper left corner relative to the origin of another screen. InputDevice "idev-id" "option" 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.
The idev-id field is mandatory, and specifies the name of the Input- Device section being referenced. Multiple option fields may be specified, each in double quotes.
The options permitted here are any that may also be given in the InputDevice sections. Normally only session-specific input device options would be used here. The most commonly used options are: "CorePointer" "CoreKeyboard" "SendCoreEvents" and the first two should normally be used to indicate the core pointer and core keyboard devices respectively.
MatchSeat seat-id Only apply this ServerLayout section if X server was started with -seat seat-id option. Options In addition to the following, any option permitted in the ServerFlags section may also be specified here. When the same option appears in both places, the value given here overrides the one given in the ServerFlags section.
Option "IsolateDevice" "bus-id" Restrict device resets to the specified bus-id. This option overrides SingleCard, if specified. At present, only PCI devices can be isolated in this manner. Multiple Vendor sections may be present, and they may contain an Identifier entry and multiple Option flags. The data therein is not used in this release.
Not all modules or interfaces are available on all platforms. Display drivers: apm 4 , ati 4 , chips 4 , cirrus 4 , cyrix 4 , fbdev 4 , glide 4 , glint 4 , i 4 , i 4 , imstt 4 , intel 4 , mga 4 , neomagic 4 , nv 4 , openchrome 4 , r 4 , radeon 4 , rendi- tion 4 , savage 4 , s3virge 4 , siliconmotion 4 , sis 4 , sisusb 4 , sunbw2 4 , suncg14 4 , suncg3 4 , suncg6 4 , sunffb 4 , sunleo 4 , suntcx 4 , tdfx 4 , trident 4 , tseng 4 , vesa 4 , vmware 4 , voodoo 4 , wsfb 4 , xgi 4 , xgixp 4.
Input drivers: acecad 4 , citron 4 , elographics 4 , evdev 4 , fpit 4 , joystick 4 , kbd 4 , mousedrv 4 , mutouch 4 , penmount 4 , synap- tics 4 , vmmouse 4 , void 4 , wacom 4. Other modules and interfaces: exa 4 , fbdevhw 4 , v4l 4. X Version 11 xorg-server 1. It's so annoying and irritating.
I have a Dell Touchpad. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.
Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. If the X config file does not have a Module section, you can safely skip the last step if the X server installed on your system is an X.
Org X server or an XFree86 X release version 4. If you are using an older XFree86 X server, add the following to your X config file:. Once you have completed these edits to the X config file, you may restart X and begin using the accelerated OpenGL libraries.
Otherwise, X may fail to start, since the driver it was configured to use will no longer be present on the system after uninstallation. If you edited the file manually, revert any edits you made. If you used the nvidia-xconfig utility, either by answering "Yes" when prompted to configure the X server by the installer, or by running it manually later on, then you may restore the backed-up X config file, if it exists and reflects the X config state that existed before the NVIDIA driver was installed.
If you do not recall any manual changes that you made to the file, or do not have a backed-up X config file that uses a non-NVIDIA X driver, you may want to try simply renaming the X configuration file, to see if your X server loads a sensible default. If you do this again, don't delete the file, just rename it. That way it will still be there in case you need it for troubleshooting.
April 28th, 8. Originally Posted by Telengard C April 28th, 9. How does that wo Here's the output of lspci -v. April 28th, How does that wo As others have said. Around the time of 9. Typically it gets it right, but every once and awhile it gets it wrong.
If xorg. On a seperate note
0コメント