wacom tablet stops working using new kernel

[Andcor]

Binary package hint: linux-image-2.6.27-11-generic

I've just reinstalled my tablet device at exact the same day as a new kernel became available (i think). Then, after installing the ubuntu base system, I made a apt-get update and a apt-get dist-upgrade. Here I got the kernel version 2.6.27.11 where the base system came with 2.6.27.7, and in the new kernel my wacom device doesn't work and just causes xorg to crash and go into failsafe mode.

I can't find any wacom related lines in /var/log/syslog but I found a single line in my Xorg.0.log:

(**) Option "FlowControl" "Xoff"
usbDetect: can not ioctl version
(==) Wacom using pressure threshold of 15 for button 1

I've attached both my xorg.conf and my Xorg.0.log

[Andcor (corneliussen)]

I've, by the way, also written about the bug here: http://ubuntuforums.org/showthread.php?p=6655982#post6655982

[Bruno Ranieri (mail-bruno-ranieri)]

I have the same problem here with an IBM/Lenovo X60tablet.

Option "ForceDevice" "ISDV4"

in the xorg.conf force X into failsafe. Omitting this option leaves the wacom pen not working.

Skipping the hole wacom config from xorg.conf and hoping for hal gives:

(WW) config/hal: no driver or path specified for /org/freedesktop/Hal/devices/pnp_WACf004

output of lshal is attached.

The current workaround is to use kernel 2.6.27-9-generic.

[Andcor (corneliussen)]

It should be said that the tablet PC I own also is a Lenovo x60 tablet. But
it is very irretatating that you cannot use the latest kernel.

[Stefan Bader (smb)]

Sorry for the late response to this. I just checked the wacom driver between 2.6.27-9.19 and now and that does not seem to have changed. So, this might be a side effect from something else. Could you please attach the dmesg output for the old and new kernel?
Another thing you could try is to enable my PPA which contains a version of the current proposed kernel. This will also install aside of the current kernels, so it is always possible to load the old kernel again. My PPA can be found at: https://launchpad.net/~stefan-bader-canonical/+archive/ppa
Please let me know whether the new kernel works better or the contents of the dmesg. Thanks

[Stefan Bader (smb)]

Waiting for feedback

[Andcor (corneliussen)]

Sorry, didn't see that you have written anything. I just thought you had updated the status a number of times. Here is the dmesg outputs for both kernels

[Andcor (corneliussen)]

By the way, I've tried the kernel in your PPA, and that has exactly the same problem as the other one.

[Stefan Bader (smb)]

Thanks, for testing Andcor. I will try to have a look at the dmesg output later to see whether this reveals anything.

[Andcor (corneliussen)]

Great, you just write if you need something else tested. I will try to
do it faster next time.

[Stefan Bader (smb)]

Unfortunately, from the logs there is really nothing special to note (except the hdaps driver, but that is completely unrelated). Even the Xorg log looks like there is something found. From lshal I take it that this is just a device attached to some serial port. Both kernel dmesg show ttyS0 and ttyS1 found, so I wonder whether this is a kernel related problem.

[Stefan Bader (smb)]

Timo, is there something we can do to debug this? What packages would include the tablet driver part, so we could compare there versions?

[Timo Aaltonen (tjaalton)]

if it's the xserver crashing, getting a proper backtrace would be nice:

http://wiki.ubuntu.com/X/Backtracing

there's also bug 325101 which looks similar, but happened after upgrading to jaunty.

[Stefan Bader (smb)]

I am setting this back to incomplete. Timo suggested some X backtrace and from the kernel side I currently cannot see a real handle to grasp. It looks like a generic serial attachment and the kernel seems to know nothing more about that.

[Stefan Bader (smb)]

I am closing this as won't fix for the kernel as I do not really see a kernel issue with this and there has been no response for quite some time. If the problem persists and you can provide a backtrace of the xserver crash, please reopen.