HOW TO Set Up a Wacom Serial Tablet in Ubuntu

[Favux]

I'm afraid you have lost me. There is now reaction to the stylus which is good.

I gather you were able to compile inputattach and wacom_serial.ko? Did you use my changes to the HOW TO for that?

Did you copy (cp) the wacom_serial.ko and inputattach into place?

Have you put the inputattach command into rc.local? If so what do you see when you run list modules?

lsmod

You should see wacom_serial and inputattach.

What is the output of?

xinput list

[bruis]

Sorry, I guess my last post was a bit sparse.

Following your How To section II, subsection a) , wacom_serial.ko (wacom_serial-120301-1) was installed.
NB: This was your earlier version of subsection a)
Then following tokenrove #306 a make before leaving the wacom_serial dir. (Should this be make all instead?)
Copied inputattach to /usr/bin
Then sudo ./inputattach --wacom_iv /dev/ttyS0 & which returns a a four digit number like 4497.
Then added: inputattach --wacom_iv /dev/ttyS0 to etc/ rc.local
Logging out and in loads inputattach as shown in System Monitor.
However when I run lsmod I get:
wacom_serial 12646 0 but no sign of inputattach

Xinput list returns:
Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Microsoft Microsoft Basic Optical Mouse v2.0 id=8 [slave pointer (2)]
⎜ ↳ Microsoft Wired Keyboard 600 id=10 [slave pointer (2)]
⎜ ↳ Wacom protocol 4 serial tablet id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ Microsoft Wired Keyboard 600 id=9 [slave keyboard (3)]

Wacom Tablet setting is not working in System Settings. Xsetwacom also not working.

[Favux]

Thanks that helped.

My mistake, seeing wacom_serial in lsmod indicates inputattach is working. Also seeing in xinput list:

⎜ ↳ Wacom protocol 4 serial tablet id=11 [slave pointer (2)]

indicates that. So I think you have a working serio wacom_serial.ko with a /dev/input node being created by inputattach, which dmesg is showing you.

However it looks like there may be a problem with the Wacom X driver (xf86-input-wacom) because we should see stylus, and at least eraser appended to the Parent "device name" you're getting from xinput list. A quick way to check if you are on the Wacom X driver is to run:

xsetwacom list

or

xinput list-props "Wacom protocol 4 serial tablet"

Since it is behaving like a mouse I suspect it will show the tablet is on the evdev X driver.

So we need to look at your Xorg.0.log and see if that will tell us what is going wrong. It is in /var/log. Since it is big compress it by right clicking on it and using Create Archive. Then attach it to your next post. I'm concerned you may be running into a problem similar to the one tmtke encountered, see post #294, although X isn't crashing on your system.

[bruis]

The situation has worsened. After booting up today :
sudo ./inputattach -–wacom_iv /dev/ttyS0 $ returns: inputattach: invalid mode '-–wacom_iv'.
I replaced inputtach but the result was the same. I have had this happen a few times and do not know why it stopped or why it has started again. All that I did that might have some relevance was to tinker with xorg.conf and 50-wacom.rules.
With this situation I guess its not surprising that xsetcom list does nothing and xinput list-props "Wacom protocol 4 serial tablet" returns: unable to find device Wacom protocol 4 serial tablet.

It can be a rocky road to Serial Wacom Happiness...

[tokenrove]

Wacom Tablet setting is not working in System Settings. Xsetwacom also not working.

Hi,

I have to run so this is a bit quick, but make sure the udev rules are installed properly (70-serial-wacom.rules). You should not need to patch anything with the 120301 driver. I'll look at this again tonight in case that didn't fix it.

Cheers.

[bruis]

Here are my /etc/udev/rules.d/70-serial-wacom.rules :

ACTION=="add|change", SUBSYSTEM=="pnp", ENV{PRODUCT}=='13/3d/*', ENV{NAME}=="Wacom protocol IV serial tablet",SYMLINK+="input/wacom",ENV{ID_INPUT}="1",ENV{ID_INPUT_TABLET}="1"

There are also /lib/udev/rules.d/69-xserver-xorg-input-wacom.rules.
Could there be a conflict?

[Favux]

I don't think so, and besides 70 runs after 69 not to mention /etc/udev/rules.d runs after /lib/udev/rules.d. Whatever runs last controls so the custom serial rule should override anything earlier.

What the Xorg.0.log mainly shows us is:

[    16.862] (II) LoadModule: "wacom"
[    16.862] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
[    16.875] (II) Module wacom: vendor="X.Org Foundation"
[    16.875] 	compiled for 1.10.4, module version = 0.11.0
[    16.875] 	Module class: X.Org XInput Driver
[    16.875] 	ABI class: X.Org XInput driver, version 12.3
......
[    18.391] (II) Using input driver 'wacom' for 'stylus'
[    18.391] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
[    18.391] (**) stylus: always reports core events
[    18.391] (**) Option "Device" "/dev/ttyS0"
[    18.391] (**) Option "StopBits" "1"
[    18.391] (**) Option "DataBits" "8"
[    18.391] (**) Option "Parity" "None"
[    18.391] (**) Option "Vmin" "1"
[    18.391] (**) Option "Vtime" "10"
[    18.391] (**) Option "FlowControl" "Xoff"
[    18.391] (**) Option "Mode" "Relative"
[    18.391] (**) Option "Threshold" "5"
[    21.645] (WW) stylus: Waited too long for answer (failed after 3 tries).
[    21.645] (WW) stylus: Query failed with 19200 baud. Trying 38400.
[    24.898] (WW) stylus: Waited too long for answer (failed after 3 tries).
[    24.898] (II) stylus: serial tablet id 0x90.
[    24.898] (EE) PreInit returned 8 for "stylus"
[    24.898] (II) UnloadModule: "wacom"
[    24.898] (II) Unloading wacom
[    24.898] (II) Using input driver 'wacom' for 'eraser'
[    24.898] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
[    24.898] (**) eraser: always reports core events
[    24.898] (**) Option "Device" "/dev/ttyS0"
[    24.898] (**) Option "StopBits" "1"
[    24.898] (**) Option "DataBits" "8"
[    24.898] (**) Option "Parity" "None"
[    24.898] (**) Option "Vmin" "1"
[    24.898] (**) Option "Vtime" "10"
[    24.898] (**) Option "FlowControl" "Xoff"
[    24.898] (**) Option "Mode" "Relative"
[    24.899] (**) Option "Threshold" "5"
[    24.899] (WW) eraser: TPCButton option can only be set by stylus.
[    28.149] (WW) eraser: Waited too long for answer (failed after 3 tries).
[    28.149] (WW) eraser: Query failed with 19200 baud. Trying 38400.
[    31.403] (WW) eraser: Waited too long for answer (failed after 3 tries).
[    31.403] (II) eraser: serial tablet id 0x90.
[    31.403] (EE) PreInit returned 8 for "eraser"
[    31.403] (II) UnloadModule: "wacom"
[    31.403] (II) Unloading wacom
[    31.403] (II) Using input driver 'wacom' for 'cursor'
[    31.403] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
[    31.403] (**) cursor: always reports core events
[    31.403] (**) Option "Device" "/dev/ttyS0"
[    31.403] (**) Option "StopBits" "1"
[    31.403] (**) Option "DataBits" "8"
[    31.403] (**) Option "Parity" "None"
[    31.403] (**) Option "Vmin" "1"
[    31.403] (**) Option "Vtime" "10"
[    31.403] (**) Option "FlowControl" "Xoff"
[    31.403] (**) Option "Mode" "  Absolute"
[    31.403] (**) Option "Threshold" "5"
[    31.403] (WW) cursor: TPCButton option can only be set by stylus.
[    34.657] (WW) cursor: Waited too long for answer (failed after 3 tries).
[    34.657] (WW) cursor: Query failed with 19200 baud. Trying 38400.
[    37.910] (WW) cursor: Waited too long for answer (failed after 3 tries).
[    37.910] (II) cursor: serial tablet id 0x90.
[    37.910] (EE) PreInit returned 8 for "cursor"
[    37.910] (II) UnloadModule: "wacom"
[    37.910] (II) Unloading wacom
.....
[  4443.844] (II) config/udev: Adding input device Wacom Serial Touchscreen (/dev/input/event6)
[  4443.844] (II) No input driver/identifier specified (ignoring)

The part with stylus, eraser, and cursor repeats multiple times. It would be nice if it said it was trying on /dev/input/event7, which I presume is the node it is using.

So I have two questions. In the old wcmSerial.c the code seems to expect at least some serial tablets are on 9600 baud. Has there been any evidence for that? Given the error message 'Waited too long for answer' is from wcmWaitForTablet --wait for tablet data in wcmISDV4.c is it the Digitizer II (UD series) isn't responding with recognisable data or is it not at the right baud rate?

[tokenrove]

Copied inputattach to /usr/bin
Then sudo ./inputattach --wacom_iv /dev/ttyS0 & which returns a a four digit number like 4497.
Then added: inputattach --wacom_iv /dev/ttyS0 to etc/ rc.local
Logging out and in loads inputattach as shown in System Monitor.

Forget about copying inputattach anywhere or adding it to rc.local until you have it working in one session -- there should be no need to log in and out to get it to work. Immediately after you run sudo ./inputattach --wacom_iv /dev/ttyS0 (ensuring that no other inputattach is running), what lines appear in your kernel log? (/var/log/kern.log or /var/log/kernel.log)

Thanks.

[tokenrove]

So I have two questions. In the old wcmSerial.c the code seems to expect at least some serial tablets are on 9600 baud. Has there been any evidence for that? Given the error message 'Waited too long for answer' is from wcmWaitForTablet --wait for tablet data in wcmISDV4.c is it the Digitizer II (UD series) isn't responding with recognisable data or is it not at the right baud rate?

I have tried for some time to confirm whether any of the protocol IV tablets handle a speed greater than 9600 bps. This is the speed my driver runs at; you might note in the newer inputattach, I have added the same kind of reset sequence as the old wcmSerial, starting at 38400 and going down to 9600.

Certainly my Digitizer II doesn't seem to handle anything faster than 9600 bps, and that seems to be the report from other users, but I remain curious. It must be a win to have a higher link speed, but as far as I could see, in the case of protocol IV tablets, the old driver always ran at 9600 bps. Note that for protocol V tablets, it seemed to have some negotiation code for moving to a higher link speed.

It would be great if I could get consistent reports about this behavior from owners of other tablets, but I guess I would have to write an appropriate testing tool -- easy enough to do, but I don't have a lot of time to dedicate to it.

In this case, I'm wondering if my recent changes have broken older tablets -- my Digitizer II works fine, but it's a newer ROM version.

[Favux]

OK, that clears it up some. I did see the new reset code which is why I brought it up. So the serial tablets are at 9600 and not going to 19200, as far as we can tell. So why the heck does the old wcmSerial.c code start negotiation at 38400? Leftover before ISDV4 devices were moved to ISDV4.c? And why duplicate that in inputattach? Are we thinking one of the last models of serial V tablets was at 38400? Maybe with 19200 skipped altogether?

Maybe there is a "secret" command/request to turn on a higher link speed we don't know?

Since wcmISDV4.c only seems to handle 19200 and 38400 for the ISDV4 devices I was wondering if that was a problem. I gather from what you're saying it isn't, what matters is what inputattach has negotiated for the baud speed. And once the correct one is determined we're golden baud-wise.

In this case, I'm wondering if my recent changes have broken older tablets -- my Digitizer II works fine, but it's a newer ROM version.

I hope not.