How to set up a Wacom Tablet

How to do things, solutions, recipes, tutorials
Message
Author
melannen
Posts: 2
Joined: Mon 11 Aug 2008, 13:17

#41 Post by melannen »

There are no obviously wacom-related errors in either of those log files, and it appears to be successfully using all the inputs I added to the xorg.config file. (There are some other errors which I don't recognize, but none of them are happening near the points where it loads the wacom stuff.)


Here's the current server and input sections in my xorg.config, if that helps:

Section "ServerLayout"
Identifier "Default"
Screen "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "pad" # For Intuos3/CintiqV5/Graphire4/Bamboo tablets
EndSection


Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "dvorak" #xkeymap0
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/event2" # USB ONLY
Option "Type" "stylus"
Option "USB" "on" # USB ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/event2" # USB ONLY
Option "Type" "eraser"
Option "USB" "on" # USB ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/event2" # USB ONLY
Option "Type" "cursor"
Option "USB" "on" # USB ONLY
EndSection

# This section is for Intuos3, CintiqV5, Graphire4, or Bamboo
Section "InputDevice"
Driver "wacom"
Identifier "pad"
Option "Device" "/dev/input/event2" # USB ONLY
Option "Type" "pad"
Option "USB" "on" # USB ONLY
EndSection


...to the limit of my limited knowledge and what google shows me, I don't know what else to try changing: I did find a google result where somebody fixed this problem by changing xorg.config, but they changed it to look like mine, so. And it does currently work in every other way.

Those two log files are mostly complaining about not being able to load glx, dri, acpi and apm : are any of those things relevant?
xerrs.log says, about wacom,
(==) Using config file: "/etc/X11/xorg.conf"

stylus X driver grabbed event device
(==) Wacom using pressure threshold of 30 for button 1
(==) Wacom USB Graphire4 tablet speed=9600 maxX=10208 maxY=7424 maxZ=511 resX=2032 resY=2032 suppress=2 tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=10208 bottom Y=7424
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=10208 bottom Y=7424
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=10208 bottom Y=7424
(==) Wacom device "pad" top X=0 top Y=0 bottom X=10208 bottom Y=7424
/usr/X11R7/bin/jwm
JWM: warning: color depth is 16, disabling icon alpha channel

and xorg.0.log says

(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "stylus"
(**) |-->Input Device "eraser"
(**) |-->Input Device "cursor"
(**) |-->Input Device "pad"

and then, later,

II) LoadModule: "wacom"
(II) Loading /usr/X11R7/lib/xorg/modules/input//wacom_drv.so
(II) Module wacom: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.5

and

(**) stylus: always reports core events
(**) stylus device is /dev/input/event2
(**) stylus is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) stylus: reading USB link
(**) Option "BaudRate" "9600"
(**) Option "SendCoreEvents"
(**) eraser: always reports core events
(**) eraser device is /dev/input/event2
(**) eraser is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) eraser: reading USB link
(**) Option "BaudRate" "9600"
(**) Option "SendCoreEvents"
(**) cursor: always reports core events
(**) cursor device is /dev/input/event2
(**) cursor is in relative mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) cursor: reading USB link
(**) Option "BaudRate" "9600"
(**) pad device is /dev/input/event2
(**) pad is in absolute mode
(**) WACOM: suppress value is 2
(**) Option "USB" "on"
(**) pad: reading USB link
(**) Option "BaudRate" "9600"
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(**) Option "Device" "/dev/input/event2"
stylus Wacom X driver grabbed event device
(==) Wacom using pressure threshold of 30 for button 1
(==) Wacom USB Graphire4 tablet speed=9600 maxX=10208 maxY=7424 maxZ=511 resX=2032 resY=2032 suppress=2 tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=10208 bottom Y=7424
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=10208 bottom Y=7424
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=10208 bottom Y=7424
(==) Wacom device "pad" top X=0 top Y=0 bottom X=10208 bottom Y=7424
(II) Mouse0: ps2EnableDataReporting: succeeded


