[HOWTO] Wacom Volito2 and other Wacom tablets

[red-wolf76]

Finally, I'd like to hear opinions of people who do use tablets. I've never actually used a tablet before (apart from trialling them out in shops), but the main reason I'm looking at getting one is because my wrist is starting to get sore from my normal mouse (which is starting to play up on me anyway). Is a tablet usable as an everyday pointing device? And whilst I don't game much, is it usable when gaming, especially in FPSs?

Hi,

I'm pretty new to tablets myself and just bought a Bamboo One as a gift for my photo-editing ex-gf. Apart from trying to get it to work under Gentoo, I tried it also on my work laptop, which uses WinXP and I can tell you that after being put off at first (p&p installs it as a HID-mousey thing, relative mouse motion by stylus) I got hammered into my seat when I installed the drivers and went through the tutorial. The answer to your first question is definitely yes. I hardly ever touched the pad during my session when absolute positioning was on. As for FPS, I'll conservatively advise to use an optical cord mouse instead.

EDIT: Ok, slowly making progress here, seems I set the kernel event setting to module. I now get the event devices for everything hooked up to the box. I had to tweak the wacom_wac.c-file in the source archive so the driver would recognize my Bamboo one as a Graphire (which it really is) tablet and it now works just dandy in gdm.

Unfortunately, logging in and starting Gnome crashes the X server. Seems I'm now between a rock and a hard place. If I compile xorg-server with evdev-support, it crashes when trying to use the regular drivers kbd and mouse, using evdev for mouse works, but the keyboard stays dead if I try it. And finally, if I leave evdev altogether, I can use the keyboard, mouse and tablet in gdm, but once I log into Gnome the X server freaks out. :rolleyes: A view in the log tells me it apparently wishes to load an evdev driver (which I just removed to get my mouse and keyboard to work properly.

[red-wolf76]

Update: Evdev trouble seems to be entirely Wacom-unrelated and was fixed by downgrading to hal-0.5.9.1-r3.

BTW: This and including this

Code: Select all

 /*{ "Wacom Bamboo", 9, 14760, 9225, 511, 63, WACOM_MO },*/
 { "Wacom Bamboo One", 8, 5104, 3712, 511, 63, GRAPHIRE },

at the proper place in the linuxwacom-0.7.8-3.tar.bz2 tarball have helped me bunches too.

Now I've just to figure out why Gnome keeps crashing on me when I log in.

[mellofone]

Just a quick note for those of you that are trying to get things working with a Bamboo Fun. I am using the small version, but the medium supposedly is identical. Please make sure you try to manually install the DEV version (now 0.7.9-3) to add support for these tablets. Otherwise, things work PERFECTLY after the upgrade.

[SupuS]

Hi

I have Bamboo Fun Small but it doesn't work as it should .. I installed dev version of linuxwacom driver but tablet is as "second mouse" .. it move only if I put pen directly on the tablet atc. I tried this howto and http://gentoo-wiki.com/HOWTO_Wacom_Tablet too but withnout success .. any help appreciated

[mellofone]

Isn't that how it is supposed to work?

[SupuS]

Isn't that how it is supposed to work?

Not exactly .. If I move pen above the tablet than cursor not move .. only if I put pen directly to tablet .. I tried this in Vista too and if I move pen above tablet so cursor move too. I set "mode absolute" in Gentoo and also in Vista so I supposed it will be same .. but it isn't

[mellofone]

Interesting, I didn't have to mess with it at all. What version of the -dev are you using? What does dmesg show right at the time you plug the tablet in?

[red-wolf76]

Isn't that how it is supposed to work?

In "relative mode", yes. But in "absolute" mode it should move the cursor to the position on the board.

I've so far only managed to do that in GDM with my Bamboo One. Xorg/Gnome still crashes when I log in.

Today is the company holiday do, so I'll probably be too knackered tonight, but I'll try to remember to post my setup here.

[SupuS]

2red-wolf76: It will be great

Interesting, I didn't have to mess with it at all. What version of the -dev are you using? What does dmesg show right at the time you plug the tablet in?

Yes it is interesting I use latest dev version 0.7.9-4 .. in fury I mixed this howto and howto on gentoo-wiki .. so it can be some stupid typo .. but I don't think so ..
Gimp don't show the "stylus" thing as described in this howto too ..

my related xorg lines:

Code: Select all

