Skip to contentSkip to conversation

Touchpad problems with 2.6.11-rc2

DISCUSSION David Brownell 4 participants 6 messages Jan 25, 2005 – Jan 31, 2005

lore
Share & tools
lore
#0 lore raw

Quoth Pete Zaitcev:

Quoted 3 lines

ALPS Touchpad (Dualpoint) detected
Disabling hardware tapping
input: AlpsPS/2 ALPS TouchPad on isa0060/serio1

I have problems with an ALPS on serio4 ... different ones though. And it may be that RC2 is a bit better here than previous kernels.

For example, it says it disabled tapping -- but it's still active. Evidently there are model-specific differences that the ALPS driver doesn't handle correctly.

Quoted 7 lines

Looks like detection is correct, however either ALPS specific code doesn't work right, or it sets wrong parameters, I cannot tell. Here's the list of problems, from worst to least annoying:

- Very often, keyboard stops working after a click. Typing anything has no effect. However, any smallest pointer movement will restore keyboard, and then an application receives all buffered characters. This is very bad.

I've got similar interactions between keyboard and touchpad -- no-effect, than after magic to unblock, a flood of characters. The Way To Fix It is different though. There seems to be an interaction with window focus, since another symptom is that for example there's no cursor in the active window ... until it's fixed. Sometimes things like newlines will cause scrolling, without any other characters appearing... maybe there's a KDE/x86_64 interaction too.

Quoted 5 lines

- Double-click sometimes fails to work. I have to wait a second and retry it. Retrying right away is likely not to work again.

- Slow motion of finger produces no motion, then a jump. So, it's very hard to target smaller UI elements and some web links.

I don't think I've seen either of those two problems.

I have two problems during mouse motion. One of them is that sometimes it seems to stop working or go into ultra-slow tracking mode. Workaround: wait a second, start again; it's as if there's some timed mode that it automagically enters/exits.

The more serious one is that sometimes it seems to spontaneously emit click events while I'm moving finger across pad. Which means I've had to learn to plan my "mouse" motions to avoid areas where clicking could have bad effects. But that's not always possible ...

- Dave

#1 lore raw
Quoted 5 lines · David Brownell

Quoth Pete Zaitcev:

Quoted 3 lines

ALPS Touchpad (Dualpoint) detected
Disabling hardware tapping
input: AlpsPS/2 ALPS TouchPad on isa0060/serio1

Quoted 7 lines

I have problems with an ALPS on serio4 ... different ones though. And it may be that RC2 is a bit better here than previous kernels.

For example, it says it disabled tapping -- but it's still active. Evidently there are model-specific differences that the ALPS driver doesn't handle correctly.

Note that it says "Disabling hardware tapping". mousedev module still does software tap emulation which can be turned off with mousedev.tap_time = 0

Quoted 6 lines
Quoted 6 lines

Looks like detection is correct, however either ALPS specific code doesn't work right, or it sets wrong parameters, I cannot tell. Here's the list of problems, from worst to least annoying:

- Very often, keyboard stops working after a click. Typing anything has no effect.

I am not quite sure about the keyboard iteractions but all-in-all I don't think ALPS support is really ready for prime-time yet, there some issues with tap and double-tap detection. I think Peter has some patches improving it though, but for now I recommend psmouse.proto=imps.

Quoted 6 lines

The more serious one is that sometimes it seems to spontaneously emit click events while I'm moving finger across pad. Which means I've had to learn to plan my "mouse" motions to avoid areas where clicking could have bad effects. But that's not always possible ...

That is default sensitivity not suiting your habits I think. I would recomment trying out Synaptics X driver (which also does ALPS) so you will be able adjust sensitivity the way you like it.

Signature · 1 line
Dmitry
#2 lore raw
Quoted 9 lines · Dmitry Torokhov
Quoted 4 lines · David Brownell

The more serious one is that sometimes it seems to spontaneously emit click events while I'm moving finger across pad. Which means I've had to learn to plan my "mouse" motions to avoid areas where clicking could have bad effects. But that's not always possible ...

That is default sensitivity not suiting your habits I think. I would recomment trying out Synaptics X driver (which also does ALPS) so you will be able adjust sensitivity the way you like it.

I think the problem is that the tap detection in mousedev.c is very simplistic. It always generates a button click if the time between "finger down" and "finger up" is small enough, even if the finger was moved a large x/y distance. The X driver handles this with another parameter that specifies the maximum allowed distance. If the finger moved more than this distance, no button event is generated.

