Synaptics support kills my mouse
It is true, 2.5.73 unconditionally detects and tries to use the Syn. Touchpad in 'absolute mode'. I wouldn't blame the authors of the module, however. They are already doing a great job :).
I 've read the code to see what's wrong and found that the problem is that the Touchpad itself doesn't report any data to the PS/2 port. The code still looks conforming to the specs.
However, you shouldn't give up 2.5.73 because of that. You can still use the PS/2 compatibility mode
o Compile the ps mouse as a module "psmouse"
o Arrange so that the module is loaded with the option "psmouse_noext=1"
o Have gpm and X (you can even use both of them) read /dev/input/mice as an
exps2 or imps2 mouse (Intellimouse Explorer PS/2) .
I don't think the "event interface" has any support yet. Nor the synaptics driver.
Reading from /dev/input/mice means that the psmouse module doesn't have to be loaded before X starts. You can safely rmmod/modprobe the module while X run. You may find that tapping with the finger may not work (produce 'click' effect). I hope next release will have a fix (contact me in personal until the official patch is out).
Quoted 4 lines · P. Christeas
It is true, 2.5.73 unconditionally detects and tries to use the Syn. Touchpad in 'absolute mode'. I wouldn't blame the authors of the module, however. They are already doing a great job :).
Quoted 9 lines
I 've read the code to see what's wrong and found that the problem is that the Touchpad itself doesn't report any data to the PS/2 port. The code still looks conforming to the specs.
However, you shouldn't give up 2.5.73 because of that. You can still use the PS/2 compatibility mode
o Compile the ps mouse as a module "psmouse"
o Arrange so that the module is loaded with the option "psmouse_noext=1"
o Have gpm and X (you can even use both of them) read/dev/input/miceas an
exps2 or imps2 mouse (Intellimouse Explorer PS/2) .
It is an ugly workaround, but it works. Thanks.
Quoted 4 lines · P. Christeas
It is true, 2.5.73 unconditionally detects and tries to use the Syn. Touchpad in 'absolute mode'. I wouldn't blame the authors of the module, however. They are already doing a great job :).
Quoted 9 lines
I 've read the code to see what's wrong and found that the problem is that the Touchpad itself doesn't report any data to the PS/2 port. The code still looks conforming to the specs.
However, you shouldn't give up 2.5.73 because of that. You can still use the PS/2 compatibility mode
o Compile the ps mouse as a module "psmouse"
o Arrange so that the module is loaded with the option "psmouse_noext=1"
o Have gpm and X (you can even use both of them) read/dev/input/miceas an
exps2 or imps2 mouse (Intellimouse Explorer PS/2) .
Further update. I can get the same effect/workaround by making the mouse support built in (my preference) and specifying the above option on the kernel options line.
Quoted 15 lines · Thomas Molina
Quoted 4 lines · P. Christeas
It is true, 2.5.73 unconditionally detects and tries to use the Syn. Touchpad in 'absolute mode'. I wouldn't blame the authors of the module, however. They are already doing a great job :).
Quoted 9 lines
I 've read the code to see what's wrong and found that the problem is that the Touchpad itself doesn't report any data to the PS/2 port. The code still looks conforming to the specs.
However, you shouldn't give up 2.5.73 because of that. You can still use the PS/2 compatibility mode
o Compile the ps mouse as a module "psmouse"
o Arrange so that the module is loaded with the option "psmouse_noext=1"
o Have gpm and X (you can even use both of them) read/dev/input/miceas
an exps2 or imps2 mouse (Intellimouse Explorer PS/2) .
Quoted 3 lines
Further update. I can get the same effect/workaround by making the mouse support built in (my preference) and specifying the above option on the kernel options line.
You can, but I wouldn't recommend that. Having a module allows you to change the behaviour runtime (even inside X).