HOW TO: Install a LinuxWacom Kernel Driver for Tablet PC's

[oberonking]

I don't think you can do it with a .conf file in xorg.conf.d. You may be able to do it using xorg.conf, but I doubt it. I think that will only work with the Wacom driver. In wacom when doing a section you define type as stylus and that's what shows up in xinput, stylus.

you're right, don't work at all, tried to use the config with xorg.conf.d...
I try to use Option "type" "stylus"... and guess what... right, nothing happens

[Zayfox]

Got mine working, however it still decides to mess around by the fact that after I have touched the pen to the pad, it will not register me moving it unless I move it completely off and back on again.

[Favux]

Hi Zayfox,

Great! You got your Waltop tablet "working" in Lucid following Ayuthia's instructions.

Let's check that Wacom has your tablet by entering in a terminal:

xsetwacom list

If it's blank the wacom drivers don't have it and we'll want to look at the output of the xinput command below.

We can try a couple of things. Enter in a terminal:

xsetwacom set Stylus mode relative

also try:

xsetwacom set Stylus TPCButton off

But first to find out what stylus is being called enter:

xinput --list

in a terminal. Then change Stylus in the above commands to the device name that is being used in quotes or use the ID number.

[Zayfox]

I get this when I try to run the xsetwacom commands (first one is blank):

X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 143 (XInputExtension)
Minor opcode of failed request: 5 (X_SetDeviceMode)
Serial number of failed request: 15
Current serial number in output stream: 15

[Favux]

OK, what does:

xinput --list

look like?

[Zayfox]

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ HID 062a:0001 id=8 [slave pointer (2)]
⎜ ↳ WALTOP International Corp. Slim Tablet id=13 [slave pointer (2)]
⎜ ↳ Macintosh mouse button emulation id=14 [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)]
↳ Power Button id=7 [slave keyboard (3)]
↳ Lite-On Technology USB Productivity Option Keyboard( has the hub in # 1 )id=9 [slave keyboard (3)]
↳ Lite-On Technology USB Productivity Option Keyboard( has the hub in # 1 )id=10 [slave keyboard (3)]
↳ USB Keyboard id=11 [slave keyboard (3)]
↳ USB Keyboard id=12 [slave keyboard (3)]

That.

[Favux]

Alright, there it is, Waltop. My guess is Wacom isn't picking it up and so evdev is. We can look at your Xorg.0.log to check. It's in /var/log. Right click on it to compress it with Create Archive and then attach it to your post with Manage Attachments.

[Zayfox]

Thanks Favux,

Xorg.0.log is attached.

[Favux]

Hi Zayfox,

Unfortunately I was correct, Wacom isn't grabbing the tablet so it's defaulting to evdev, which is why it is funky. Your Xorg.0.log is clearer on that then oberonking's was, so I'm wondering if you had a problem implementing Ayuthia's "fix"?

The Xorg dev. at the LWP just added a patch that has a bunch of Waltop ID's for xf86-input-wacom. It hasn't been comitted yet but they are clearly planning on supporting Waltops. So all that is missing is a Waltop usb kernel driver. I don't know where that stands.

I'll have to look at what Ayuthia did to modify the wacom.ko (usb kernel driver) to support Waltop and see if there is anything else to try. Obviously I'm hoping Ayuthia will join in.

In the meantime you can try the WizardPen driver like oberonking did: http://ubuntuforums.org/showthread.php?t=1475433 I think the wacom drivers will be a better option once the kinks are worked out. And now you know to check Xorg.0.log to verify the WizardPen driver has your tablet.

[Zayfox]

Thanks Favux, I look forward to finally getting this thing working again so I can go back to my regular schedules.