Skip to contentSkip to conversation

2.6.11-rc4: Alps touchpad too slow

DISCUSSION Andy Isaacson 4 participants 7 messages Mar 4, 2005 – Mar 22, 2005

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

My Vaio r505te comes up with an unusably slow touchpad if I allow the ALPS driver to drive it. It says

Quoted 3 lines

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

and then the trackpad operates at about 1/8 the speed I've gotten used to.

I'm running 2.6.11-rc4; this started happening somewhere between 2.6.10 and 2.6.11-rc3.

I've toyed with 'xset m', but nothing I've done there seems to have any effect. (I suspect that Linux never generates the appropriate sequence of mouse events to trigger the X cursor acceleration regime.)

I can restore the original behavior by passing "proto=exps" to psmouse.o, in which case I get

Quoted 1 line

input: PS/2 Generic Mouse on isa0060/serio1

On a related note, how are users supposed to control this newfangled PS2 driver? I'd like at least the *option* to turn tapping back on, but I can't find any knobs *anywhere*. And of course I'd like to adjust the tracking speed, too.

-andy

#1 lore raw
Quoted 17 lines · Andy Isaacson

My Vaio r505te comes up with an unusably slow touchpad if I allow the ALPS driver to drive it. It says

Quoted 3 lines

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

and then the trackpad operates at about 1/8 the speed I've gotten used to.

I'm running 2.6.11-rc4; this started happening somewhere between 2.6.10 and 2.6.11-rc3.

I've toyed with 'xset m', but nothing I've done there seems to have any effect. (I suspect that Linux never generates the appropriate sequence of mouse events to trigger the X cursor acceleration regime.)

Quoted 8 lines

I can restore the original behavior by passing "proto=exps" to psmouse.o, in which case I get

Quoted 1 line

input: PS/2 Generic Mouse on isa0060/serio1

On a related note, how are users supposed to control this newfangled PS2 driver? I'd like at least the *option* to turn tapping back on, but I can't find any knobs *anywhere*. And of course I'd like to adjust the tracking speed, too.

You can install the synaptics X driver

	http://web.telia.com/~u89404340/touchpad/

Which has all the knobs available and works with ALPSes too.

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#2 lore raw
In reply to Andy Isaacson
Quoted 18 lines · Andy Isaacson

My Vaio r505te comes up with an unusably slow touchpad if I allow the ALPS driver to drive it. It says

Quoted 3 lines

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

and then the trackpad operates at about 1/8 the speed I've gotten used to.

I'm running 2.6.11-rc4; this started happening somewhere between 2.6.10 and 2.6.11-rc3.

I've toyed with 'xset m', but nothing I've done there seems to have any effect. (I suspect that Linux never generates the appropriate sequence of mouse events to trigger the X cursor acceleration regime.)

Quoted 9 lines

I can restore the original behavior by passing "proto=exps" to psmouse.o, in which case I get

Quoted 1 line

input: PS/2 Generic Mouse on isa0060/serio1

On a related note, how are users supposed to control this newfangled PS2 driver? I'd like at least the *option* to turn tapping back on, but I can't find any knobs *anywhere*. And of course I'd like to adjust the tracking speed, too.

Andy, could you please test 2.6.12-rc1 and let us know which problems remain?

Thanks.

#3 lore raw
Quoted 8 lines · Andrew Morton
Quoted 7 lines · Andy Isaacson

My Vaio r505te comes up with an unusably slow touchpad if I allow the ALPS driver to drive it. It says

Quoted 3 lines

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

Quoted 5 lines
Quoted 2 lines

and then the trackpad operates at about 1/8 the speed I've gotten used to. ... 2.6.11-rc4 ...

Andy, could you please test 2.6.12-rc1 and let us know which problems remain?

With cvsbk rev 423b66b6oJOGN68OhmSrBFxxLOtIEA (rsynced Monday, it claims to be "2.6.12-rc1"), the situation is much improved. The AlpsPS/2 driver recognizes the trackpad, tracking speed is back to normal, and tapping is turned on by default. (Drat, now I need to figure out how to turn that off again.)

The kernel output is a bit odd, though:

[ 1200.254707] Adding 987988k swap on /dev/hda3.  Priority:-1 extents:1
[ 1200.330453] EXT3 FS on hda2, internal journal
[ 1203.504154] SCSI subsystem initialized
[ 1204.039053]   Enabling hardware tapping
[ 1204.099034] ieee1394: Initialized config rom entry `ip1394'
[ 1204.266077] input: PS/2 Mouse on isa0060/serio1
[ 1204.400583] input: AlpsPS/2 ALPS GlidePoint on isa0060/serio1
[ 1204.779799] sbp2: $Rev: 1219 $ Ben Collins <[email protected]>
[ 1206.183165] kjournald starting.  Commit interval 5 seconds

Note how the "Enabling hardware tapping" message is several lines earlier than it seems it should be... I don't think I'm supposed to be tapping on my SCSI hardware.

... ah, I think I'm missing the "ALPS GlidePoint detected" message which I used to get. Without it, the "Enabling hardware tapping" message is a bit opaque.

Other than that, I have no complaints about the trackpad.

Thanks for the ping.

-andy

#4 lore raw
Quoted 13 lines · Andy Isaacson
Quoted 11 lines · Andrew Morton
Quoted 9 lines · Andy Isaacson

My Vaio r505te comes up with an unusably slow touchpad if I allow the ALPS driver to drive it. It says

Quoted 3 lines

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

and then the trackpad operates at about 1/8 the speed I've gotten used to. ... 2.6.11-rc4 ...

Quoted 8 lines
Quoted 2 lines

Andy, could you please test 2.6.12-rc1 and let us know which problems remain?

With cvsbk rev 423b66b6oJOGN68OhmSrBFxxLOtIEA (rsynced Monday, it claims to be "2.6.12-rc1"), the situation is much improved. The AlpsPS/2 driver recognizes the trackpad, tracking speed is back to normal, and tapping is turned on by default. (Drat, now I need to figure out how to turn that off again.)

Wonderful, thanks.

Quoted 12 lines

The kernel output is a bit odd, though:

[ 1200.254707] Adding 987988k swap on /dev/hda3.  Priority:-1 extents:1
[ 1200.330453] EXT3 FS on hda2, internal journal
[ 1203.504154] SCSI subsystem initialized
[ 1204.039053]   Enabling hardware tapping
[ 1204.099034] ieee1394: Initialized config rom entry `ip1394'
[ 1204.266077] input: PS/2 Mouse on isa0060/serio1
[ 1204.400583] input: AlpsPS/2 ALPS GlidePoint on isa0060/serio1
[ 1204.779799] sbp2: $Rev: 1219 $ Ben Collins <[email protected]>
[ 1206.183165] kjournald starting.  Commit interval 5 seconds
Quoted 7 lines

Note how the "Enabling hardware tapping" message is several lines earlier than it seems it should be... I don't think I'm supposed to be tapping on my SCSI hardware.

... ah, I think I'm missing the "ALPS GlidePoint detected" message which I used to get. Without it, the "Enabling hardware tapping" message is a bit opaque.

Yes, alps_init() had a printk removed and now the output looks funny.

drivers/input/mouse/alps.c renamed from drivers/input/mouse/alps.c~alps-printk-tidy +1 -1
diff -puN drivers/input/mouse/alps.c~alps-printk-tidy drivers/input/mouse/alps.c
@@ -395,7 +395,7 @@ int alps_init(struct psmouse *psmouse)
 	}
 
 	if (param[0] & 0x04) {
-		printk(KERN_INFO "  Enabling hardware tapping\n");
+		printk(KERN_INFO "alps.c: Enabling hardware tapping\n");
 		if (alps_tap_mode(psmouse, 1))
 			printk(KERN_WARNING "alps.c: Failed to enable hardware tapping\n");
 	}

_

#5 lore raw
Quoted 5 lines · Andrew Morton
Quoted 5 lines

With cvsbk rev 423b66b6oJOGN68OhmSrBFxxLOtIEA (rsynced Monday, it claims to be "2.6.12-rc1"), the situation is much improved. The AlpsPS/2 driver recognizes the trackpad, tracking speed is back to normal, and tapping is turned on by default. (Drat, now I need to figure out how to turn that off again.)

Setting "MaxTapTime" in XF86Config if you're using the Synaptics X driver, or mousedev.maxtaptime=0 if you are using /dev/input.mice, to 0 should work.

Quoted 18 lines

Wonderful, thanks.

Quoted 16 lines

The kernel output is a bit odd, though:

[ 1200.254707] Adding 987988k swap on /dev/hda3.  Priority:-1 extents:1
[ 1200.330453] EXT3 FS on hda2, internal journal
[ 1203.504154] SCSI subsystem initialized
[ 1204.039053]   Enabling hardware tapping
[ 1204.099034] ieee1394: Initialized config rom entry `ip1394'
[ 1204.266077] input: PS/2 Mouse on isa0060/serio1
[ 1204.400583] input: AlpsPS/2 ALPS GlidePoint on isa0060/serio1
[ 1204.779799] sbp2: $Rev: 1219 $ Ben Collins <[email protected]>
[ 1206.183165] kjournald starting.  Commit interval 5 seconds

Note how the "Enabling hardware tapping" message is several lines earlier than it seems it should be... I don't think I'm supposed to be tapping on my SCSI hardware.

Quoted 5 lines
Quoted 3 lines

... ah, I think I'm missing the "ALPS GlidePoint detected" message which I used to get. Without it, the "Enabling hardware tapping" message is a bit opaque.

Yes, alps_init() had a printk removed and now the output looks funny.

I think just removing the message is better.

Quoted 13 lines

diff -puN drivers/input/mouse/alps.c~alps-printk-tidy drivers/input/mouse/alps.c

drivers/input/mouse/alps.c renamed from drivers/input/mouse/alps.c~alps-printk-tidy +1 -1
@@ -395,7 +395,7 @@ int alps_init(struct psmouse *psmouse)
 	}
 
 	if (param[0] & 0x04) {
-		printk(KERN_INFO "  Enabling hardware tapping\n");
+		printk(KERN_INFO "alps.c: Enabling hardware tapping\n");
 		if (alps_tap_mode(psmouse, 1))
 			printk(KERN_WARNING "alps.c: Failed to enable hardware tapping\n");
 	}

_

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#6 lore raw
Quoted 11 lines · Vojtech Pavlik
Quoted 5 lines · Andrew Morton
Quoted 5 lines

With cvsbk rev 423b66b6oJOGN68OhmSrBFxxLOtIEA (rsynced Monday, it claims to be "2.6.12-rc1"), the situation is much improved.  The AlpsPS/2 driver recognizes the trackpad, tracking speed is back to normal, and tapping is turned on by default.  (Drat, now I need to figure out how to turn that off again.)

Setting "MaxTapTime" in XF86Config if you're using the Synaptics X driver, or mousedev.maxtaptime=0 if you are using /dev/input.mice, to 0 should work.

Actually it is mousedev.tap_time=0

Signature · 1 line
Dmitry