Lenovo Active Pen 2 and wacom tablet on yoga 920

Lenovo Active Pen 2 and wacom tablet on yoga 920

[Kevin Fenzi]

[-- Attachment #1.1: Type: text/plain, Size: 1685 bytes --]

Greetings.

I'm running into some problems with Lenovo active pen 2 and wacom tablet
on a new yoga 920.

Filed:
https://bugzilla.redhat.com/show_bug.cgi?id=1514837

but I thought I would ask here if anyone had any ideas...

Basically when pairing the pen it shows for a second, then drops:

[Sat Nov 18 12:22:42 2017] input: Lenovo Active Pen2 as
/devices/virtual/misc/uhid/0005:17EF:60A8.0006/input/input23
[Sat Nov 18 12:22:42 2017] hid-generic 0005:17EF:60A8.0006:
input,hidraw4: BLUETOOTH HID v0.02 Keyboard [Lenovo Active Pen2] on
64:6E:69:D1:A0:48
[Sat Nov 18 12:22:47 2017] Bluetooth: hci0: last event is not cmd
complete (0x0f)
[Sat Nov 18 12:23:03 2017] Bluetooth: hci0: last event is not cmd
complete (0x0f)
[Sat Nov 18 12:23:19 2017] Bluetooth: hci0: last event is not cmd
complete (0x0f)

The wacom tablet is never connecting:

[Fri Nov 24 21:47:01 2017] input: Wacom HID 5110 Pen as
/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input26
[Fri Nov 24 21:47:01 2017] input: Wacom HID 5110 Finger as
/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input27
[Fri Nov 24 21:47:01 2017] wacom 0018:056A:5110.0003: hidraw3: I2C HID
v1.00 Mouse [WCOM5110:00 056A:5110] on i2c-WCOM5110:00
[Fri Nov 24 21:47:02 2017] i2c_hid i2c-WCOM5110:00: failed to set a
report to device.
[Fri Nov 24 21:47:02 2017] wacom 0018:056A:5110.0003: wacom_set_report:
ran out of retries (last error = -121)
[Fri Nov 24 21:47:02 2017] i2c_hid i2c-WCOM5110:00: failed to set a
report to device.

Happy to gather more info and/or try patches.

Thanks.

kevin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Lenovo Active Pen 2 and wacom tablet on yoga 920

[Jason Gerecke]

Hi Kevin,

The Bluetooth and tablet issues are likely to be unrelated. The
Bluetooth button is completely independent from the rest of the
tablet, with neither the tablet sensor nor the Wacom driver being
aware of it.

>From what I understand, in normal operation the Bluetooth button is
disconnected most of the time. When you press it, it briefly wakes up,
connects to the paired PC, appears as a keyboard, sends a key combo,
and then disconnects until you press it again. If you run something
like `sudo libinput-debug-events` and then press the button, you
should be able to see the key combo being sent (as well as the
connect/disconnect). I'm not sure what's up with the deadlock warning
that appears in dmesg, however...

As for the tablet, the "last error = -121" indicates that we got an
EREMOTEIO error. I've not come across that particular error in this
function before. I'll need some time to track down why we might be
getting this from the lower layers.

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 Mon, Nov 27, 2017 at 12:23 PM, Kevin Fenzi <kevin@scrye.com> wrote:
> Greetings.
>
> I'm running into some problems with Lenovo active pen 2 and wacom tablet
> on a new yoga 920.
>
> Filed:
> https://bugzilla.redhat.com/show_bug.cgi?id=1514837
>
> but I thought I would ask here if anyone had any ideas...
>
> Basically when pairing the pen it shows for a second, then drops:
>
> [Sat Nov 18 12:22:42 2017] input: Lenovo Active Pen2 as
> /devices/virtual/misc/uhid/0005:17EF:60A8.0006/input/input23
> [Sat Nov 18 12:22:42 2017] hid-generic 0005:17EF:60A8.0006:
> input,hidraw4: BLUETOOTH HID v0.02 Keyboard [Lenovo Active Pen2] on
> 64:6E:69:D1:A0:48
> [Sat Nov 18 12:22:47 2017] Bluetooth: hci0: last event is not cmd
> complete (0x0f)
> [Sat Nov 18 12:23:03 2017] Bluetooth: hci0: last event is not cmd
> complete (0x0f)
> [Sat Nov 18 12:23:19 2017] Bluetooth: hci0: last event is not cmd
> complete (0x0f)
>
> The wacom tablet is never connecting:
>
> [Fri Nov 24 21:47:01 2017] input: Wacom HID 5110 Pen as
> /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input26
> [Fri Nov 24 21:47:01 2017] input: Wacom HID 5110 Finger as
> /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input27
> [Fri Nov 24 21:47:01 2017] wacom 0018:056A:5110.0003: hidraw3: I2C HID
> v1.00 Mouse [WCOM5110:00 056A:5110] on i2c-WCOM5110:00
> [Fri Nov 24 21:47:02 2017] i2c_hid i2c-WCOM5110:00: failed to set a
> report to device.
> [Fri Nov 24 21:47:02 2017] wacom 0018:056A:5110.0003: wacom_set_report:
> ran out of retries (last error = -121)
> [Fri Nov 24 21:47:02 2017] i2c_hid i2c-WCOM5110:00: failed to set a
> report to device.
>
> Happy to gather more info and/or try patches.
>
> Thanks.
>
> kevin
>

Re: Lenovo Active Pen 2 and wacom tablet on yoga 920

[Kevin Fenzi]

[-- Attachment #1.1: Type: text/plain, Size: 3773 bytes --]

On 11/29/2017 01:43 PM, Jason Gerecke wrote:
> Hi Kevin,
> 
> The Bluetooth and tablet issues are likely to be unrelated. The
> Bluetooth button is completely independent from the rest of the
> tablet, with neither the tablet sensor nor the Wacom driver being
> aware of it.
> 
>>From what I understand, in normal operation the Bluetooth button is
> disconnected most of the time. When you press it, it briefly wakes up,
> connects to the paired PC, appears as a keyboard, sends a key combo,
> and then disconnects until you press it again. If you run something
> like `sudo libinput-debug-events` and then press the button, you
> should be able to see the key combo being sent (as well as the
> connect/disconnect). I'm not sure what's up with the deadlock warning
> that appears in dmesg, however...

Ah, quite right. Sorry about that, this is my first device with a pen. I
expected it to just connect and stay there, but I suppose doing things
this way saves a ton of power since it's likely not writing most of the
time.

> 
> As for the tablet, the "last error = -121" indicates that we got an
> EREMOTEIO error. I've not come across that particular error in this
> function before. I'll need some time to track down why we might be
> getting this from the lower layers.

ok, thanks! If you need any more info from me just ask. Happy to test
patches or gather more info.

kevin
--
> 
> 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 Mon, Nov 27, 2017 at 12:23 PM, Kevin Fenzi <kevin@scrye.com> wrote:
>> Greetings.
>>
>> I'm running into some problems with Lenovo active pen 2 and wacom tablet
>> on a new yoga 920.
>>
>> Filed:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1514837
>>
>> but I thought I would ask here if anyone had any ideas...
>>
>> Basically when pairing the pen it shows for a second, then drops:
>>
>> [Sat Nov 18 12:22:42 2017] input: Lenovo Active Pen2 as
>> /devices/virtual/misc/uhid/0005:17EF:60A8.0006/input/input23
>> [Sat Nov 18 12:22:42 2017] hid-generic 0005:17EF:60A8.0006:
>> input,hidraw4: BLUETOOTH HID v0.02 Keyboard [Lenovo Active Pen2] on
>> 64:6E:69:D1:A0:48
>> [Sat Nov 18 12:22:47 2017] Bluetooth: hci0: last event is not cmd
>> complete (0x0f)
>> [Sat Nov 18 12:23:03 2017] Bluetooth: hci0: last event is not cmd
>> complete (0x0f)
>> [Sat Nov 18 12:23:19 2017] Bluetooth: hci0: last event is not cmd
>> complete (0x0f)
>>
>> The wacom tablet is never connecting:
>>
>> [Fri Nov 24 21:47:01 2017] input: Wacom HID 5110 Pen as
>> /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input26
>> [Fri Nov 24 21:47:01 2017] input: Wacom HID 5110 Finger as
>> /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input27
>> [Fri Nov 24 21:47:01 2017] wacom 0018:056A:5110.0003: hidraw3: I2C HID
>> v1.00 Mouse [WCOM5110:00 056A:5110] on i2c-WCOM5110:00
>> [Fri Nov 24 21:47:02 2017] i2c_hid i2c-WCOM5110:00: failed to set a
>> report to device.
>> [Fri Nov 24 21:47:02 2017] wacom 0018:056A:5110.0003: wacom_set_report:
>> ran out of retries (last error = -121)
>> [Fri Nov 24 21:47:02 2017] i2c_hid i2c-WCOM5110:00: failed to set a
>> report to device.
>>
>> Happy to gather more info and/or try patches.
>>
>> Thanks.
>>
>> kevin
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Lenovo Active Pen 2 and wacom tablet on yoga 920

[Jason Gerecke]

Sorry about the delay in getting back to you on this issue. It looks
like there are several different reasons that we could be getting
EREMOTEIO from the lower levels. Would you mind running the sysinfo.sh
script described at [1] and filing a bug to the project with the
output attached? This should give me an idea of what kind of hardware
is present in your 920. You might also try doing the following to see
if anything interesting gets printed to the dmesg log:

    # echo "file drivers/i2c/*.c +p" > /sys/kernel/debug/dynamic_debug/control
    # modprobe -r wacom
    # modprobe wacom

Some of the I2C modules (which I suspect your sensor is using) log
debug messages prior to returning EREMOTEIO. The above will cause
these debug messages to be printed to dmesg and then reload the wacom
module. With luck, we might gain a little more information about
what's triggering the error.

[1]: https://github.com/linuxwacom/wacom-hid-descriptors/

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 Thu, Nov 30, 2017 at 12:53 PM, Kevin Fenzi <kevin@scrye.com> wrote:
> On 11/29/2017 01:43 PM, Jason Gerecke wrote:
>> Hi Kevin,
>>
>> The Bluetooth and tablet issues are likely to be unrelated. The
>> Bluetooth button is completely independent from the rest of the
>> tablet, with neither the tablet sensor nor the Wacom driver being
>> aware of it.
>>
>>>From what I understand, in normal operation the Bluetooth button is
>> disconnected most of the time. When you press it, it briefly wakes up,
>> connects to the paired PC, appears as a keyboard, sends a key combo,
>> and then disconnects until you press it again. If you run something
>> like `sudo libinput-debug-events` and then press the button, you
>> should be able to see the key combo being sent (as well as the
>> connect/disconnect). I'm not sure what's up with the deadlock warning
>> that appears in dmesg, however...
>
> Ah, quite right. Sorry about that, this is my first device with a pen. I
> expected it to just connect and stay there, but I suppose doing things
> this way saves a ton of power since it's likely not writing most of the
> time.
>
>>
>> As for the tablet, the "last error = -121" indicates that we got an
>> EREMOTEIO error. I've not come across that particular error in this
>> function before. I'll need some time to track down why we might be
>> getting this from the lower layers.
>
> ok, thanks! If you need any more info from me just ask. Happy to test
> patches or gather more info.
>
> kevin
> --
>>
>> 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 Mon, Nov 27, 2017 at 12:23 PM, Kevin Fenzi <kevin@scrye.com> wrote:
>>> Greetings.
>>>
>>> I'm running into some problems with Lenovo active pen 2 and wacom tablet
>>> on a new yoga 920.
>>>
>>> Filed:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1514837
>>>
>>> but I thought I would ask here if anyone had any ideas...
>>>
>>> Basically when pairing the pen it shows for a second, then drops:
>>>
>>> [Sat Nov 18 12:22:42 2017] input: Lenovo Active Pen2 as
>>> /devices/virtual/misc/uhid/0005:17EF:60A8.0006/input/input23
>>> [Sat Nov 18 12:22:42 2017] hid-generic 0005:17EF:60A8.0006:
>>> input,hidraw4: BLUETOOTH HID v0.02 Keyboard [Lenovo Active Pen2] on
>>> 64:6E:69:D1:A0:48
>>> [Sat Nov 18 12:22:47 2017] Bluetooth: hci0: last event is not cmd
>>> complete (0x0f)
>>> [Sat Nov 18 12:23:03 2017] Bluetooth: hci0: last event is not cmd
>>> complete (0x0f)
>>> [Sat Nov 18 12:23:19 2017] Bluetooth: hci0: last event is not cmd
>>> complete (0x0f)
>>>
>>> The wacom tablet is never connecting:
>>>
>>> [Fri Nov 24 21:47:01 2017] input: Wacom HID 5110 Pen as
>>> /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input26
>>> [Fri Nov 24 21:47:01 2017] input: Wacom HID 5110 Finger as
>>> /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input27
>>> [Fri Nov 24 21:47:01 2017] wacom 0018:056A:5110.0003: hidraw3: I2C HID
>>> v1.00 Mouse [WCOM5110:00 056A:5110] on i2c-WCOM5110:00
>>> [Fri Nov 24 21:47:02 2017] i2c_hid i2c-WCOM5110:00: failed to set a
>>> report to device.
>>> [Fri Nov 24 21:47:02 2017] wacom 0018:056A:5110.0003: wacom_set_report:
>>> ran out of retries (last error = -121)
>>> [Fri Nov 24 21:47:02 2017] i2c_hid i2c-WCOM5110:00: failed to set a
>>> report to device.
>>>
>>> Happy to gather more info and/or try patches.
>>>
>>> Thanks.
>>>
>>> kevin
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-input" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
>

Re: Lenovo Active Pen 2 and wacom tablet on yoga 920

[Kevin Fenzi]

[-- Attachment #1.1: Type: text/plain, Size: 1386 bytes --]

On 12/08/2017 01:24 PM, Jason Gerecke wrote:
> Sorry about the delay in getting back to you on this issue. It looks

No problem at all. Thanks for looking into it!

> like there are several different reasons that we could be getting
> EREMOTEIO from the lower levels. Would you mind running the sysinfo.sh
> script described at [1] and filing a bug to the project with the
> output attached? 

Done:
https://github.com/linuxwacom/wacom-hid-descriptors/issues/9

> This should give me an idea of what kind of hardware
> is present in your 920. You might also try doing the following to see
> if anything interesting gets printed to the dmesg log:
> 
>     # echo "file drivers/i2c/*.c +p" > /sys/kernel/debug/dynamic_debug/control
>     # modprobe -r wacom
>     # modprobe wacom

Seems to say:

# echo "file drivers/i2c/*.c +p" > /sys/kernel/debug/dynamic_debug/control
-bash: /sys/kernel/debug/dynamic_debug/control: Operation not permitted

> 
> Some of the I2C modules (which I suspect your sensor is using) log
> debug messages prior to returning EREMOTEIO. The above will cause
> these debug messages to be printed to dmesg and then reload the wacom
> module. With luck, we might gain a little more information about
> what's triggering the error.

Sadly not... but I will poke and it and see if I can figure out why it's
not working.

kevin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Lenovo Active Pen 2 and wacom tablet on yoga 920

[Jason Gerecke]

[-- Attachment #1: Type: text/plain, Size: 2830 bytes --]

On Fri, Dec 8, 2017 at 2:24 PM, Kevin Fenzi <kevin@scrye.com> wrote:
> On 12/08/2017 01:24 PM, Jason Gerecke wrote:
>> Sorry about the delay in getting back to you on this issue. It looks
>
> No problem at all. Thanks for looking into it!
>
>> like there are several different reasons that we could be getting
>> EREMOTEIO from the lower levels. Would you mind running the sysinfo.sh
>> script described at [1] and filing a bug to the project with the
>> output attached?
>
> Done:
> https://github.com/linuxwacom/wacom-hid-descriptors/issues/9
>
>> This should give me an idea of what kind of hardware
>> is present in your 920. You might also try doing the following to see
>> if anything interesting gets printed to the dmesg log:
>>
>>     # echo "file drivers/i2c/*.c +p" > /sys/kernel/debug/dynamic_debug/control
>>     # modprobe -r wacom
>>     # modprobe wacom
>
> Seems to say:
>
> # echo "file drivers/i2c/*.c +p" > /sys/kernel/debug/dynamic_debug/control
> -bash: /sys/kernel/debug/dynamic_debug/control: Operation not permitted
>
>>
>> Some of the I2C modules (which I suspect your sensor is using) log
>> debug messages prior to returning EREMOTEIO. The above will cause
>> these debug messages to be printed to dmesg and then reload the wacom
>> module. With luck, we might gain a little more information about
>> what's triggering the error.
>
> Sadly not... but I will poke and it and see if I can figure out why it's
> not working.
>
> kevin
>

Thanks for the sysinfo output :) It looks like your system has the
sensor connected through a designware I2C controller. The only place I
see EREMOTEIO used within the designware driver is to signal that it
got a NAK at some point during the transfer. It is supposed to print
out additional details using dev_dbg, but that won't be useful until
the "Operation not permitted" error is overcome.

Some NAK conditions are transient, so its possible that our driver
just needs to retry the command. Please read the page at [1] for
instructions to compile out out-of-tree version of the wacom driver.
In place of the "Download" instructions on that page, use the
"Development" instructions. Once you're set, apply the attached patch
by running `git am /path/to/file.patch` from within the input-wacom
directory. Compile the driver and then load it in place of the system
driver by running `sudo modprobe -r wacom && sudo insmod
4.5/wacom.ko`. Check to see if there's any interesting dmesg output
and if the pen works.

[1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

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....

[-- Attachment #2: 0001-TEST-Always-retry-in-get-set-report.patch --]
[-- Type: text/x-patch, Size: 1140 bytes --]

From 1f846c7d78034b1946080cc9ffb6672f5cfe638c Mon Sep 17 00:00:00 2001
From: Jason Gerecke <killertofu@gmail.com>
Date: Mon, 11 Dec 2017 10:16:11 -0800
Subject: [PATCH input-wacom] TEST: Always retry in get/set report

---
 4.5/wacom_sys.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/4.5/wacom_sys.c b/4.5/wacom_sys.c
index 39aaab0..036b5bb 100644
--- a/4.5/wacom_sys.c
+++ b/4.5/wacom_sys.c
@@ -52,7 +52,7 @@ static int wacom_get_report(struct hid_device *hdev, u8 type, u8 *buf,
 	do {
 		retval = hid_hw_raw_request(hdev, buf[0], buf, size, type,
 				HID_REQ_GET_REPORT);
-	} while ((retval == -ETIMEDOUT || retval == -EAGAIN) && --retries);
+	} while (--retries);
 
 	if (retval < 0)
 		hid_err(hdev, "wacom_get_report: ran out of retries "
@@ -69,7 +69,7 @@ static int wacom_set_report(struct hid_device *hdev, u8 type, u8 *buf,
 	do {
 		retval = hid_hw_raw_request(hdev, buf[0], buf, size, type,
 				HID_REQ_SET_REPORT);
-	} while ((retval == -ETIMEDOUT || retval == -EAGAIN) && --retries);
+	} while (--retries);
 
 	if (retval < 0)
 		hid_err(hdev, "wacom_set_report: ran out of retries "
-- 
2.15.1

Re: Lenovo Active Pen 2 and wacom tablet on yoga 920

[Kevin Fenzi]

[-- Attachment #1.1: Type: text/plain, Size: 2324 bytes --]

On 12/11/2017 10:19 AM, Jason Gerecke wrote:
> 
> Thanks for the sysinfo output :) It looks like your system has the
> sensor connected through a designware I2C controller. The only place I
> see EREMOTEIO used within the designware driver is to signal that it
> got a NAK at some point during the transfer. It is supposed to print
> out additional details using dev_dbg, but that won't be useful until
> the "Operation not permitted" error is overcome.
> 
> Some NAK conditions are transient, so its possible that our driver
> just needs to retry the command. Please read the page at [1] for
> instructions to compile out out-of-tree version of the wacom driver.
> In place of the "Download" instructions on that page, use the
> "Development" instructions. Once you're set, apply the attached patch
> by running `git am /path/to/file.patch` from within the input-wacom
> directory. Compile the driver and then load it in place of the system
> driver by running `sudo modprobe -r wacom && sudo insmod
> 4.5/wacom.ko`. Check to see if there's any interesting dmesg output
> and if the pen works.
> 
> [1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom

So, not much change in dmesg:

[Mon Dec 11 12:38:16 2017] wacom: loading out-of-tree module taints kernel.
[Mon Dec 11 12:38:16 2017] wacom: module verification failed: signature and/or required key missing - tainting kernel
[Mon Dec 11 12:38:18 2017] input: Wacom HID 5110 Pen as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input24
[Mon Dec 11 12:38:18 2017] input: Wacom HID 5110 Finger as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input25
[Mon Dec 11 12:38:18 2017] wacom 0018:056A:5110.0003: hidraw3: I2C HID v1.00 Mouse [WCOM5110:00 056A:5110] on i2c-WCOM5110:00
[Mon Dec 11 12:38:20 2017] i2c_hid i2c-WCOM5110:00: failed to set a report to device.
[Mon Dec 11 12:38:20 2017] wacom 0018:056A:5110.0003: wacom_set_report: ran out of retries (last error = -121)
[Mon Dec 11 12:38:20 2017] i2c_hid i2c-WCOM5110:00: failed to set a report to device.

However, the pen now works. ;) 

The tablet/stylus doesn't show up in gnome prefs oddly, but that could be
a problem in the stack somewhere. ;( 

kevin



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Lenovo Active Pen 2 and wacom tablet on yoga 920

[Jason Gerecke]

On Mon, Dec 11, 2017 at 1:03 PM, Kevin Fenzi <kevin@scrye.com> wrote:
> On 12/11/2017 10:19 AM, Jason Gerecke wrote:
>>
>> Thanks for the sysinfo output :) It looks like your system has the
>> sensor connected through a designware I2C controller. The only place I
>> see EREMOTEIO used within the designware driver is to signal that it
>> got a NAK at some point during the transfer. It is supposed to print
>> out additional details using dev_dbg, but that won't be useful until
>> the "Operation not permitted" error is overcome.
>>
>> Some NAK conditions are transient, so its possible that our driver
>> just needs to retry the command. Please read the page at [1] for
>> instructions to compile out out-of-tree version of the wacom driver.
>> In place of the "Download" instructions on that page, use the
>> "Development" instructions. Once you're set, apply the attached patch
>> by running `git am /path/to/file.patch` from within the input-wacom
>> directory. Compile the driver and then load it in place of the system
>> driver by running `sudo modprobe -r wacom && sudo insmod
>> 4.5/wacom.ko`. Check to see if there's any interesting dmesg output
>> and if the pen works.
>>
>> [1]: http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom
>
> So, not much change in dmesg:
>
> [Mon Dec 11 12:38:16 2017] wacom: loading out-of-tree module taints kernel.
> [Mon Dec 11 12:38:16 2017] wacom: module verification failed: signature and/or required key missing - tainting kernel
> [Mon Dec 11 12:38:18 2017] input: Wacom HID 5110 Pen as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input24
> [Mon Dec 11 12:38:18 2017] input: Wacom HID 5110 Finger as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-6/i2c-WCOM5110:00/0018:056A:5110.0003/input/input25
> [Mon Dec 11 12:38:18 2017] wacom 0018:056A:5110.0003: hidraw3: I2C HID v1.00 Mouse [WCOM5110:00 056A:5110] on i2c-WCOM5110:00
> [Mon Dec 11 12:38:20 2017] i2c_hid i2c-WCOM5110:00: failed to set a report to device.
> [Mon Dec 11 12:38:20 2017] wacom 0018:056A:5110.0003: wacom_set_report: ran out of retries (last error = -121)
> [Mon Dec 11 12:38:20 2017] i2c_hid i2c-WCOM5110:00: failed to set a report to device.
>
> However, the pen now works. ;)
>

\o/

Guess I'll have to add EREMOTEIO to our whitelist of "things to retry on"...

> The tablet/stylus doesn't show up in gnome prefs oddly, but that could be
> a problem in the stack somewhere. ;(
>
> kevin
>
>

GNOME only shows devices that have a libwacom entry, so we'll need to
add one for your device. The sysinfo output you gave should be enough
for me to whip one up. Go ahead and file a bug at
https://github.com/linuxwacom/libwacom/issues with a link to your
wacom-hid-descriptors bug in case somebody else gets to it before me.
If I don't get to it myself in the next few days, please do poke me :)

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....