HOW TO set up a Waltop tablet in Lucid & Maverick

[Favux]

& Natty & Oneiric & Precise

Last updated: May 29, 2012

Preliminaries
Waltop tablets are often re-branded by the various Tablet Vendors. To determine if you have a Waltop tablet enter in a terminal:

xinput list

One of the devices labeled pointer should have WALTOP in the <device name>. The Vendors usually give the re-branded tablet their own model name. To determine the actual underlying "model" or Product ID enter in a terminal:

lsusb

In the output should be a line containing Waltop and the Waltop Vendor ID = 172f. It will be immediately followed by the Product ID, separated from the Vendor ID, by a colon. For example:

Bus 007 Device 003: ID 172f:0038 Waltop International Corp. Genius G-Pen F509

In this case the Product ID = 0038.


Sources
DIGImend SourceForge site
DIGImend mediawiki

See "Attention Waltop tablet in Lucid & Maverick users" near the top of the LinuxWacom HOW TO.
Graphic Tablet working in 5 steps!! by al.do
How to make your Genius G-pen F610 Tablet work on Ubuntu 10.04 Lucid Lynx by AlexDS
waltop weirdness

Releases prior to Lucid:
Tablet Buttons don't work (Genius GPEN F610)
Still can't get waltop/medion graphics tablet to work, can't build drivers in karmic


Ubuntu Release Specific Notes
Oneiric (11.10): Setup should be the same as with Maverick and Natty only requiring a custom 52-waltop-on-wacom.conf in /etc/X11/xorg.conf.d as with them. However things are in a bit of a state of flux and some Waltop tablets may in fact work better on the new 2.6 version of evdev X driver that comes with Oneiric. See the Tablet support status page on the DIGImend mediawiki. So you may want to try the xf86-input-evdev driver if your tablet is not behaving well with the xf86-input-wacom driver.

Maverick (10.10) & Natty (11.04): The Waltop tablets work with the Wacom X driver, xf86-input-wacom. Ubuntu calls the xf86-input-wacom driver the xserver-xorg-input-wacom package. However the stylus side buttons do not work correctly with Maverick's 2.6.35 kernel. The two side buttons can not be given different settings. They do work in Natty's 2.6.38 kernel thanks to Nikolai Kondrashov's kernel patches.

Lucid (10.04): The Waltop tablets are actually suppose to be using xf86-input-wacom (the xserver-xorg-input-wacom package). Just like they did with linuxwacom in the long, long ago (i.e. Intrepid (8.10)). Unfortunately the Waltop usb driver in the hid part of the kernel does not quite support the tablet using the xf86-input-wacom X driver wacom_drv.so. Patches have been submitted by Nikolai Kondrashov to the kernel that partially fixes this with Maverick and gets everything working with Natty. In the meantime you can get the tablet functioning surprisingly well with the WizardPen driver. The main difference is pressure is linear instead of on a bezier curve like with the wacom driver. You can use the application, e.g. Gimp, to adjust pressure a little.


Precise Pangolin (12.04) & Oneiric Ocelot (11.10) & Natty Narwhal (11.04) & Maverick Meerkat (10.10)
I. Verify the Wacom X driver xf86-input-wacom is installed
Check in Synaptic Package Manager that the Ubuntu package that contains xf86-input-wacom, xserver-xorg-input-wacom, is installed (green box checked). Or check in the Software Center. It should be by default.

II. Create a USB snippet to match the WALTOP to the Wacom X driver
The default usb tablet snippet in the 50-wacom.conf in /usr/share/X11/xorg.conf.d will look something like:

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

As you can see the WALTOP keyword is commented out. You want to add WALTOP back into the match line. But since files in /usr/share/X11/xorg.conf.d are placed there by Ubuntu and may be overwritten during an update it is recommended you not make any user-specific configuration changes there.

Instead user-specific changes are suppose to go in /etc/X11/xorg.conf.d. So we'll create a file called 52-waltop.conf and place the Waltop match to the wacom driver there.

Section "InputClass"
	Identifier "Waltop buttons"
	MatchProduct "WALTOP"
        MatchIsKeyboard "on"
	MatchDevicePath "/dev/input/event*"
	Driver "evdev"
EndSection

Section "InputClass"
	Identifier "Waltop scroll"
	MatchProduct "WALTOP"
	MatchIsPointer "off"
	MatchIsKeyboard "off"
	MatchIsTouchpad "off"
	MatchIsTablet "off"
	MatchIsTouchscreen "off"
	MatchDevicePath "/dev/input/event*"
	Driver "evdev"
EndSection

Section "InputClass"
	Identifier "Waltop pen"
	MatchProduct "WALTOP"
	MatchIsTablet "on"
	MatchDevicePath "/dev/input/event*"
	Driver "wacom"
        # Apply custom Options below this line.

EndSection

The MatchIsTablet match is used so only the Waltop's digitizer/stylus is matched, not its pad buttons. This is because other Waltop devices (/dev/input) exported from the kernel such as tablet buttons are not supported by xf86-input-wacom and should instead be on xf86-input-evdev. Use:

gksudo gedit /etc/X11/xorg.conf.d/52-waltop-on-wacom.conf

to create and edit the 52-waltop.conf file. Save, Close, and reboot. You may need to reboot several times for things to "shake out".

You may need to create the /etc/X11/xorg.conf.d directory if it is not already there. To do so run this command:

sudo mkdir /etc/X11/xorg.conf.d

For more details see 52-waltop.conf on the DIGImend wiki. But basically the "Waltop scroll" snippet is to enable scroll for your tablet's multifuction dial or jog wheel if it has one. And the "Waltop buttons" snippet is to reclaim the keyboard events for evdev if you have a 50-wacom.conf with Waltop in the usb snippet rather than in the new stand alone Waltop snippet. The new Waltop stand alone snippet is in xf86-input-wacom-0.14+ but has been backported into Precise's xf86-input-wacom-0.14.0. Oneiric's xf86-input-wacom-0.12.0 has the Waltop keyword in the usb snippet in 50-wacom.conf. So Oneiric requires that the keyboard events (buttons, volume, etc.) be reclaimed from Wacom for evdev. Natty still has the Waltop match commented out in its default xf86-input-wacom-0.11.10.

III. Consider updating xf86-input-wacom
There are more changes being made to the Wacom X driver to make it more non-wacom tablet friendly. You may want to consider cloning the git repository. If you do you can use step "II. Install Xorg'sxf86-input-wacom tar or clone the git repository for Lucid, Maverick, Natty, & Oneiric (the X driver)" at the Bamboo Pen & Touch HOW TO.

IV. Using the xsetwacom script .xsetwacom.sh
To gain finer control over your styus with the wacom drivers you can use a script of xsetwacom commands. The script is an example and you may need to change the xsetwacom Parameter names depending on you version of xsetwacom. See the Linux Wacom Project's mediawiki HOW TOs and Waltop Tablet Set Up.

To set it up to auto-start, download the attached file, and rename it .xsetwacom.sh (or whatever you want) and place it in your home directory or create a bin folder to place scripts in. Remember it will be a hidden file. You can remove the . in front so the file isn't hidden if placing it in a bin directory. Making it hidden is just to prevent directory clutter. To enable the xsetwacom commands in the .xsetwacom.sh file to apply to Xserver through a reboot you enter in a terminal:

chmod +x ~/.xsetwacom.sh

or you could right click on the file and in Properties, in the Permission tab, check Execute as program. Then go to System->Preferences->Startup Applications and click on add and for the command write "sh /home/yourusername/.xsetwacom.sh" (without the quotes). You can also change your settings on the fly using the xsetwacom parameters in a terminal. They only apply during the current session since they are runtime commands. Remember to use the "device name" that:

xinput list

returns for your stylus.

If you are happy with the driver's default settings there is no need to reapply them with the script. Just comment (#) out those lines. But leave those lines in so you have a list of valid modifications available.

V. Dual and Multi-Monitor Set.
See HOW TO Setup a Wacom Tablet with Multi-Monitors in Maverick and Natty or Dual and Multi-Monitor Set Up on the mediawiki.

