Originally Posted by
johnny2k
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 vendor
roduct 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:
Code:
# tail -f /var/log/Xorg.0.log -f|grep 'button=[0-9]'
which produced:
Code:
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
Bookmarks