Very well, but how do you do a "reset"? "reset" is not an option of tpconfig, and I can't see anything that will particularly help. I've never needed to use gpm for a mouse before - is this flakey behavior with it firing random events typical of gpm, or is it something specific to the touchpad? All of the synaptics package documentation, and the gpm & tpconfig man pages are pretty much useless in describing how to actually configure a mouse of any kind, let alone a touchpad. -- derek
"Mark S. Mathews" wrote: > > Use tpconfig to do a reset on the touchpad before firing up gpm or X. > I've had similar problems with my Acers and this seems to do the trick. > > -Mark > > Derek Broughton wrote: > > > > I've got a brand new Inspiron 2500 with an almost working Linux system. > > It runs a 2.2.19pre17 kernel for PCMCIA and a 2.4.9 kernel for X. It > > needs the 2.4 kernel for the intel 815 video, but I haven't managed to > > get PCMCIA to work there, yet. > > > > However, I can't get the touchpad to work very well. It's configured as > > a gpm mouse using synps2, but I _must_ define the PS/2 mouse as > > "CorePointer" and have it attached before starting X. If I don't the > > touchpad is unusable. If I detach the PS/2 mouse after X starts, the > > touchpad is activated (mostly) but has a bad habit of moving the pointer > > to the upper right corner of the screen and sending random clicks. I > > have also tried with the Touchpad protocol set to "MouseSystems" which > > was slightly less useful. > > > > Section "InputDevice" > > Identifier "PS2Mouse" > > Driver "mouse" > > Option "CorePointer" > > Option "Device" "/dev/psaux" > > Option "Protocol" "PS/2" > > Option "ZAxisMapping" "4 5" > > Option "Buttons" "5" > > EndSection > > > > Section "InputDevice" > > Identifier "Touchpad" > > Driver "mouse" > > Option "Device" "/dev/gpmdata" > > Option "Protocol" "PS/2" > > EndSection