Section "InputDevice"
    Driver        "wacom"
    Identifier    "stylus"
    Option        "Device"       "/dev/input/wacom"
    Option        "Type"         "stylus"
    Option        "USB"          "on"                 # USB ONLY
    Option        "Mode"         "Absolute"           # other option: "Absolute"
    Option        "Vendor"       "WACOM"
    Option        "tilt"         "on"  # add this if your tablet supports tilt
    Option        "Threshold"    "5"   # the official linuxwacom howto advises this line
EndSection

Section "InputDevice"
    Driver        "wacom"
    Identifier    "eraser"
    Option        "Device"       "/dev/input/wacom"
    Option        "Type"         "eraser"
    Option        "USB"          "on"                  # USB ONLY
    Option        "Mode"         "Absolute"            # other option: "Absolute"
    Option        "Vendor"       "WACOM"
    Option        "tilt"         "on"  # add this if your tablet supports tilt
    Option        "Threshold"    "5"   # the official linuxwacom howto advises this line
EndSection

Section "InputDevice"
    Driver        "wacom"
    Identifier    "cursor"
    Option        "Device"       "/dev/input/wacom"
    Option        "Type"         "cursor"
    Option        "USB"          "on"                  # USB ONLY
    Option        "Mode"         "Absolute"            # other option: "Absolute"
    Option        "Vendor"       "WACOM"
EndSection

dmesg:

Code: Select all

usb 3-2: new full speed USB device using uhci_hcd and address 3
usb 3-2: configuration #1 chosen from 1 choice
input: Wacom BambooFun 4x5 as /class/input/input6

and proc:

Code: Select all

T:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=056a ProdID=0017 Rev= 1.13
S:  Manufacturer=Wacom Co.,Ltd.
S:  Product=CTE-450
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 60mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=wacom
E:  Ad=81(I) Atr=03(Int.) MxPS=   9 Ivl=4ms

[mellofone]

That is about identical to my setup, without the Absolute setting. However, the fun models do not support tilt. Try removing that just as a test.

[SupuS]

That is about identical to my setup, without the Absolute setting. However, the fun models do not support tilt. Try removing that just as a test.

I tried with Relative setting and without this Option but it is same .. maybe wrong X version? I have xorg-x11 7.2 .. Xorg -version shows:

Code: Select all

X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.23-gentoo-r4 x86_64
Current Operating System: Linux supus 2.6.23-gentoo-r4 #3 SMP PREEMPT Tue Dec 18 14:54:11 CET 2007 x86_64
Build Date: 18 December 2007  04:07:43PM

If I test functions by ~/linuxwacom/src/util/wacdump /dev/input/wacom everything works as expected .. move above the tablet etc.

[SupuS]

I configure, make and make install whole thing again and after restart X it works .. I hope that after reboot too ..
before I used prebuild version of wacom_drv.so and it was not compatible with my Xorg
Now it works as I expected Thank a lot for your help .. I'll back if pad will not work

[red-wolf76]

Great to hear...

Here's my setup anyways, since I've not yet gotten my "One" to properly function under Gnome.

I'm using a slightly modified linuxwacom-0.7.8_p3. Modifications include putting a line in the tarball that will tell the driver to address the Bamboo One as a Graphire (which it apparently is, under the hood). As already mentioned, it works flawlessly in GDM, but crashes Gnome, so it's probably some Gnome issue.

Code: Select all

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0"  "CoreKeyboard"
    InputDevice    "Mouse0"     "CorePointer"
    InputDevice    "stylus"     "SendCoreEvents"
    InputDevice    "cursor"     "SendCoreEvents"
EndSection

Section "Files"
#    RgbPath         "/usr/lib/X11/rgb"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "ServerFlags"
    Option         "Xinerama" "0"
EndSection

Section "InputDevice"
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "CorePointer"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/input/mice"
    Option         "Resolution" "1200"
    Option         "Buttons" "8"
    Option         "ZAxisMapping" "7 8"
    Option         "Emulate3Buttons" "false"
    #Option         "Emulate3Timeout" "50"
EndSection

Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
    Option         "CoreKeyboard"
    Option         "XkbRules" "xorg"
    Option         "XkbModel" "logidmd"
    Option         "XkbLayout" "de"
    Option         "XkbVariant" "deadgraveacute"
EndSection

Section "InputDevice"
     Driver        "wacom"
     Identifier    "stylus"
     Option        "Device"       "/dev/input/wacom-bamboo-one"
     Option        "Type"         "stylus"
     Option        "USB"          "on"                 # USB ONLY
     Option        "Mode"         "Absolute"           # other option: "Relative"
     Option        "Vendor"       "WACOM"
