I got it working under SuSE 9.2 and then upgraded to 9.3 and it broke. The same steps don't seem to work in 9.3 as they did in 9.2. I am still experimenting. (see last but one para below)
However. There is a linux wacom howto that is very comprehensive. 'fraid you will have to read it all.
http://linuxwacom.sourceforge.net/index.php/howto/main
This includes XF86Config setup.
If you have a serial mouse, then life is easier (read the above doc).
For me - on 9.2 SuSE with a USB mouse, I had to experiment to find out which device was getting input from the
keyboard, mouse (mice) and tablet. It was trial and error, and I got different results on different
machines with the same O/S loaded.
go to /dev/input
cat -vet mouse0
{try the keyboard, the mouse, and the tablet in turn. Note which gives you chars on the screen}
Hit ^C to end
Try again with mouse1 mouse 2 mouse3 event0 event1 event2 event3
Note which does what.
Data read from mouseX is processed differently than it's equivalent on eventX, although they
are the same stream, your mouse will only work with mouseX data. Data read from eventX is what
potentially contains the tilt, and pressure sensitive stuff. Now here is the rub. Most times, the
graphire (and other wacoms) are recognised as a USB mouse. The drivers involved are likely
for USB mouse to actually combine the data from all detected mice. This is why your tablet seems
to work (as a mouse). However, even if you set up /etc/X11/XF86config as the above link says, it
won't work properly until you separate the mouse from the tablet data. For my system, I chose to
download and install the precompiled updated driver, and set up XF86Config to use /dev/input/mouse2
instead of /dev/mice. This meant that I could then set up the wacom using /dev/input/event2.
Finally, you have to set up GIMP to use those features. Look in preferences ^ Input Devices ^
Confgure Extended devices
If it says "No extended devices" then you have not got it installed properly.
Otherwise, there will be drop-down options that you set for using special features. (excludes
tilt on Gimp anyway)
Most wacom driver doc talks about event0, but on my systems it was not happening there.
So I had to add /dev/input/event2 as a device.
This is the new stuff that I put in my config:
# in the files section...
Load "wacom"
# new stuff...
Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/event2" # USB ONLY
Option "Type" "cursor"
Option "USB" "on" # USB ONLY
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
# and you put these lines in the ServerLayout section
InputDevice "cursor" "SendCoreEvents"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
If you stuff up the XF86Config - then restore the original file when logged in from console. (I make
copies of config files before editing them) Start up graphics again with
> startx
ok. That got me up and running - however, I think it was a rough hack as there should not be a
dependence on machine to machine with the same OS for a device like a mouse and different
entry points if it is a clean solution. So I am not surprised that it broke on upgrade to 9.3. The link
above talks about replacement mouse driver that ignores wacom data. I think that's a cleaner
way to go so that my XF86Config can continue to use /dev/mice (all MICE from one entry point)
and then I just use event<whatever> for the wacom setup.
BTW - YaST on Suse creates XF86Config each time the mouse module (and probably other stuff)
is manipulated and the resulting config file is not supposed to be edited directly. I have not worked
out how you are supposed to make custom changes. I tried the wacom setup in YaST but it didn't
seem to work. Can't find it in 9.3 !