Chris Tyler - Fedora Linux

$ synclient VertScrollDelta=10

$ synclient PalmDetect=0

If you need to find position or pressure values for these options, you can use the monitor ( -m ) option of synclient to experiment:

$ synclient -m 100

time x y z f w l r u d m multi gl gm gr gdx gdy

0.000 3277 2899 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0

1.247 3687 3172 65 1 5 0 0 0 0 0 00000000 0 0 0 0 0

1.351 3402 3070 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0

1.871 3926 3650 62 1 4 0 0 0 0 0 00000000 0 0 0 0 0

1.975 4337 3339 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0

2.495 3932 3133 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0

2.599 3816 3245 1 1 9 0 0 0 0 0 00000000 0 0 0 0 0

2.703 3810 3286 1 1 7 0 0 0 0 0 00000000 0 0 0 0 0

2.807 3923 3224 1 1 14 0 0 0 0 0 00000000 0 0 0 0 0

2.911 3923 3224 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0

8.423 4018 3986 131 2 5 0 0 0 0 0 00000000 0 0 0 0 0

8.527 4104 3933 134 2 5 0 0 0 0 0 00000000 0 0 0 0 0

8.631 4653 3827 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0

...(

Ctrl-C to terminate )...

In this output, the following options indicate:

x , y , and z

Position and pressure of touch.

f

Finger count.

w

Finger width.

l , r , u , d , m , and multi

Button state (most touchpads have only the l and r buttons). 0 indicates the button is up; 1 indicates the button is down.

All columns starting with g

Guest (secondary) pointing device information, such as a finger button.

Once you have tweaked the values to suit your needs, add your preferred values to the Synaptics InputDevice section of the /etc/X11/xorg.conf file, using the Option keyword:

Section "InputDevice"

Identifier "Touchpad0"

Driver "synaptics"

Option "SHMConfig" "on"

Option "VertScrollDelta" "10"

Option "PalmDetect" "0"

EndSection

These settings will then take effect when the system is restarted.

The Synaptics TouchPad (or Alps GlidePad) device is connected through a PS/2 or USB interface and contains a microcontroller, touch sensor, buttons, and interface electronics. The firmware is programmed to emulate a standard mouse unless (or until) the device driver sends it codes to switch it into native mode.

The Synaptics driver works with the microcontroller in the touchpad to translate user activity into standard mouse signals. There are only 16 types of events that are reported to the X server: button down and button up for buttons 1 through 7, and horizontal and vertical motion. All of the possible tap, press, and slide gestures are translated into combinations of these 16 events.

For example, touching the pad with one finger on the right side (X position greater than RightEdge , and Y position between TopEdge and BottomEdge ), and then moving your finger up more than VertScrollDelta units will be interpreted as a vertical scroll action, which will result in a button-down event on button 4, followed by a button-up event on button 4 (this corresponds to rotating the scroll wheel forward one click on a standard mouse).

Not all touchpad models have the hardware or firmware to provide all of the features supported by the driver; for example, most models do not have all of the possible buttons, and some lack multiple-finger or finger-width detection.

This can be done if the Synaptics device is defined in addition to a traditional mouse, as recommended in the X11 configuration shown in this lab.

Even with palm detection, some typists and touchpads register false information during typing (especially true with certain laptop case designs, which transmit case stress to the touchpad). To help in these situations, the Synaptics software includes the syndaemon program, which will automatically disable the touchpad when the keyboard is in use. To start this daemon, simply type its name as a command:

$ syndaemon

 The manpages for synaptics , synclient , and syndaemon

 The driver home page: http://web.telia.com/~u89404340/touchpad/

The video circuits of most laptops support two video outputs: one to the built-in LCD panel and one for external devices. The external output is not enabled by default, but you can switch between the internal and external displays using a function key.

More advanced configurations of the two outputs are supported by some video cards. For example, you can configure a single large desktop spanning both displays, or set up the external display to show a subset of what is shown on the internal display.

Output from one card to multiple monitors is supported only by some drivers. The most commonly used ones are the NVIDIA and ATI proprietary drivers, and the open source Radeon driver. All of these drivers have some limitations; for example, the NVIDIA driver, when used on a laptop, will always configure an external monitor as primary (screen 0), and the ATI drivers permit only general monitor positioning (you can specify that one monitor is to the right of another, but you can't indicate a difference in their vertical alignment).

Note that for the changes described in this section to take effect, you will need to restart the X server in one of these ways: changing to runlevel 3 and then back to 5, restarting the system, or terminating the running X server with Ctrl-Alt-Backspace (save your work first!).

First, configure and test your system using the NVIDIA proprietary driver (see Lab 5.3, "Using Repositories "), and then add the highlighted lines to the Device section of your /etc/X11/ xorg.conf file:

Section "Device"

Identifier "Card0"

Driver "nvidia"

VendorName "nVidia Corporation"

BoardName "NV34 [GeForce FX 5200]"

BusID "PCI:1:0:0"

Option "TwinView"

Option "SecondMonitorHorizSync" "31.0 - 80.0"

Option "SecondMonitorVertRefresh" "50.0 - 75.0"

Option "TwinViewXineramaInfo" "on"

Option "MetaModes" "800x600,1024x768"

Option "TwinViewOrientation" "LeftOf"

EndSection

The SecondMonitorHorizSync and SecondMonitorVertRefresh options configure the horizontal and vertical frequency ranges for the second monitor (the settings for the primary monitor are in the Monitor section of the file). The values given here are reasonable for most small monitors. The TwinViewXineramaInfo line configures the driver to inform applications about the fact that the desktop is on two screens, so that windows can be placed intelligently (avoiding dialog boxes that span both screens, for example).

The MetaModes option configures the relative sizes of the two screens; the first screen is always the external display. The TwinViewOrientation specifies the position of the second display relative to the first for the purpose of mouse movement and window positioning (possible values are Above , Below , LeftOf , or RightOf ).