#     Option        "tilt"         "on"  # add this if your tablet supports tilt
     Option        "Threshold"    "5"   # the official linuxwacom howto advises this line
EndSection

Section "InputDevice"
     Driver        "wacom"
     Identifier    "cursor"
     Option        "Device"       "/dev/input/wacom-bamboo-one"
     Option        "Type"         "cursor"
     Option        "USB"          "on"                  # USB ONLY
     Option        "Mode"         "Relative"            # other option: "Absolute"
     Option        "Vendor"       "WACOM"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "LG"
    ModelName      "FLATRON L2000CE"
    HorizSync       28.0 - 83.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
    ModeLine "1400x1050" 121.75  1400 1488 1632 1864  1050 1053 1057 1089 +hsync +vsync
EndSection

Section "Device"
    Identifier     "Videocard0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 7600 GS"
#    Option         "ModeValidation" "NoDFPNativeResolutionCheck"
#    Option         "ExactModeTimingsDVI" "true" 
    Option         "RenderAccel" "true"
#    Option        "AddARGBGLXVisuals" "true"
#    Option        "DisableGLXRootClipping" "true"
    Option         "AllowGLXWithComposite" "true"
    Option         "NoLogo" "true"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Videocard0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "MetaModes" "1400x1050 1280x1024 1024x768 640x480"
    SubSection     "Display"
        Depth       24
        Modes      "1400x1050"
    EndSubSection
EndSection

Section "Extensions"
    Option         "Composite" "Enable"
    Option         "RENDER"    "Disable"
EndSection

[Ray ishido]

hi all,

is the last version of the drivers (2.8.3) support Xorg 1.4?

thanks

[csim]

Hi CRV§ADER//KY and all,

i'd like to ask a few questions:

1. do i need to enable wacom USE flag for xorg-server ? I suppose i don't have to if i install linuxwacom drivers?
2. when installing ALSA separately it is recomended to disable ALSA modules in the kernel...would it work if i disabled Wacom in the kernel config entirelywhen installing linuxwacom drivers? Somewhere i have read that the kernel module was present in linuxwacom package only until 2.6.17, is that true?
3. someone reported that with xorg-server 1.4 it's impossible to draw in GIMP/Inkscape (i have that problem too).... has this issue been reported to the devs?Does anyone know? *EDIT* I can confirm that by downgrading to 1.3 it started to work again..while googling i found a msg from the linuxwacom project author, that 1.4 isn't supported yet, this was from sept 07 IIRC.

[red-wolf76]

Hi CRV§ADER//KY and all,

i'd like to ask a few questions:

1. do i need to enable wacom USE flag for xorg-server ? I suppose i don't have to if i install linuxwacom drivers?
2. when installing ALSA separately it is recomended to disable ALSA modules in the kernel...would it work if i disabled Wacom in the kernel config entirelywhen installing linuxwacom drivers? Somewhere i have read that the kernel module was present in linuxwacom package only until 2.6.17, is that true?
3. someone reported that with xorg-server 1.4 it's impossible to draw in GIMP/Inkscape (i have that problem too).... has this issue been reported to the devs?Does anyone know? *EDIT* I can confirm that by downgrading to 1.3 it started to work again..while googling i found a msg from the linuxwacom project author, that 1.4 isn't supported yet, this was from sept 07 IIRC.

Cheers,

To answer your questions (as best I can)

(2) You could think so, but I think that the linuxwacom driver in fact replaces the kernel module, so after building a new kernel, it is wise to remerge linuxwacom-drivers as well. As for the wacom USE-flag (1), I'm not completely sure, but I think that it needs to be enabled to allow components that allow communication with the driver to work.

As for (3), I have xorg 1.4 and it works, albeit only in GDM, and the server bails when I start Gnome. I have a Wacom Bamboo One, so I'll sadly have to wait some more until a newer driver version makes it into portage or I can be arsed to learn enough about ebuilds to craft my own overlay... Even so, the prospect of finding out which patches to include, abhors me. I'm not a programmer, sadly, and don't have the time to become one.

