-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wacom_set_report: ran out of retries (EREMOTEIO) #25
Comments
Looks like a proper fix was never created and sent upstream (just the test patch in your link). We should have something for you to test shortly. |
It appears that some I2C controllers will send EREMOTEIO if a NAK is triggered at some point during the transfer. Some NAK conditions are transient, so it makes sense to retry the get/set command rather than failing, especially if the get/set occurs during the probe process. Ref: https://patchwork.kernel.org/patch/10105647/ Ref: linuxwacom#25 Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
Sorry for the delay. I've created a
|
Same error :( I'm using the correct version, I believe (freshly compiled).
|
Same exact problem on my Lenovo Yoga 920. Touchscreen works fine as well.
|
I haven't been able to come up with any reason the patch shouldn't work, so I've updated my branch to have the same (completely hacky) fix in the linked Yoga 920 thread. Let's see if that at least works, and then work backwards towards something that still reliably sets up the sensor without being as hacky. @AndreaOrru please run @phileas2 Please run |
Sorry for the late response, as you can see the driver is reinstalled properly
But the issue still persists :
But here's another update to the issue:
Once I turn the pen off, the system freeze goes off. And everything works out of the box including the pen itself after turning it on again. There's also a more technical related bug that might solve the issue. |
Hmm. Does what you're experiencing sound like bug #28? The "last error" in your logs is -110 which better matches that bug (as opposed to a "last error" of -121 for this bug). These two bugs could very well be related... @AndreaOrru can you see if your system reports error number -121 while using the fix-issue-25 branch? I wonder if this branch is fixing one error (-121) but then something else is still failing later in the process (-110). |
Oops, nevermind. I forgot that bug #28 is dealing with a system that has a USB-attached sensor, not an I2C-attached sensor like for these systems. Its less likely that they're the same or related issues... |
I'd say it is a system/hardware, not a tablet/driver, issue. Those integrated systems/laptops require more integration testing, which is beyond the scope of this project. |
I'm using the latest version of the driver (0.39.0) on a 4.15.15 kernel (Arch Linux) on my Lenovo Yoga 920. I'm getting the following message when I load the module:
-121
seems to be aEREMOTEIO
error. However, the touchscreen works just fine. Any idea why this is happening?P.S. This seems to be related:
https://patchwork.kernel.org/patch/10105647/
The text was updated successfully, but these errors were encountered: