> Not to point out the obvious but: did you enable the mouse?
:"> You cannot imagine how I feel now... It was disabled, I don't know how I didn't figure this out... Strange, because it was enabled before loading the driver, I guess the PS/2 device is what was enabled, but not the touchpad....
In any case, the good news is that the driver works now, and it is pretty usable!!! Thank you!!! You can claim support for a new device and laptop: Dell Inspiron 17R SE (aka 7720).
More details follow:
- Pointer moves fine.
- Click by tapping works.
- Buttons (for click and right-click) work. Middle-button simulation by simultaneous click works too.
- Both vertical and horizontal scroll do work. However, it does not work exactly in the edge. As reported in comment #165, there is about 1cm of space near the edges where the touchpad does not work. That is, the edges of the touchpad are useless: no scrolling, no pointer movement, no click... I wonder if that is related to this property reported by "xinput list-props":
Synaptics Edges (701): 204, 1156, 99, 561
Moving the finger on the right edge, for example, reports:
that is, x=1365, higher than the 1156 reported as synaptics edge. Btw, what is that??
- Tapping on the "right top corner" (I mean, ignoring the useless edges), simulates a middle-button click. On the right bottom, a right-button click. Same behavior as reported in comment #167. Mostly useless, however, because of the "useless edges": it is not obvious which are the corners ;-) The right-click effect is very hard to get, it seems only a small surface triggers that behavior.
- Fn+F3 works for enabling/disabling the device. One minor flaw: the LED that is supposed to show that the device is disabled is never on.
- Using two fingers makes the mouse go crazy, and the driver reports this kind of things:
psmouse serio1: alps: refusing packet[1] = be
psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 2
psmouse serio1: alps: refusing packet[0] = 0 (mask0 = c8, byte0 = c8)
psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
psmouse serio1: alps: bare_ps2_packet: 3 0 -67
psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced.
psmouse serio1: alps: d: ca 28 72 8 16 18 = 808 242 24
psmouse serio1: alps: refusing packet[1] = be
psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 2
psmouse serio1: alps: refusing packet[0] = 0 (mask0 = c8, byte0 = c8)
psmouse serio1: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
psmouse serio1: alps: bare_ps2_packet: 3 0 -67
psmouse serio1: GlidePoint at isa0060/serio1/input0 - driver resynced.
...
(I know it is not supported, but I give it a try). It may be good to log the packets that are being refused, in order to get some feedback of what is sending the touchpad.
In any case, I can only thank Dave for his efforts. Really great job!!! Thank you!
One suggestion: even if two-finger support is hard to get, it would be great to disable it at all, at least to avoid the device to go crazy. With that, the driver could be used for everyday work. Is that possible?
Regards
Vreixo
PS: Btw, this is the whole output of xinput list-props on the touchpad
Dave:
> Not to point out the obvious but: did you enable the mouse?
:"> You cannot imagine how I feel now... It was disabled, I don't know how I didn't figure this out... Strange, because it was enabled before loading the driver, I guess the PS/2 device is what was enabled, but not the touchpad....
In any case, the good news is that the driver works now, and it is pretty usable!!! Thank you!!! You can claim support for a new device and laptop: Dell Inspiron 17R SE (aka 7720).
More details follow:
- Pointer moves fine.
- Click by tapping works.
- Buttons (for click and right-click) work. Middle-button simulation by simultaneous click works too.
- Both vertical and horizontal scroll do work. However, it does not work exactly in the edge. As reported in comment #165, there is about 1cm of space near the edges where the touchpad does not work. That is, the edges of the touchpad are useless: no scrolling, no pointer movement, no click... I wonder if that is related to this property reported by "xinput list-props":
Synaptics Edges (701): 204, 1156, 99, 561
Moving the finger on the right edge, for example, reports:
psmouse serio1: alps: d: c8 55 16 8 3a 9 = 1365 406 9
psmouse serio1: alps: d: c8 55 18 8 3a 9 = 1365 408 9
psmouse serio1: alps: d: c8 55 1a 8 3a 9 = 1365 410 9
psmouse serio1: alps: d: c8 55 1c 8 3a 9 = 1365 412 9
psmouse serio1: alps: d: c8 55 1d 8 3a 9 = 1365 413 9
that is, x=1365, higher than the 1156 reported as synaptics edge. Btw, what is that??
- Tapping on the "right top corner" (I mean, ignoring the useless edges), simulates a middle-button click. On the right bottom, a right-button click. Same behavior as reported in comment #167. Mostly useless, however, because of the "useless edges": it is not obvious which are the corners ;-) The right-click effect is very hard to get, it seems only a small surface triggers that behavior.
- Fn+F3 works for enabling/disabling the device. One minor flaw: the LED that is supposed to show that the device is disabled is never on.
- Using two fingers makes the mouse go crazy, and the driver reports this kind of things:
psmouse serio1: alps: refusing packet[1] = be serio1/ input0 lost sync at byte 2 serio1/ input0 lost sync at byte 1 serio1/ input0 - driver resynced. serio1/ input0 lost sync at byte 2 serio1/ input0 lost sync at byte 1 serio1/ input0 - driver resynced.
psmouse serio1: GlidePoint at isa0060/
psmouse serio1: alps: refusing packet[0] = 0 (mask0 = c8, byte0 = c8)
psmouse serio1: GlidePoint at isa0060/
psmouse serio1: alps: bare_ps2_packet: 3 0 -67
psmouse serio1: GlidePoint at isa0060/
psmouse serio1: alps: d: ca 28 72 8 16 18 = 808 242 24
psmouse serio1: alps: refusing packet[1] = be
psmouse serio1: GlidePoint at isa0060/
psmouse serio1: alps: refusing packet[0] = 0 (mask0 = c8, byte0 = c8)
psmouse serio1: GlidePoint at isa0060/
psmouse serio1: alps: bare_ps2_packet: 3 0 -67
psmouse serio1: GlidePoint at isa0060/
...
(I know it is not supported, but I give it a try). It may be good to log the packets that are being refused, in order to get some feedback of what is sending the touchpad.
In any case, I can only thank Dave for his efforts. Really great job!!! Thank you!
One suggestion: even if two-finger support is hard to get, it would be great to disable it at all, at least to avoid the device to go crazy. With that, the driver could be used for everyday work. Is that possible?
Regards
Vreixo
PS: Btw, this is the whole output of xinput list-props on the touchpad
$ xinput list-props 16
Device 'AlpsPS/2 ALPS GlidePoint':
Device Enabled (132): 1
Coordinate Transformation Matrix (134): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (262): 1
Device Accel Constant Deceleration (263): 2.500000
Device Accel Adaptive Deceleration (264): 1.000000
Device Accel Velocity Scaling (265): 12.500000
Synaptics Edges (701): 204, 1156, 99, 561
Synaptics Finger (702): 12, 15, 128
Synaptics Tap Time (703): 180
Synaptics Tap Move (704): 66
Synaptics Tap Durations (705): 180, 180, 100
Synaptics ClickPad (706): 0
Synaptics Tap FastTap (707): 0
Synaptics Middle Button Timeout (708): 75
Synaptics Two-Finger Pressure (709): 141
Synaptics Two-Finger Width (710): 7
Synaptics Scrolling Distance (711): 30, 30
Synaptics Edge Scrolling (444): 1, 1, 0
Synaptics Two-Finger Scrolling (445): 0, 0
Synaptics Move Speed (712): 1.000000, 1.750000, 0.132363, 40.000000
Synaptics Edge Motion Pressure (713): 15, 80
Synaptics Edge Motion Speed (714): 1, 120
Synaptics Edge Motion Always (715): 0
Synaptics Off (442): 0
Synaptics Locked Drags (716): 0
Synaptics Locked Drags Timeout (717): 5000
Synaptics Tap Action (443): 2, 3, 0, 0, 1, 3, 0
Synaptics Click Action (718): 1, 1, 0
Synaptics Circular Scrolling (719): 0
Synaptics Circular Scrolling Distance (720): 0.100000
Synaptics Circular Scrolling Trigger (721): 0
Synaptics Circular Pad (722): 0
Synaptics Palm Detection (723): 0
Synaptics Palm Dimensions (724): 10, 100
Synaptics Coasting Speed (725): 20.000000, 50.000000
Synaptics Pressure Motion (726): ... of unknown type CARDINAL
Synaptics Pressure Motion Factor (727): 1.000000, 1.000000 event14"
Synaptics Resolution Detect (728): 1
Synaptics Grab Event Device (729): 1
Synaptics Gestures (730): 1
Synaptics Capabilities (731): 1, 1, 1, 1, 1, 1, 0
Synaptics Pad Resolution (732): 1, 1
Synaptics Area (733): 0, 0, 0, 0
Synaptics Noise Cancellation (734): 7, 7
Device Product ID (251): 2, 8
Device Node (252): "/dev/input/