New Wacom Bamboo not working

[Favux]

Hi kgingeri,

At this point I think you have it working well enough to use 'wacomcpl' the LWP's calibration and settings gui. Type 'wacomcpl' in a terminal and it pops up. To set it up see "Section 3: Calibrating your Tablet" here: http://ubuntuforums.org/showthread.php?t=1038949 Let's see if the pressure curve it generates helps with pressure. And if you can map buttons. And right now you may be in 'hover' mode.

[kgingeri]

Wow. I really should have checked for a thread like this before going out and getting a Bamboo Craft about 3 hours ago. It has a vendorroduct of 056a:00d2 so this should help me and as soon as I catch up to how far it has come I will help if I can. Iḿ was considering taking it back and getting a less expensive one that has better support but it seems like this should be working pretty well in not too long.

@jJohnn2k: Yeah, welcome! Start at post #102 and don't bother with the fdi stuff. In fact your better off ignoring the 40-xserver-xorg-input-wacom.rules and moving the 10-wacom.fdi to your home directory if it exists and has content. Use the 'locate' command to find these. Where you see me us d4 or D4 use d2 (case isn't important).

When we're satified the driver is work as it should we'll get a patch off to linuxwacom for it but you'll still need to tweek X as shown here.

Of course, stay tuned

@Favux, with debug at level 7 I did:

# tail -f /var/log/Xorg.0.log -f|grep 'button=[0-9]'

which produced:

sendAButton TPCButton(off) button=0 state=1 code=00000001, for stylus coreEvent=no 
sendAButton TPCButton(off) button=0 state=0 code=00000001, for stylus coreEvent=no 
sendAButton TPCButton(off) button=0 state=1 code=00000001, for stylus coreEvent=no 
sendAButton TPCButton(off) button=0 state=0 code=00000001, for stylus coreEvent=no 
sendAButton TPCButton(off) button=2 state=4 code=00000002, for stylus coreEvent=no 
sendAButton TPCButton(off) button=2 state=0 code=00000002, for stylus coreEvent=no 
sendAButton TPCButton(off) button=0 state=1 code=00000001, for stylus coreEvent=no 
sendAButton TPCButton(off) button=2 state=4 code=00000002, for stylus coreEvent=no 
sendAButton TPCButton(off) button=2 state=0 code=00000002, for stylus coreEvent=no 
sendAButton TPCButton(off) button=0 state=0 code=00000001, for stylus coreEvent=no

..for taping and clicking on and off the pad. Looks like X "Button1" - button=0

[kgingeri]

At this point I think you have it working well enough to use 'wacomcpl' the LWP's calibration and settings gui. Type 'wacomcpl' in a terminal and it pops up. To set it up see "Section 3: Calibrating your Tablet" here: http://ubuntuforums.org/showthread.php?t=1038949 Let's see if the pressure curve it generates helps with pressure. And if you can map buttons. And right now you may be in 'hover' mode.

Nope - still get...

can't read "isLCD(212)": no such element in array
can't read "isLCD(212)": no such element in array
    while executing