VI. Pre-patched Kernels for Waltop Support.
Kernels are now available for Oneiric and Precise that add more support and new Waltop models. So if yours isn't working check the DIGImend site for the status of your tablet. The kernels are available here in DIGImend Files. Instructions are on the DIGImend mediawiki page "Kernel packages" with further details on the DIGImend blog.

VII. Waltop Kernel Patches - Fix Both Stylus Buttons Work the Same in Maverick.
According to Nikolai Kondrashov:

The issue is the Waltop HID report descriptor. It doesn't describe buttons correctly. Please try applying my patches for 2.6.36 kernel [1], or use 2.6.37, which has them integrated.

The patch set is on his DIGImend project site. Plenty of goodies on the site. It includes a patch set for kernel 2.6.35 (Maverick) as well as 2.6.32 (Lucid) and 2.6.36. Instructions for patching the kernel are on "HOW TO Add Support for KYE, UC-logic, and Waltop Tablets in Ubuntu".


Lucid Lynx (10.04)
I. Install the WizardPen driver
To get the WizardPen X driver download and install the appropriate xserver-xorg-input-wizardpen package from DoctorMO's (Martin Owens) PPA: https://launchpad.net/~doctormo/+arc...dpen/+packages

Or add the PPA to Software Sources: System-Administration > Software Sources > Other Software tab > +Add > then in the "APT line" enter: ppa:doctormo/xorg-wizardpen

II. Configure your Waltop tablet through the wizardpen.conf
Replace the 70-wizardpen.conf with this modified one:

Section "InputClass"
    Identifier "WizardPen class"
    MatchIsTablet "on"
    MatchProduct "WALTOP"
    MatchDevicePath "/dev/input/event*"
    Driver "wizardpen"
EndSection

Section "InputClass"
    Identifier "WizardPen ignore mouse dev class"
    MatchIsTablet "on"
    MatchProduct "WALTOP"
    MatchDevicePath "/dev/input/mouse*"
    Option "Ignore" "yes"
EndSection

In Lucid use:

gksudo gedit /usr/lib/X11/xorg.conf.d/70-wizardpen.conf

In Maverick (if you prefer not to use the Wacom X driver) use:

gksudo gedit /usr/share/X11/xorg.conf.d/70-wizardpen.conf

Save, close, and reboot.

III. Available Options
You can add any of the following Options below the [Driver "wizardpen"] line in the first snippet of the modified 70-wizardpen.conf. The driver should automatically set these for you. However you may want to change some of them, especially Rotation, DebugLevel, TPCButton, and Mode, depending on your preference.:

# first four Options set automatically, unless you want to use wizardpen-calibrate
Option  "TopX"  "0"
Option  "TopY"  "0"
Option  "BottomX"  "17782"
Option  "BottomY"  "10584"

Option  "TopZ"  "0"  # minumum pressure, default is 20?
    # not sure that the default is 20; you should able to treat it as a pressure threshold
    # (or "ZThreshold") using values like 5, 10, or 20 if stylus seems too sensitive

Option  "BottomZ"  "511"  # or "1023"; maximum pressure
    # depending on whether the tablet has 512 or 1024 pressure levels

Option  "Rotate90"  "0"  # or "1"
    # 1 rotates tablet 90 degrees

# following two options set automatically
Option  "ScreenX"  "1280"
Option  "ScreenY"  "1024"

Option  "DebugLevel"  "0"  # or "1" to turn debug on
    # Not sure how many debug levels are available, at a guess 0 - 12

Option  "MouseSpeed"  "30"
    # don't know the allowed range or which are useful

Option  "MouseAccel"  "0"  # or "1"
    # 1 turns acceleration on, useful if you are using the tablet as a "mouse"
    # i.e. using [Option "Mode" "Relative"]

Option  "TPCButton"  "on"  # or "off"
    # on is "tip + buttons" while off is "hover mode" i.e. buttons only

Option  "Mode"  "Absolute"  # or "Relative"
    # I believe this is an available option, "Relative" would make the tablet
    # function like a "mouse"

At this point some of these Options are educated guesses. So experimentation needed and use with caution.

As an example of using the Options in the first snippet:

Section "InputClass"
    Identifier "WizardPen class"
    MatchIsTablet "on"
    MatchProduct "WALTOP"
    MatchDevicePath "/dev/input/event*"
    Driver "wizardpen"
        Option  "TopZ"  "20"  # pressure threshold
        Option  "TopX"  "0"
        Option  "TopY"  "0"
        Option  "BottomX"  "17782"
        Option  "BottomY"  "10584"
EndSection

Note: Some Waltops need a pressure threshold over 50 to work correctly on the WizardPen driver.

IV. Calibrate your tablet (if needed) using wizardpen-calibrate
You need to determine the event # for your tablet. In a terminal enter:

cat /proc/bus/input/devices

In the output you'll see something like:

H: Handlers=kbd mouse1 event4

Using your event # enter in a terminal:

wizardpen-calibrate /dev/input/event4

Follow the instructions and use the data from the yellow rectangle in the appropriate Options (see above).
* thanks to al.do & AlexDS

Edit (11-18-10): I was using the linuxwacom ClickForce default and range in the script below for stylus based on a device with 1,024 pressure levels. Howeveer xf86-input-wacom does things differently. The default ClickForce for the stylus is FILTER_PRESSURE_MAX/75. Whatever pressure levels a device reports is normalized to 2048 levels. So even for the Waltop stylus, with I think 1024 pressure levels (let me know if I'm wrong), the ClickForce line should look something like:

xsetwacom set "WALTOP International Corp. Slim Tablet stylus" ClickForce "27"  # default is 27, 0-2047

They renamed ClickForce to Threshold. So now, if you have xf86-input-wacom 0.10.9+, it is something like:

xsetwacom set "WALTOP International Corp. Slim Tablet stylus" Threshold "27"  # default is 27, 0-2047

See the commit "xsetwacom: rename ClickForce to Threshold"

Edit (12-7-10): Updated Sample Waltop .xsetwacom.sh. First version had 37 downloads.

Note: Since they do change the xsetwacom Parameter names, defaults, and ranges from time to time you should check in man xsetwacom or Xsetwacom for the current names and values.

[Favux]

Materials for Possible Additional Configuration in Lucid

Enter in a terminal 'man wizardpen' after installing the driver. Notice that it is pretty dated.

THE MANPAGE FOR WIZARDPEN:

WizardPen(4)

NAME
wizarpen - WizardPen tablet input driver

SYNOPSIS
Section "InputDevice"
Identifier "Tablet"
Driver "wizardpen"
Option "Device" "devpath"
...
EndSection
...
Section "ServerLayout"
...
InputDevice "Tablet"
...
EndSection

DESCRIPTION
wizardpen is an Xorg input driver for WizardPen Tablet devices...

The wizardpen driver functions as a pointer input device, and may be
used as the X server's core pointer. THIS MAN PAGE NEEDS TO BE FILLED
IN.

SUPPORTED HARDWARE
What is supported...
WizardPen tablets

CONFIGURATION DETAILS
Please refer to xorg.conf(5) for general configuration details and for
options that can be used with all input drivers. This section only
covers configuration details specific to this driver.

Option "TopX" "val"
Allows the use of an alternative left edge location.

val should be equal to the x value of the new left edge

Option "TopY" "val"
Allows the use of an alternative top edge location.

val should be equal to the y value of the new top edge

Option "TopZ" "val"
Allows the use of an alternative minimum pressure.

val should be equal to the value of the new minimum pressure

Option "BottomX" "val"
Allows the use of an alternative right edge location.

val should be equal to the x value of the new right edge

Option "BottomY" "val"
Allows the use of an alternative bottom edge location.

val should be equal to the y value of the new bottom edge

Option "BottomZ" "val"
Allows the use of an alternative maximum pressure.

val should be equal to the value of the new maximum pressure

SEE ALSO
Xorg(1), xorg.conf(5), xorgconfig(1), Xserver(1), X(7).

AUTHORS
Authors include... Edouard TISSERANT Zachary Cornelius

X Version 11 wizardpen 0.7.4 WizardPen(4)

* thanks to keevee09

It's possible additional configuration could also be done through X. If you enter 'man xinput' in a terminal there are a few parameters that may be worth looking at:

xinput get-feedbacks device_name
Display the feedbacks of device_name. Uses XGetFeedbackCon‐
trol(3).

xinput set-pointer device_name
Switch device_name in core pointer. Uses XChangePointerDe‐
vice(3).

xinput set-mode device_name ABSOLUTE|RELATIVE
Change the mode of device_name. Uses XSetDeviceMode(3).

xinput set-ptr-feedback device_name threshold num denom
Change the acceleration of device_name. Uses XChangeFeedback‐
Control(3).

xinput set-integer-feedback device_name index value
Change the value of an integer feedback of device_name. Uses
XChangeFeedbackControl(3).

xinput set-button-map device_name map button 1 [map button 2 [...]]
Change the button mapping of device_name. Uses XSetDeviceBut‐
tonMapping(3).

xinput set-int-prop device_name property format value
Sets an integer property for the device. Appropriate values
for format are 8, 16, or 32, depending on the property.

xinput test [-proximity] device_name
Register all extended events from device_name and enter an end‐
less loop displaying events received. If the -proximity is
given, ProximityIn and ProximityOut are registered.

First figure out what your device is called. Enter in a terminal:

xinput --list

Then using the device name in quotes enter:

xinput list-props "WALTOP International Corp. Slim Tablet"

Device 'WALTOP International Corp. Slim Tablet':
Device Enabled (134): 1
Coordinate Transformation Matrix (136): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (267): 0
Device Accel Constant Deceleration (268 ): 1.000000
Device Accel Adaptive Deceleration (269): 1.000000
Device Accel Velocity Scaling (270): 10.000000

* thanks to icodemonkey

xinput get-feedbacks "WALTOP International Corp. Slim Tablet"

1 feedback class
PtrFeedbackClass id=0
accelNum is 2
accelDenom is 1
threshold is 4

* thanks to keevee09 He also ran:

xinput test "WALTOP International Corp. Slim Tablet" > tablet_feedback.txt

The text file was quite long but scrolling through I found it gave max/min values for

a[0] of 9496/500 # x values I guess
a[1] of 5932/312 # y values
a[2] of 1023/0 # z values - pressure

[Favux]

Reserved.

[Favux]

Hi everyone,

Updated and corrected the Waltop .xsetwacom.sh (xsetwacom commands script). Also added some more, and hopefully more useful comments into the script. Please read through them.

[aapo4]

(I started this on bamboo -topic, but this might be better topic)

I have Aiptek 14000u Media Tablet, which is re-branded Waltop.

When I just plug-it to the Ubuntu-10.10, it is not using wacom-driver at all (if I read logs properly). I can move mouse cursor with pen and make clicks. Pen has two buttons, so I think it is possible to make clicks button1+button2+button3. Even I try remapping, both modifier buttons send same (button2 or button3).
With 'xinput test' I can see pressure is detected.

But when I try to use pen with applications it doesn't work. I have tested Gimp and MyPaint. They both have default that pressure is not used. (disabled), and can be changed to 'screen' or 'window'. If I change it to the screen, pen is not then drawn anything. Error messages to console are:

(gimp:2466): Gdk-CRITICAL **: gdk_input_update_axes: assertion `first_axis >= 0 && first_axis + axes_count <= gdkdev->info.num_axes' failed

/usr/share/mypaint/gui/main.py:54: GtkWarning: gdk_input_update_axes: assertion `first_axis >= 0 && first_axis + axes_count <= gdkdev->info.num_axes' failed

*
With wacom driver
I change /usr/share/X11/xorg.conf.d/50-wacom.conf and rebooted. According to the /var/log/Xorg.0.log (attached) it is now using wacom (0.10.99 from git)
Loading /usr/lib/xorg/modules/input/wacom_drv.so
compiled for 1.9.2.901, module version = 0.10.99

With this driver pen is not working, when I touch anywhere on the tablet, mouse cursor jumps to top-left-corner and doesn't move.
With xinput test I can see all motion events are the very same:
motion a[0]=0 a[1]=0 a[2]=0 a[3]=0 a[4]=0 a[5]=-900

Am I understood correctly that long term plan is that every tablets uses same 'wacom-driver'? So must useful is try to get this tablet working with wacom?

[Favux]

Am I understood correctly that long term plan is that every tablets uses same 'wacom-driver'?

I don't know about every tablet, but certainly the Waltops.

I can move mouse cursor with pen and make clicks. Pen has two buttons, so I think it is possible to make clicks button1+button2+button3. Even I try remapping, both modifier buttons send same (button2 or button3).

That's due to a bug in the 2.6.35 and 2.6.36 kernels. It's fixed in the 2.6.37 kernel by Nikolai Kondrashov. I think he has a fix on his DIGImend project site for the 2.6.35 kernel, but I'm not sure I'd use it.

With 'xinput test' I can see pressure is detected. But when I try to use pen with applications it doesn't work.

Well we know it worked for earlier 2.6.35 kernels and the default xf86-input-wacom-0.10.8. So something may have been broken in the recent kernel update or in xf86-input-wacom after 0.10.8.

However your xinput list shows:

⎜ ↳ WALTOP International Corp. Media Tablet eraser id=10 [slave pointer (2)]
⎜ ↳ WALTOP International Corp. Media Tablet pad id=11 [slave pointer (2)]
⎜ ↳ WALTOP International Corp. Media Tablet stylus id=12 [slave pointer (2)]

But you don't have an eraser or pad. Even though the Xorg.0.log shows them happily being set up. Do you see the same 3 input tools with xsetwacom list? Maybe that's causing the problem with Gimp and MyPaint. Let's try eliminating eraser and pad with a different match. Change the match line from:

	MatchProduct "Wacom|WALTOP|WACOM"

to

#	MatchProduct "Wacom|WALTOP|WACOM"
	MatchProduct "WALTOP International Corp. Media Tablet stylus"

Hopefully evdev won't pick up the eraser and pad.

[aapo4]

Attached Xorg-log when wacom-driver is not used, but waltop.

With this settings pointer can be used, and xinput test detects pressure, but gimp not.

xinput list

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ A4TECH USB Device                       	id=8	[slave  pointer  (2)]
⎜   ↳ A4TECH USB Device                       	id=9	[slave  pointer  (2)]
⎜   ↳ WALTOP International Corp. Media Tablet 	id=10	[slave  pointer  (2)]

(Note: there are not word stylus, like with wacom driver)

[Favux]

Attached Xorg-log when wacom-driver is not used, but waltop.

Don't understand what you are telling me.

That Xorg.0.log shows the tablet/stylus on the evdev driver, matched by the "evdev tablet catchall" snippet. You definitely don't want the evdev driver for a stylus.

A short cut to find out what driver a device is on is to use the "device name" in quotes from xinput list with list-props.

xinput list-props "WALTOP International Corp. Media Tablet"

in the current xinput list output. Or to check if it is on the wacom driver you could use xsetwacom list.

[aapo4]

Ok, know I understand.

So currently only way how I can use tablet at all is use it with evdev driver.

*
When I add MatchProduct "Wacom|WALTOP|WACOM" ( on /usr/share/X11/xorg.conf.d/50-wacom.conf) I get stylus, eraser and pad. But mouse cursor is not moving, but it jumps to the upper left corner.

xsetwacom list
WALTOP International Corp. Media Tablet eraser	id: 10	type: ERASER    
WALTOP International Corp. Media Tablet pad	id: 11	type: PAD       
WALTOP International Corp. Media Tablet stylus	id: 12	type: STYLUS

I tried: MatchProduct "WALTOP International Corp. Media Tablet stylus"
(written exactly same way than xinput/xsetwacom list shows it.) But then wacom driver is not used, but evdev instead.

[aapo4]

I got eraser and pad out from list with these:

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|Hanwang"
        MatchDevicePath "/dev/input/event*"
        Driver "wacom"
EndSection

Section "InputClass"
    Identifier     "no eraser or pad"
    MatchProduct   "eraser|pad"
    Option         "Ignore" "on"
EndSection

But mouse cursor is not moving.
Attached Xorg.log