1

I just installed Arch Linux on my Laptop (Lenovo Y720 Gaming laptop). 9/10 times I boot the drive it just spams me with:

i2c_hid i2c-ite33d1:00: i2c_hid_get_input: incomplete report (2/4)

(Attached in the image below).

It outputs like a couple hundred thousand of these messages infinitely and I can't access the system for further installation/configuration.

People reported a similar problem with some ELAN device, but I don't have that (or I'm not aware of it). I found that there was a fix for this in the kernel 2 years ago but I can't seem to bypass it.

EDIT: The fix was committed here, but it's somewhat not for the same error.

enter image description here

Improve this question
2
  • Try blacklisting the module that's causing this. I assume by "you can't access the system" you mean "the error messages get in the way, so I can't type"? If yes, (a) try a different VT (CTRL-ALT-F2 etc.), or try to ssh in from another computer. Then do an lsmod, or look at syslog/dmesg to identify the module that's causing it.
    – dirkt
    Commented Jan 2, 2020 at 12:12
  • this seems to be a common issue with touchpads on Asus laptops.
    – Michael Altfield
    Commented Dec 30, 2020 at 22:47

2 Answers 2

Reset to default
1

Had the same bugs with y720, and solved it as follows:

  1. sudo vim /etc/default/grub
  2. exchange this line :
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi="
  3. sudo update-grub
  4. reboot
Improve this answer
2
  • Did you do this from the Live USB or were you able to boot in the system?
    – HenrijsS
    Commented Jan 2, 2020 at 12:16
  • in my case , it seems to be a problem with the touchpad . the system boot right, and cpu came down。
    – piaohao
    Commented Jan 3, 2020 at 1:51
0

I was able to solve this by unloading/blacklisting the i2c_hid kernel module. I have not observed any loss of functionality after doing that (keyboard and touchpad still work).

I have found that a patch was very recently added to the kernel which silences these kernel messages. I have tested it but found that while it does fix the messages, there is still high CPU usage (about 25% of one core) due to the interrupt firing all the time. Unloading the kernel module stopped this.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .