X220t Tablet no longer working

[Jonas Jelten]

Hi list!

After updating packages and rebooting 1 week ago, my integrated Wacom
tablet ISDv4 (pen and touch) (056a:0094) no longer works.
Laptop: LENOVO X220t 4296CTO/4296CTO, BIOS 8DET61WW (1.31 ) 04/25/2012
Arch Linux x86_64, testing

Things that got updated and had to do with wacom:

[2012-01-17 08:37] upgraded xf86-input-wacom (0.12.0-1 -> 0.13.0-1)
[2012-02-12 12:21] upgraded xf86-input-wacom (0.13.0-1 -> 0.13.0-2)
[2012-03-10 18:28] upgraded xf86-input-wacom (0.13.0-2 -> 0.14.0-1)
[2012-04-01 22:15] installed libwacom (0.4-1)
[2012-04-14 14:12] upgraded xf86-input-wacom (0.14.0-1 -> 0.14.0-2)
[2012-05-13 14:35] upgraded xf86-input-wacom (0.14.0-2 -> 0.15.0-1)
[2012-07-03 02:40] upgraded libwacom (0.4-1 -> 0.6-1)
[2012-07-13 09:03] upgraded xf86-input-wacom (0.15.0-1 -> 0.16.0-1)
[2012-07-23 19:10] reinstalled xf86-input-wacom (0.16.0-1 -> 0.16.0-1)
[2012-07-25 03:40] reinstalled libwacom (0.6-1 -> 0.6-1)
[2012-07-28 10:05] Running 'pacman -U
/tmp/yaourt-tmp-jj/PKGDEST.opX/xf86-input-wacom-git-20120728-1-x86_64.pkg.tar.xz'
[2012-07-28 10:05] removed xf86-input-wacom (0.16.0-1)
[2012-07-28 10:05] installed xf86-input-wacom-git (20120728-1)
[2012-07-28 10:13] removed xf86-input-wacom-git (20120728-1)
[2012-07-28 10:13] installed xf86-input-wacom (0.16.0-1)

Kernel updates:

[2012-07-17 19:55] upgraded linux (3.4.4-3 -> 3.4.5-1)
[2012-07-20 19:29] upgraded linux (3.4.5-1 -> 3.4.6-1)
[2012-07-23 16:11] upgraded linux (3.4.6-1 -> 3.5-1)
[2012-07-30 14:53] upgraded linux (3.5-1 -> 3.4.6-1) //downgradetest
[2012-07-30 15:00] upgraded linux (3.4.6-1 -> 3.5-2)

The day it stopped working was 2012-07-23 I think (I rebooted cause of
new kernel, dunno the uptime till then).


I already figured a couple of things out:

No difference between Kernel 3.4.6 and 3.5 (this was my first guess).
My device USB id: 056a:0094 is mentioned nowhere: neither in libwacom,
modinfo wacom, or on any serious documentation on the internet.
No driver is loaded for the device (as the id is missing in modinfo), so
i tried to manually assign it with

# echo "056a 0094" > /sys/bus/usb/drivers/wacom/new_id

but this didn't help. Next thing i might want to try is downgrade
xf86-input-wacom, but that wouldn't add the usbid to the kernel module.

Maybe these are related errors:
http://lists.debian.org/debian-kernel/2012/06/msg00869.html
http://lists.debian.org/debian-kernel/2012/06/msg00430.html

Other users (https://bbs.archlinux.org/viewtopic.php?id=119332) have a
different usb id for their tablet: 056a:00e6, maybe my tablet's firmware
is messed up and reports a different usbid from now.

I would appreciate any help for getting the tablet to work again, i need
it for university (ok, holidays for next 2 months).


tl;dr X220t Tablet no longer working after updates, usbid listed
nowhere, downgrading kernel doesn't fix -> help please


Cheers,

Jonas



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Favux ...]

Hi Jonas,

That's a known kernel bug.  See this linuxwacom-discuss thread:
http://sourceforge.net/mailarchive/forum.php?thread_name=4FE7F002.8000802%40ugcs.caltech.edu&forum_name=linuxwacom-discuss

I took a quick peek at linux-input and didn't see the patch Ping
mentioned yet, but might have missed it.

Since I don't know where the bug is I'm not sure if trying input-wacom
is a reasonable idea or not.

Favux

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Jason G.]

On Mon, Jul 30, 2012 at 7:59 PM, Favux ... <favux.is@...> wrote:

> Hi Jonas,
>
> That's a known kernel bug.  See this linuxwacom-discuss thread:
> http://sourceforge.net/mailarchive/forum.php?thread_name=4FE7F002.8000802%40ugcs.caltech.edu&forum_name=linuxwacom-discuss
>
> I took a quick peek at linux-input and didn't see the patch Ping
> mentioned yet, but might have missed it.
>
> Since I don't know where the bug is I'm not sure if trying input-wacom
> is a reasonable idea or not.
>
> Favux
>

I believe Ping rolled the fix in with her sync to Dmitry's 'next'
branch (commit 04ada808). Building/installing input-wacom 0.14 should
do the trick.

If you want to stick with the AUR though, you might try the
wacom-linux-git[1] package. From what I can tell, that should have the
fix as well. If it doesn't, you can try wacom-mainline-linux-git[2] or
wacom-next-linux-git[3] -- these are just based on less stable (but
more current) branches of the upstream driver.

[1] http://aur.archlinux.org/packages.php?ID=55439
[2] http://aur.archlinux.org/packages.php?ID=55441
[3] http://aur.archlinux.org/packages.php?ID=55440

Jason

---
Day xee-nee-svsh duu-'ushtlh-ts'it;
nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it.
Huu-chan xuu naa~-gha.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Ping Cheng-2]

Hi Jonas,

056a:0094 has never been supported by this project. I am not sure
which kernel driver your device was using when it was working. The
LENOVO X220t supported by the community is 056a:00e6. I do not have
the tablet specs for LENOVO systems. So, I am not sure why your id is
0094. Your guess of malfunction firmware might be right.

Let's first make sure your system is not in firmware update mode. I
don't see how it could be. But, just in case, please

Turn off your computer. Disconnect power and take the battery out. Let
the system sit for a while, say a few minutes. This will reset any
commands left on your system.

Then start your system and check dmesg to see if your device is
listed. You can use "dmesg | grep 056a" to see all Wacom devices in
your system.

Meanwhile, if your are curious, you can update your kernel driver from
input-wacom or linux-wacom-git to see if the driver gives you anything
new.

Ping

On Mon, Jul 30, 2012 at 7:12 PM, Jonas Jelten <jelten@...> wrote:

> Hi list!
>
> After updating packages and rebooting 1 week ago, my integrated Wacom
> tablet ISDv4 (pen and touch) (056a:0094) no longer works.
> Laptop: LENOVO X220t 4296CTO/4296CTO, BIOS 8DET61WW (1.31 ) 04/25/2012
> Arch Linux x86_64, testing
>
> Things that got updated and had to do with wacom:
>
> [2012-01-17 08:37] upgraded xf86-input-wacom (0.12.0-1 -> 0.13.0-1)
> [2012-02-12 12:21] upgraded xf86-input-wacom (0.13.0-1 -> 0.13.0-2)
> [2012-03-10 18:28] upgraded xf86-input-wacom (0.13.0-2 -> 0.14.0-1)
> [2012-04-01 22:15] installed libwacom (0.4-1)
> [2012-04-14 14:12] upgraded xf86-input-wacom (0.14.0-1 -> 0.14.0-2)
> [2012-05-13 14:35] upgraded xf86-input-wacom (0.14.0-2 -> 0.15.0-1)
> [2012-07-03 02:40] upgraded libwacom (0.4-1 -> 0.6-1)
> [2012-07-13 09:03] upgraded xf86-input-wacom (0.15.0-1 -> 0.16.0-1)
> [2012-07-23 19:10] reinstalled xf86-input-wacom (0.16.0-1 -> 0.16.0-1)
> [2012-07-25 03:40] reinstalled libwacom (0.6-1 -> 0.6-1)
> [2012-07-28 10:05] Running 'pacman -U
> /tmp/yaourt-tmp-jj/PKGDEST.opX/xf86-input-wacom-git-20120728-1-x86_64.pkg.tar.xz'
> [2012-07-28 10:05] removed xf86-input-wacom (0.16.0-1)
> [2012-07-28 10:05] installed xf86-input-wacom-git (20120728-1)
> [2012-07-28 10:13] removed xf86-input-wacom-git (20120728-1)
> [2012-07-28 10:13] installed xf86-input-wacom (0.16.0-1)
>
> Kernel updates:
>
> [2012-07-17 19:55] upgraded linux (3.4.4-3 -> 3.4.5-1)
> [2012-07-20 19:29] upgraded linux (3.4.5-1 -> 3.4.6-1)
> [2012-07-23 16:11] upgraded linux (3.4.6-1 -> 3.5-1)
> [2012-07-30 14:53] upgraded linux (3.5-1 -> 3.4.6-1) //downgradetest
> [2012-07-30 15:00] upgraded linux (3.4.6-1 -> 3.5-2)
>
> The day it stopped working was 2012-07-23 I think (I rebooted cause of
> new kernel, dunno the uptime till then).
>
>
> I already figured a couple of things out:
>
> No difference between Kernel 3.4.6 and 3.5 (this was my first guess).
> My device USB id: 056a:0094 is mentioned nowhere: neither in libwacom,
> modinfo wacom, or on any serious documentation on the internet.
> No driver is loaded for the device (as the id is missing in modinfo), so
> i tried to manually assign it with
>
> # echo "056a 0094" > /sys/bus/usb/drivers/wacom/new_id
>
> but this didn't help. Next thing i might want to try is downgrade
> xf86-input-wacom, but that wouldn't add the usbid to the kernel module.
>
> Maybe these are related errors:
> http://lists.debian.org/debian-kernel/2012/06/msg00869.html
> http://lists.debian.org/debian-kernel/2012/06/msg00430.html
>
> Other users (https://bbs.archlinux.org/viewtopic.php?id=119332) have a
> different usb id for their tablet: 056a:00e6, maybe my tablet's firmware
> is messed up and reports a different usbid from now.
>
> I would appreciate any help for getting the tablet to work again, i need
> it for university (ok, holidays for next 2 months).
>
>
> tl;dr X220t Tablet no longer working after updates, usbid listed
> nowhere, downgrading kernel doesn't fix -> help please
>
>
> Cheers,
>
> Jonas
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Linuxwacom-devel mailing list
> Linuxwacom-devel@...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Jonas Jelten]

> 056a:0094 has never been supported by this project. I am not sure
> which kernel driver your device was using when it was working. The
> LENOVO X220t supported by the community is 056a:00e6. I do not have
> the tablet specs for LENOVO systems. So, I am not sure why your id is
> 0094. Your guess of malfunction firmware might be right.

It definitely worked before, but can't find an old lsusb log for the id.
How can i restore the firmware?
And how can i install digitizer_update_fwdigi01.exe and does this even
help under linux, or is this already integrated into the wacom-driver?

> Let's first make sure your system is not in firmware update mode. I
> don't see how it could be. But, just in case, please
>
> Turn off your computer. Disconnect power and take the battery out. Let
> the system sit for a while, say a few minutes. This will reset any
> commands left on your system.

Did that, but i'm afraid it didn't help.

> Then start your system and check dmesg to see if your device is
> listed. You can use "dmesg | grep 056a" to see all Wacom devices in
> your system.

Nothing listed here, but lsusb is as follows:
$ lsusb -d 056a:
Bus 002 Device 003: ID 056a:0094 Wacom Co., Ltd

But:
$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
        |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
        |__ Port 3: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
        |__ Port 4: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
        |__ Port 4: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M
        |__ Port 4: Dev 5, If 2, Class=Vendor Specific Class, Driver=, 12M
        |__ Port 4: Dev 5, If 3, Class=Application Specific Interface,
Driver=, 12M
        |__ Port 6: Dev 6, If 0, Class=Video, Driver=uvcvideo, 480M
        |__ Port 6: Dev 6, If 1, Class=Video, Driver=uvcvideo, 480M


the tablet is completely missing...

> Meanwhile, if your are curious, you can update your kernel driver from
> input-wacom or linux-wacom-git to see if the driver gives you anything
> new.


I don't think this will help as the usb id will most likely stay wrong.

So what do you think should i do next? Contact Lenovo so they tell me
"install windows"?

Cheers,

Jonas




------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Jonas Jelten]

Ok, tablet working now again...

What i did:

Install wacom-udev (from Arch-AUR) and added to 10-wacom.conf:

ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0094",
SYMLINK="input/tablet-tpc-e6-$env{WACOM_TYPE}"

my idea was to treat the tablet as an ISD-V4 even the usbid was different.

After a reboot, it still had 056a:0094. Then i removed the udev rules,
rebooted again. Nothing changed. Then, to experiment with this issue
https://bbs.archlinux.org/viewtopic.php?pid=1144732
I rebooted to a live-Xubuntu 12.04. Also here the tablet was 0094.

Last thing i did reboot to archlinux again, and suddenly the id is
056a:00e6
and everything works again as it should.

I really do not understand what happened there..

Cheers,
Jonas



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Wataru Sakurai]

Hi Jonas,

I had the same problem. my tablet's product id is 0094 before I know,
and Tablet not working.

So, I built linux kernel 3.6-rc1 and boot it, then the problem is resolved.
Please don't do "reboot", do power off ( "shutdown" ) and next do power on.
Now I can use stylus, eraser, and touch. tablet's product id is 00E6.

My environment is below:
PC: Thinkpad X220 tablet ( don't update the firmware )
distribution : Gentoo Linux 10.1
linux kernel:
    trouble ocurred:  3.5, 3.5.1
    touble resolved: 3.6-rc1
Xorg server: 1.12.3
xf86-input-wacom: 0.15.0

---
Wataru Sakurai : wataru@...
http://www.aoisakura.jp

On Sat, 11 Aug 2012 03:35:58 +0200
Jonas Jelten <jelten@...> wrote:

>
> > 056a:0094 has never been supported by this project. I am not sure
> > which kernel driver your device was using when it was working. The
> > LENOVO X220t supported by the community is 056a:00e6. I do not have
> > the tablet specs for LENOVO systems. So, I am not sure why your id is
> > 0094. Your guess of malfunction firmware might be right.
>
> It definitely worked before, but can't find an old lsusb log for the id.
> How can i restore the firmware?
> And how can i install digitizer_update_fwdigi01.exe and does this even
> help under linux, or is this already integrated into the wacom-driver?
>
> > Let's first make sure your system is not in firmware update mode. I
> > don't see how it could be. But, just in case, please
> >
> > Turn off your computer. Disconnect power and take the battery out. Let
> > the system sit for a while, say a few minutes. This will reset any
> > commands left on your system.
>
> Did that, but i'm afraid it didn't help.
>
> > Then start your system and check dmesg to see if your device is
> > listed. You can use "dmesg | grep 056a" to see all Wacom devices in
> > your system.
>
> Nothing listed here, but lsusb is as follows:
> $ lsusb -d 056a:
> Bus 002 Device 003: ID 056a:0094 Wacom Co., Ltd
>
> But:
> $ lsusb -t
> /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>     |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
>         |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=, 12M
> /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/3p, 480M
>     |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
>         |__ Port 3: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
>         |__ Port 4: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
>         |__ Port 4: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M
>         |__ Port 4: Dev 5, If 2, Class=Vendor Specific Class, Driver=, 12M
>         |__ Port 4: Dev 5, If 3, Class=Application Specific Interface,
> Driver=, 12M
>         |__ Port 6: Dev 6, If 0, Class=Video, Driver=uvcvideo, 480M
>         |__ Port 6: Dev 6, If 1, Class=Video, Driver=uvcvideo, 480M
>
>
> the tablet is completely missing...
>
> > Meanwhile, if your are curious, you can update your kernel driver from
> > input-wacom or linux-wacom-git to see if the driver gives you anything
> > new.
>
>
> I don't think this will help as the usb id will most likely stay wrong.
>
> So what do you think should i do next? Contact Lenovo so they tell me
> "install windows"?
>
> Cheers,
>
> Jonas
>
>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Jan Alexander Steffens]

On Sat, Aug 11, 2012 at 5:24 PM, Wataru Sakurai <wataru@...> wrote:
> Hi Jonas,
>
> I had the same problem. my tablet's product id is 0094 before I know,
> and Tablet not working.
>
> So, I built linux kernel 3.6-rc1 and boot it, then the problem is resolved.
> Please don't do "reboot", do power off ( "shutdown" ) and next do power on.
> Now I can use stylus, eraser, and touch. tablet's product id is 00E6.

Is there a particular commit in 3.6 that fixes it?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Favux ...]

I think I need to expand on my original reply on this thread.

Rafi Rubin encountered the same ID change, see my original post for link.

To answer my own question the patch set isn't in input-wacom yet
because the last Dmitry next merge by Ping was  from 6-12-12 and the
patch set was after that.

Patch set explanation and two replies including Rafi's test:
http://www.spinics.net/lists/linux-input/msg21303.html
Patch set:
http://www.spinics.net/lists/linux-input/msg21304.html
http://www.spinics.net/lists/linux-input/msg21305.html
http://www.spinics.net/lists/linux-input/msg21306.html
http://www.spinics.net/lists/linux-input/msg21307.html

My assumption was this patch set also fixes the ID problem(a fall
through?).  Because Rafi reported it fixed his digitizer and he had
the same ID change.  It is just not obvious that fixing the ID is what
this patch set does but I don't see another patch that does do that so
I think this is what you need.

If you don't want to patch you can get the source code from Przemo's
Wacom-kernel Repository:
http://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Wacom-kernel_Repository

Then you'll need to substitute the wacom.h, wacom_wac.h, wacom_sys.c,
and wacom_wac.c you obtain for the ones in your kernel source code
before compiling the wacom.ko module:
make -C/lib/modules/`uname -r`/build M=`pwd` modules

sudo cp wacom.ko /lib/modules/`uname -r`/kernel/drivers/input/tablet/


Or it might be simpler to do that in input-wacom's 2.6.38 folder and
use its Makefiles.  You may want to make a dkms.

Good luck.

Favux

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Jan Alexander Steffens]

On Sat, Aug 11, 2012 at 8:32 PM, Favux ... <favux.is@...> wrote:

> I think I need to expand on my original reply on this thread.
>
> Rafi Rubin encountered the same ID change, see my original post for link.
>
> To answer my own question the patch set isn't in input-wacom yet
> because the last Dmitry next merge by Ping was  from 6-12-12 and the
> patch set was after that.
>
> Patch set explanation and two replies including Rafi's test:
> http://www.spinics.net/lists/linux-input/msg21303.html
> Patch set:
> http://www.spinics.net/lists/linux-input/msg21304.html
> http://www.spinics.net/lists/linux-input/msg21305.html
> http://www.spinics.net/lists/linux-input/msg21306.html
> http://www.spinics.net/lists/linux-input/msg21307.html
>
> My assumption was this patch set also fixes the ID problem(a fall
> through?).  Because Rafi reported it fixed his digitizer and he had
> the same ID change.  It is just not obvious that fixing the ID is what
> this patch set does but I don't see another patch that does do that so
> I think this is what you need.
>
> If you don't want to patch you can get the source code from Przemo's
> Wacom-kernel Repository:
> http://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Wacom-kernel_Repository
>
> Then you'll need to substitute the wacom.h, wacom_wac.h, wacom_sys.c,
> and wacom_wac.c you obtain for the ones in your kernel source code
> before compiling the wacom.ko module:
> make -C/lib/modules/`uname -r`/build M=`pwd` modules
>
> sudo cp wacom.ko /lib/modules/`uname -r`/kernel/drivers/input/tablet/
>
>
> Or it might be simpler to do that in input-wacom's 2.6.38 folder and
> use its Makefiles.  You may want to make a dkms.
>
> Good luck.
>
> Favux

Tried those patches on 3.5.1. No luck.

dmesg of that boot: http://sprunge.us/HajV

As you can see (if you grep for "wacom" or the device number,
"2-1.5"), the digitizer is initially recognized.
However, something happens that causes the digitizer to disconnect
from the bus, subsequently reconnecting as a new device that is not
recognized.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Favux ...]

All I see in the dmesg is after the:
[   18.410146] input: Wacom ISDv4 E6 Pen as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input7
[   18.414956] input: Wacom ISDv4 E6 Finger as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input8
[   18.415622] usbcore: registered new interface driver wacom

is  the usb 2.0 ehci_hcd (Enhanced Host Controller Interface) having
its power state modified.  I'm not seeing the disconnection or
re-connection as a new device.  Am I missing that?

Does Xorg.0.log show anything?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Jan Alexander Steffens]

On Sun, Aug 12, 2012 at 1:05 AM, Favux ... <favux.is@...> wrote:

> All I see in the dmesg is after the:
> [   18.410146] input: Wacom ISDv4 E6 Pen as
> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input7
> [   18.414956] input: Wacom ISDv4 E6 Finger as
> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input8
> [   18.415622] usbcore: registered new interface driver wacom
>
> is  the usb 2.0 ehci_hcd (Enhanced Host Controller Interface) having
> its power state modified.  I'm not seeing the disconnection or
> re-connection as a new device.  Am I missing that?
>
> Does Xorg.0.log show anything?

[    2.461144] usb 2-1.5: new full-speed USB device number 3 using ehci_hcd
[   18.538446] usb 2-1.5: USB disconnect, device number 3
[   19.745315] usb 2-1.5: new full-speed USB device number 4 using ehci_hcd

This all happens before X starts. No wacom stuff in the X log.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Favux ...]

Thanks.  So you're saying it reads;

[    2.461144] usb 2-1.5: new full-speed USB device number 3 using ehci_hcd
[   18.410146] input: Wacom ISDv4 E6 Pen as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input7
[   18.414956] input: Wacom ISDv4 E6 Finger as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input8
[   18.415622] usbcore: registered new interface driver wacom
[   18.538446] usb 2-1.5: USB disconnect, device number 3

[   19.745315] usb 2-1.5: new full-speed USB device number 4 using ehci_hcd

And now you see the ID change from 0xe6 to 0x94.  No clue.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Favux ...]

Hi Rafi,

Sorry to bother you.  But we were wondering how you dealt with the ID
change from 0xe6 to 0x94 on your ThinkPad X220t?

Thanks in advance.

Favux

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Rafi Rubin]

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

On 08/11/12 19:49, Favux ... wrote:
> Hi Rafi,
>
> Sorry to bother you.  But we were wondering how you dealt with the ID
> change from 0xe6 to 0x94 on your ThinkPad X220t?

No trouble.  One of Ping's patch sets fixed it.  I think those patches made it
into 3.6.0-rc1, but will have to check.

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

iQIcBAEBAgAGBQJQJvbSAAoJEPILXytRLnK28GcQAI4iMZDZla3KhK1M58sJLV1z
3Q3fm6nrgHdKgqrrVrvfMiIksNsZ9ZBqzCvD9eAzvbHSGsNHCNFnHrcEIV0NYW37
w0MGDaH7OkODfI/DgcR2IuVJLgKa80H7to4Fyqjz3gIfG8wp/po817dvm+MsKEaC
cTgh3s1+IEPHKZ0Ph9G4tJNmXL1SnJhYFraubPrUBB6DpxprwQ0/BW7B/DsJA6qF
5hv0z5gUwJWAe4QGiVxx57veWJujJ+2sfV4VgB1uP4rlktBlYxpSXi42Smd8bvlD
cN7FZBiS9QndmpQwTlPPvS2QX1Il4+8mhecMzN623qYhZkyKFsXiQlAi9kH1114r
0l0zm0VlQ7zqsj8uI5kONqSaZXnv5lAmxOAcRlOYME5mDQ5cG7G4R14q4NYYAtDd
g6uUSn2Ywzw+8Zv7vs342lIGFSBAM4Cr3/La5je+E+9EFdyKGnqk1qOwzFvYqft5
863OoEY1knU1XV0abdP81fw6NaUK9+lbJhsvaQ0daW5xxwhzIeBP/Wc+dQGm5dKu
3y9gwYcdIFx/UoaHpSMFJPGMbSegyPQbSsxf1Oz7J1tu3FS4D87OtrHiZ2yrNWdM
f+l8ciEnG4tvb+wF8rzOPDwe5+RZpX2Bf+sv8CpI0Awrt5KXdtAhHDako4lncT15
Ha6IwXRLw8CbA3X0KbKr
=ZBKd
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Rafi Rubin]

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

On 08/11/12 20:20, Rafi Rubin wrote:
> No trouble.  One of Ping's patch sets fixed it.  I think those patches made
> it into 3.6.0-rc1, but will have to check.

There were four patches in the set I tested (that fixed the problem).

Commits:
adad004e1a50f8c64d9f116cd4934da937b51e27
6795a524f0b049ceb5417d5036ab5e233345b900
61c91dd4a58b21a783e37208f4d02e3cb4b637c4
1cecc5cc0658e128bcad0b29edb96f286066571d

I can confirm they are all in 3.6-rc1, and that it does in fact the rc works fine.

Now I get to find out if the other bugs that were keeping me at 3.5.0 have
been fixed yet :)

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

iQIcBAEBAgAGBQJQJwI/AAoJEPILXytRLnK2eIMP/iC9ECfKnu/CwU0s1COfSNVG
pXEGskB/1TS/M2lV6OzvXFBPooBN1IblB7O2vh4YuZG8bIeYE2y33XPPERLMMRJ6
a61bxsubyB5SNHklyNMciCraasi9nieTLWwCAs/Xe6Lgep7iOq3Vs4dz49a6GeoF
MAMorYp9ulRVATw+J8E0JbU/WrKoYb+sBSzHnnfwUgtZHVazyl5AdvMF8HdvCGzf
72N4vQ6VdT0aUrzKfU7ZtsFqrQ2kvMfePmHEvmGnnbbH3Jcy/fDKzclqcX0ONfSM
7LvraLEIvA2IlzXf7Tkx/C0RVvYEEeIShWyNWXyQ65I+hEbk1/p97/dJqlBM28PJ
EWZh/ePhi02TY7PjamKLFKG0177nBe6C1t2FTnwXudPKtxd3eKxRQLg6BoIGCJGR
RAR5N1mUt9goDL+s4IBarCXNwrYZ2hgYHswBWVHBTuGQRMtzNTes2P81tCDfl6Pz
FMefsBGIMW4yrZXFbB6RihwLViXtF5AtnOQknr+h+w5tT2ceBDcb8yUK/zpGkk3R
6I3YI7/ak8zQzkUtJ3qZMoRFS4WPHCsUhSxLR1V7TvzONm0xQRG38gQOAXWzMWbg
FTXbCzrKq4ALBBiGQX26KbyXoFOFw4+QbcuYMmpKfsAb56/VVv1WXjR+8Wg2opN/
lO9FmR4Lwd1PIhjuhw+H
=HMjz
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Jan Alexander Steffens]

