Alps touchpad not recognized, defaults to macintosh mouse button emulation

This looks like it affects me too. I have a Gateway NV5610u (NV 56 series), and it appears to have some type of ALPS GlidePoint touchpad (judging by the filenames of the driver updates for Windows). It is not recognized as a touchpad at all in Ubuntu Karmic. It is registered as either an IMPS/2 mouse with Scrollwheel, or a Macintosh mouse. Does anyone have any ideas about how to fix this?

Same on Toshiba U500-115.

Same on HP dm3. I hope someone can create a fix for beginners!

It affects me too on a HP dm3-1080ef.

This issue is still present using a Lucid LiveCD from yesterday.

Jonathan,
    Thank you for confirming this issue.

~JFo

It would be helpful to have a log of the output from lshal. Please run lshal and attach the output here.

Here is my lshal...

lshal on Dell Latitude XT

Here it is. This is from my HP Pavillion dm3 with Ubuntu 9.10. Let me know
if you need it from Lucid.
It is great you are working on this!

On Mon, Mar 22, 2010 at 10:59 AM, Chase Douglas <<email address hidden>
> wrote:

> It would be helpful to have a log of the output from lshal. Please run
> lshal and attach the output here.
>
> --
> Alps touchpad not recognized, defaults to macintosh mouse button emulation
> https://bugs.launchpad.net/bugs/505474
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: xserver-xorg-input-synaptics
>
> Hi , i'm using Ubuntu karmic 9.10 with 2.6.31-16-generic kernel.
>
> The Alps touchpad in my Dell Latitude XT isn't recognized by synaptics,
> that means i can't use the scrolling on touchpad and configure it via
> gsynaptics.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505474/+subscribe
>

--
Mary Henderson
(207) 212-8805

I believe this issue is fixed in Lucid. I would appreciate it if someone could download the Lucid beta 1 iso and run it to see if it properly detects the alps touchpad. You don't need to install lucid; trying lucid out from the cd is enough. If it is fixed, we can then work on backporting the fix to Karmic.

Thanks

I ran Lucid on my computer from a current live CD on March 16th and the
touch pad still did not show up with Systems, preferences, mouse. When I ran
the xinput list, it still showed the Macintosh mouse button emulation and no
touchpad.

On Mon, Mar 22, 2010 at 4:29 PM, Chase Douglas
<email address hidden>wrote:

> I believe this issue is fixed in Lucid. I would appreciate it if someone
> could download the Lucid beta 1 iso and run it to see if it properly
> detects the alps touchpad. You don't need to install lucid; trying lucid
> out from the cd is enough. If it is fixed, we can then work on
> backporting the fix to Karmic.
>
> Thanks
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Triaged
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> --
> Alps touchpad not recognized, defaults to macintosh mouse button emulation
> https://bugs.launchpad.net/bugs/505474
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-input-synaptics
>
> Hi , i'm using Ubuntu karmic 9.10 with 2.6.31-16-generic kernel.
>
> The Alps touchpad in my Dell Latitude XT isn't recognized by synaptics,
> that means i can't use the scrolling on touchpad and configure it via
> gsynaptics.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505474/+subscribe
>

--
Mary Henderson
(207) 212-8805

I have the same issue with Lucid beta 1...although my laptop is Acer 7736Z. The symptoms are the same. ALPS recognized as PS/2 mouse by the kernel. Same problem with 2.6.33.1 stock kernel.

I've uploaded a kernel to http://people.canonical.com/~cndougla/505474/. The kernel contains the fix for alps that is included in Lucid. I don't expect it to work here though, since Lucid doesn't appear to work. However, it has some debugging output enabled. Please install and run the kernel. Capture the dmesg output and attach a log here. (Note: The packages are i386. If someone needs an amd64 set of packages I can build them.)

Thanks

Looks the same to me with the kernel posted.

Dmesg attached

