Trackpad on Razer Blade Pro (2016) only functions as mouse

[Stefanie Jane 🌠]

The new Razer Blade Pro (2016) is an extremely high-end gaming laptop and hasn't seen much Linux activity as of yet. I've worked on several drivers and improvements already, however the trackpad on this laptop is not functioning correctly and needs upstream love.

The trackpad appears to be a new Glidepoint model from Cirque, and I am unable to find any information or even similar models compare with. It is connected over the Designware I2C bus, and ends up claimed as a mouse by the hid-generic driver. Simple usage works, but multitouch, gestures, and other customizations are not possible. I have tried to use the hid-alps driver with it, but it does not work (after adding the relevant identifiers). I've also tried a laundry list of hacks and workarounds found in dubious places of the internet, with no help. Additionally, I tried Dell's uinput-based Glidepoint driver which of course did not work. I've not done any protocol sniffing or reverse engineering as of yet.

I've tested with both the yakkety production kernel and am now on mainline 4.9-rc8 with the same behavior.

Output from evemu-describe:

# EVEMU 1.2
# Input device name: "CRQ1001:00 0488:D020"
# Input device ID: bus 0x18 vendor 0x488 product 0xd020 version 0x100
# Supported events:
# Event type 0 (EV_SYN)
# Event code 0 (SYN_REPORT)
# Event code 1 (SYN_CONFIG)
# Event code 2 (SYN_MT_REPORT)
# Event code 3 (SYN_DROPPED)
# Event code 4 ((null))
# Event code 5 ((null))
# Event code 6 ((null))
# Event code 7 ((null))
# Event code 8 ((null))
# Event code 9 ((null))
# Event code 10 ((null))
# Event code 11 ((null))
# Event code 12 ((null))
# Event code 13 ((null))
# Event code 14 ((null))
# Event type 1 (EV_KEY)
# Event code 272 (BTN_LEFT)
# Event code 273 (BTN_RIGHT)
# Event code 274 (BTN_MIDDLE)
# Event type 2 (EV_REL)
# Event code 0 (REL_X)
# Event code 1 (REL_Y)
# Event code 8 (REL_WHEEL)
# Event type 4 (EV_MSC)
# Event code 4 (MSC_SCAN)
# Event type 20 (EV_REP)
# Event code 0 (REP_DELAY)
# Properties:
N: CRQ1001:00 0488:D020
I: 0018 0488 d020 0100
P: 00 00 00 00 00 00 00 00
B: 00 0b 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 07 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 02 03 01 00 00 00 00 00 00
B: 03 00 00 00 00 00 00 00 00
B: 04 10 00 00 00 00 00 00 00
B: 05 00 00 00 00 00 00 00 00
B: 11 00 00 00 00 00 00 00 00
B: 12 00 00 00 00 00 00 00 00
B: 14 01 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00

The Windows driver .inf identifies it as "Glide_RazerFrancine":
%GlideTpd.Francine% = Glide_RazerFrancine, HID\CRQ1001&Col02

Filing the bug here in case someone at Canonical can help, otherwise it probably needs to go to linux-input (where I've seen folks from Cirque and Alps post frequently).

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1648259

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.

[Kaz Wolfe (kazwolfe)]

ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kazwolfe 1793 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=78ce5bfd-9a16-45fb-94b6-087cccb7e466
InstallationDate: Installed on 2017-10-05 (1 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
MachineType: Razer Blade Pro
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-36-generic.efi.signed root=/dev/mapper/ubuntu-root ro quiet nosplash
ProcVersionSignature: Ubuntu 4.10.0-36.40~16.04.1-generic 4.10.17
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-36-generic N/A
 linux-backports-modules-4.10.0-36-generic N/A
 linux-firmware 1.157.12
Tags: xenial
Uname: Linux 4.10.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/24/2017
dmi.bios.vendor: Razer
dmi.bios.version: 02.00
dmi.board.name: Razer
dmi.board.vendor: Razer
dmi.chassis.type: 9
dmi.chassis.vendor: Razer
dmi.modalias: dmi:bvnRazer:bvr02.00:bd01/24/2017:svnRazer:pnBladePro:pvr2.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
dmi.product.name: Blade Pro
dmi.product.version: 2.06
dmi.sys.vendor: Razer

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

apport information

[Kaz Wolfe (kazwolfe)]

Attached my own logs to this bug - I have the model up (Razer Blade Pro 2017), but the touchpad reports the exact same.

I can confirm this bug on Ubuntu 16.04 with kernel 4.10.0-36-generic.

[Kai-Heng Feng (kaihengfeng)]

Can you try latest mainline kernel, v4.14-rc3?

[Kaz Wolfe (kazwolfe)]

I can only test a console in the mainline kernel (dependency on NVIDIA drivers), however evemu-describe reports the exact same thing as in OP's post"

# EVEMU 1.2
# Input device name: "Razer Razer Blade Pro"
# Input device ID: bus 0x03 vendor 0x1532 product 0x225 version 0x111
# Supported events:
# Event type 0 (EV_SYN)
# Event code 0 (SYN_REPORT)
# Event code 1 (SYN_CONFIG)
# Event code 2 (SYN_MT_REPORT)
# Event code 3 (SYN_DROPPED)
# Event code 4 ((null))
# Event code 5 ((null))
# Event code 6 ((null))
# Event code 7 ((null))
# Event code 8 ((null))
# Event code 9 ((null))
# Event code 10 ((null))
# Event code 11 ((null))
# Event code 12 ((null))
# Event code 13 ((null))
# Event code 14 ((null))
# Event type 1 (EV_KEY)
# Event code 272 (BTN_LEFT)
# Event code 273 (BTN_RIGHT)
# Event code 274 (BTN_MIDDLE)
# Event code 275 (BTN_SIDE)
# Event code 276 (BTN_EXTRA)
# Event type 2 (EV_REL)
# Event code 0 (REL_X)
# Event code 1 (REL_Y)
# Event code 8 (REL_WHEEL)
# Event type 4 (EV_MSC)
# Event code 4 (MSC_SCAN)
# Properties:
N: Razer Razer Blade Pro
I: 0003 1532 0225 0111
P: 00 00 00 00 00 00 00 00
B: 00 0b 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 1f 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 02 03 01 00 00 00 00 00 00
B: 03 00 00 00 00 00 00 00 00
B: 04 10 00 00 00 00 00 00 00
B: 05 00 00 00 00 00 00 00 00
B: 11 00 00 00 00 00 00 00 00
B: 12 00 00 00 00 00 00 00 00
B: 14 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00

If I had to guess, the issue is still there, but I can't truly tell without a graphical session (which I can not get at this time).