"if { ![ string compare $type "pad" ] } {
	    if { $hasPad($model) } {
		createPanel 0 1 0 0
	    }
	} elseif { ![ string compare $type "touch" ] } {
..."
    (procedure "updateDevice" line 24)
    invoked from within
"updateDevice"
    (command bound to event)

...from wacomcpl What's with the "pad" stuff?! Don't have it defined anywhere - or is that the problem maybe?

Gonna reboot and try again.

EDIT: BTW "xinput -l" gives...

Virtual core pointer           disabled
Virtual core keyboard          keyboard
stylus                         extension
eraser                         extension
AT Translated Set 2 keyboard   extension
Video Bus                      extension
Macintosh mouse button emulation extension
Microsoft Compact Optical Mouse 500 extension
SynPS/2 Synaptics TouchPad     extension
EVTouch TouchScreen            extension
Wacom Bamboo Pen 4x5           extension
Wacom Bamboo Pen 4x5           extension

[Favux]

OK, don't know what that means.

I may be totally confabulating the following. It seems I have a dim memory of Xorg changing how Xinput did mapping of buttons. Changing 1 to 0 rings a dim bell? And Tom Jaeger submitting a patch (to LWP?) called something like "don't mess with my buttons". Maybe around February? If any of that is even close to right maybe it suggests we still aren't quite picking up the linuxwacom driver right?

Any luck with wacomcpl/.xinitrc?

Edit: OK, wacomcpl not working does go along with the driver still isn't locking in quite right. Pad stuff makes no sense.

[Favux]

Hi kgingeri,

Alright, found it in January (or something similar). See: http://sourceforge.net/mailarchive/f...nuxwacom-devel The patch applies to 'wcmCommon.c' in "linuxwacom-0,8.x/src/xdrv/". And in there, there seems to be a table of stylus serial number ID's at about line 1364. Not sure if any of this applies. Also whether it is relevant that pad id is mentioned too.

Maybe we should see if the stylus is returning a serial number:

xsetwacom get stylus ToolSerial

[kgingeri]

Man something weird. X wasn't locking up, there was a very small popup window and if I clicked again on the xterm I had data - ONLY FOR A BIT - then it stop (I even saw some button3 up/down events but couldn't reproduct them). Now I get nothing - not in X - the LED on the tablet doesn't go bright on a button press like usual, nothing. Not even afte a reboot plug/unplug!!

Gonna check my tablet on my Mac - very weird!

I didn't notice if I was getting pressure or not

I'll check my tablet, reboot again with it unplugged too. I tried to re-enable the 40-xserver... line but nothing either. I was in Gimp messin with Linux Xinput settings so I put those all back. I got caught changing too much at once and I don't usually do that!

I do want to know if it's driver stuff before I bother to get a patch to Ping tho.

I won't be at it for much longer and I'll have to leave it again, but I'll get back once more at least...

[kgingeri]

Ok - all is well again. A reboot with it disconnected did it. whew!

Still get wonky graphics tho. That, and my Mac reports the upper press on the stylus as button 3 no problem!! These two things make me think I should mess with driver stuff again. I may have to do that and see what I get.

xsetwacom get stylus ToolSerial just returns "0"...

root@kganb:~# xsetwacom get stylus ToolSerial
0

BTW all docs are for Windows/Mac and are electronic. Might try xidump just to check for pressure too.

Anyway, probably enough for now.

Summary is:
No fdi defs at all and only stylus in xorg.conf which is now (ignore TouchKit stuff):

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# Note that some configuration settings that could be done previously
# in this file, now are automatically configured by the server and settings
# here are ignored.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#
#   sudo dpkg-reconfigure -phigh xserver-xorg
#
Section "Device"
	Identifier  "Videocard"
#	Driver      "intel"
#	VendorName  "Intel Corporation"
#	BoardName   "Mobile 945GME Express Integrated Graphics Controller"
EndSection

Section "Monitor"
	Identifier  "Monitor"
EndSection

Section "Screen"
	Identifier	"Screen"
EndSection

### TouchKit start
Section "InputDevice"
	Identifier      "EETI"
	Driver          "egalax"
	Option          "Device" "usbauto"
	Option          "Parameters" "/var/lib/eeti.param"
	Option          "ScreenNo" "0"
	Option          "SkipClick" "1"
EndSection
### TouchKit end

### Wacom start
#  see http://linuxwacom.sourceforge.net/index.php/howto/inputdev for details
#  or 'man wacom'
#
Section "InputDevice"
	Identifier	"stylus"
	Driver		"wacom"
	Option		"Device"      "/dev/input/wacom"
	Option		"Type"        "stylus"
	Option		"USB"         "on"
	Option 		"Mode"        "Absolute" # ...in relation to screen (default is abs)
	Option 		"KeepShape"   "on"	 # ...conform to screen size
	Option		"Button1"     "1"
	Option		"Button2"     "3"	 # ...seems my buttons are mixed?
	Option		"Button3"     "2"
	Option		"Threshold"   "1"	 # ...presure required for event button1
	Option		"Num_buttons" "2"	 # ...seems to be 32 by default!
	Option		"ButtonsOnly" "off"	 # ...TEMPORARY: "on" for trouble shooting
	Option		"DebugLevel"  "7" 
	# Option 	"commonDBG"   "3"	 # ...driver debug