I've uploaded a new kernel to http://people.canonical.com/~cndougla/505474/alps2. This kernel adds support for the alps device that zK has according to his dmesg. There are a few options that I had to guess at, so I'm hoping they are correct. For instance, I had to guess that it has both a trackpad and a mouse nub/stick/eraser head/etc. Please test the kernel out. Test all movement and buttons and anything else you can think of to ensure that things are working right.

Thanks

Thanks again for your work. I'm embarrassed to say I don't know how to
download and install it, but would love to learn! Did you get the lshal log
I sent? I don't have one of those eraserheads; just the touch pad - will
that affect the over-all operation?

On Tue, Mar 23, 2010 at 12:00 PM, Chase Douglas <<email address hidden>
> wrote:

> I've uploaded a new kernel to
> http://people.canonical.com/~cndougla/505474/alps2<http://people.canonical.com/%7Ecndougla/505474/alps2>.
> This kernel adds
> support for the alps device that zK has according to his dmesg. There
> are a few options that I had to guess at, so I'm hoping they are
> correct. For instance, I had to guess that it has both a trackpad and a
> mouse nub/stick/eraser head/etc. Please test the kernel out. Test all
> movement and buttons and anything else you can think of to ensure
> things are working right.
>
> Thanks
>
> --
> Alps touchpad not recognized, defaults to macintosh mouse button emulation
> https://bugs.launchpad.net/bugs/505474
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-input-synaptics
>
> Hi , i'm using Ubuntu karmic 9.10 with 2.6.31-16-generic kernel.
>
> The Alps touchpad in my Dell Latitude XT isn't recognized by synaptics,
> that means i can't use the scrolling on touchpad and configure it via
> gsynaptics.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505474/+subscribe
>

--
Mary Henderson
(207) 212-8805

I tried your kernel.

Touchpad gets correctly identified as an Alps touchpad and gsynaptics works ( Vertical scrolling,sensitivity etc).

Unfortunately the pointing stick and its buttons don't work and actually they mess up the touchpad buttons causing them to stop working.

See this picture to understand what pointing stick i'm talking about:

http://farm3.static.flickr.com/2094/2198540287_5efe66b142.jpg

There are also 2 buttons under it,see this picture:

http://farm3.static.flickr.com/2298/2199331142_9d4443f93b.jpg

Both the pointing stick and upper buttons don't work with this kernel, they work fine with old kernel.

@Mary:

I did get your lshal output (it's attached to this bug now). Since you don't have an eraserhead/stick, I think you have a different model of alps touchpad. Please attach a dmesg log by running "dmesg > dmesg.txt" and attaching it to this bug.

Thanks

@zk:

OK, we're getting somewhere then. Can you try out the buttons and stick (to generate log messages) and then post your dmesg from this new kernel? It may have some output in it from when you tried to use the other buttons and stick but they failed.

Thanks

Here it is...

On Tue, Mar 23, 2010 at 1:22 PM, Chase Douglas
<email address hidden>wrote:

> @Mary:
>
> I did get your lshal output (it's attached to this bug now). Since you
> don't have an eraserhead/stick, I think you have a different model of
> alps touchpad. Please attach a dmesg log by running "dmesg > dmesg.txt"
> and attaching it to this bug.
>
> Thanks
>
> --
> Alps touchpad not recognized, defaults to macintosh mouse button emulation
> https://bugs.launchpad.net/bugs/505474
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-input-synaptics
>
> Hi , i'm using Ubuntu karmic 9.10 with 2.6.31-16-generic kernel.
>
> The Alps touchpad in my Dell Latitude XT isn't recognized by synaptics,
> that means i can't use the scrolling on touchpad and configure it via
> gsynaptics.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505474/+subscribe
>

--
Mary Henderson
(207) 212-8805

I don't see any new output produced in dmesg when using the pointing stick or its buttons.

Here it is anyway.

@Mary:

As I suspected, your ALPS device is different than zK's. Please open a new bug report for your device and include all the apport information along with it. You can do this by running "ubuntu-bug -p linux". I'd suggest a title for the bug report like: "ALPS device (E7: 73 02 64) needs new model entry in alps.c".

Thanks

Great bug reporting feature! The new bug is #545307.

On Tue, Mar 23, 2010 at 2:06 PM, Chase Douglas
<email address hidden>wrote:

> @Mary:
>
> As I suspected, your ALPS device is different than zK's. Please open a
> new bug report for your device and include all the apport information
> along with it. You can do this by running "ubuntu-bug -p linux". I'd
> suggest a title for the bug report like: "ALPS device (E7: 73 02 64)
> needs new model entry in alps.c".
>
> Thanks
>
> --
> Alps touchpad not recognized, defaults to macintosh mouse button emulation
> https://bugs.launchpad.net/bugs/505474
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-input-synaptics
>
> Hi , i'm using Ubuntu karmic 9.10 with 2.6.31-16-generic kernel.
>
> The Alps touchpad in my Dell Latitude XT isn't recognized by synaptics,
> that means i can't use the scrolling on touchpad and configure it via
> gsynaptics.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/505474/+subscribe
>

--
Mary Henderson
(207) 212-8805

@zK:

I forgot to mention the best way to test mouse buttons. If the two extra buttons are supposed to be mapped to left and right click, then obviously they should just work. However, if they are supposed to be mapped to some other function, then you may not realize they are working properly. To test these buttons, run xev from the terminal. A window will pop up. Move your mouse cursor anywhere within the window. You should see lots of output in the terminal as you move the mouse around and press buttons. Try the working right and left mouse buttons to get an idea of what a proper print out would be. Next, try the two extra buttons. If they work, you should see some print out from them as well. If they don't work, you won't see anything.

Please test the extra mouse buttons to see if they are recognized. If they aren't, I will try some other options in the driver.

P.S.: I may know how to get your "stick" working as well, but I'll wait for feedback on your buttons before I spin a new kernel.

Thanks

No events in xev when using the two upper buttons.

They are suppose to replace the lower one to be used with the stick, they should act like them.

@zK:

I've uploaded a new test kernel to http://people.canonical.com/~cndougla/505474/alps3. I'm hoping this will enable both the stick and the upper two buttons. Please test it out and report back.

Thanks

I tried it.

Now the stick cursor doesn't move at all now, before it was jumping around.

Same for the stick buttons, they don't mess up the touchpad buttons like before but they do nothing.

Xev reports nothing for both.

@zK:

Anything interesting in the dmesg? I wouldn't mind seeing the output of dmesg | grep -i alps. If the output is too large you can attach it to the bug.

Thanks

[ 0.000000] Linux version 2.6.31-21-generic (root@emerald) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) ) #58~alps1 SMP Mon Mar 22 21:16:34 UTC 2010 (Ubuntu 2.6.31-21.58~alps1-generic)
[ 43.722690] alps.c: E6 report: 00 00 64
[ 43.765495] alps.c: E7 report: 73 00 14
[ 43.808535] alps.c: E6 report: 00 00 64
[ 43.856614] alps.c: E7 report: 73 00 14
[ 44.048778] alps.c: Status: 00 02 0a
[ 44.253943] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input10
[ 86.846725] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 86.847725] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 86.848736] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 129.430799] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 129.431760] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 129.432710] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 320.088003] alps.c: E6 report: 20 00 64
[ 320.897365] alps.c: E6 report: 00 00 64
[ 320.956662] alps.c: E7 report: 73 00 14
[ 320.999268] alps.c: E6 report: 00 00 64
[ 321.045753] alps.c: E7 report: 73 00 14
[ 321.251788] alps.c: Status: 00 02 0a
[ 321.473897] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input16

@zk:

I've built a new kernel with a new option. I'm not sure whether it will work based on your last comment. The "refusing packet[0]" lines worry me, because they aren't valid for any protocol that I see. Hopefully this new option will make things better *crosses fingers*.

