HP Elite x2 1013 G3: i2c_hid errors on boot about input-wacom HOT 6 CLOSED

With those “failed” message, does your pen and touch still work?

from input-wacom.

Yes, both of touchscreen and pen works.

from input-wacom.

Still trying to understand what's causing these errors. We have logs from a similar system that doesn't show these errors. Information about the Dell XPS 15 9575 (whose HID descriptor is identical aside from min/max values) was received from a user with Linux 4.19-rc0 and Fedora 28. There is no indication of problems on that system.

The error returned from 'wacom_set_device_mode' is -EREMOTEIO. The i2c_designware driver that your system has should only return that error when the transfer is aborted due to a "noack" condition (https://elixir.bootlin.com/linux/latest/source/drivers/i2c/busses/i2c-designware-common.c#L308). This could be due to a bus error, the sensor not responding, or the sensor not liking the commands that we're sending it.

The "supply vdd not found, using dummy regulator" errors may be unrelated, but could also point to possible errors in the system's ACPI tables...

Please try following the instructions to temporarily add a kernel parameter for testing and add the parameter i2c_hid.debug=1 to the end of the kernel commandline. When the system starts up, run journalctl -b0 | grep -Ei -C5 "WCOM|wacom" > ~/wacom-i2c.log and then reboot again to disable the logging. On the second startup, attach the wacom-i2c.log that is in your home directory to this bug.

from input-wacom.

Thank you for looking into this issue!

wacom-i2c.log is here: https://paste.fedoraproject.org/paste/3naM-FsaApf-f-NcNBlkcw

from input-wacom.

The commands being sent to the sensor do look a little suspect, but I'll need more time to fully understand if the data is normal or not...

from input-wacom.

We have no idea what those set commands were doing. Since the device worked and the commands were from i2c_hid, it could be something specific in the common i2c HID layer. Just ignore them.

from input-wacom.