- This topic has 2 replies, 2 voices, and was last updated Jan 19-10:43 am by stevesr0.
-
Posts
-
stevesr0
I recently installed antix 17.1 to a second laptop. It is in a dual boot using GRUB on a GPT partitioned machine. When I select antiX, the first few lines of the boot are i2c_hid i2c_ITE8386:00: failed to reset device.
Searched online and saw only references to MSINFO. Not sure if this is related to having two OSes on the one machine. THEY ARE IN SEPARATE PARTITIONS.
After boot is complete, everything was running as normal until today. When the system finished boot, the mouse didn’t respond. The mouse cursor sat there, fixed on the machine.
After I shut down the computer and rebooted, the mouse is working normally.
Two questions:
1. Anybody familiar with this error message?2. Is it dealing with the mouse as an hid?
I am not sure how to identify which device it refers to – and the error is always the same, even though the mouse is usually working.
Thanks.
stevesr0
rokytnji
No to questions 1 & 2. I don’t dual boot. Windows has it’s own hard drive for tuning motorcycles.
Intermittent one off failures like the mouse? No telling. May be hardware or software. I usually use dmesg when looking for reasons for failures,
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsUPDATE: Kernel.org Bugzilla – Bug 205745 i2c_hid i2c-SYNA7DB5:01: failed to reset device.
This seems to be related to my error message.
A patch has been included in kernel 5.4.1-arch1-1 2 weeks ago.
Not sure when this will be in a kernel that I can try for antiX.
For anyone who has had a similar mouse/touchpad error.
stevesr0
- You must be logged in to reply to this topic.