EndSection

Section "InputDevice"
	Identifier	"eraser"
	Driver		"wacom"
	Option		"Device" "/dev/input/wacom" # .../dev/input/event<n> instead maybe?
	Option		"Type"   "eraser"
	Option		"USB"	 "on"
EndSection
### Wacom end

Section "ServerLayout"
	Identifier      "Default Layout"
	Screen          0 "Screen" 0 0
	Option		"DontZap" "false"
### TouchKit start
	InputDevice     "EETI" "SendCoreEvents"
### TouchKit end
### Wacom start
	InputDevice     "stylus" "SendCoreEvents"
	InputDevice     "eraser" "SendCoreEvents"
### Wacom end
EndSection

'night

EDIT: Ok, had to try xidump. Nope no pressure, tilt or anything other then X/Y and buttons 1 and 2.

[Favux]

Hi kgingeri,

Glad it's working again. And you've ruled out hardware problems. Always good. Lot's of ground covered.

My idea, such as it is, was to approach it like you would trying to set up two or more styli on your tablet. First you enter in a terminal:

xsetwacom set Stylus0 CommonDBG 6

After using the stylus on the tablet check "/var/log/Xorg.0.log" and see what it says the serial number is. Then add it to the stylus and eraser sections in xorg.conf:

Option        "Serial"        "<serial #>"

See if that forces the driver to recognize it. And you'd have to enable it in Gimp too. As a side note I think the serial number in Xorg.0.log doesn't agree with the one in wacomcpl for some reason.

Maybe try commenting out the eraser section and line in "ServerLayout" while checking out the buttons?

Good night.

[johnny2k]

Favux: Thanks! I really enjoy this site.

It's cool that this thread was opened less than a week ago and so much progress has been made.

I thought I'd be able to get farther than I have but I'm a little stuck. Maybe I'm more of a noob than I thought because I can't even get the driver to compile. Check this out. I normally use the 2.6.28-3-rt kernel and I've also tried two different generic kernels but always get an error. First some info from

./configure --enable-wacom

----------------------------------------
  BUILD ENVIRONMENT:
       architecture - i486-linux-gnu
       linux kernel - yes 2.6.28
  module versioning - no 
      kernel source - yes /lib/modules/2.6.28-15-generic/build
     XFree86 source - no 
           Xorg SDK - yes /usr/include/xorg
          XSERVER64 - no
           dlloader - yes
               XLib - yes /usr/lib
         xf86config - no
                TCL - yes /usr/include/tcl8.4
                 TK - yes /usr/include/tcl8.4
            ncurses - yes

  BUILD OPTIONS:
            wacom.o - yes
            wacdump - yes 
             xidump - yes 
        libwacomcfg - yes
         libwacomxi - yes
          xsetwacom - yes
              hid.o - no 
       wacom_drv.so - yes /usr/lib/xorg/modules/input 
        wacom_drv.o - no
  wacom*_drv quirks - Uninit-called IsXExtensionPointer key-events dixScreenOrigins
----------------------------------------

I've specified the build directory and tried each one I have but always get this error when making...

 Building linuxwacom drivers for 2.6 kernel.
***Note: Drivers not enabled as modules in your kernel config but requested through configure are NOT built

Has anyone else run into this error before?

[Favux]

Hi johnny2k,

Thank you for your kind words. I think kgingeri and Ayuthia and the rest have done awesome work.

Did you install the linux-headers for the kernel? See this HOW TO: http://ubuntuforums.org/showthread.php?t=1038949