X6x Tablet Wacom not recognized

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

X6x Tablet Wacom not recognized

Matthias
I have two X61 Tablet. Each reequipped with an SXGA+ Screen (Part 93P5607), which is combined with an so called G4 Digitizer from Wacom.
I also had to renew the connection cables with Part 93P4361, because they were for the "G5" digitizer and to short to fit correctly. I recall both of them worked, with old and new displays.
Both Tablets are now working with the bundled Windows Vista and latest Drivers from Wacom.
Only one Tablet is working fine in Linux. The other has problems in Linux Mint Quiana and a Ubuntu 14.04 LTS Live CD.
In most cases it it not recognized. When I hold the stylus on the screen it works sometimes (xorg.0.log):
[    10.491] (II) Serial Wacom Tablet stylus: serial tablet id 0x90.
[    10.491] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
[    10.491] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=61440 maxY=64561 maxZ=542 resX=100000 resY=100000 tilt=enabled
But the coordinates are wrong, so I get wrong movement on the screen.
In an old log I found:
[ 78215.912] (II) Serial Wacom Tablet stylus: serial tablet id 0x90.
[ 78215.912] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
[ 78215.912] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=24576 maxY=18432 maxZ=255 resX=100000 resY=100000 tilt=disabled

I tried: xxd -b -c 9 /dev/ttyS4 I get this, while holding the pen:
0000000: 00000000 11111110 11100000 10000110 01100110 00110011 00000110 00001100 11111000  ....f3...
0000009: 10000110 00000000 00000000 11111000 00000000 00000000 00000000 11111110 11100000  .........
0000012: 10000110 01100110 00110011 00000110 00001100 11111000 10000110 00000000 00000000  .f3......
000001b: 11111000 00000000 00000000 00000000 11111110 11100000 10000110 01100110 00110011  .......f3
0000024: 00000110 00001100 11111000 10000110 00000000 00000000 11111000 00000000 00000000  .........
000002d: 00000000 11111110 11100000 10000110 01111110 00110011 00000110 00001100 00011000  ....~3...
0000036: 00001111 00000000 00000000 01111110 00000000 00000000 00000000 11111110 11100000  ...~.....
000003f: 10000110 01111110 00110011 00000110 00001100 00011000 00001111 00000000 00000000  .~3......
0000048: 01111110 00000000 00000000 00000000 11111110 11100000 10000110 10011000 11100110  ~........
0000051: 00000110 00001100 01111000 00001111 00000000 00000000 11100110 00000000 00000000  ..x......
000005a: 00000000 11111110 11100000 10000110 11100000 11100110 00000110 00001100 10011000  .........
0000063: 11111000 00000000 00000000 11111000 00000000 00000000 00000000 11111110 11100000  .........
000006c: 10000110 11111000 11100110 00000110 00001100 11100110 11111000 00000000 00000000  .........
0000075: 11111000 00000000 00000000 00000000 11111110 11100000 10000110 00000000 01111110  ........~
000007e: 00000011 11000011 11111000 11111000 00000000 10000000 11100110 00000000 00000000  .........

After I tried isdv4-serial-debugger -v /dev/ttyS4
... Opening device '/dev/ttyS4'.
... Baud rate is 38400
... Querying tablet.
... Writing STOP command.
... Written '0'.
... Written '*'.
timeout.
error during query.
... Waiting for tablet...

Later I get from xxd, while holding the pen:

0000000: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
0000009: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
0000012: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
000001b: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
0000024: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
000002d: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
0000036: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
000003f: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
0000048: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....

Which are commands of the protocol. The cursor moves, if the digitizer was initialized, but in a wrong coordinate system.
I assume this because, when I hold on the screen while debugging I get ("garbage flushed" messages omitted):
... Opening device '/dev/ttyS4'.
... Baud rate is 38400
... Querying tablet.
... Writing STOP command.
... Written '0'.
... garbage flushed

... garbage flushed
... Written '*'.
... Waiting for tablet...... data available.
... Reading 11 bytes from device.
... read 6 bytes in one chunk.
... read 8 bytes in one chunk.
... Read 14 bytes.
... 3 bytes unexpected data.
... 0x80 ... 0xf8 ... 0 ...
... Parsing query reply.
TABLET: version: 16191
TABLET: x max: 536 y max 16280
TABLET: tilt_x max: 48 tilt_y max 96
TABLET: pressure max: 480
... Trying touch query
... Writing STOP command.
... Written '0'.
... garbage flushed

... garbage flushed
... Written '%'.
... Waiting for tablet...... data available.
... Reading 11 bytes from device.
... read 1 bytes in one chunk.
... read 8 bytes in one chunk.
... read 7 bytes in one chunk.
... Read 16 bytes.
... skipping over 1 bytes.
... 1 bytes garbage.
... read 1 bytes in one chunk.
... Read 16 bytes.
... 5 bytes unexpected data.
... 0x6 ... 0x33 ... 0 ... 0 ... 0x6 ...
... Parsing touch query reply.
TOUCH: version: 16128
TOUCH: x max: 920 y max 49164
TOUCH: panel resolution: 128
TOUCH: capacity resolution: 158
TOUCH: sensor id: 6
*** stack smashing detected ***: isdv4-serial-debugger terminated
Aborted