[CRV§ADER//KY]

updated to linux-2.6.24. No more overlays... yeppie.

[wah_wah_69]

Hi you all, I recently purchased a wacom bamboo fun (the A6 sized one). It works in windows but I haven't been able to make it to work in linux.

I followed http://gentoo-wiki.com/HOWTO_Wacom_Tablet without success. the wacom event file is never created.

I updated to kernel 2.6.24 , added the intuos/graphire driver as module, event interface is compiled and working (my gamepad shows just fine).

The module is loaded without errors output of dmesg:

Code: Select all

eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
usbcore: registered new interface driver wacom
drivers/input/tablet/wacom_sys.c: v1.47:USB Wacom Graphire and Wacom Intuos tablet driver

lsusb lists it

Code: Select all

thisbox kk # lsusb 
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 004: ID 045e:0202 Microsoft Corp. Xbox Controller
Bus 001 Device 003: ID 045e:001c Microsoft Corp. 
Bus 001 Device 002: ID 056a:0017 Wacom Co., Ltd 
Bus 001 Device 001: ID 0000:0000  

I emerged xorg-server with:

Code: Select all

 INPUT_DEVICES="keyboard mouse wacom joystick" emerge xorg-server 

I created the 10-local.rules with:

Code: Select all

 KERNEL=="event*", SYSFS{idVendor}=="056a", NAME="input/%k", SYMLINK="input/wacom"

But noticed there was also a file called 60-wacom.rules Wich I suppouse was created by linux-wacom ebuild I have 0.78 installed since the wiki says you don't need the dev version if you're running a 2.6.24 kernel.

Code: Select all

# udev rules for wacom tablets.
# These rules were compiled for the Debian GNU/Linux distribution,
# but others may, and indeed are encouraged to, use them also.
#
# Should you do so, PLEASE CO-ORDINATE ANY CHANGES OR ADDITIONS
# of new devices with Ron <ron@debian.org> so that we can try
# to present users with with a standard set of device nodes
# which they can rely on across the board.

# Convenience link for the common case of a single tablet.
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYMLINK="input/wacom"

# Type-named links for multiple tablets.  If you want to use multiple
# tablets of the _same_ type, you will probably need to use the links
# from /dev/input/by-path to identify which is plugged into what usb
# port.  For different types though, just pick your links from the
# list below.
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0000", SYMLINK+="input/tablet-penpartner"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0010", SYMLINK+="input/tablet-graphire"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0011", SYMLINK+="input/tablet-graphire2-4x5"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0012", SYMLINK+="input/tablet-graphire2-5x7"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0013", SYMLINK+="input/tablet-graphire3"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0014", SYMLINK+="input/tablet-graphire3-6x8"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0015", SYMLINK+="input/tablet-graphire4-4x5"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0016", SYMLINK+="input/tablet-graphire4-6x8"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0060", SYMLINK+="input/tablet-volito"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0061", SYMLINK+="input/tablet-penstation2"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0062", SYMLINK+="input/tablet-volito2-4x5"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0063", SYMLINK+="input/tablet-volito2-2x3"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0064", SYMLINK+="input/tablet-penpartner2"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0020", SYMLINK+="input/tablet-intuos-4x5"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0021", SYMLINK+="input/tablet-intuos-6x8"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0022", SYMLINK+="input/tablet-intuos-9x12"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0023", SYMLINK+="input/tablet-intuos-12x12"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0024", SYMLINK+="input/tablet-intuos-12x18"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0030", SYMLINK+="input/tablet-pl400"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0031", SYMLINK+="input/tablet-pl500"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0032", SYMLINK+="input/tablet-pl600"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0033", SYMLINK+="input/tablet-pl600sx"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0034", SYMLINK+="input/tablet-pl550"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0035", SYMLINK+="input/tablet-pl800"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0037", SYMLINK+="input/tablet-pl700"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0038", SYMLINK+="input/tablet-pl510"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0039", SYMLINK+="input/tablet-dtu710"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="00C0", SYMLINK+="input/tablet-dtf521"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="00C4", SYMLINK+="input/tablet-dtf720"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0003", SYMLINK+="input/tablet-cintiq_partner"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0041", SYMLINK+="input/tablet-intuos2-4x5"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0042", SYMLINK+="input/tablet-intuos2-6x8"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0043", SYMLINK+="input/tablet-intuos2-9x12"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0044", SYMLINK+="input/tablet-intuos2-12x12"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0045", SYMLINK+="input/tablet-intuos2-12x18"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="00B0", SYMLINK+="input/tablet-intuos3-4x5"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="00B1", SYMLINK+="input/tablet-intuos3-6x8"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="00B2", SYMLINK+="input/tablet-intuos3-9x12"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="00B3", SYMLINK+="input/tablet-intuos3-12x12"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="00B4", SYMLINK+="input/tablet-intuos3-12x19"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="00B5", SYMLINK+="input/tablet-intuos3-6x11"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="003F", SYMLINK+="input/tablet-cintiq21ux"
KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", SYSFS{idProduct}=="0047", SYMLINK+="input/tablet-intuos2-6x8a"

# Check and repossess the device if a module other than the wacom one
# is already bound to it.

KERNEL=="event[0-9]*", SYSFS{idVendor}=="056a", ACTION=="add", RUN+="/lib/udev/check_driver wacom $devpath $env{ID_BUS}"

Should I add the line to the 60-wacom.rules with the correct Product id?


Since calling udevstart didn't seem to add the /dev/input/wacom file I updated the latest udev version in portage sys-fs/udev-118 right after that the udevstart command wasn't available anymore.

What am I missing?

[red-wolf76]

Wah_wah: What does lsusb tell you about the tablet? I have a Bamboo One (not "Fun") which needs some tweaking in the driver, as it secretly uses the graphire hardware specs, apparently. Long story short, I've managed to get it to work in GDM, but it crashes Xorg upon logging in. Haven't yet tried the new kernel with it though.

[wah_wah_69]

Wah_wah: What does lsusb tell you about the tablet? I have a Bamboo One (not "Fun") which needs some tweaking in the driver, as it secretly uses the graphire hardware specs, apparently. Long story short, I've managed to get it to work in GDM, but it crashes Xorg upon logging in. Haven't yet tried the new kernel with it though.

ls usb lists it just fine , see my previous message:

Bus 001 Device 002: ID 056a:0017 Wacom Co., Ltd

[red-wolf76]

D'OH! It surely would help if I could read...

If you look in the list, you'll find that 056a:0017 isn't included in the udev rules file as such. But it maybe that it is internally identical to another. My Bamboo one has 056a:0069 and is a graphire, as I found out here (link in German, sorry, but there's another link to an english source and some of the commands might prove helpful).

In the end, I tweaked the driver sources before compilation and put it into an overlay. Still gotta try 2.6.24, though.

[wah_wah_69]

D'OH! It surely would help if I could read...

If you look in the list, you'll find that 056a:0017 isn't included in the udev rules file as such. But it maybe that it is internally identical to another. My Bamboo one has 056a:0069 and is a graphire, as I found out here (link in German, sorry, but there's another link to an english source and some of the commands might prove helpful).

In the end, I tweaked the driver sources before compilation and put it into an overlay. Still gotta try 2.6.24, though.

Das ist gut!
It was me actually the one who's not paying attention

The Wiki asks you to run the command

Code: Select all

cat /proc/bus/usb/devices | grep -A5 056a | grep Driver | grep wacom

But as I wasn't getting any output I simply checked cat /proc/bus/usb/devices output and didn't noticed that the device is using no driver.

Code: Select all

mybox io # lsmod
Module                  Size  Used by
wacom                  15744  0 
nvidia               4703408  22 
8250_pnp                9216  0 
8250                   19980  1 8250_pnp
serial_core            17792  1 8250

mybox io # lsusb
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 005: ID 056a:0017 Wacom Co., Ltd 
Bus 001 Device 004: ID 045e:0202 Microsoft Corp. Xbox Controller
Bus 001 Device 003: ID 045e:001c Microsoft Corp. 
Bus 001 Device 001: ID 0000:0000  


thisbox me # cat /proc/bus/usb/devices | grep -A5 056a | grep Driver
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=(none)

dmesg output: 
drivers/input/tablet/wacom_sys.c: v1.47:USB Wacom Graphire and Wacom Intuos tablet driver
Since the wiki says the dev version 1.46.something included bamboo support I supouse it's no issue with the driver.

Code: Select all

cat /proc/bus/inpI: Bus=0019 Vendor=0000 Product=0002 Version=0000
N: Name="Power Button (FF)"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button (CM)"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/virtual/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=045e Product=0202 Version=0100
N: Name="Microsoft X-Box pad v1 (US)"
P: Phys=usb-0000:00:02.0-2.1/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb1/1-2/1-2.1/1-2.1:1.0/input/input3
U: Uniq=
H: Handlers=js0 event3 
B: EV=20000b
B: KEY=683f0000 400000 0 0 0 0 0 0 0 0
B: ABS=3003f
B: FF=1 7030000 0 0

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input4
U: Uniq=
H: Handlers=kbd event4 
B: EV=40001
B: SND=6

I: Bus=0011 Vendor=0002 Product=0006 Version=0000
N: Name="ImExPS/2 Generic Explorer Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
U: Uniq=
H: Handlers=mouse0 event5 
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=143
ut/devices 

So the tablet is not being controlled by any driver ,although the wacom module from the 2.6.24 kernel is loaded.


tail -f /var/log/messages output when unplugged and plugged again:

Code: Select all

Jan 30 15:15:09 mybox usb 1-1: USB disconnect, address 6
Jan 30 15:15:12 mybox usb 1-1: new full speed USB device using ohci_hcd and address 7
Jan 30 15:15:12 mybox usb 1-1: configuration #1 chosen from 1 choice

[acasto]

Wah_wha: Hey, I came across your post while looking in the exact same problem under Debian (unstable branch, kernel 2.6.24). Anyways, I made a bit of headway and thought I'd let you know what seemed to help me. In the krenel source, look at, drivers/input/tablet/wacom_wac.c, particularly where this part starts:

Code: Select all

static struct usb_device_id wacom_ids[] = {
        { USB_DEVICE(USB_VENDOR_ID_WACOM, 0x00) },
        { USB_DEVICE(USB_VENDOR_ID_WACOM, 0x10) },
        { USB_DEVICE(USB_VENDOR_ID_WACOM, 0x11) },
        { USB_DEVICE(USB_VENDOR_ID_WACOM, 0x12) },
        { USB_DEVICE(USB_VENDOR_ID_WACOM, 0x13) },

...at least for me, the Bamboo Fun product id of 0x17 wasn't listed. Copying a line and changing the id to 0x17 (then recompiling the kernel) got the tablet manged by the wacom driver for me, however it was coming up as a Wacom Volito tablet. Through trial and error I found that if I moved the Bamboo entries above the Volito entry under wacom_features[] (see below), it correctly detected it as the BambooFun:

Code: Select all

static struct wacom_features wacom_features[] = {
        { "Wacom Penpartner",    7,   5040,  3780,  255,  0, PENPARTNER },
        { "Wacom Graphire",      8,  10206,  7422,  511, 63, GRAPHIRE },
        { "Wacom Graphire2 4x5", 8,  10206,  7422,  511, 63, GRAPHIRE },
        { "Wacom Graphire2 5x7", 8,  13918, 10206,  511, 63, GRAPHIRE },
        { "Wacom Graphire3",     8,  10208,  7424,  511, 63, GRAPHIRE },
        { "Wacom Graphire3 6x8", 8,  16704, 12064,  511, 63, GRAPHIRE },
        { "Wacom Graphire4 4x5", 8,  10208,  7424,  511, 63, WACOM_G4 },
        { "Wacom Graphire4 6x8", 8,  16704, 12064,  511, 63, WACOM_G4 },
        { "Wacom BambooFun 4x5", 9,  14760,  9225,  511, 63, WACOM_MO },
        { "Wacom Volito",        8,   5104,  3712,  511, 63, GRAPHIRE },
        { "Wacom PenStation2",   8,   3250,  2320,  255, 63, GRAPHIRE },
        { "Wacom Volito2 4x5",   8,   5104,  3712,  511, 63, GRAPHIRE },
        { "Wacom Volito2 2x3",   8,   3248,  2320,  511, 63, GRAPHIRE },
        { "Wacom PenPartner2",   8,   3250,  2320,  255, 63, GRAPHIRE },

Okay, I just took a minute and tested it with wacdump and it does seem to properly pickup and detect everything. Anyways, I never got around to learning C, so I don't really know why this works (I assume the ID missing had a lot to do with it ), but it seems to do the trick. Hope this helps.

[wah_wah_69]

Thanks !

I never thought about looking at the driver source as the wiki claimed 2.6.24 had bamboo support out of the box.


The wacom_features wacom struct did have the bamboo info but as you told the id's struct was missing 0x17 , the id of the bamboo fun.

Changed 64 for 17 in the 14th line of the id struct (the bamboo features was the 14th in the features struct).

And now the dev file is created I can see the raw data with cat.

Now all that is left for me is adding it to the xorg.conf file.

[acasto]

Changed 64 for 17 in the 14th line of the id struct (the bamboo features was the 14th in the features struct).

Ahh... that's how they are related. I didn't think about order. I couldn't figure out how it was picking an entry out of the features structure. Thanks for the info!