The notebook touchpad under Fedora9 cannot be clicked to solve the problem

The downloaded Fedora9 has been installed for two or three days, and the touchpad is always abnormal. It shows that when the system is installed and used properly after installation, the touchpad cannot be clicked or double-clicked (notebook model: HaierH40S ), however, the touchpad can be used properly for the first configuration after installation and restart. After one day of hard work yesterday, we finally solved this problem by using the following methods: 1. Install the synaptics program, yuminstallgsynaptics under gnome, and yuminstallksyna under KDE.

The downloaded Fedora9 has been installed for two or three days, and the touchpad is always abnormal. It shows that when the system is installed and used properly after installation, the touchpad cannot be clicked or double-clicked (the model of the notebook is Haier H40S ), however, the touchpad can be used properly for the first configuration after installation and restart.

After one day of hard work yesterday, we finally solved the problem by using the following methods:

1. install the synaptics program, yum install gsynaptics under gnome, and yum install ksynaptics under KDE.

2. Modify the/etc/X11/xorg. conf file and add it after the Section "InputDevice" field (after EndSection ).

Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "Device" "/dev/input/event2" (very important !! Most people may be/dev/input/mice, which is changed to event2, because I used cat/proc/bus/input/device to view my touchpad Handlers = mouse1 event2, I changed it to event2, therefore, this value is determined based on the Handlers value of the notebook touchpad)
Option "Protocol" "auto-dev" (if not, use event instead of auto-dev, depending on the hardware)

Option "Emulate3Buttons" "yes"
Option "SendCoreEvents" "true" (in this example, it does not play a role, nor does it affect)
Option "SHMConfig" "on" (this should have been Option "SHMConfig" "true", but this true always says it is not true when running. If you get angry, change it to on, on or true is determined based on the actual situation, and the meaning is the same. If you do not set it, running gsynaptics prompts you to set it to true, and running ksynaptics prompts you to set it to on, set "on" to "normal" on my machine. No conflict occurs)
Option "TapButton1" "1"
Option "TapButton2" "2" (this is two items added according to the windsea brother. In fact, it is necessary to click on the touchpad instead of attaching the key)
EndSection

3. Modify the Section "ServerLayout" field as follows:

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
Inputdevice "Synaptics" (new, required, should it be used for boot and boot ?)

Now I can use it. I am really bored. I spent a whole day yesterday, and I am also bored with "Nostalgia in midnight" for a day, thank you for your patience !! Hope to give a demonstration to the brothers who have similar problems ...... So far, my notebook touchpad has been completely completed, just like in windows.

PS: The red part is the code, and the rest is treated as the old lady .................. Haha

(Author: qingcrazy)