I hope there is no fault in the cable. And in Windows it is working fine. Do you have any ideas?

Thanks

Matthias

------------------------------------------------------------------------------
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: X6x Tablet Wacom not recognized

Jason Gerecke
Matthias,

Each of your logs reports different values for the the hardware resolution:
61440 x 64561 x 542
24576 x 18432 x 255
536 x 16280 x 480

This, along with the "garbage flushed" message, strongly indicates
that we're receiving bad data. This could be a hardware issue (either
the digitizer or cable), though its also possible the software is
negotiating the wrong baud rate for communication. Try running
`isdv4-serial-debugger -v /dev/ttyS4 -b 19200` a few times and see if
you get more consistent resolutions. In particular, the "TABLET:
pressure max:" looks like it should be 255 for your tablet.

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....

On Sun, Nov 8, 2015 at 5:59 AM, [hidden email] <[hidden email]> wrote:

> I have two X61 Tablet. Each reequipped with an SXGA+ Screen (Part 93P5607), which is combined with an so called G4 Digitizer from Wacom.
> I also had to renew the connection cables with Part 93P4361, because they were for the "G5" digitizer and to short to fit correctly. I recall both of them worked, with old and new displays.
> Both Tablets are now working with the bundled Windows Vista and latest Drivers from Wacom.
> Only one Tablet is working fine in Linux. The other has problems in Linux Mint Quiana and a Ubuntu 14.04 LTS Live CD.
> In most cases it it not recognized. When I hold the stylus on the screen it works sometimes (xorg.0.log):
> [    10.491] (II) Serial Wacom Tablet stylus: serial tablet id 0x90.
> [    10.491] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
> [    10.491] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=61440 maxY=64561 maxZ=542 resX=100000 resY=100000 tilt=enabled
> But the coordinates are wrong, so I get wrong movement on the screen.
> In an old log I found:
> [ 78215.912] (II) Serial Wacom Tablet stylus: serial tablet id 0x90.
> [ 78215.912] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
> [ 78215.912] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=24576 maxY=18432 maxZ=255 resX=100000 resY=100000 tilt=disabled
>
> I tried: xxd -b -c 9 /dev/ttyS4 I get this, while holding the pen:
> 0000000: 00000000 11111110 11100000 10000110 01100110 00110011 00000110 00001100 11111000  ....f3...
> 0000009: 10000110 00000000 00000000 11111000 00000000 00000000 00000000 11111110 11100000  .........
> 0000012: 10000110 01100110 00110011 00000110 00001100 11111000 10000110 00000000 00000000  .f3......
> 000001b: 11111000 00000000 00000000 00000000 11111110 11100000 10000110 01100110 00110011  .......f3
> 0000024: 00000110 00001100 11111000 10000110 00000000 00000000 11111000 00000000 00000000  .........
> 000002d: 00000000 11111110 11100000 10000110 01111110 00110011 00000110 00001100 00011000  ....~3...
> 0000036: 00001111 00000000 00000000 01111110 00000000 00000000 00000000 11111110 11100000  ...~.....
> 000003f: 10000110 01111110 00110011 00000110 00001100 00011000 00001111 00000000 00000000  .~3......
> 0000048: 01111110 00000000 00000000 00000000 11111110 11100000 10000110 10011000 11100110  ~........
> 0000051: 00000110 00001100 01111000 00001111 00000000 00000000 11100110 00000000 00000000  ..x......
> 000005a: 00000000 11111110 11100000 10000110 11100000 11100110 00000110 00001100 10011000  .........
> 0000063: 11111000 00000000 00000000 11111000 00000000 00000000 00000000 11111110 11100000  .........
> 000006c: 10000110 11111000 11100110 00000110 00001100 11100110 11111000 00000000 00000000  .........
> 0000075: 11111000 00000000 00000000 00000000 11111110 11100000 10000110 00000000 01111110  ........~
> 000007e: 00000011 11000011 11111000 11111000 00000000 10000000 11100110 00000000 00000000  .........
>
> After I tried isdv4-serial-debugger -v /dev/ttyS4
> ... Opening device '/dev/ttyS4'.
> ... Baud rate is 38400
> ... Querying tablet.
> ... Writing STOP command.
> ... Written '0'.
> ... Written '*'.
> timeout.
> error during query.
> ... Waiting for tablet...
>
> Later I get from xxd, while holding the pen:
>
> 0000000: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
> 0000009: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
> 0000012: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
> 000001b: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
> 0000024: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
> 000002d: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
> 0000036: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
> 000003f: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
> 0000048: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>
> Which are commands of the protocol. The cursor moves, if the digitizer was initialized, but in a wrong coordinate system.
> I assume this because, when I hold on the screen while debugging I get ("garbage flushed" messages omitted):
> ... Opening device '/dev/ttyS4'.
> ... Baud rate is 38400
> ... Querying tablet.
> ... Writing STOP command.
> ... Written '0'.
> ... garbage flushed
>
> ... garbage flushed
> ... Written '*'.
> ... Waiting for tablet...... data available.
> ... Reading 11 bytes from device.
> ... read 6 bytes in one chunk.
> ... read 8 bytes in one chunk.
> ... Read 14 bytes.
> ... 3 bytes unexpected data.
> ... 0x80 ... 0xf8 ... 0 ...
> ... Parsing query reply.
> TABLET: version: 16191
> TABLET: x max: 536 y max 16280
> TABLET: tilt_x max: 48 tilt_y max 96
> TABLET: pressure max: 480
> ... Trying touch query
> ... Writing STOP command.
> ... Written '0'.
> ... garbage flushed
>
> ... garbage flushed
> ... Written '%'.
> ... Waiting for tablet...... data available.
> ... Reading 11 bytes from device.
> ... read 1 bytes in one chunk.
> ... read 8 bytes in one chunk.
> ... read 7 bytes in one chunk.
> ... Read 16 bytes.
> ... skipping over 1 bytes.
> ... 1 bytes garbage.
> ... read 1 bytes in one chunk.
> ... Read 16 bytes.
> ... 5 bytes unexpected data.
> ... 0x6 ... 0x33 ... 0 ... 0 ... 0x6 ...
> ... Parsing touch query reply.
> TOUCH: version: 16128
> TOUCH: x max: 920 y max 49164
> TOUCH: panel resolution: 128
> TOUCH: capacity resolution: 158
> TOUCH: sensor id: 6
> *** stack smashing detected ***: isdv4-serial-debugger terminated
> Aborted
>
> I hope there is no fault in the cable. And in Windows it is working fine. Do you have any ideas?
>
> Thanks
>
> Matthias
>

------------------------------------------------------------------------------
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: X6x Tablet Wacom not recognized

Matthias
Jason,

I tried isdv4-serial-debugger -v /dev/ttyS4 -b 19200 several times. I get:

... Opening device '/dev/ttyS4'.
... Baud rate is 19200
... Querying tablet.
... Writing STOP command.
... Written '0'.
... Written '*'.
timeout.
error during query.
... Waiting for tablet...

while holding the pen I get:

... Opening device '/dev/ttyS4'.
... Baud rate is 19200
... Querying tablet.
... Writing STOP command.
... Written '0'.
... Written '*'.
... Waiting for tablet...... data available.
... Reading 11 bytes from device.
... read 8 bytes in one chunk.
... read 8 bytes in one chunk.
... Read 16 bytes.
... skipping over 1 bytes.
... 1 bytes garbage.
... read 8 bytes in one chunk.
... Read 23 bytes.
... 12 bytes unexpected data.
... 0x3f ... 0x15 ... 0x6f ... 0 ... 0x40 ... 0x15 ... 0x6d ... 0 ...
... 0x10 ... 0 ... 0 ... 0xa0 ...
... +++ out of cheese error +++ redo from start +++
... Reading 11 bytes from device.
... read 8 bytes in one chunk.
... read 8 bytes in one chunk.
... Read 16 bytes.
... 5 bytes unexpected data.
... 0x40 ... 0x15 ... 0x6d ... 0 ... 0x10 ...
... Parsing query reply.
parsing error code -1
error during query.
*** stack smashing detected ***: isdv4-serial-debugger terminated

In my opinion this is only, because it tries to interpret pen commands
as tablet information.

I monitored /dev/ttyS4 with xxd, while holding the pen.
As soon as I issue the isdv4-serial-debugger command the output changes
to commands of the protocol. (See my first message)
But the device never sends a package with tablet information.

Is there a way to force the loading of the wacom module with manual
entered parameters?

Perhaps this could help me.

Thanks, Matthias.

On 11/10/2015 01:12 AM, Jason Gerecke wrote:

> Matthias,
>
> Each of your logs reports different values for the the hardware resolution:
> 61440 x 64561 x 542
> 24576 x 18432 x 255
> 536 x 16280 x 480
>
> This, along with the "garbage flushed" message, strongly indicates
> that we're receiving bad data. This could be a hardware issue (either
> the digitizer or cable), though its also possible the software is
> negotiating the wrong baud rate for communication. Try running
> `isdv4-serial-debugger -v /dev/ttyS4 -b 19200` a few times and see if
> you get more consistent resolutions. In particular, the "TABLET:
> pressure max:" looks like it should be 255 for your tablet.
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one  /
> (That is to say, eight) to the two,     /
> But you can’t take seven from three,    /
> So you look at the sixty-fours....
>
> On Sun, Nov 8, 2015 at 5:59 AM, [hidden email] <[hidden email]> wrote:
>> I have two X61 Tablet. Each reequipped with an SXGA+ Screen (Part 93P5607), which is combined with an so called G4 Digitizer from Wacom.
>> I also had to renew the connection cables with Part 93P4361, because they were for the "G5" digitizer and to short to fit correctly. I recall both of them worked, with old and new displays.
>> Both Tablets are now working with the bundled Windows Vista and latest Drivers from Wacom.
>> Only one Tablet is working fine in Linux. The other has problems in Linux Mint Quiana and a Ubuntu 14.04 LTS Live CD.
>> In most cases it it not recognized. When I hold the stylus on the screen it works sometimes (xorg.0.log):
>> [    10.491] (II) Serial Wacom Tablet stylus: serial tablet id 0x90.
>> [    10.491] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
>> [    10.491] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=61440 maxY=64561 maxZ=542 resX=100000 resY=100000 tilt=enabled
>> But the coordinates are wrong, so I get wrong movement on the screen.
>> In an old log I found:
>> [ 78215.912] (II) Serial Wacom Tablet stylus: serial tablet id 0x90.
>> [ 78215.912] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
>> [ 78215.912] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=24576 maxY=18432 maxZ=255 resX=100000 resY=100000 tilt=disabled
>>
>> I tried: xxd -b -c 9 /dev/ttyS4 I get this, while holding the pen:
>> 0000000: 00000000 11111110 11100000 10000110 01100110 00110011 00000110 00001100 11111000  ....f3...
>> 0000009: 10000110 00000000 00000000 11111000 00000000 00000000 00000000 11111110 11100000  .........
>> 0000012: 10000110 01100110 00110011 00000110 00001100 11111000 10000110 00000000 00000000  .f3......
>> 000001b: 11111000 00000000 00000000 00000000 11111110 11100000 10000110 01100110 00110011  .......f3
>> 0000024: 00000110 00001100 11111000 10000110 00000000 00000000 11111000 00000000 00000000  .........
>> 000002d: 00000000 11111110 11100000 10000110 01111110 00110011 00000110 00001100 00011000  ....~3...
>> 0000036: 00001111 00000000 00000000 01111110 00000000 00000000 00000000 11111110 11100000  ...~.....
>> 000003f: 10000110 01111110 00110011 00000110 00001100 00011000 00001111 00000000 00000000  .~3......
>> 0000048: 01111110 00000000 00000000 00000000 11111110 11100000 10000110 10011000 11100110  ~........
>> 0000051: 00000110 00001100 01111000 00001111 00000000 00000000 11100110 00000000 00000000  ..x......
>> 000005a: 00000000 11111110 11100000 10000110 11100000 11100110 00000110 00001100 10011000  .........
>> 0000063: 11111000 00000000 00000000 11111000 00000000 00000000 00000000 11111110 11100000  .........
>> 000006c: 10000110 11111000 11100110 00000110 00001100 11100110 11111000 00000000 00000000  .........
>> 0000075: 11111000 00000000 00000000 00000000 11111110 11100000 10000110 00000000 01111110  ........~
>> 000007e: 00000011 11000011 11111000 11111000 00000000 10000000 11100110 00000000 00000000  .........
>>
>> After I tried isdv4-serial-debugger -v /dev/ttyS4
>> ... Opening device '/dev/ttyS4'.
>> ... Baud rate is 38400
>> ... Querying tablet.
>> ... Writing STOP command.
>> ... Written '0'.
>> ... Written '*'.
>> timeout.
>> error during query.
>> ... Waiting for tablet...
>>
>> Later I get from xxd, while holding the pen:
>>
>> 0000000: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>> 0000009: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>> 0000012: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>> 000001b: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>> 0000024: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>> 000002d: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>> 0000036: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>> 000003f: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>> 0000048: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>
>> Which are commands of the protocol. The cursor moves, if the digitizer was initialized, but in a wrong coordinate system.
>> I assume this because, when I hold on the screen while debugging I get ("garbage flushed" messages omitted):
>> ... Opening device '/dev/ttyS4'.
>> ... Baud rate is 38400
>> ... Querying tablet.
>> ... Writing STOP command.
>> ... Written '0'.
>> ... garbage flushed
>>
>> ... garbage flushed
>> ... Written '*'.
>> ... Waiting for tablet...... data available.
>> ... Reading 11 bytes from device.
>> ... read 6 bytes in one chunk.
>> ... read 8 bytes in one chunk.
>> ... Read 14 bytes.
>> ... 3 bytes unexpected data.
>> ... 0x80 ... 0xf8 ... 0 ...
>> ... Parsing query reply.
>> TABLET: version: 16191
>> TABLET: x max: 536 y max 16280
>> TABLET: tilt_x max: 48 tilt_y max 96
>> TABLET: pressure max: 480
>> ... Trying touch query
>> ... Writing STOP command.
>> ... Written '0'.
>> ... garbage flushed
>>
>> ... garbage flushed
>> ... Written '%'.
>> ... Waiting for tablet...... data available.
>> ... Reading 11 bytes from device.
>> ... read 1 bytes in one chunk.
>> ... read 8 bytes in one chunk.
>> ... read 7 bytes in one chunk.
>> ... Read 16 bytes.
>> ... skipping over 1 bytes.
>> ... 1 bytes garbage.
>> ... read 1 bytes in one chunk.
>> ... Read 16 bytes.
>> ... 5 bytes unexpected data.
>> ... 0x6 ... 0x33 ... 0 ... 0 ... 0x6 ...
>> ... Parsing touch query reply.
>> TOUCH: version: 16128
>> TOUCH: x max: 920 y max 49164
>> TOUCH: panel resolution: 128
>> TOUCH: capacity resolution: 158
>> TOUCH: sensor id: 6
>> *** stack smashing detected ***: isdv4-serial-debugger terminated
>> Aborted
>>
>> I hope there is no fault in the cable. And in Windows it is working fine. Do you have any ideas?
>>
>> Thanks
>>
>> Matthias
>>

------------------------------------------------------------------------------
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: X6x Tablet Wacom not recognized

Jason Gerecke
Matthias,

Hmm... Apparently the baud rate is not the issue since that doesn't
solve things. I'm afraid I don't have much experience with the serial
protocol, so I can't really help. You might see if the "inputattach" (or
"isdv4-serial-inputattach") daemon is running and modifying the commands
it is started with. IIRC, it is responsible for setting the baud rate
and line discipline so that the kernel module can communicate.

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one /
(That is to say, eight) to the two, /
But you can’t take seven from three, /
So you look at the sixty-fours....

On 11/9/2015 10:50 PM, Matthias wrote:

> Jason,
>
> I tried isdv4-serial-debugger -v /dev/ttyS4 -b 19200 several times. I get:
>
> ... Opening device '/dev/ttyS4'.
> ... Baud rate is 19200
> ... Querying tablet.
> ... Writing STOP command.
> ... Written '0'.
> ... Written '*'.
> timeout.
> error during query.
> ... Waiting for tablet...
>
> while holding the pen I get:
>
> ... Opening device '/dev/ttyS4'.
> ... Baud rate is 19200
> ... Querying tablet.
> ... Writing STOP command.
> ... Written '0'.
> ... Written '*'.
> ... Waiting for tablet...... data available.
> ... Reading 11 bytes from device.
> ... read 8 bytes in one chunk.
> ... read 8 bytes in one chunk.
> ... Read 16 bytes.
> ... skipping over 1 bytes.
> ... 1 bytes garbage.
> ... read 8 bytes in one chunk.
> ... Read 23 bytes.
> ... 12 bytes unexpected data.
> ... 0x3f ... 0x15 ... 0x6f ... 0 ... 0x40 ... 0x15 ... 0x6d ... 0 ...
> ... 0x10 ... 0 ... 0 ... 0xa0 ...
> ... +++ out of cheese error +++ redo from start +++
> ... Reading 11 bytes from device.
> ... read 8 bytes in one chunk.
> ... read 8 bytes in one chunk.
> ... Read 16 bytes.
> ... 5 bytes unexpected data.
> ... 0x40 ... 0x15 ... 0x6d ... 0 ... 0x10 ...
> ... Parsing query reply.
> parsing error code -1
> error during query.
> *** stack smashing detected ***: isdv4-serial-debugger terminated
>
> In my opinion this is only, because it tries to interpret pen commands
> as tablet information.
>
> I monitored /dev/ttyS4 with xxd, while holding the pen.
> As soon as I issue the isdv4-serial-debugger command the output changes
> to commands of the protocol. (See my first message)
> But the device never sends a package with tablet information.
>
> Is there a way to force the loading of the wacom module with manual
> entered parameters?
>
> Perhaps this could help me.
>
> Thanks, Matthias.
>
> On 11/10/2015 01:12 AM, Jason Gerecke wrote:
>> Matthias,
>>
>> Each of your logs reports different values for the the hardware resolution:
>> 61440 x 64561 x 542
>> 24576 x 18432 x 255
>> 536 x 16280 x 480
>>
>> This, along with the "garbage flushed" message, strongly indicates
>> that we're receiving bad data. This could be a hardware issue (either
>> the digitizer or cable), though its also possible the software is
>> negotiating the wrong baud rate for communication. Try running
>> `isdv4-serial-debugger -v /dev/ttyS4 -b 19200` a few times and see if
>> you get more consistent resolutions. In particular, the "TABLET:
>> pressure max:" looks like it should be 255 for your tablet.
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one  /
>> (That is to say, eight) to the two,     /
>> But you can’t take seven from three,    /
>> So you look at the sixty-fours....
>>
>> On Sun, Nov 8, 2015 at 5:59 AM, [hidden email] <[hidden email]> wrote:
>>> I have two X61 Tablet. Each reequipped with an SXGA+ Screen (Part 93P5607), which is combined with an so called G4 Digitizer from Wacom.
>>> I also had to renew the connection cables with Part 93P4361, because they were for the "G5" digitizer and to short to fit correctly. I recall both of them worked, with old and new displays.
>>> Both Tablets are now working with the bundled Windows Vista and latest Drivers from Wacom.
>>> Only one Tablet is working fine in Linux. The other has problems in Linux Mint Quiana and a Ubuntu 14.04 LTS Live CD.
>>> In most cases it it not recognized. When I hold the stylus on the screen it works sometimes (xorg.0.log):
>>> [    10.491] (II) Serial Wacom Tablet stylus: serial tablet id 0x90.
>>> [    10.491] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
>>> [    10.491] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=61440 maxY=64561 maxZ=542 resX=100000 resY=100000 tilt=enabled
>>> But the coordinates are wrong, so I get wrong movement on the screen.
>>> In an old log I found:
>>> [ 78215.912] (II) Serial Wacom Tablet stylus: serial tablet id 0x90.
>>> [ 78215.912] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
>>> [ 78215.912] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=24576 maxY=18432 maxZ=255 resX=100000 resY=100000 tilt=disabled
>>>
>>> I tried: xxd -b -c 9 /dev/ttyS4 I get this, while holding the pen:
>>> 0000000: 00000000 11111110 11100000 10000110 01100110 00110011 00000110 00001100 11111000  ....f3...
>>> 0000009: 10000110 00000000 00000000 11111000 00000000 00000000 00000000 11111110 11100000  .........
>>> 0000012: 10000110 01100110 00110011 00000110 00001100 11111000 10000110 00000000 00000000  .f3......
>>> 000001b: 11111000 00000000 00000000 00000000 11111110 11100000 10000110 01100110 00110011  .......f3
>>> 0000024: 00000110 00001100 11111000 10000110 00000000 00000000 11111000 00000000 00000000  .........
>>> 000002d: 00000000 11111110 11100000 10000110 01111110 00110011 00000110 00001100 00011000  ....~3...
>>> 0000036: 00001111 00000000 00000000 01111110 00000000 00000000 00000000 11111110 11100000  ...~.....
>>> 000003f: 10000110 01111110 00110011 00000110 00001100 00011000 00001111 00000000 00000000  .~3......
>>> 0000048: 01111110 00000000 00000000 00000000 11111110 11100000 10000110 10011000 11100110  ~........
>>> 0000051: 00000110 00001100 01111000 00001111 00000000 00000000 11100110 00000000 00000000  ..x......
>>> 000005a: 00000000 11111110 11100000 10000110 11100000 11100110 00000110 00001100 10011000  .........
>>> 0000063: 11111000 00000000 00000000 11111000 00000000 00000000 00000000 11111110 11100000  .........
>>> 000006c: 10000110 11111000 11100110 00000110 00001100 11100110 11111000 00000000 00000000  .........
>>> 0000075: 11111000 00000000 00000000 00000000 11111110 11100000 10000110 00000000 01111110  ........~
>>> 000007e: 00000011 11000011 11111000 11111000 00000000 10000000 11100110 00000000 00000000  .........
>>>
>>> After I tried isdv4-serial-debugger -v /dev/ttyS4
>>> ... Opening device '/dev/ttyS4'.
>>> ... Baud rate is 38400
>>> ... Querying tablet.
>>> ... Writing STOP command.
>>> ... Written '0'.
>>> ... Written '*'.
>>> timeout.
>>> error during query.
>>> ... Waiting for tablet...
>>>
>>> Later I get from xxd, while holding the pen:
>>>
>>> 0000000: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>> 0000009: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>> 0000012: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>> 000001b: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>> 0000024: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>> 000002d: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>> 0000036: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>> 000003f: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>> 0000048: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>>
>>> Which are commands of the protocol. The cursor moves, if the digitizer was initialized, but in a wrong coordinate system.
>>> I assume this because, when I hold on the screen while debugging I get ("garbage flushed" messages omitted):
>>> ... Opening device '/dev/ttyS4'.
>>> ... Baud rate is 38400
>>> ... Querying tablet.
>>> ... Writing STOP command.
>>> ... Written '0'.
>>> ... garbage flushed
>>>
>>> ... garbage flushed
>>> ... Written '*'.
>>> ... Waiting for tablet...... data available.
>>> ... Reading 11 bytes from device.
>>> ... read 6 bytes in one chunk.
>>> ... read 8 bytes in one chunk.
>>> ... Read 14 bytes.
>>> ... 3 bytes unexpected data.
>>> ... 0x80 ... 0xf8 ... 0 ...
>>> ... Parsing query reply.
>>> TABLET: version: 16191
>>> TABLET: x max: 536 y max 16280
>>> TABLET: tilt_x max: 48 tilt_y max 96
>>> TABLET: pressure max: 480
>>> ... Trying touch query
>>> ... Writing STOP command.
>>> ... Written '0'.
>>> ... garbage flushed
>>>
>>> ... garbage flushed
>>> ... Written '%'.
>>> ... Waiting for tablet...... data available.
>>> ... Reading 11 bytes from device.
>>> ... read 1 bytes in one chunk.
>>> ... read 8 bytes in one chunk.
>>> ... read 7 bytes in one chunk.
>>> ... Read 16 bytes.
>>> ... skipping over 1 bytes.
>>> ... 1 bytes garbage.
>>> ... read 1 bytes in one chunk.
>>> ... Read 16 bytes.
>>> ... 5 bytes unexpected data.
>>> ... 0x6 ... 0x33 ... 0 ... 0 ... 0x6 ...
>>> ... Parsing touch query reply.
>>> TOUCH: version: 16128
>>> TOUCH: x max: 920 y max 49164
>>> TOUCH: panel resolution: 128
>>> TOUCH: capacity resolution: 158
>>> TOUCH: sensor id: 6
>>> *** stack smashing detected ***: isdv4-serial-debugger terminated
>>> Aborted
>>>
>>> I hope there is no fault in the cable. And in Windows it is working fine. Do you have any ideas?
>>>
>>> Thanks
>>>
>>> Matthias
>>>

------------------------------------------------------------------------------
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: X6x Tablet Wacom not recognized

Matthias
Jason,

it is working now. My solution was to rewrite some of the code and
compile it. I skipped the waiting for the tablet answer, and inserted
fixed values for the tablet (24576 x 18432 x 255).
This was a quick fix. I reassemble the tablet first, because this
solution has proven that the cable is usable.
Then I'll try to find a better solution.

Thanks

Matthias


On 11/13/2015 01:07 AM, Jason Gerecke wrote:

> Matthias,
>
> Hmm... Apparently the baud rate is not the issue since that doesn't
> solve things. I'm afraid I don't have much experience with the serial
> protocol, so I can't really help. You might see if the "inputattach" (or
> "isdv4-serial-inputattach") daemon is running and modifying the commands
> it is started with. IIRC, it is responsible for setting the baud rate
> and line discipline so that the kernel module can communicate.
>
> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one /
> (That is to say, eight) to the two, /
> But you can’t take seven from three, /
> So you look at the sixty-fours....
>
> On 11/9/2015 10:50 PM, Matthias wrote:
>> Jason,
>>
>> I tried isdv4-serial-debugger -v /dev/ttyS4 -b 19200 several times. I get:
>>
>> ... Opening device '/dev/ttyS4'.
>> ... Baud rate is 19200
>> ... Querying tablet.
>> ... Writing STOP command.
>> ... Written '0'.
>> ... Written '*'.
>> timeout.
>> error during query.
>> ... Waiting for tablet...
>>
>> while holding the pen I get:
>>
>> ... Opening device '/dev/ttyS4'.
>> ... Baud rate is 19200
>> ... Querying tablet.
>> ... Writing STOP command.
>> ... Written '0'.
>> ... Written '*'.
>> ... Waiting for tablet...... data available.
>> ... Reading 11 bytes from device.
>> ... read 8 bytes in one chunk.
>> ... read 8 bytes in one chunk.
>> ... Read 16 bytes.
>> ... skipping over 1 bytes.
>> ... 1 bytes garbage.
>> ... read 8 bytes in one chunk.
>> ... Read 23 bytes.
>> ... 12 bytes unexpected data.
>> ... 0x3f ... 0x15 ... 0x6f ... 0 ... 0x40 ... 0x15 ... 0x6d ... 0 ...
>> ... 0x10 ... 0 ... 0 ... 0xa0 ...
>> ... +++ out of cheese error +++ redo from start +++
>> ... Reading 11 bytes from device.
>> ... read 8 bytes in one chunk.
>> ... read 8 bytes in one chunk.
>> ... Read 16 bytes.
>> ... 5 bytes unexpected data.
>> ... 0x40 ... 0x15 ... 0x6d ... 0 ... 0x10 ...
>> ... Parsing query reply.
>> parsing error code -1
>> error during query.
>> *** stack smashing detected ***: isdv4-serial-debugger terminated
>>
>> In my opinion this is only, because it tries to interpret pen commands
>> as tablet information.
>>
>> I monitored /dev/ttyS4 with xxd, while holding the pen.
>> As soon as I issue the isdv4-serial-debugger command the output changes
>> to commands of the protocol. (See my first message)
>> But the device never sends a package with tablet information.
>>
>> Is there a way to force the loading of the wacom module with manual
>> entered parameters?
>>
>> Perhaps this could help me.
>>
>> Thanks, Matthias.
>>
>> On 11/10/2015 01:12 AM, Jason Gerecke wrote:
>>> Matthias,
>>>
>>> Each of your logs reports different values for the the hardware resolution:
>>> 61440 x 64561 x 542
>>> 24576 x 18432 x 255
>>> 536 x 16280 x 480
>>>
>>> This, along with the "garbage flushed" message, strongly indicates
>>> that we're receiving bad data. This could be a hardware issue (either
>>> the digitizer or cable), though its also possible the software is
>>> negotiating the wrong baud rate for communication. Try running
>>> `isdv4-serial-debugger -v /dev/ttyS4 -b 19200` a few times and see if
>>> you get more consistent resolutions. In particular, the "TABLET:
>>> pressure max:" looks like it should be 255 for your tablet.
>>>
>>> Jason
>>> ---
>>> Now instead of four in the eights place /
>>> you’ve got three, ‘Cause you added one  /
>>> (That is to say, eight) to the two,     /
>>> But you can’t take seven from three,    /
>>> So you look at the sixty-fours....
>>>
>>> On Sun, Nov 8, 2015 at 5:59 AM, [hidden email] <[hidden email]> wrote:
>>>> I have two X61 Tablet. Each reequipped with an SXGA+ Screen (Part 93P5607), which is combined with an so called G4 Digitizer from Wacom.
>>>> I also had to renew the connection cables with Part 93P4361, because they were for the "G5" digitizer and to short to fit correctly. I recall both of them worked, with old and new displays.
>>>> Both Tablets are now working with the bundled Windows Vista and latest Drivers from Wacom.
>>>> Only one Tablet is working fine in Linux. The other has problems in Linux Mint Quiana and a Ubuntu 14.04 LTS Live CD.
>>>> In most cases it it not recognized. When I hold the stylus on the screen it works sometimes (xorg.0.log):
>>>> [    10.491] (II) Serial Wacom Tablet stylus: serial tablet id 0x90.
>>>> [    10.491] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
>>>> [    10.491] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=61440 maxY=64561 maxZ=542 resX=100000 resY=100000 tilt=enabled
>>>> But the coordinates are wrong, so I get wrong movement on the screen.
>>>> In an old log I found:
>>>> [ 78215.912] (II) Serial Wacom Tablet stylus: serial tablet id 0x90.
>>>> [ 78215.912] (--) Serial Wacom Tablet stylus: using pressure threshold of 27 for button 1
>>>> [ 78215.912] (--) Serial Wacom Tablet stylus: Wacom General ISDV4 tablet maxX=24576 maxY=18432 maxZ=255 resX=100000 resY=100000 tilt=disabled
>>>>
>>>> I tried: xxd -b -c 9 /dev/ttyS4 I get this, while holding the pen:
>>>> 0000000: 00000000 11111110 11100000 10000110 01100110 00110011 00000110 00001100 11111000  ....f3...
>>>> 0000009: 10000110 00000000 00000000 11111000 00000000 00000000 00000000 11111110 11100000  .........
>>>> 0000012: 10000110 01100110 00110011 00000110 00001100 11111000 10000110 00000000 00000000  .f3......
>>>> 000001b: 11111000 00000000 00000000 00000000 11111110 11100000 10000110 01100110 00110011  .......f3
>>>> 0000024: 00000110 00001100 11111000 10000110 00000000 00000000 11111000 00000000 00000000  .........
>>>> 000002d: 00000000 11111110 11100000 10000110 01111110 00110011 00000110 00001100 00011000  ....~3...
>>>> 0000036: 00001111 00000000 00000000 01111110 00000000 00000000 00000000 11111110 11100000  ...~.....
>>>> 000003f: 10000110 01111110 00110011 00000110 00001100 00011000 00001111 00000000 00000000  .~3......
>>>> 0000048: 01111110 00000000 00000000 00000000 11111110 11100000 10000110 10011000 11100110  ~........
>>>> 0000051: 00000110 00001100 01111000 00001111 00000000 00000000 11100110 00000000 00000000  ..x......
>>>> 000005a: 00000000 11111110 11100000 10000110 11100000 11100110 00000110 00001100 10011000  .........
>>>> 0000063: 11111000 00000000 00000000 11111000 00000000 00000000 00000000 11111110 11100000  .........
>>>> 000006c: 10000110 11111000 11100110 00000110 00001100 11100110 11111000 00000000 00000000  .........
>>>> 0000075: 11111000 00000000 00000000 00000000 11111110 11100000 10000110 00000000 01111110  ........~
>>>> 000007e: 00000011 11000011 11111000 11111000 00000000 10000000 11100110 00000000 00000000  .........
>>>>
>>>> After I tried isdv4-serial-debugger -v /dev/ttyS4
>>>> ... Opening device '/dev/ttyS4'.
>>>> ... Baud rate is 38400
>>>> ... Querying tablet.
>>>> ... Writing STOP command.
>>>> ... Written '0'.
>>>> ... Written '*'.
>>>> timeout.
>>>> error during query.
>>>> ... Waiting for tablet...
>>>>
>>>> Later I get from xxd, while holding the pen:
>>>>
>>>> 0000000: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>>> 0000009: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>>> 0000012: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>>> 000001b: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>>> 0000024: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>>> 000002d: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>>> 0000036: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>>> 000003f: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>>> 0000048: 10100000 00101110 01110010 00100010 00100001 00000000 00011000 00000000 00000000  ..r"!....
>>>>
>>>> Which are commands of the protocol. The cursor moves, if the digitizer was initialized, but in a wrong coordinate system.
>>>> I assume this because, when I hold on the screen while debugging I get ("garbage flushed" messages omitted):
>>>> ... Opening device '/dev/ttyS4'.
>>>> ... Baud rate is 38400
>>>> ... Querying tablet.
>>>> ... Writing STOP command.
>>>> ... Written '0'.
>>>> ... garbage flushed
>>>>
>>>> ... garbage flushed
>>>> ... Written '*'.
>>>> ... Waiting for tablet...... data available.
>>>> ... Reading 11 bytes from device.
>>>> ... read 6 bytes in one chunk.
>>>> ... read 8 bytes in one chunk.
>>>> ... Read 14 bytes.
>>>> ... 3 bytes unexpected data.
>>>> ... 0x80 ... 0xf8 ... 0 ...
>>>> ... Parsing query reply.
>>>> TABLET: version: 16191
>>>> TABLET: x max: 536 y max 16280
>>>> TABLET: tilt_x max: 48 tilt_y max 96
>>>> TABLET: pressure max: 480
>>>> ... Trying touch query
>>>> ... Writing STOP command.
>>>> ... Written '0'.
>>>> ... garbage flushed
>>>>
>>>> ... garbage flushed
>>>> ... Written '%'.
>>>> ... Waiting for tablet...... data available.
>>>> ... Reading 11 bytes from device.
>>>> ... read 1 bytes in one chunk.
>>>> ... read 8 bytes in one chunk.
>>>> ... read 7 bytes in one chunk.
>>>> ... Read 16 bytes.
>>>> ... skipping over 1 bytes.
>>>> ... 1 bytes garbage.
>>>> ... read 1 bytes in one chunk.
>>>> ... Read 16 bytes.
>>>> ... 5 bytes unexpected data.
>>>> ... 0x6 ... 0x33 ... 0 ... 0 ... 0x6 ...
>>>> ... Parsing touch query reply.
>>>> TOUCH: version: 16128
>>>> TOUCH: x max: 920 y max 49164
>>>> TOUCH: panel resolution: 128
>>>> TOUCH: capacity resolution: 158
>>>> TOUCH: sensor id: 6
>>>> *** stack smashing detected ***: isdv4-serial-debugger terminated
>>>> Aborted
>>>>
>>>> I hope there is no fault in the cable. And in Windows it is working fine. Do you have any ideas?
>>>>
>>>> Thanks
>>>>
>>>> Matthias
>>>>

------------------------------------------------------------------------------
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss