<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Touchscreen function broken on F24 Alpha"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95169#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Touchscreen function broken on F24 Alpha"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95169">bug 95169</a>
from <span class="vcard"><a class="email" href="mailto:killertofu@gmail.com" title="Jason Gerecke <killertofu@gmail.com>"> <span class="fn">Jason Gerecke</span></a>
</span></b>
<pre>We once received a report of a Lenovo Yoga Thinkpad 260 producing the same kind
of "wacom_set_report: ran out of retries (last error = -32)" messages, but the
issue apparently resolved itself. We've heard from several other 260 and X1
users, but none of them had this issue.
To debug this further, I would first be interested in knowing if the fix for
another issue affecting the 260 and X1 (pen/touch doesn't work after rebooting
into Linux from Windows) has any effect on this issue. That fix subtly changes
the operation of the code which calls "wacom_set_report" (which is failing for
you) -- perhaps enough to resolve this.
To do this, follow the instructions at [1], except downloading the driver from
[2] instead of from Sourceforge. If all goes well, running `modinfo wacom |
grep version` should show the version as "v2.00-UNKNOWN".
If that doesn't seem to do anything, it would be interesting to know if the
device works properly in Windows. Its hard to say right now if this is a
hardware issue or some subtle software bug that others haven't run into.
[1]: <a href="http://linuxwacom.sourceforge.net/wiki/index.php/input-wacom">http://linuxwacom.sourceforge.net/wiki/index.php/input-wacom</a>
[2]: <a href="https://github.com/linuxwacom/input-wacom/archive/jiri/for-4.6.zip">https://github.com/linuxwacom/input-wacom/archive/jiri/for-4.6.zip</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>