Wacom Bamboo Pen and Touch Series Development

[GolemdX]

16 Nov, 2009 Report #2
(patch 27 | ob1kenobi's FDI)

What I gather...

• Nothing Works.

Correct?

Additional Information: Is it just me, or is NOTHING working?

[kgingeri]

Ok, so I think I am squeaky clean and have patch 27 and ob1's fdi from Post #1 (not ob1-fav yet - that's next) and I've attached sample log data. I have NO touch or stylus at this point!? Looks like I do have stylus data only too.

I'm a bit concerned tho, as others seemed to be getting different result then I was. For some reason I'm not sure you should trust these results. Just intuition tho - like I said I've done what I think is a very clean rebuild...

EDIT: Hmmmm - I feel better, just refreshed the page and saw GolemdX's results

[Ayuthia]

Ok, so I think I am squeaky clean and have patch 27 and ob1's fdi from Post #1 (not ob1-fav yet - that's next) and I've attached sample log data. I have NO touch or stylus at this point!? Looks like I do have stylus data only too.

I'm a bit concerned tho, as others seemed to be getting different result then I was. For some reason I'm not sure you should trust these results. Just intuition tho - like I said I've done what I think is a very clean rebuild...

EDIT: Hmmmm - I feel better, just refreshed the page and saw GolemdX's results

Can you go into sys/2.6.28/wacom_wac.c and change the value of

#define WACOM_PKGLEN_BBPT

from 18 back to 20? Once you rebuild it, please let us know if the touch and pen values come back.

There is currently a bug with the packet length that has currently caused the data to report differently. ob1kenobi is planning on testing out a solution that looks promising.

[kgingeri]

Can you go into sys/2.6.28/wacom_wac.c and change the value of

#define WACOM_PKGLEN_BBPT

from 18 back to 20? Once you rebuild it, please let us know if the touch and pen values come back.

There is currently a bug with the packet length that has currently caused the data to report differently. ob1kenobi is planning on testing out a solution that looks promising.

Ayuthia, I have pen values again but I get a constant stream of the following in var messages:

Nov 16 22:11:01 kgulnb kernel: [  230.185028] [wacom-27] data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:11:01 kgulnb kernel: [  230.189029] [wacom-27] data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:11:01 kgulnb kernel: [  230.193040] [wacom-27] data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:11:01 kgulnb kernel: [  230.197021] [wacom-27] data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:11:01 kgulnb kernel: [  230.201025] [wacom-27] data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Nothing for touch on Xorg and this for pen (not eraser) in Xorg:

xf86WcmReadPacket: device=/dev/input/event9 fd=12 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=12 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=12 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=12 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=12 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240

UPDATE: xinput and xsetwacom...

$ xinput --list --short
"Virtual core pointer"	id=0	[XPointer]
"Virtual core keyboard"	id=1	[XKeyboard]
"Wacom Bamboo P&T 4x5"	id=2	[XExtensionKeyboard]
"Wacom Bamboo P&T 4x5 cursor"	id=3	[XExtensionKeyboard]
"Power Button"	id=4	[XExtensionKeyboard]
"Acer Crystal Eye webcam"	id=5	[XExtensionKeyboard]
"Wacom Bamboo P&T 4x5"	id=6	[XExtensionKeyboard]
"AT Translated Set 2 keyboard"	id=7	[XExtensionKeyboard]
"Wacom Bamboo P&T 4x5 touch"	id=8	[XExtensionKeyboard]
"Video Bus"	id=9	[XExtensionKeyboard]
"Wacom Bamboo P&T 4x5 eraser"	id=10	[XExtensionKeyboard]
"Power Button"	id=11	[XExtensionKeyboard]
"Sleep Button"	id=12	[XExtensionKeyboard]
"Macintosh mouse button emulation"	id=13	[XExtensionPointer]
"SynPS/2 Synaptics TouchPad"	id=14	[XExtensionPointer]
"Microsoft Compact Optical Mouse 500"	id=15	[XExtensionPointer]
$ xsetwacom list dev

[Ayuthia]

Ayuthia, I have pen values again but I get a constant stream of the following in var messages:

Nov 16 22:11:01 kgulnb kernel: [  230.185028] [wacom-27] data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:11:01 kgulnb kernel: [  230.189029] [wacom-27] data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:11:01 kgulnb kernel: [  230.193040] [wacom-27] data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:11:01 kgulnb kernel: [  230.197021] [wacom-27] data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:11:01 kgulnb kernel: [  230.201025] [wacom-27] data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

]

This is with WACOM_PKGLEN_BBPT set to 20? I am just confirming because the info above only has 18 reported.

[Favux]

Hi everyone,

Maybe I should mention that something in 0.8.5-4 is broken. When I rotate the tablet the stylus, eraser, and touch don't rotate and remain messed up when I go back to laptop. I've been assuming it's the xsetwacom rotate commands. I haven't mentioned it before because it didn't seem relevant. But...

There's a faint chance this could affect those of you adding the HALF line to the .fdi to make the tablet left-handed. So maybe hold off on that for now.

[kgingeri]

This is with WACOM_PKGLEN_BBPT set to 20? I am just confirming because the info above only has 18 reported.

Ooops - I reran my script instead of manual compile (Duh!) - I should've check the data first.

Will try again and update this post...

UPDATE: OK, already have touch back just reloading wacom.ko - will reboot tho anyway and give you logs.

[kgingeri]

This is with WACOM_PKGLEN_BBPT set to 20? I am just confirming because the info above only has 18 reported.

OK, much better again. I have touch back (ver 27 ob1's fid - will try ob1-fav next)

Here's messages data...

Nov 16 22:53:01 kgulnb kernel: [  119.116665] [wacom-27] data: 02 00 45 80 dc 00 b6 80 d9 00 b3 00 00 00 00 00 81 11 00 00 
Nov 16 22:53:01 kgulnb kernel: [  119.136669] [wacom-27] data: 02 00 93 80 dc 00 b6 80 d9 00 b2 00 00 00 00 00 81 11 00 00 
Nov 16 22:53:01 kgulnb kernel: [  119.156660] [wacom-27] data: 02 00 93 80 dc 00 b4 80 d9 00 b1 00 00 00 00 00 81 11 00 00 
Nov 16 22:53:01 kgulnb kernel: [  119.176650] [wacom-27] data: 02 00 83 80 dd 00 b6 80 da 00 b2 00 00 00 00 00 81 11 00 00 
Nov 16 22:53:01 kgulnb kernel: [  119.192084] [wacom-27] data: 02 00 5b 80 dd 00 ba 80 da 00 b5 00 00 00 00 00 80 11 00 00 
Nov 16 22:53:01 kgulnb kernel: [  119.216645] [wacom-27] data: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

these msgs are not streaming now - just when there is activity - touch tap above....

Nov 16 22:54:13 kgulnb kernel: [  191.400532] [wacom-27] data: 02 80 00 00 00 00 00 00 00 02 80 00 00 00 00 00 00 00 02 80 
Nov 16 22:54:13 kgulnb kernel: [  191.416523] [wacom-27] data: 02 80 00 00 00 00 00 00 00 02 80 00 00 00 00 00 00 00 02 80 
Nov 16 22:54:14 kgulnb kernel: [  191.436498] [wacom-27] data: 02 80 00 00 00 00 00 00 00 02 80 00 00 00 00 00 00 00 02 00 
Nov 16 22:54:14 kgulnb kernel: [  191.452507] [wacom-27] data: 02 00 51 24 37 16 12 00 12 02 f1 43 24 32 16 9a 02 13 02 f1 
Nov 16 22:54:14 kgulnb kernel: [  191.464499] [wacom-27] data: 02 f1 3b 24 34 16 66 02 14 02 f1 3b 24 2f 16 0e 02 15 02 f1 
Nov 16 22:54:14 kgulnb kernel: [  191.480495] [wacom-27] data: 02 f1 46 24 2d 16 f8 01 15 02 f1 46 24 26 16 fc 01 16 02 f1 
Nov 16 22:54:14 kgulnb kernel: [  191.496486] [wacom-27] data: 02 f1 49 24 28 16 f9 01 16 02 f1 50 24 21 16 ed 01 16 02 f1 
Nov 16 22:54:14 kgulnb kernel: [  191.512479] [wacom-27] data: 02 f1 5a 24 1b 16 bb 01 17 02 f1 67 24 13 16 6f 01 17 02 f1 
Nov 16 22:54:14 kgulnb kernel: [  191.524469] [wacom-27] data: 02 f1 78 24 11 16 ff 00 17 02 f1 92 24 10 16 42 00 17 02 f0 
Nov 16 22:54:14 kgulnb kernel: [  191.540465] [wacom-27] data: 02 f0 a6 24 0e 16 00 00 17 02 f0 b4 24 0c 16 00 00 15 02 f0 
Nov 16 22:54:14 kgulnb kernel: [  191.556456] [wacom-27] data: 02 f0 b9 24 03 16 00 00 13 02 f0 be 24 f8 15 00 00 11 02 f0 
Nov 16 22:54:14 kgulnb kernel: [  191.572429] [wacom-27] data: 02 f0 bb 24 f3 15 00 00 0e 02 f0 ba 24 f4 15 00 00 0b 02 f0 
Nov 16 22:54:14 kgulnb kernel: [  191.584443] [wacom-27] data: 02 f0 b8 24 ee 15 00 00 08 02 f0 bb 24 e9 15 00 00 06 02 f0 
Nov 16 22:54:14 kgulnb kernel: [  191.596436] [wacom-27] data: 02 f0 af 24 d8 15 00 00 04 02 80 00 00 00 00 00 00 00 02 80 
Nov 16 22:54:14 kgulnb kernel: [  191.612424] [wacom-27] data: 02 80 00 00 00 00 00 00 00 02 80 00 00 00 00 00 00 00 02 80 
Nov 16 22:54:14 kgulnb kernel: [  191.628421] [wacom-27] data: 02 80 00 00 00 00 00 00 00 02 80 00 00 00 00 00 00 00 02 00 

that was pen tap  

[Nov 16 22:54:36 kgulnb kernel: [  213.725367] [wacom-27] data: 02 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:54:36 kgulnb kernel: [  213.877287] [wacom-27] data: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:54:37 kgulnb kernel: [  214.984739] [wacom-27] data: 02 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:54:37 kgulnb kernel: [  215.160653] [wacom-27] data: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:54:38 kgulnb kernel: [  215.680386] [wacom-27] data: 02 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:54:38 kgulnb kernel: [  215.856302] [wacom-27] data: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:54:39 kgulnb kernel: [  216.424013] [wacom-27] data: 02 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Nov 16 22:54:39 kgulnb kernel: [  216.551955] [wacom-27] data: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

that was all four buttons.

here is some from Xorg...

first touch...

xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 112 bytes
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 7 events received
usbParseChannel event[0]->type=3 code=0 value=234
usbParseChannel event[1]->type=3 code=1 value=143
usbParseChannel event[2]->type=3 code=24 value=149
usbParseChannel event[3]->type=3 code=40 value=3
usbParseChannel event[4]->type=1 code=333 value=1
USB Touch detected 14d (value=1)
usbParseChannel event[5]->type=1 code=330 value=1
usbParseChannel event[6]->type=0 code=0 value=0
xf86WcmEvent at channel = 0
xf86WcmEvent: c=0 i=3 t=2 s=0 x=234 y=143 b=1 p=149 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=1 st=402940 cs=0 
initialize Channel data.
commonDispatchDevice device type = 2
tool id=2 for Wacom Bamboo P&T 4x5 touch
xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 touch - usbParse: dropping empty event for serial 0
xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 touch - usbParse: dropping empty event for serial 0
xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 touch - usbParse: dropping empty event for serial 0
xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 touch - usbParse: dropping empty event for serial 0
xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 touch - usbParse: dropping empty event for serial 0
xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 touch - usbParse: dropping empty event for serial 0
xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 touch - usbParse: dropping empty event for serial 0
xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 touch - usbParse: dropping empty event for serial 0
xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 touch - usbParse: dropping empty event for serial 0
xf86WcmReadPacket: device=/dev/input/event10 fd=14 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 112 bytes
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 7 events received
usbParseChannel event[0]->type=3 code=0 value=0
usbParseChannel event[1]->type=3 code=1 value=0
usbParseChannel event[2]->type=3 code=24 value=0
usbParseChannel event[3]->type=3 code=40 value=0
usbParseChannel event[4]->type=1 code=333 value=0
USB Touch detected 14d (value=0)
usbParseChannel event[5]->type=1 code=330 value=0
usbParseChannel event[6]->type=0 code=0 value=0
xf86WcmEvent at channel = 0
xf86WcmEvent: c=0 i=3 t=2 s=0 x=0 y=0 b=0 p=149 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=0 st=403159 cs=1 
xf86WcmFilterCoord with common->wcmRawSample = 4 
xf86WcmSuppress at level = 2 return value = 1
commonDispatchDevice device type = 2
tool id=2 for Wacom Bamboo P&T 4x5 touch


and pen...

xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 64 bytes
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 4 events received
usbParseChannel event[0]->type=1 code=325 value=0
USB Pad detected 145 (value=0)
usbParseChannel event[1]->type=3 code=40 value=0
usbParseChannel event[2]->type=4 code=0 value=240
usbParseChannel event[3]->type=0 code=0 value=0
xf86WcmEvent at channel = 1
xf86WcmEvent: c=1 i=15 t=16 s=240 x=0 y=0 b=0 p=0 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=0 st=0 cs=2 
xf86WcmSuppress at level = 2 return value = 1
commonDispatchDevice device type = 16
no device matches with id=16, serial=240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 64 bytes
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 4 events received
usbParseChannel event[0]->type=1 code=325 value=1
USB Pad detected 145 (value=1)
usbParseChannel event[1]->type=3 code=40 value=15
usbParseChannel event[2]->type=4 code=0 value=240
usbParseChannel event[3]->type=0 code=0 value=0
xf86WcmEvent at channel = 1
xf86WcmEvent: c=1 i=15 t=16 s=240 x=0 y=0 b=0 p=0 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=1 st=0 cs=0 
initialize Channel data.
commonDispatchDevice device type = 16
no device matches with id=16, serial=240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 48 bytes
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 3 events received
usbParseChannel event[0]->type=1 code=257 value=1
usbParseChannel event[1]->type=4 code=0 value=240
usbParseChannel event[2]->type=0 code=0 value=0
xf86WcmEvent at channel = 1
xf86WcmEvent: c=1 i=15 t=16 s=240 x=0 y=0 b=2 p=0 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=1 st=0 cs=1 
xf86WcmSuppress at level = 2 return value = 1
commonDispatchDevice device type = 16
no device matches with id=16, serial=240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 48 bytes
usbParseEvent 
usbParseEvent 
usbParseEvent 
usbParseChannel 3 events received
usbParseChannel event[0]->type=1 code=257 value=0
usbParseChannel event[1]->type=4 code=0 value=240
usbParseChannel event[2]->type=0 code=0 value=0
xf86WcmEvent at channel = 1
xf86WcmEvent: c=1 i=15 t=16 s=240 x=0 y=0 b=0 p=0 rz=0 tx=0 ty=0 aw=0 rw=0 t=0 df=0 px=1 st=0 cs=2 
xf86WcmSuppress at level = 2 return value = 1
commonDispatchDevice device type = 16
no device matches with id=16, serial=240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
xf86WcmReadPacket: device=/dev/input/event9 fd=13 
xf86WcmReadPacket: pos=0 remaining=256
xf86WcmReadPacket buffer has 32 bytes
usbParseEvent 
usbParseEvent 
Wacom Bamboo P&T 4x5 eraser - usbParse: dropping empty event for serial 240
^C

UPDATE: ob1-fav fdi didn't seem to make any difference except I do have xsetwacom devices listed. However setting relative mode leaves the cursor stuck on the left side of my screen.

ALSO I am only able to navigate the mouse in the upper left quad of my screen. This is a 0xd1 tablet.

[Ayuthia]

I have removed a portion of a submitted patch in hopes that it will bring the packet data back to the way it was prior to all the data issues we have encountered today.

If this does not work, we will go back to patch 22 and start over.

I had to remove that patch because it seemed to cause more data to fill into the pen's report. This could cause issues with the TabletPC devices if we keep the code there.

By the way, this is patch 29. 28 was there, but I realized that I forgot to fix another portion of the pen code.

[ob1kenobi]

I have removed a portion of a submitted patch in hopes that it will bring the packet data back to the way it was prior to all the data issues we have encountered today.

If this does not work, we will go back to patch 21 again and start over.

I had to remove that patch because it seemed to cause more data to fill into the pen's report. This could cause issues with the TabletPC devices if we keep the code there.

By the way, this is patch 29. 28 was there, but I realized that I forgot to fix another portion of the pen code.

Not to throw a wrench into things, but I now have my 0xD1 tablet back up and running with touch and pen (and eraser) based on the 25.x I put up earlier (which has more touch sensitive code). The fdi I uploaded last night should not be used (yet). I was having good results with it because I did not restart X.org. Somehow there is a different initialisation order when X.org boots cleanly verses reinitialising input devices when the module is reinserted. This is a bug in my opinion, and I'll have to figure out where it is.

I'm working on the patch now... upload in a few.
EDIT: Patch attached...

EDIT2: So this works, pen is now working to the white outline on the tablet instead of the full report range (Maybe because I enabled gestures in X.org code)?

EDIT3: ooooh, got a nice crunch crash "BUG: scheduling while atomic: Xorg" on CPU 3. The stylus was in and out of range while I was drawing in gimp and touch was toggled a few times, may have something to do with the static int's for stylusInProx being read and written by two different usb devices. May have to do a kernel mutex lock on the wacom before touching those variables... that's for tomorrow...