All of that looks good to me, but I don't read log files very fluently. Any help? Thanks.

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#42 Post by mikeb »

hmmm..well fortunately or unfortunately that all looks 100% to me too.

xsetpointer -l in a console will list input devices...you could try that...see what you get
http://linuxwacom.sourceforge.net/index ... to/ptrstat

mike

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#43 Post by Pizzasgood »

Not sure how to rotate the screen off the top of my head. My guess is you need to look into an option for xorg.conf.


As for GIMP pressure sensitivity, I don't think it's any problem with what you've done. I tried it out myself recently and couldn't get it to work with Puppy 4.00. 4.00 uses a newer version of GIMP than 3.01 did, and I'm guessing something is goofed up with it. Probably Barry disabled a bunch of the more esoteric options when compiling it to keep things small. One of these days I'll have to look into compiling the latest version myself and seeing if it makes a difference.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#44 Post by mikeb »

If what pizzagood suggests about the GImp is true then i use the Gimpshop pup and it has pressure sensitivity working just fine (and printing)
http://www.dotpups.de/dotpups/Graphics/ ... 2.2.10.pup
you might want to try just to see.

regards

mike

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#45 Post by Pizzasgood »

It's not gimp. I compiled the latest (at the time, they just released a new one a couple days ago) and it didn't work. I also tried the one from 2.14 that I know works, and it didn't work either.

So I rebooted into 2.14 and installed the 2.6.18 kernel drivers and that version's gimp. Worked fine. Rebooted into 3.01 and installed the 2.6.21.7 drivers (the ones 4.00 uses), and tried the version of gimp I had installed already (2.4.3) and it worked fine. Switched to the new version of Gimp that I compiled, and it still worked.

So I rebooted into a fresh 4.00 and installed the 2.6.21.7 drivers again, and the new gimp package I made. No dice.

So I think it's either the kernel, a supporting library, or Xorg that's goofed up. Probably one of the latter two. I'll look into this more later tonight.


EDIT: Looks like the problem is probably GTK. I'm going to a little more research, then try rebuilding gtk with the --with-xinput=yes option, which I suspect is what's wrong.

EDIT 2: Definitely GTK. I'll get some sort of package working tomorrow.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#46 Post by Pizzasgood »

Okay, here's a version of GTK that will work. It's the same version in Puppy 4.00, but with the --with-xinput=yes flag. After installing this, restart X and Gimp should let you configure things.
http://www.murga-linux.com/puppy/viewto ... 255#227255
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

#47 Post by charlie6 »

Hi,
Pizzasgood wrote
Next, you need drivers. Run the command uname -r to find out which kernel you have, then install the driver below that matches:
wacom_k2.6.18.1.pet
wacom_k2.6.21.7.pet
While searching across the web to get my (pretty old now! - 6 years) wacom tablet working on Puppy4.11 (automatically recognized on Puppy4.0) I went to this post.

It would be nice if a
wacom_k2.6.25.16.pet
could be issued.

Testing Puppy411 as live-cd: the wacom tablet is not recognized ('usb mouse' selected at startup configuation. (was recognized on Puppy4.0). Same result testing on pPuppy411retro.

Cheers

Charlie

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#48 Post by Pizzasgood »

Yep, been meaning to do that. I've been pretty busy for the last couple weeks so I kept putting it off. I have some time this week though so I should be able to get it done tomorrow afternoon.


To anybody trying to access these files over the last couple days, I have to apologize. My host seems to have been attacked over the weekend. They claim to have fixed everything now so that we can re-upload our content, but I still can't get into my site. Hopefully that will be fixed soon. (This is also why my avatar seems to be on vacation - actually, that's what alerted me to this in the first place, as I didn't receive any kind of email from them! Grrr...)
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#49 Post by Pizzasgood »

Actually, it turns out the old package will work fine in 4.10 and 4.11. The only part that is different is the kernel driver, but kernel drivers are installed in a way that lets drivers from multiple versions of the kernel coexist because the location they install into is named after the kernel they belong to, so there wouldn't be any danger of Puppy using the wrong driver. It would just use the kernel driver that is included with Puppy rather than the one I packaged.

I think the kernel driver included with Puppy 4.11 is slightly older than the latest stable version though (but it does appear to be new enough to support the bamboo), so I went ahead and recompiled it anyways. Since my site is still down, I attached it here.
Last edited by Pizzasgood on Thu 04 Dec 2008, 01:56, edited 1 time in total.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#50 Post by Pizzasgood »

Turns out they were attacked, but my server wasn't. My issue was completely unrelated. Something glitched and caused my site to start hogging resources, so it was auto-suspended. Anyways, it's back up and running again. I added a link to the new file on the first page, and took down the attachment.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

#51 Post by charlie6 »

Hi Pizzasgoog !
Many thanks for wacom_k.2.6.25.16.pet
Cheers,Charlie

User avatar
gymnart
Posts: 105
Joined: Wed 10 Dec 2008, 20:32
Contact:

#52 Post by gymnart »

Would this work on a very old Graphire 1?
I have Puppy 4.1 k2.6.25.16

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#53 Post by Pizzasgood »

I think it should, but I don't have one to test with so I can't be certain.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
gymnart
Posts: 105
Joined: Wed 10 Dec 2008, 20:32
Contact:

#54 Post by gymnart »

Edit: problem solved:

What I did was to go into the boot manager (Menu > System > Boot Manager) and looked in the list of drivers to load and finally found the Wacom driver (apparently it was not showing up before because I had loaded it when I did the modprobe wacom command. This time I did not do that and the driver finally did show up).

I selected it to load at boot time as I had to do for my sound drivers.

It worked!! It works only as a mouse (and the pen does too!) and that's all I need for my artwork. I'm accustomed to moving the opacity slider bar in Gimp if I want lighter strokes anyway. I have to do it like that in SuSE 10.0.

*w00t*

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#55 Post by Pizzasgood »

Several posts back I uploaded a recompiled version of GTK that has xinput enabled, which lets the stylus's pressure sensitivity work. I also posted another recompiled version in another thread that has debug mode enabled along with xinput, which causes Seamonkey and Firefox to not die when you press the insert key. Just in case you decide you do want that.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
gymnart
Posts: 105
Joined: Wed 10 Dec 2008, 20:32
Contact:

#56 Post by gymnart »

That sounds good.
Do I have to watch out for any incompatibilities?

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#57 Post by Pizzasgood »

I haven't noticed any yet.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
vtpup
Posts: 1420
Joined: Thu 16 Oct 2008, 01:42
Location: Republic of Vermont
Contact:

#58 Post by vtpup »

I've got an original Wacom Graphire (ET type) USB version.

Using Puppy 4.1.2 retro (2.6.21.7 kernel).

Doing a

Code: Select all

modprobe wacom
works out of the box without loading any drivers.

However the eraser isn't recognized and Gimp doesn't list it as one of the extended input devices, even though you can actually draw with it in Gimp.

To fix this, I tried the Xorg config changes as listed in the first post for USB and also installed the wacom_k2.6.21.7.pet , but afterwards, when I tried to modprobe wacom, I got a warning

Code: Select all

# modprobe wacom
FATAL: Error inserting wacom (/lib/modules/2.6.21.7/kernel/drivers/usb/input/wacom.ko): Invalid module format
FATAL: Error running install command for wacom
When I unistalled the pet, and rebooted and modprobed the wacom module the tablet worked again, but still had the same problem with the eraser not working and Gimp's problem listing it as an extended input device.

I had hoped that the xorg config changes might have corrected this, even though I had unloaded the new wacom dotpet. But they didn't.

Perhaps it is because I don't have the right event setup.

Doing:

Code: Select all

cat /proc/bus/input/devices
gave:
"H: Handlers=mouse2 event4".
Here's what I put into the config file:

Code: Select all

Section "InputDevice"
  Driver        "wacom"
  Identifier    "stylus"
  Option        "Device"        "/dev/input/event4"   # USB ONLY
  Option        "Type"          "stylus"
  Option        "USB"           "on"                  # USB ONLY
EndSection

Section "InputDevice"
  Driver        "wacom"
  Identifier    "eraser"
  Option        "Device"        "/dev/input/event4"   # USB ONLY
  Option        "Type"          "eraser"
  Option        "USB"           "on"                  # USB ONLY
EndSection

Section "InputDevice"
  Driver        "wacom"
  Identifier    "cursor"
  Option        "Device"        "/dev/input/event4"   # USB ONLY
  Option        "Type"          "cursor"
  Option        "USB"           "on"                  # USB ONLY
EndSection
and for the server layout section:

Code: Select all

Section "ServerLayout"
	InputDevice "Synaptics Mouse" "AlwaysCore"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "stylus"    "SendCoreEvents"
    InputDevice    "eraser"    "SendCoreEvents"
    InputDevice    "cursor"    "SendCoreEvents"    # For non-LCD tablets only
EndSection
Finally, I have done a:

Code: Select all

mknod /dev/input/event4 c 13 68 
and event4 shows up in /dev/input/

Still no go.

I think it needs the first post wacom module dotpet. But that won't load for some reason. I don't think that is related to the pad itself -- the module should load whether a pad is attached or not, shouldn't it?

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#59 Post by Pizzasgood »

I haven't tested it in retro yet. I'll give it a try later tonight. EDIT: Scratch that, I don't have time tonight so I'll have to try it tomorrow. Sorry.


First, you need to grab a version of gtk compiled with xinput, otherwise programs like Gimp won't see it as anything but a mouse. I posted one in this thread, but since then I've found out that enabling debug-mode will stop Seamonkey from crashing when you press 'insert', so use this one instead:
gtk+-2.12.1-xinput-debug.pet

Then you'll need to restart X.

If that doesn't help, you might still need the xorg driver. Puppy 4.12 doesn't include that, just the kernel module. The package I posted has both (slightly newer IIRC). Since the kernel module was causing problems, try extracting the package and manually installing only the xorg driver. You can do that like this:

Code: Select all

tar xf wacom_k2.6.21.7.pet
cp -a wacom_k2.6.21.7/usr /
(Ignore the error about trailing garbage - that's just the md5sum appended to the tar.gz file)

After finishing, you'll need to restart X again.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
vtpup
Posts: 1420
Joined: Thu 16 Oct 2008, 01:42
Location: Republic of Vermont
Contact:

#60 Post by vtpup »

It works!

Thanks so much Pizzasgood :D .

A couple notes:

I made the GTK change first and restarted X, but couldn't see any difference.

I then did the module download, tar and copy, and restarted X and still no change.

But I suspected that it needed a reboot, not just an X restart, and this proved to be true. After that Gimp showed the extended input devices, and I suddenly had pressure sensitivity in the stylus, which is amazing!

I didn't realize that this very old Graphire pad (the earliest version) was capable of doing pressure sensitivity. In the years since I've owned it, this is the first time that ever experienced that possibility. I didn't have it on Windows., I'm pretty sure -- at least not with the original Graphire drivers and the graphic programs I had.

The eraser works that way as well, however, the eraser tool isn't automatically selected in Gimp when you use the pen eraser. In other words, it doesn't select the background color, but continues in the selected color, with the paintbrush cursor. Maybe that's how Gimp works? Or maybe it's a matter of setting the extended input device?

Well whatever, I'm really happy with what I can do now. Drawing with the brush and pressure is like working in real artist materials, and the eraser is pressure sensitive, too!

Thank you again Pizzasgood for all your work with this. You've made a lot of people happy in this thread!

Post Reply