Wacom stylus and touch not recognised on Lenovo X220t

[Richard Brown]

The wacom touch and pen digitisers are not working on Quantal at all. The USB device shows up as

Bus 002 Device 005: ID 056a:0094 Wacom Co., Ltd

on lsusb, but if I type xinput list, the touch, pen, and eraser inputs do not show up. The Wacom Graphics Tablet tool reports that there is no tablet connected.

The problem has been present throughout pretty much the entire release I think. It works fine under Precise.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-input-wacom 1:0.14.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CasperVersion: 1.320
Date: Tue Aug 7 04:37:04 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120806.1)
MachineType: LENOVO 4298CTO
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
SourcePackage: xf86-input-wacom
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/14/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET58WW (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4298CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4298CTO:pvrThinkPadX220Tablet:rvnLENOVO:rn4298CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4298CTO
dmi.product.version: ThinkPad X220 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.37-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.12.1.902-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~really6.14.4-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-1build1

[Ritesh Khadgaray (khadgaray)]

Also seen with X230t .

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Maarten Lankhorst (mlankhorst)]

Can you start the Xorg server with -verbose 10, then plug in the device and paste the log?

[Richard Brown (rgbrown)]

It's the built in device (embedded in the screen). Is there something equivalent I can do?

[Timo Aaltonen (tjaalton)]

this is actually a known regression in the kernel, something in the input layer in the newer kernel changes the device ID (it should be 00e6, not 0094). See this thread:

http://sourceforge.net/mailarchive/forum.php?thread_name=CAF8JNhL%3DguPxnyqxHbreN%3DtNxfzXw2o8HZKN%2BHGYn%3DVjV6PXuQ%40mail.gmail.com&forum_name=linuxwacom-devel

it's fixed in 3.6-rc1, but not simply by pulling the wacom changes, something else got changed as well.

[Anton Anikin (anton-anikin)]

I have the same problem
056a:0094 Wacom
HP tm2 laptop
Ubuntu 12.10

[Joseph Salisbury (jsalisbury)]

Can folks affected by this bug test the latest Quantal kernel? You can update to the latest kernel for this release by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get install linux

[Richard Brown (rgbrown)]

Hi Joseph

I just tried it on the daily live image (with kernel 3.5.0.13.13) and it still doesn't work -- is this the right kernel? Attempting to upgrade didn't seem to reveal any newer one ...

[Richard Brown (rgbrown)]

I've just tested it on kernel 3.6-rc5 from the kernel-ppa, and touch and pen both work with this kernel

[Anton Anikin (anton-anikin)]

What about backporting fixes to 3.5 kernel? )

[Joseph Salisbury (jsalisbury)]

@Anton, It might be possible for this fix to be backported. We first need to identify the commit upstream that fixes this bug.

Can you test the following two kernels and report back? I expect v3.5 final to have the bug and v3.6-rc1 to not:

v3.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-quantal/
v3.6-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc1-quantal/

I can then perform a reverse kernel-bisect to find the upstream fix.

[Richard Brown (rgbrown)]

I've tested 3.5 final and 3.6rc1. It is as you predicted, the bug exists on 3.5 final, but is fixed in 3.6rc1.

By the way, for anyone else testing this, if you boot into a working kernel after having been in a not-working one, touch/pen won't initially work. Putting the laptop to sleep and waking it up again seems to reliably get it going again.

[George Shuklin (george-shuklin)]

confirm: 3.2-20, after boot wacom is inactive, going to sleep and back (closing and opeing lid) activate wacom and touchscreen.

[Timo Aaltonen (tjaalton)]

3.5.1 should have the fixes to the wacom driver that were supposed to fix this, but 3.6-rc1 had something else that they need, so a bisect is needed..

the suspend/resume issue is probably bug 1050724

[Joseph Salisbury (jsalisbury)]

I started a reverse bisect between v3.5 and v3.6-rc1. The first kernel has been built up to commit:
614a6d4341b3760ca98a1c2c09141b71db5d1e90

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1033783

Can you test that kernel and report back if it has the bug or not?

[Richard Brown (rgbrown)]

Hi Joseph, this kernel still has the bug

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
aa0b3b2bee1d3ca8355de76caebf65b836c9bb6e

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1033783

Can you test that kernel and report back if it has the bug or not?

[Richard Brown (rgbrown)]

The bug is fixed in this kernel

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
419e9266884fa853179ab726c27a63a9d3ae46e3

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1033783

Can you test that kernel and report back if it has the bug or not?

[Richard Brown (rgbrown)]

This kernel has the bug

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
c1b669b72a05aeae0882742dd40f30d51732ed15

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1033783

Can you test that kernel and report back if it has the bug or not?

[Richard Brown (rgbrown)]

(found some broadband in Brisbane!) The bug is fixed in this kernel

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
9fc377799bc9bfd8d5cb35d0d1ea2e2458cbdbb3

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1033783

Can you test that kernel and report back if it has the bug or not?

[Richard Brown (rgbrown)]

This kernel still has the bug

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, which is up to commit:
32830f207691176234b4c4dd17f0d7ab6d87d94b

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1033783

Can you test that kernel and report back if it has the bug or not?

