Comment 414 for bug 550625

Revision history for this message
David Cramer (david-thingbag) wrote : Re: [Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/22/2011 04:13 PM, Seth Forshee wrote:
> On Thu, Sep 22, 2011 at 07:57:42PM -0000, David Cramer wrote:
>> Hi Seth,
>>
>> I'll be very happy to have multi-touch. Thank you for working on this.
>
> Note that "multi-touch" for this device is basically going to be
> two-fingered scrolling. The data isn't good enough to do much more with
> it.

That's fine. Two-fingered scrolling is all I really care about.

>
>> 2. After rebooting and before logging in, the touchpad works as before.
>> 3. After logging in, the touchpad stops working completely, but:
>> a. The pointer still works.
>> b. I now see a Touchpad tab in the mouse preferences, but changing settings had no effect on the non working touchpad.
>
> If it works in the window manager but not on the desktop, I don't think
> the driver is to blame. You can prove this by switching to a virtual
> console (e.g. Ctrl-Alt-F1) and running 'sudo lsinput', finding the Alps
> touchpad device, and then running 'sudo input-events' with the device
> number of the touchpad. If you see output spewing on the screen then you
> move your finger on the touchpad, the driver is probably working
> correctly.

Yes, that test indicates that the driver is working.

> If it is working correctly, the problem would seem to be elsewhere. I'm
> not very familiar with debugging problems in those areas, but I'll share
> what I do know. Return to the desktop (Ctrl-Alt-F7), open a terminal,
> and run 'xinput list'. You should see an "ALPS DualPoint Touchpad"
> device listed, followed by an id number. Run 'xinput --list-props <id>'
> using the id for the touchpad. At the top there should be a line labeled
> "Device Enabled", and the value should be 1. If it's not, run 'xinput
> --set-prop <id> "Device Enabled" 1' and see if your touchpad works.

Ok. When I do that, I see:

dcramer@anatine ~
$ xinput --list-props 13
Device 'AlpsPS/2 ALPS DualPoint TouchPad':
 Device Enabled (121): 0
...

When I run:

dcramer@anatine ~
$ xinput --set-prop 13 "Device Enabled" 1

The command completes without any error or output, but the touchpad
doesn't start working and when I run --list-props again, "Device Enable"
is still set to 0. If I do --set-prop while tailing /var/log/Xorg.0.log,
I see:

[ 9830.351] (--) AlpsPS/2 ALPS DualPoint TouchPad: touchpad found

Let me know if there are any other things I can try or if there's any
other information I can provide.

Thanks,
David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOe8yLAAoJEMHeSXG7afUhDhUH+QF9NgyqRwSUQIVybvqyFNMr
1lGfwRlHOMGSPlWSAexUhOrGjWM0WqFry7mw55dPzEjfI5OYludYA+WJMHAwHXKK
GtDOls/jD/TUNqdvbVwA/OXRnvdXYIYDDyqZcfw+nEkNJQtRaQ+3pqkxmv5z29sC
fobK8LpojIYfZ61Vj+ErcVNqt11cusXGVguByfblwd7apdm/McPcizu0lQc78BSe
k+xqtLqXjDYS0PAArRQ+wfiKMO4nqO31TLmH4aXjJWqIH4oFgpBBGtNJFDUhZYG2
bkpF1ewC+EO0Ava7+mdGh70FP7ZMjxN2IKCWrnj8BpZSi3XCNQ5nDAGNJk45OhY=
=CDUh
-----END PGP SIGNATURE-----