On Sun, Aug 12, 2012 at 3:09 AM, Rafi Rubin <rafi@...> wrote:

> There were four patches in the set I tested (that fixed the problem).
>
> Commits:
> adad004e1a50f8c64d9f116cd4934da937b51e27
> 6795a524f0b049ceb5417d5036ab5e233345b900
> 61c91dd4a58b21a783e37208f4d02e3cb4b637c4
> 1cecc5cc0658e128bcad0b29edb96f286066571d
>
> I can confirm they are all in 3.6-rc1, and that it does in fact the rc works fine.
>
> Now I get to find out if the other bugs that were keeping me at 3.5.0 have
> been fixed yet :)

My current kernel (based on 3.5.1) contains all those patches, yet
displays the problem.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Favux ...]

Thanks a lot Rafi!

Those are the 4 patches I thought we needed.

I may be reading this wrong but I only see 2 of the 4 patches in 3.5.1:
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fstable%2Flinux-stable.git&a=search&h=HEAD&st=author&s=Ping+Cheng
They all appear to be in 3.6.rc1:
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git&a=search&h=HEAD&st=commit&s=Ping+Cheng

http://kernel.org/

So the Wacom-kernel repository may not be quite up to date enough.

Favux

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Ping Cheng-2]

On Sat, Aug 11, 2012 at 6:37 PM, Favux ... <favux.is@...> wrote:
> Thanks a lot Rafi!
>
> Those are the 4 patches I thought we needed.
>
> I may be reading this wrong but I only see 2 of the 4 patches in 3.5.1:
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fstable%2Flinux-stable.git&a=search&h=HEAD&st=author&s=Ping+Cheng
> They all appear to be in 3.6.rc1:
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git&a=search&h=HEAD&st=commit&s=Ping+Cheng

These two patches are the ones that fix the 0xE6 issue in the driver.
The other two patches were preparing for future development, which do
not affect 0xE6. Since the PID change happened outside of the driver,
I suspect there are other issues in the kernel/input subsystem that
need to be addressed. 3.5.1 itself might be unstable.

Sorry for not replying to Favux' earlier post about the status of
input-wacom. The 0xE6 fix was backported along with Dmitry's next
branch of June 12. My commit comments had an typo though "Add fix 0xE6
bug" should be "And fix 0xE6 bug".

Ping

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[Peter Hutterer-3]

On Sat, Aug 11, 2012 at 05:56:33PM +0200, Jan Steffens wrote:

> On Sat, Aug 11, 2012 at 5:24 PM, Wataru Sakurai <wataru@...> wrote:
> > Hi Jonas,
> >
> > I had the same problem. my tablet's product id is 0094 before I know,
> > and Tablet not working.
> >
> > So, I built linux kernel 3.6-rc1 and boot it, then the problem is resolved.
> > Please don't do "reboot", do power off ( "shutdown" ) and next do power on.
> > Now I can use stylus, eraser, and touch. tablet's product id is 00E6.
>
> Is there a particular commit in 3.6 that fixes it?

bringing this up late, but still:
I suspect this may be a hardware issue. I had this same issue for a while
and after digging into this today it doesn't seem to be related to a kernel
version. I even downgraded to an older kernel

$> uname -r
3.3.4-5.fc17.x86_64

rebooting, etc. didn't work. Powering off, waiting a few secs and starting
it up again worked (with that kernel above).

Cheers,
   Peter

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel