This is the latest in my series of “I spent so long searching on google for this, trawling through out of date nonsense to eventually twig the right answer to this problem” blog posts.

If you are running Ubuntu linux 7.10 (also known as Gutsy Gibbon) and are trying to get the Wacom tablet functions of an HP 2710p tablet to work, then hopefully you won’t waste about 6 hours trying. Or if you’re lucky, you also spend 6 hours of your employer’s time trying to figure it out, and it won’t seem so bad. Ahem.

Alternatively, to get the digitizer working quickly, simply edit the xorg configuration by running “sudo nano /etc/X11/xorg.conf”, scroll down to the bottom, and where it says “Uncomment if you have a Wacom tablet” simply remove the # signs from the next three lines. It’s really that easy. I would say annoyingly easy.

Maybe you followed all the other stuff and got as far as trying to run “wacdump -f c100 /dev/ttyS0″ or “wacdump -f c100 /dev/input/wacom” or “wacdump -f c100 /dev/event0″ but they are all wrong. Variations on the wacdump theme might get you “WacomOpenTablet: Connection timed out” but that’s a red herring too. It’s actually “wacdump -f tpc /dev/input/wacom”, and you don’t actually need to setserial or compile tc1100ts.c or anything else. Hopefully the Ubuntu guys will figure out how to detect that there’s a Wacom tablet and do the uncommenting automagically for Hardy or later, but if not perhaps this’ll help. I’ve no idea if this will help for Fedora or SuSE or anything else, but if it does, feel free to let everyone know in the comments.

Update: Hardy 8.04

For anyone who is trying on Hardy, it works fine too. At the time of writing you just have to copy some stuff into /etc/X11/xorg.conf and restart the X server. No recompilation or anything like that. Add three more input devices, and then add the activation within the section ServerLayout. So actually marginally more difficult than it was in Gutsy, since the code used to be there ready and waiting.

Section “InputDevice”
Driver “wacom”
Identifier “stylus”
Option “Device” “/dev/input/wacom”
Option “Type” “stylus”
Option “ForceDevice” “ISDV4″# Tablet PC ONLY
EndSection

Section “InputDevice”
Driver “wacom”
Identifier “cursor”
Option “Device” “/dev/input/wacom”
Option “Type” “cursor”
Option “ForceDevice” “ISDV4″# Tablet PC ONLY
EndSection

Section “ServerLayout”
Identifier “Default Layout”
Screen “Default Screen”
InputDevice “Synaptics Touchpad”
InputDevice “stylus” “SendCoreEvents”
InputDevice “cursor” “SendCoreEvents”
InputDevice “eraser” “SendCoreEvents”
EndSection

(or how I learned to stop worrying and trust my instincts)

I use wikis a fair amount nowadays, and I get used to just being able to update things that are wrong. Unfortunately, a lot of info on the web is still in forums and suchlike, which aren’t quite suited to collaborative documentation. For that, we still have to rely on many people writing their own documentation, and let google filter out the right one.

For instance, I was trying to install freenx on ubuntu dapper today. This thread seems to be widely acknowledged as the definitive guide to setting it up, but it just smelled a bit to complicated to me. A bit more hunting around, and I found this guide, which is a lot more straightforward (and just as importantly, worked fine). But even then, it’s not quite right – the URL for the repository seems suspiciously unofficial. So I found this list of mirrors, which is on a wiki, but isn’t part of any install guide.

Don’t underestimate how hard it is to write good documentation – it needs to be minimalistic as well as comprehensive. But today’s lesson is that if something seems more complicated than it needs to be, it probably is. Oh, and I wish freenx was in dapper by default, but I’m not sure that anyone is working on it.

I like Linux a lot, and I think the sentiments in this article are pretty much spot on. But seriously, look at the graph on the front page. Can anyone really keep a straight face during a board meeting with a projected growth like that? A quite-blatantly levelling off turning into a doubling just because you can squiggle the axis? Anyhoo, I’m sure that linux’s natural level will be a bit higher than a measley 3%. Eventually.