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

[Zayfox]

I don't actually have an eraser with this tablet. :\
I don't know why it's registering one.

[Favux]

Sorry, I forgot. I assume that's because your tablet is being matched to a Bamboo1 which probably has a eraser on it's stylus. I don't think the spurious eraser is a problem.

OK, try thing in the 50-wacom.conf. We're going to add another snippet below the current usb one. So it looks like this:

Section "InputClass"
   Identifier "Wacom class"
   # WALTOP needs a patched kernel driver, that isn't in mainline lk yet,
   # so for now just let it fall through and be picked up by evdev instead.
   MatchProduct "Wacom|WALTOP|WACOM"
   # MatchProduct "Wacom|WACOM"
   MatchDevicePath "/dev/input/event*"
   Driver "wacom"
EndSection 

Section "InputClass"
   Identifier "Waltop ignore input/mouse2"
   MatchIsPointer "on"
   MatchDevicePath "/dev/input/mouse*"
   MatchVendor "WALTOP"
   Driver ""
EndSection

After changing reboot and cross your fingers. Again be sure to have a backup.

[Zayfox]

Seems like it won't work at all now. Not sure why.

Here's my 50-wacom.conf:

Section "InputClass"
Identifier "Wacom class"
# WALTOP needs a patched kernel driver, that isn't in mainline lk yet,
# so for now just let it fall through and be picked up by evdev instead.
MatchProduct "Wacom|WALTOP|WACOM"
# MatchProduct "Wacom|WACOM"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
EndSection

Section "InputClass"
Identifier "Waltop ignore input/mouse2"
MatchIsPointer "on"
MatchDevicePath "/dev/input/mouse*"
MatchVendor "WALTOP"
Driver ""
EndSection

Section "InputClass"
Identifier "Wacom serial class"
MatchProduct "Serial Wacom Tablet"
Driver "wacom"
Option "ForceDevice" "ISDV4"
EndSection

Section "InputClass"
Identifier "Wacom serial class identifiers"
MatchProduct "WACf|FUJ02e5|FUJ02e7"
Driver "wacom"
Option "ForceDevice" "ISDV4"
EndSection

Edit:

xsetwacom list and xinput --list still output the tablet though.

Edit 2:

Just commented your addition out and reloaded X, it still doesn't work.

[eWheeler]

Wow, Favux, amazing. I am grateful for all of your development on the Wacom drivers.

I have a CTL460 0xd1 series and just got it working on Lucid using today's git of xf86-input-wacom and linuxwacom-0.8.7-1. I purchased this 6 months ago and the drivers have come a long way since then!

I am having two problems ate the moment:
1. The mouse "jumps" when I use my finger and works fine with the pen; does this need calibrated?
2. How do I enable tap-to-click?

You note that TopX/Y/BottomX/Y are used for a "crude calibration" and to use wacomcpl to calibrate the touchpad. --- unfortunately, wacomcpl does not exist yet on Lucid.

Currently I am using TopX=200, TopY=200, BottomX=4000, BottomY=4000

When I move the mouse with the "touch" feature, the mouse jumps exactly 8-pixels-per-jump in the X direction and about 11-14 pixels-per-jump in the Y direction. My display resolution is 3840x1200 (two 1920x1200 displays using nVidia TwinView).

Is there a way to manually calibrate my touch without wacomcpl under Lucid?

-Eric

[Favux]

Hi Zayfox,

Try a few variations. Turn MatchVendor to MatchProduct. Or mouse2 to event2 on the path line. Commenting out MatchisPointer. Etc.

If that doesn't work we may be blocking the wrong event, or the block isn't working. The other possibility is there is a bug in the xf86-input-wacom code and for whatever reason it isn't quite working for Waltop ie not picking up the stylus.


Hi Eric,

Congratulations on getting it working!

The jump with touch I'm not sure about. I put in a bug report about a similar/same bug and they fixed it in linuxwacom. I thought the fix had made it into xf86-input-wacom too. As long as the pointer arrow comes back to your finger, ie it's cosmetic, I wouldn't worry about it too much. There's a new touch/gesture patch in the approval process. It may fix the problem. Just waiting for it to be committed to the git repository.

Tap to click for finger should be enabled. What's happening?

You have to manually change the coordinates and zero in on them that way. Starting with:

Section "InputClass"
   Identifier "Wacom class"
   # WALTOP needs a patched kernel driver, that isn't in mainline lk yet,
   # so for now just let it fall through and be picked up by evdev instead.
   # MatchProduct "Wacom|WALTOP|WACOM"
   MatchProduct "Wacom|WACOM"
   MatchDevicePath "/dev/input/event*"
   Driver "wacom"
   Option "TopX" "200"
   Option "TopY" "200"
   Option "BottomX" "4000"
   Option "BottomY" "4000"
EndSection

to begin with.

[Favux]

Ha, the new/updated touch gestures just got added to the git repository in the last hour!

[Zayfox]

Hyrr!
lsusb, xsetwacom list, and xinput --list all return the tablet, yet it still will not actually pick up a stylus or what not. I'm pretty sure it's not the config though, any other possible factors?

[Favux]

Hi Zayfox,

It's looking more and more like we're dealing with a bug in the code. You may need to make a bug report on the LWP's bug tracker. Let's look everything over again tommorrow and see if we're missing something before you do that.

[Zayfox]

Alright, it was working as a cursor (if I didn't 'click' it) before, but now even with the vanilla .conf file it won't work at all.
I'll look around see if anyone else has been having these issues on the LWP forums / bugtracker.

[eWheeler]

The jump with touch I'm not sure about. I put in a bug report about a similar/same bug and they fixed it in linuxwacom. I thought the fix had made it into xf86-input-wacom too. As long as the pointer arrow comes back to your finger, ie it's cosmetic, I wouldn't worry about it too much. There's a new touch/gesture patch in the approval process. It may fix the problem. Just waiting for it to be committed to the git repository.

It might be considered cosmetic. The mouse moves and stays under my finger. It just isn't a "smooth" motion as it skips pixels.

Tap to click for finger should be enabled. What's happening?

Nothing. I tap to click and it acts like tap to click is disabled. The pointer moves fine, and I can click using "Button1". Just not with tap.

You have to manually change the coordinates and zero in on them that way. Starting with:

Section "InputClass"
   Identifier "Wacom class"
   # WALTOP needs a patched kernel driver, that isn't in mainline lk yet,
   # so for now just let it fall through and be picked up by evdev instead.
   # MatchProduct "Wacom|WALTOP|WACOM"
   MatchProduct "Wacom|WACOM"
   MatchDevicePath "/dev/input/event*"
   Driver "wacom"
   Option "TopX" "200"
   Option "TopY" "200"
   Option "BottomX" "4000"
   Option "BottomY" "4000"
EndSection

to begin with.

Can I use xsetwacom to adjust topxy/bottomxy live, or does X need restarted between adjustments?

Is this related to the jumpiness somehow with such a high-res screen0? Its like the conversion from touchpad units to screen units is too low resolution to move pixel-by-pixel (jumpiness as described above).

Your thoughts?