Missing Wacom support

I can confirm this. The problem is that the wacom_drv.o file is installed under /usr/X11R6/lib/modules/input where it really belongs under /usr/lib/xorg/modules/input. I made a symlink and my wacom started working again.

The symlink made _a_ difference, but not much. X still doesn't detect events (maybe because it's a graphire4 and the driver is so old it doesn't know about that...)

Please get the latest version of this driver.

Sorry, I did not find this bug when I searched earlier, so someone can go ahead and mark bug #32574 as a duplicate.

I am running Dapper Flight 3 +the latest updates.

I have checked and my /usr/X11R6/lib directory does not contain a modules subdirectory, so that fix will not work for me.

I'm using a USB Graphire3 tablet, and Xorg will recognize it as a simple mouse like cursor...but that's about it. According to my var log for X, it can not find the "wacom" driver at all, even though the kernel and wacdump are finding it and reporting it to be working properly.

Clearly the issue has something to do with the fact that the drivers are so incredibly out of date. I checked and the 0.6.6 driver that comes with Dapper was released in 2004! The latest stable driver from the LinuxWacom project is 0.7.2 and it was released in December of 2005, so it was available long before the upstream freeze this past month. Please consider updating this before the final release guys or Ubuntu 6.04 won't look very dapper after all :(

The wacom xorg driver was depreached in xorg 7.0 (see http://wiki.x.org/wiki/DeprecatedInX11R7).

Because of this, there must be an alternative package of the xorg driver component. I managed to get my tablet recognised by copying the old xorg driver to the right location, but this is not a real option. There were many problems such as click- and movement events not appearing, wrong mapping of the screen space to the tablet space and the touchpads freezing the whole input system (mouse, keyboard and tablet). All of these problems were, more or less, taken care of in the newest driver from the linuxwacom project.

Also, since the latest kernel update (2.6.15-16-686) there is a problem with the loading order of kernel modules. The tablet is only recognised as a simple mouse device through usbhid. To make the kernel aware of the tablet functions, the "wacom" module has to be loaded before the "usbhid" module. I tested this by unloading both modules and reloading them with the "wacom" module first.

Unfortunately i don't know the right way to get those modules properly ordered at boottime.

What is the news on this? I'm getting a Graphire 4 now and it seems there is a suitable driver on the linuxwacom homepage (http://linuxwacom.sourceforge.net/). I would really, really be thankful to whoever enables me to use it in Ubuntu. =)

So it's past feature freeze now. Does that mean there won't be any wacom support in dapper? (That would be a step back from breezy which had [buggy] wacom support)

See also bug #4773 https://launchpad.net/distros/ubuntu/+source/wacom-tools/+bug/4773

Just to give some feedback on this,

i did a fresh install of Dapper Flight5, installed wacom-tools from the repros to get the wacom symlink in /dev/input/, copied the already compiled version of the xorg driver (wacom_drv.so in the prebuilt directory) from the linuxwacom site to /usr/lib/xorg/modules/input/, chowned the driver to root:root, chmoddet the driver -x and changed /etc/X11/xorg.conf according to the linuxwacom HOWTO.
(http://linuxwacom.sourceforge.net/index.php/howto/inputdev)
(http://linuxwacom.sourceforge.net/index.php/howto/srvlayout)

Note that in the InputDevices section in the HOWTO, the Option "Device" lines are set to /dev/ttyS# for serial devices and to /dev/input/event# for usb devices.
Because the init script in wacom-tools takes care of symlinking the right device to /dev/wacom or /dev/input/wacom, you'll just have to replace the path in the device lines in xorg and set them accordingly.

So now, after weeks of fighting with the kernel driver, the old breezy X11 driver and the new xorg driver from linuxwacom i am finally able to use my wacom tablet (yay!).

With my previous installation (breezy dist-upgraded to dapper), i was unable to get any events out of wacdump and therefore the xorg driver refused to do anything.

That said, the issue still stands. All of that shebang shouldn't be necessary and there should be an easy method for wacom users to actually use their tablet. Dapper is considered to be "enterprise-ready". I am a graphics artist in a small company with no administrator employed. A wacom tablet is as important as e.g. a mouse or a monitor for us and i know many other companies that are in the very same situation. Not being able to use a tablet more or less "out-of-the-box(tm)" simply is a no-go for Ubuntu in such coorperate environments.

Maybe there could be a new xserver-xorg-input-wacom package with an updated xorg driver from linuxwacom and a script similar to the "nvidia-glx-config" script that tages care of the necessary entries in /etc/X11/xorg.conf as stated above?

i simply want to concur what has already been said. Without a current wacom drive, one that will allow a wacom user to plug in and go, Dapper is most definately not enterpise ready!
  I too need a wacom tablet for my work, if it is not fixed in Dapper I cannot use ubuntu at all.

it affects only dapper (and it is already marked as such)

working on it.

Ok i just uploaded the new wacom-tools 0.7.2 that will also ship the Xorg driver. It will take a few hours to propagate in the archive and i am waiting for Flight6 to be released before i can change X dependendency to have it automatically installed. In the meanwhile you can test it.
The init script should be able to create the /dev/wacom symlink. If not please file a bug but it is a possible issue we are aware of.

Fabio

Thanks a lot. Dapper is really going to rock!
I'll test in in the next few days in Dapper 5.

That's really nice, but remember theres still bug 35101 which blocks wacom stuff.

Have been using since the new drivers were added, and I've experienced no problem so far ;)

Fabio Massimo Di Nitto said :
"The init script should be able to create the /dev/wacom symlink. If not please file a bug but it is a possible issue we are aware of."

For anyone interested, that is covered by Bug #40473, filled the 21 april 2006.