Kip touchpad can't be added by ACPI
Reported by
charliemooney@chromium.org,
Jul 21 2016
|
|||
Issue descriptionA user has submitted a feedback report on their kip and it shows the touchpad failing to connect. It looks like the whole i2c bus might even be toast in some way. feedback report (internal to Google only): http://feedback/#/Report/12610346314 Snippet from /log/var/messages: ... [ 0.149170] i2c i2c-0: failed to add I2C device ATML0000:00 from ACPI [ 0.149809] i2c i2c-0: failed to add I2C device ATML0000:01 from ACPI [ 0.150437] i2c i2c-0: failed to add I2C device ELAN0000:00 from ACPI [ 1.152401] i2c_designware 80860F41:02: controller timed out [ 1.178829] i2c_designware 80860F41:02: timeout in disabling adapter [ 1.178836] i2c i2c-2: failed to add I2C device LSD2918:00 from ACPI ... This was found over on Issue 624001 , but it looks to be a separate problem. The devices effected by that bug were successfully connected to the driver/etc but reported an incorrect product ID that would confuse the FW updater. This device can't get any traction whatsoever when bringing up the touchpad
,
Jul 21 2016
It sounds possibly like that to me. The owner says they have 5 units that are misbehaving. I got logs from 2 of them -- one just needs an update but the other was this device. I've pointed them to this information, so maybe we'll see if there are others like this one in the remaining 3 broken units.
,
Jul 24 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 24 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bleung@chromium.org
, Jul 21 2016