HOWTO: Wacom in 8.04 Hardy

[mykes]

Doesn't work for me on my HP Tx2110 laptop - tablet / touch screen

A few issues.

mykes@mykes-laptop:~$ lsusb | grep -i wacom
Bus 002 Device 006: ID 056a:0093 Wacom Co., Ltd

Both the linuxwacom-0.7.9-11.tar.bz and the 0.8 version do not compile in step 6 for me. I had to hack the Makefile to add a -I for the compiler to find pixman.h

I never had a /dev/input/wacom device, and still don't after following this how-to.

From the Xorg.0.log file:

(**) |-->Input Device "stylus"
(**) |-->Input Device "cursor"
(**) |-->Input Device "eraser"
(**) |-->Input Device "pad"
(**) |-->Input Device "Synaptics Touchpad"
... (later on)
(**) Option "SendCoreEvents"
(**) stylus: always reports core events
(**) stylus device is /dev/input/wacom
(**) stylus is in absolute mode
(**) stylus: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) stylus: reading USB link
(**) Option "BaudRate" "9600"
(**) Option "SendCoreEvents"
(**) cursor: always reports core events
(**) cursor device is /dev/input/wacom
(**) cursor is in relative mode
(**) cursor: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) cursor: reading USB link
(**) Option "BaudRate" "9600"
(**) Option "SendCoreEvents"
(**) eraser: always reports core events
(**) eraser device is /dev/input/wacom
(**) eraser is in absolute mode
(**) eraser: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) eraser: reading USB link
(**) Option "BaudRate" "9600"
(**) Option "SendCoreEvents"
(**) pad: always reports core events
(**) pad device is /dev/input/wacom
(**) pad is in relative mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) pad: reading USB link
(**) Option "BaudRate" "9600"
... and later on again
(II) evaluating device (pad)
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) evaluating device (eraser)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) evaluating device (cursor)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) evaluating device (stylus)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
        No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom

The xf86OpenSerial errors repeat about 100 times

Thanks for your help!

[neko18]

@mykes
Open a terminal and make sure you have a scrollback of at least 500 lines (Edit > Current Profile, Scrolling tab). Run the following commands. Copy the entire terminal session into a text file and attach it.

cd wacom/linuxwacom-0.7.9-11
./configure --enable-wacom
make clean > /dev/null
make | tail -n 300

[welldone101]

Hey thanks for the big setup here. I'm working my way through it and ran into my first problem.

First, a preamble, When I did step 4 I got the ouput "Reading package lists... done; Building dependence tree; Reading state info... done; E: Couldn't find package linux-headers-uname -r

Then when I got to step 6 and type "make" it says:
make: *** No targets specified and no makefile found. Stop.
I tried the next line "sudo make install" and got:
make: *** No rule to make target `install'. Stop.

Since my first time ever using linux was this morning I'm not sure exactly what this means >.< Any advice?

[rajivnavada]

Hi. I went through all the commands in this post without any error messages. However, the touchscreen still does not work. I am using an HP Pavilion tx2000 laptop with Ubuntu 8.04. Does the nvidia driver have anything to do with this? Also, does compiz work with the touchscreen? Can you please help me resolve this? I have attached the outputs you requested as text files. Thanks a lot!

[Brown Betty]

I've followed the instructions here to the end without getting any errors, but my tablet is behaving just as it was before; it seems be unable to reach the edges of the screen, and the buttons on the stylus are not working like they ought. Anyway, I've attached my output files, and would be grateful for any suggestions you have.

[neko18]

@welldone101
It looks like you missed the backticks (the ` character) on the package name. It should be

linux-headers-`uname -r`

instead of

linux-headers-uname -r

@Brown Betty
Your driver appears to be installed and working correctly. I suggest you file a bug at the Linux Wacom bug tracker: http://sourceforge.net/tracker/?atid...96&func=browse

@rajivnavada
What is the output of this command?

lsusb | grep -i wacom

[pommattski]

Great howto, neko18...

I feel I must point out that that procedure is not necessary for all Wacom tablets.

I have a Graphire3 and have it working in a new installation of Hardy (64 bit) based on information in this thread - thanks to twisted_steel.
In summary:
I installed wacom-tools. I then backed-up /etc/X11/xorg.conf and edited it as follows, adding:

Section "InputDevice"
        Driver          "wacom"
        Identifier      "stylus"
        Option          "Device"        "/dev/input/wacom"
        Option          "Type"          "stylus"
        Option          "USB"           "on"
EndSection
Section "InputDevice"
        Driver          "wacom"
        Identifier      "eraser"
        Option          "Device"        "/dev/input/wacom"
        Option          "Type"          "eraser"
        Option          "USB"           "on"
EndSection
Section "InputDevice"
        Driver          "wacom"
        Identifier      "cursor"
        Option          "Device"        "/dev/input/wacom"
        Option          "Type"          "cursor"
        Option          "USB"           "on"
EndSection

... and adding the 3 InputDevice lines to the ServerLayout section:

Section "ServerLayout"
	Identifier	"Default Layout"
	Screen 		"Default Screen"
        InputDevice     "stylus"        "SendCoreEvents"
        InputDevice     "cursor"        "SendCoreEvents"
        InputDevice     "eraser"        "SendCoreEvents"

EndSection

... Rebooted and was able to "configure extended input devices" in Preferences of the GIMP - no problems. Just confirmed ok in Inkscape also.
Pressure sensitivity working just fine.

[Kiongku]

Do I have to always reboot my pc to use the wacom tablet?
Seems if I unplug it and plug it again while the computer is on, the tablet reverts to its old behavior. Not as a tablet.

Just making sure if everyone has the same issue. Thanks.

[rajivnavada]

Hi neko18. Thanks for replying to my post earlier and also thanks for the entire "How-To". I have attached the output of lsusb | grep -i wacom in the attached txt file. Thanks for your help.

[neko18]

@pommattski
From what I've read, 64 bit users seem to be having better luck with Wacom tablets. I may just be seeint a false correlation though. In any case, it won't hurt to follow all the instructions.

@Kiongku
There are three ways to get Ubuntu to detect your tablet if it is plugged back in:
1. Restart your computer. This should always work.

2. Log out and log back in. This almost always works.

3.
Switch to a different virtual terminal, then back to the one running X.org. To do this, press Ctrl-Alt-F1, wait a couple seconds, then press Ctrl-Alt-F7, then wait a couple seconds.

Yours may not be F7 (though the majority seem to be), so try some other higher numbers if it isn't. The only other one I've personally seen is F9.

@rajivnavada
1. Follow steps 1, 2, 3, 4, and 5 of the original guide

2.

wget http://linuxwacom.pastebin.com/pastebin.php?dl=f3d5b9e73 -O ../zappacky_tabletpc.patch
patch -p1 < ../zappacky_tabletpc.patch

3. Follow step 6.

4. If you haven't done 8, 9, 10, and 11 before, do them. They only need to be done once.

5.

cp /lib/modules/`uname -r`/kernel/drivers/input/tablet/wacom.ko wacom.ko.normal_build.`uname -r`
sudo cp linuxwacom-0.7.9-11/src/2.6.24/wacom.ko /lib/modules/`uname -r`/kernel/drivers/input/tablet/wacom.ko

6. Follow steps 13, 14, 15, 16, 17, 18, 19, and 20.

I've read reports that the tablet calibration may be off with this patched driver. This can be fixed. If you have this problem, I can step you through calibrating it.