TrackPoint: middle button doesn't work on TrackPoint-compatible device.

Bug #1746002 reported by AaronMa on 2018-01-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HWE Next
linux (Ubuntu)
linux-oem (Ubuntu)

Bug Description

Lenovo introduced 4 new TrackPoint compatible sticks those only support the minimum commands described in the spec, which has been used in the current Windows driver.

Legacy TrackPoint: 0101 – 0E01

ALPS: 0102 – FF02

ELAN:0103 – FF03

NXP: 0104 – FF04

TrackPoint (ID: 01/02) report 0 button when reading the EXT_BUTTON command.

Setting middle button enabled to make it work.

Upstream patch:
commit f5d07b9e98022d50720e38aa936fc11c67868ece
Author: Aaron Ma <email address hidden>
Date: Fri Jan 19 09:43:39 2018 -0800

    Input: trackpoint - force 3 buttons if 0 button is reported

    Lenovo introduced trackpoint compatible sticks with minimum PS/2 commands.
    They supposed to reply with 0x02, 0x03, or 0x04 in response to the
    "Read Extended ID" command, so we would know not to try certain extended
    commands. Unfortunately even some trackpoints reporting the original IBM
    version (0x01 firmware 0x0e) now respond with incorrect data to the "Get
    Extended Buttons" command:

     thinkpad_acpi: ThinkPad BIOS R0DET87W (1.87 ), EC unknown
     thinkpad_acpi: Lenovo ThinkPad E470, model 20H1004SGE

     psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 0/0

    Since there are no trackpoints without buttons, let's assume the trackpoint
    has 3 buttons when we get 0 response to the extended buttons query.

    Signed-off-by: Aaron Ma <email address hidden>
    Cc: <email address hidden>
    Signed-off-by: Dmitry Torokhov <email address hidden>

AaronMa (mapengyu) on 2018-01-29
tags: added: originate-from-1722312 sutton
Changed in hwe-next:
assignee: nobody → AaronMa (mapengyu)

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1746002

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

Changed in linux (Ubuntu):
status: New → Incomplete
Timo Aaltonen (tjaalton) on 2018-02-02
Changed in linux (Ubuntu Xenial):
status: New → Invalid
Changed in linux-oem (Ubuntu):
status: New → Invalid
Timo Aaltonen (tjaalton) on 2018-02-12
Changed in linux-oem (Ubuntu Xenial):
status: New → Fix Committed
Timo Aaltonen (tjaalton) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-xenial
Stefan Bader (smb) on 2018-02-16
Changed in linux-oem (Ubuntu Artful):
status: New → Invalid
Changed in linux (Ubuntu Artful):
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers