Hello! On Tue, Aug 08, 2006 at 01:59:08AM +0200, Steinar H. Gunderson wrote: > Package: xserver-xorg-input-synaptics > Version: 0.14.6-1 > Severity: important > > The Latitude D420 has a touchpad which is detected by the kernel as > follows: > > input: PS/2 Mouse as /class/input/input1 > input: AlpsPS/2 ALPS GlidePoint as /class/input/input2
ah, it's a known problem, see both 351621 and 362853 > The synaptics driver in X.org uses this just fine. However there are two > major issues: > > - The sensitivity is way too low. Even when setting it to maximum in > gsynaptics makes it so slow I need something like ten full movements > across the pad just to get the mouse pointer from the middle to the > upper left corner of the screen. I had to multiply the defaults by > ten (giving MinSpeed=0.9 and MaxSpeed=1.8) and manually inject that > into xorg.conf to get what I'd expect as a reasonable default > behaviour from the mouse pointer. I assume this is gone with the configuration already suggested. > - Tapping and scrolling does not work, even though synclient seems to > indicate that both are enabled. However, there seems to be something > odd going on with the hardware tapping; FWIW, here's a record of me > tapping a few times: > > fugl:~> synclient -m 10 > time x y z f w l r u d m multi gl gm gr gdx gdy > 0.000 518 465 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0 > 2.038 472 492 40 1 0 0 0 0 0 0 00000000 0 0 0 0 0 > 2.195 472 492 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0 > 2.999 525 518 40 1 0 0 0 0 0 0 00000000 0 0 0 0 0 > 3.155 525 518 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0 > 3.887 568 431 126 1 0 0 0 0 0 0 00000000 0 0 0 0 0 > 3.899 565 422 102 1 0 0 0 0 0 0 00000000 0 0 0 0 0 > 3.947 565 422 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0 > > and here's the same thing, using the buttons instead: > > fugl:~> synclient -m 10 > time x y z f w l r u d m multi gl gm gr gdx gdy > 0.000 403 365 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0 > 0.722 403 365 0 0 0 1 0 0 0 0 00000000 0 0 0 0 0 > 0.854 403 365 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0 > 1.010 403 365 0 0 0 1 0 0 0 0 00000000 0 0 0 0 0 > 1.130 403 365 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0 > 1.286 403 365 0 0 0 1 0 0 0 0 00000000 0 0 0 0 0 > 1.406 403 365 0 0 0 0 0 0 0 0 00000000 0 0 0 0 0 ok, it's ok actually. See the 'z' column: the driver detects the pressure on the pad. The mouse button is emulated by the driver under the proper conditions (pressure past FingerHigh and 2 taps in MaxDoubleTapTime msec). > Given that I use the defaults (except MinSpeed and MaxSpeed), > shouldn't it be able to figure out for itself that I'm tapping, even > though l=0 all the time? (I'm not sure how to debug the vertical > scrolling either; FWIW, x seems to be around 970-1000 when I pull my > finger across the right edge.) hummm, can you clarify the vertical scrolling thing? On Tue, Aug 08, 2006 at 03:57:05PM +0200, Steinar H. Gunderson wrote: > On Tue, Aug 08, 2006 at 03:02:19PM +0200, Curt Manucredo wrote: > > did you try this? you will find a similar config in the doc-directory of > > the synaptics-driver. i had the same problems. since i have changed it > > to that: > > Thanks, that helped -- scrolling now works, and tapping works. However, > tapping has this odd delay... Whenever I tap, there's a 300-400ms delay, then > comes the ButtonPress and then soon after the ButtonRelease. I've tried You could try to play with the above mentioned options (FingerHigh for more sensitivity and MaxDoubleTapTime for the double click timing) or even enable FastTaps. Have you already tried? Did you already found the synaptics(5) manpage (too see full description of all the mentioned options)? :) Can you eventually provide the output of synclient -l (given you have SHMConfig enabled)? > tuning every parameter I could find, but to no avail... It's tapping, > but it's definitely not very good tapping, and the bug still stands -- this > should be working by default, if nothing else by some kind of identification > at runtime. :-) this is being worked on at least for APLS pads which need some very different defaults. Thanks -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