http://people.canonical.com/~cndougla/505474/alps4/

Still the same

@zK:

Does the dmesg look the same or is the output different?

Looks pretty much the same to me...

[ 0.000000] Linux version 2.6.31-21-generic (root@emerald) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) ) #58~alps4 SMP Wed Mar 24 21:52:27 UTC 2010 (Ubuntu 2.6.31-21.58~alps4-generic)
[ 45.113749] alps.c: E6 report: 00 00 64
[ 45.156881] alps.c: E7 report: 73 00 14
[ 45.199658] alps.c: E6 report: 00 00 64
[ 45.242545] alps.c: E7 report: 73 00 14
[ 45.440753] alps.c: Status: 00 02 0a
[ 45.634834] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input10
[ 84.102577] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 84.103534] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 84.104491] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 84.247829] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 84.248809] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 84.249818] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 85.541769] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 85.542727] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 85.543693] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 85.691582] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 85.692530] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 85.693503] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 96.866906] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 96.867874] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 96.868830] alps.c: refusing packet[0] = 0 (mask0 = f8, byte0 = f8)
[ 223.778449] alps.c: E6 report: 20 00 64
[ 224.728836] alps.c: E6 report: 00 00 64
[ 224.771495] alps.c: E7 report: 73 00 14
[ 224.814334] alps.c: E6 report: 00 00 64
[ 224.858503] alps.c: E7 report: 73 00 14
[ 225.067220] alps.c: Status: 00 02 0a
[ 225.316713] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input16

At this point, I'm not too sure what else I can try. I've exhausted the options dealing with the stick, and the log seems to indicate that there's a fundamental protocol issue going on. I would open a bug upstream at bugzilla.kernel.org to reach the maintainers of the driver who may have a better idea of what to try. If you do open a bug, please link it to this bug so it can be tracked.

Sorry I can't be more help.

Chase,

I haven't looked at all of zK's attachments, but would his problem with your kernel be related to this LKML discussion?

http://lists.zerezo.com/linux-kernel/msg19772533.html

If so, the problem is a 9-byte packet, and it doesn't look like the fix at the above URL exists in the Ubuntu kernel source.

I'd be interested in seeing your kernel that correctly detects the ALPS DualPoint for 64-bit Karmic, if it's not already too late.

I just got a 2 year-old Dell Latitude E6500 for work, which has the same problem zK is experiencing, and I'd love to get it running sooner rather than later.

@Ed:

Thanks for taking the time to look into this. The fix for your issue has recently been committed to the Karmic (and Lucid) kernel sources. It's in the current Lucid kernel, but since there's a more rigid and less frequent process for released distributions it has not yet been released for Karmic. You can find the relevant commit for Karmic at:

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-karmic.git;a=commitdiff;h=f715e7fcd18f17b94a661a0678a7e562f7557809;hp=80458d7b5e31dffead1631222440beab91483748

The first kernel with this fix is currently in karmic-proposed. After it goes through more testing it will get pushed out to karmic-updates. If you don't want to wait for it you can install the package manually by downloading it from:

https://launchpad.net/ubuntu/+source/linux/2.6.31-21.59

You should only need the linux-image-2.6.31-21-generic, linux-headers-2.6.31-21, and linux-headers-2.6.31-21-generic packages.

If this kernel fixes things for you, great! If you still have an issue, please open a separate bug for it.

I have the same problem with kernel 2.6.32-24-generic (lucid) in a HP mini 311-1000. What info do you need to help fix this?

/Matias

Having same problem with 2.6.31-22 on Lucid, with Dell XT. Touchpad appears as Macintosh mouse, and synaptics driver won't load. Note that I haven't switched to 2.6.32-xx because, so far, these make the XT's touch screen (evtouch) go haywire. Is there any progress on this bug, since it seems that it wasn't fixed in 2.6.31-21 as previously stated?

-d

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.