The program comes with an easy to use Qt based GUI system to setup the most important features X provides. If called SaX2 will detect the graphics hardware including all graphics related peripherals and presents an automatic generated configuration suggestion.
The user is now able to setup the system according to his needs using the GUI system. The wikis are now using the new authentication system. Unfortunately, there is no general tool for this purpose in Linux.
The standard configuration contains suitable default values for the dimensions of the touchscreen. Normally, no additional configuration is required. Org only supports a limited number of graphics tablets.
SaX2 enables the configuration of graphics tablets connected to the USB port or the serial port. From the configuration perspective, a graphics tablet is just an input device like a mouse. Mark the check boxes to the right if you have connected a pen or eraser. If your tablet is connected to the serial port, verify the port. Additional ports use similar notation. If you do not use a mouse on your computer, start SaX2 and activate AccessX to be able to control the mouse pointer with the keys on the numeric keypad.
See Table Use the slider to set the speed of the mouse pointer movement when a key is pressed. The left mouse button is preset if no other button was selected. The selection is reset to its default after the event. In the started module, configure your joystick by selecting the manufacturer and the model from the displayed list. The test dialog shows three charts for the analog axes of the joystick and marks for the four standard buttons.
When you move the joystick or press the buttons, you should be able to see a reaction in the test dialog. Because joysticks are usually connected to the sound card, you can also access this module from the sound card configuration. Part II. The X Window System Language and Country-Specific Settings Optimizing the X Configuration. Chapter The X Window System. Table of Contents X11 Setup with SaX2 Optimizing the X Configuration Installing and Configuring Fonts OpenGL—3D Configuration.
X11 Setup with SaX2. Figure The Main Window of SaX2. Monitor Selection. Configuring the Monitor Frequencies There are safety mechanisms, but you should still be very careful when manually changing the allowed frequencies.
Graphics Card. Selecting the Graphics Card. Colors and Resolutions. Configuring the Resolution. Virtual Resolution. Configuring the Virtual Resolution. Image Position and Size. Adjusting the Image Geometry. Traditional Multihead Each monitor represents an individual unit. The exact name of the log can vary from Xorg. If all is well, the configuration file needs to be installed in a common location where Xorg 1 can find it.
The X11 configuration process is now complete. Xorg may be now started with the startx 1 utility. The X11 server may also be started with the use of xdm 1. Note: There is also a graphical configuration tool, xorgcfg 1 , which comes with the X11 distribution. It allows you to interactively define your configuration by choosing the appropriate drivers and settings.
This program can be invoked from the console, by typing the command xorgcfg -textmode. For more details, refer to the xorgcfg 1 manual page. Alternatively, there is also a tool called xorgconfig 1. This program is a console utility that is less user friendly, but it may work in situations where the other tools do not.
See the agp 4 driver manual page for more information. This will allow configuration of the hardware as any other graphics board. Note on systems without the agp 4 driver compiled in the kernel, trying to load the module with kldload 8 will not work. This section assumes a bit of advanced configuration knowledge.
If attempts to use the standard configuration tools above have not resulted in a working configuration, there is information enough in the log files to be of use in getting the setup working. Use of a text editor will be necessary. Examples of some common screen resolutions for aspect ratios are:. At some point, it will be as easy as adding one of these resolutions as a possible Mode in the Section "Screen" as such:.
If those ModeLines do not exist in the drivers, one might need to give Xorg a little hint. Simply look for information resembling this:. This information is called EDID information. Creating a ModeLine from this is just a matter of putting the numbers in the correct order:. So that the ModeLine in Section "Monitor" for this example would look like this:. It consists of several sections, each one dealing with a certain aspect of the configuration.
The sections have the form:. The available section types are listed in Table Monitor , Device , and Screen are explained in more detail below. Further information about the other sections can be found in the manual pages of X.
Org and xorg. There can be several different Monitor and Device sections in xorg. Even multiple Screen sections are possible. The following ServerLayout section determines which one is used. First, take a closer look at the screen section, which combines a monitor with a device section and determines the resolution and color depth to use. A screen section might resemble Example The line Identifier here Screen[0] gives this section a defined name with which it can be uniquely referenced in the following ServerLayout section.
The lines Device and Monitor specify the graphics card and the monitor that belong to this definition. These are just links to the Device and Monitor sections with their corresponding names or identifiers.
These sections are discussed in detail below. Use the DefaultDepth setting to select the color depth the server should use unless it is started with a specific color depth.
There is a Display subsection for each color depth. The keyword Depth assigns the color depth valid for this subsection. Possible values for Depth are 8, 15, 16, and Not all X server modules support all these values. After the color depth, a list of resolutions is set in the Modes section. This list is checked by the X server from left to right. For each resolution, the X server searches for a suitable Modeline in the Modes section.
The Modeline depends on the capability of both the monitor and the graphics card. The Monitor settings determine the resulting Modeline. The first resolution found is the Default mode. With Ctrl - Alt - — on the number pad , switch to the left. This enables you to vary the resolution while X is running. The last line of the Display subsection with Depth 16 refers to the size of the virtual screen.
The maximum possible size of a virtual screen depends on the amount of memory installed on the graphics card and the desired color depth, not on the maximum resolution of the monitor. Because modern graphics cards have a large amount of video memory, you can create very large virtual desktops. However, you may no longer be able to use 3D functionality if you fill most of the video memory with a virtual desktop. If the card has 16 MB video RAM, for example, the virtual screen can be up to x pixels in size at 8-bit color depth.
Especially for accelerated cards, however, it is not recommended to use all your memory for the virtual screen, because this memory on the card is also used for several font and graphics caches. A device section describes a specific graphics card.
You can have as many device entries in xorg. As a rule-if you have more than one graphics card installed-the sections are simply numbered in order. The first one is called Device[0] , the second one Device[1] , and so on. The following file shows an excerpt from the Device section of a computer with a Matrox Millennium PCI graphics card:. If you use SaX2 for configuring, the device section should look something like the above example. Both the Driver and BusID are dependent on the hardware installed in your computer and are detected by SaX2 automatically.
This matches the ID displayed by the command lspci. The X server needs details in decimal form, but lspci displays these in hexadecimal form. Via the Driver parameter, specify the driver to use for this graphics card. If the card is a Matrox Millennium, the driver module is called mga. The X server then searches through the ModulePath defined in the Files section in the drivers subdirectory. The behavior of the X server or of the driver can also be influenced through additional options.
This deactivates the hardware mouse cursor and depicts the mouse cursor using software. Generally valid options can also be found in the manual pages man xorg. Like the Device sections, the Monitor and Modes sections describe one monitor each.
0コメント