Signature · 2 lines
Peter Osterlund - [email protected]
http://web.telia.com/~u89404340
#3 lore raw
Quoted 9 lines · Peter Osterlund
Quoted 8 lines · Dmitry Torokhov
Quoted 4 lines · David Brownell

The more serious one is that sometimes it seems to spontaneously emit click events while I'm moving finger across pad. Which means I've had to learn to plan my "mouse" motions to avoid areas where clicking could have bad effects. But that's not always possible ...

That is default sensitivity not suiting your habits I think.

That answer isn't good. No defaults should be that dangerous! But I suspect that's not really the issue...

Quoted 3 lines
Quoted 3 lines

I would
recomment trying out Synaptics X driver (which also does ALPS) so you will be able adjust sensitivity the way you like it.

With the Synaptics X driver (as supplied by SuSE -- but NOT configured automatically by the system install tool) and the ALPS parameters in the README.alps from synaptics-0.14.0, and kernel parameters "usb-handoff" and "mousedev.tap_time=0", I'm getting somewhat better results in this particular area.

I see some new "mouse"-specific failure modes though:

(a) Sometimes tapping automagically generates extra clicks. For example, pressing the delete button once will delete two or more mail messages. Unfortunately it's not actually smart enough to only kick in for spam! (I think this is exclusively when using the touchpad itself.)

(b) Sometimes tapping the left button seems to start half a drag event. For example a GUI button's menu pops up rather than performing the action associated with the button. That could be some funky UI settings, but it's not consistent ... and I've observed this with very quick button presses. So I think something else is afoot.

(c) Sometimes tapping seems to only generate a "down" event ... until I move the cursor, the "up" doesn't happen. Again, this is with the left button, not the touchpad itself.

I haven't recently seen that nasty "motion emits random mouseclicks" behavior, but given the way the hardware programs/trains user behavior, it's hard to say for sure quite yet.

I've not done enough with non-GUI keyboard interactions to say if that nasty keyboard blockage issue is gone or not; I wouldn't have seen it.

Quoted 6 lines

I think the problem is that the tap detection in mousedev.c is very simplistic. It always generates a button click if the time between "finger down" and "finger up" is small enough, even if the finger was moved a large x/y distance. The X driver handles this with another parameter that specifies the maximum allowed distance. If the finger moved more than this distance, no button event is generated.

Sounds like "dueling heuristics" here!

I think the behavior I'm now seeing supports that hypothesis. But it's hard to say without knowing more about how all the pieces fit together.

- Dave

#4 lore raw
In reply to Dmitry Torokhov
Quoted 8 lines · Dmitry Torokhov
Quoted 4 lines

The more serious one is that sometimes it seems to spontaneously emit click events while I'm moving finger across pad. Which means I've had to learn to plan my "mouse" motions to avoid areas where clicking could have bad effects. But that's not always possible ...

That is default sensitivity not suiting your habits I think. I would recomment trying out Synaptics X driver (which also does ALPS) so you will be able adjust sensitivity the way you like it.

Curiously enough, I did not see this effect until I applied Peter's patches 1 and 2. In sum, for a D600 with both nipple and trackpad (so, DualPoint):

2.6.10: ALPS not detected. Normal motion. No issues with sporadic tap. No issuses with keyboard. Cursor warps to the edge of the screen. 2.6.11-rc2: ALPS detected. Issues that I listed, keyboard dying is the worst. Warps still present (I wrote that they went away, but I was wrong). 2.6.11-rc1 + Peter's 1/4 and 1/2: Keyboard seems fixed by patch 1/4. The missing slow motion still present. New issue: sporadic (left button only) clicks generated by motions.

Can you tell me exactly how I go about "trying out Synaptics X driver"?

-- Pete

#5 lore raw
Quoted 3 lines · Pete Zaitcev

Can you tell me exactly how I go about "trying out Synaptics X driver"?

Peter's page is here:
http://web.telia.com/~u89404340/touchpad/

Just do "yum update synaptics" and then Adjust your xorg.conf to use "synaptics" driver. Start with the defaults as shown in the doc directory. I recommend setting protocol to "auto-dev". Make sure both psmouse and evdev are loaded.

Signature · 1 line
Dmitry