[Richard Brown (rgbrown)]

This kernel (in #26) still has the bug

[Tom Jaeger (thjaeger)]

Looks like this is the patch that we need:

commit 4e7b7337e41b84b3fc3928f7b7a1909b49c125f8
Author: Ping Cheng <email address hidden>
Date: Tue Jun 12 00:14:12 2012 -0700

    Input: wacom - rearrange type enum

    So we can simplify a few type related if statements

    Signed-off-by: Ping Cheng <email address hidden>
    Acked-by: Chris Bagwell <email address hidden>
    Reviewed-by: Jason Gerecke <email address hidden>
    Signed-off-by: Dmitry Torokhov <email address hidden>

[Tom Jaeger (thjaeger)]

Sorry, the id of the commit is ea2e60244573a9204c8cee9b4fb181106784c617.

(I rebased all the wacom patches in the range v3.5..v3.6-rc1 on top of v3.5 and then bisected, which obviously changed the commit ids)

[Joseph Salisbury (jsalisbury)]

Thanks for the info, Tom.

I cherry-picked commit ea2e60244573a9204c8cee9b4fb181106784c617 and applied it to Quantal. A test kernel is building now. I'll post a link to it shortly.

[Joseph Salisbury (jsalisbury)]

I built a Quantal test kernel with commit ea2e60244573a9204c8cee9b4fb181106784c617 applied.

This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1033783

Can you test that kernel and report back if it has the bug or not?

[Richard Brown (rgbrown)]

Yes, that is the correct commit - the bug is fixed with this kernel (in #31)

[Anton Anikin (anton-anikin)]

Hm, the #31 not works for me on HP tm2 laptop.
Bus 004 Device 003: ID 056a:0094 Wacom Co., Ltd
 - still 0094 device ID

[Joseph Salisbury (jsalisbury)]

@Richard Brown,

Can you run lsusb and post the output, while booted into the test kernel in comment #31?

[Timo Kluck (tkluck)]

The #31 does work for me on a HP tm2 laptop. Anton, perhaps you could use "uname -r" and " dpkg -s linux-image-3.5.0-16-generic" to verify that you are running the right kernel with package version 3.5.0-16.25~lp1033783v1 ?

[Anton Anikin (anton-anikin)]

root@ubuntu:~# uname -a
Linux ubuntu 3.5.0-16-generic #25~lp1033783v1 SMP Mon Oct 1 18:05:11 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu:~# lsusb | grep -i wacom
Bus 004 Device 003: ID 056a:0094 Wacom Co., Ltd

[Anton Anikin (anton-anikin)]

root@ubuntu:~# xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎜ ↳ Microsoft Wireless Laser Mouse 8000 id=15 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Video Bus id=8 [slave keyboard (3)]
    ↳ Power Button id=9 [slave keyboard (3)]
    ↳ Sleep Button id=10 [slave keyboard (3)]
    ↳ HP Webcam id=11 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
    ↳ HP WMI hotkeys id=14 [slave keyboard (3)]

No wacom in Xorg :(

[Simon K (octav14n)]

at my HP tm2 this (#31) fix solved my problem.
octavian@Octavian-Notebook:~$ lsusb | grep -i wacom
Bus 002 Device 003: ID 056a:00e3 Wacom Co., Ltd

My Wacom seems to sit at another bus than @anton-anakin? Is this possible causing this bug for him?

[Richard Brown (rgbrown)]

On my x220t with kernel in #31:

richard@krylov:~$ lsusb | grep Wacom
Bus 002 Device 003: ID 056a:00e6 Wacom Co., Ltd

@Anton, can you confirm that you've tried putting your computer to sleep before trying this? (see comment #13)

[Anton Anikin (anton-anikin)]

No, after resume it still not works.
Also I have tried to boot WIndowsXP from USB flash drive (in Windows wacom works fine) and boot Ubuntu after this - same result.

[Joseph Salisbury (jsalisbury)]

@Anton Anikin,

It is probably best for you to open a new bug. That way we can look at the details of your system.

[Anton Anikin (anton-anikin)]

I have a bugreport created before:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-wacom/+bug/1045000

[Ray-Ven (ray-ven)]

fixed in 3.5.0-17-generic

[George Shuklin (george-shuklin)]

Confirm, new kernels fix wacom touch screen, pen and eraser. But it do it only after computer going to sleep and back.

It's really interesing:

Pure Precise works fine without getting to sleep.
Quantal with precies'es kernel require sleep before wacom get alive.
Quantal with fixed kernel require sleep before wacom get alive.

Seems like 'sleep problem' is not kernel-related. Should I report separate bug for this (and if yes, which package)?

[Timo Aaltonen (tjaalton)]

yes, please file a new bug for that

[Atilla Yilmaz (atilla-2)]

I recently purchased a Fujitsu Lifebook T902 (which is a convertible tablet) and installed Quantal (12.10). I am experiencing the same problem as above i.e., the tablet mode is not recognized at all. As far as I understand, this bug is fixed for Lenovo in the newer kernels, however it still persists for Fujitsu:

http://sourceforge.net/mailarchive/message.php?msg_id=29777922

What should I do? Would installing Precise (12.04) solve this problem? Thanks!