"[ 792.858712] elan_i2c i2c-ELAN0000:00: invalid report id data (ff)" is taking up computer space.

Asked by Erick Pokladowski on 2019-02-07

So, when I try to go into shell, all I get is this:

[ 792.858712] elan_i2c i2c-ELAN0000:00: invalid report id data (ff)

Spammed. All over. Also, in syslog, that file grows and grows every millisecond. It is starting to push my computer to the limit. Could someone help me resolve this?

Edit: I solved the space problem.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2019-02-15
Last reply:
2019-02-15

Seems to relate to the touchpad. Is the system a laptop?

The system is a Braswell chipset. Yes, it is a laptop. More specifically, a setzer.

Manfred Hampl (m-hampl) said : #3

Maybe the command

sudo modprobe -rv elan_i2c

can help to stop the messages.

(This would be just a quick and dirty workaround for the symptoms, not caring for the root cause.)

If the command stops the messages and the system works as normal we can make this configuration stick

It just turned my trackpad off. My computer has a touchscreen.

i2c-ELAN0000:00 does not seem to exist, so I think that is the problem...

I updated the info, this is starting to get out of hand.

Manfred Hampl (m-hampl) said : #8

1. "my computer stays at 12.3 GB no matter what I delete"
What stays at 12.3 GB - Free memory, hard disk usage, hard disk free space amount, ...?

What is the output of the commands
df -h
sudo du -sch /*

2. elan_i2c is the kernel driver for a certain type of Elan touchpads. Do you know what make your touchpad is?

3. there are some bug reports about similar problems. e.g. Bug #1793960 but I think you already found them yourself.

1. hard disk usage

Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 390M 2.0M 388M 1% /run
/dev/mmcblk0p2 14G 9.1G 4.1G 69% /
tmpfs 1.9G 17M 1.9G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/loop0 7.5M 7.5M 0 100% /snap/canonical-livepatch/54
/dev/loop2 208M 208M 0 100% /snap/firefox/172
/dev/loop1 91M 91M 0 100% /snap/core/6350
/dev/mmcblk0p1 511M 4.8M 507M 1% /boot/efi
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 390M 20K 389M 1% /run/user/122
tmpfs 390M 2.5M 387M 1% /run/user/1000

16M /bin
150M /boot
4.0K /cdrom
24K /dev
16M /etc
1.5G /home
0 /initrd.img
0 /initrd.img.old
763M /lib
4.0K /lib64
16K /lost+found
20K /media
4.0K /mnt
du: cannot access '/proc/456/fdinfo/191': No such file or directory
du: cannot access '/proc/3751/task/3751/fd/4': No such file or directory
du: cannot access '/proc/3751/task/3751/fdinfo/4': No such file or directory
du: cannot access '/proc/3751/fd/4': No such file or directory
du: cannot access '/proc/3751/fdinfo/4': No such file or directory
0 /proc
91M /root
du: cannot access '/run/user/1000/gvfs': Permission denied
2.0M /run
16M /sbin
950M /snap
4.0K /srv
0 /sys
104K /tmp
3.9G /usr
2.8G /var
0 /vmlinuz
0 /vmlinuz.old
10G total

2. No, but it is definitely Elan

Manfred Hampl (m-hampl) said : #10

Let me try summing up what my assumptions are, partly based on Bug #1793960

You have a computer with an ELAN touchpad.
There seems to be something wrong with the driver for ELAN touchpads, leading to the situation that lots of messages "elan_i2c i2c-ELAN0000:00: invalid report …" are shown, filling up the system log.

Unloading the driver (with the command "sudo modprobe -rv elan_i2c") will stop these messages, but will also disable the touchpad. I assume that with every boot the broken driver(s) get loaded again, and this will start issuing these messages again. So you have to issue the "modprobe" command after each boot to avoid filling the log files - or to disable that the module elan_i2c gets loaded by blacklisting that module.

There are large system log files on your system, due to these messages, occupying hard disk space.
The system logs are stored below /var/log

What is the output of
ls -l /var/log/
You should be able to delete big old files (with names ending with .gz) to free up space on the hard disk.

Bug #1793960 talks about a problem that two different drivers for the ELAN touchpad might be loaded at the same time, leading to that problem.
What is the output of the command
lsmod | grep -i i2c

emattpoyourebooted@braswell-setzer:~$ ls -l /var/log/
total 1599088
-rw-r--r-- 1 root root 35195 Feb 9 13:50 alternatives.log
-rw-r----- 1 root adm 1774 Feb 9 13:52 apport.log
-rw-r----- 1 root adm 3266 Feb 9 11:24 apport.log.1
drwxr-xr-x 2 root root 4096 Feb 9 12:54 apt
-rw-r----- 1 syslog adm 44052 Feb 9 14:01 auth.log
-rw------- 1 root root 20341 Feb 9 13:51 boot.log
-rw-rw---- 1 root utmp 0 Jan 28 2018 btmp
drwxr-xr-x 2 root root 4096 Feb 9 11:29 cups
drwxr-xr-x 6 root root 4096 Feb 9 12:57 dist-upgrade
-rw-r--r-- 1 root root 1393068 Feb 9 12:58 dpkg.log
-rw-r--r-- 1 root root 11630 Feb 9 12:34 fontconfig.log
drwxr-xr-x 2 root root 4096 Feb 8 14:11 fsck
drwx--x--x 2 root gdm 4096 Oct 9 04:42 gdm3
-rw-r--r-- 1 root root 1252 Feb 9 13:51 gpu-manager.log
drwxr-xr-x 3 root root 4096 Feb 28 2017 hp
drwxr-xr-x 2 root root 4096 Feb 8 14:11 installer
drwxr-sr-x+ 3 root systemd-journal 4096 Feb 5 14:39 journal
-rw-r----- 1 syslog adm 816640530 Feb 9 14:05 kern.log
-rw-rw-r-- 1 root utmp 37084 Feb 9 12:35 lastlog
drwxr-xr-x 2 root root 4096 Feb 8 14:11 lightdm
drwxr-xr-x 2 ntp ntp 4096 Oct 5 2016 ntpstats
drwxr-xr-x 2 root root 4096 Sep 3 04:57 openvpn
drwx------ 2 root root 4096 Feb 9 12:13 private
drwxr-x--- 2 root adm 4096 Dec 12 2016 samba
drwx------ 2 speech-dispatcher root 4096 Feb 18 2016 speech-dispatcher
-rw-r----- 1 syslog adm 288122212 Feb 9 14:05 syslog
-rw-r----- 1 syslog adm 531055319 Feb 9 12:32 syslog.1
-rw------- 1 root root 8128 Feb 9 12:35 tallylog
drwxr-x--- 2 root adm 4096 Feb 9 11:25 unattended-upgrades
drwxr-xr-x 2 root root 4096 Feb 9 12:49 upgrade
-rw-rw-r-- 1 root utmp 12288 Feb 9 13:52 wtmp
emattpoyourebooted@braswell-setzer:~$ lsmod |grep -i i2c
i2c_algo_bit 16384 1 i915
regmap_i2c 16384 2 snd_soc_rt5640,snd_soc_rt5645
elan_i2c 40960 0
i2c_hid 28672 0
hid 131072 1 i2c_hid
i2c_designware_platform 16384 0
i2c_designware_core 24576 1 i2c_designware_platform
i2c_core 69632 11 i2c_designware_platform,i2c_hid,i2c_designware_core,drm_kms_helper,i2c_algo_bit,snd_soc_rt5640,elan_i2c,snd_soc_rt5645,i915,regmap_i2c,drm
emattpoyourebooted@braswell-setzer:~$

I solved my space problem, but the touchpad is now going crazy with the 4.20 kernel on 18.10. It would stop working randomly, forcing me to use a backup mouse.

Manfred Hampl (m-hampl) said : #13

Just a guess, based on Bug #1793960

What output do you receive for the commands

sudo modprobe -rv i2c_hid
sudo modprobe -rv elan_i2c
sudo modprobe -v elan_i2c

After issuing these commands, do you still get the "invalid report id data" messages?
Does the touchpad work then?

emattpoyourebooted@braswell-setzer:~$ sudo modprobe -rv i2c_hid
[sudo] password for emattpoyourebooted:
3rSorry, try again.
[sudo] password for emattpoyourebooted:
Sorry, try again.
[sudo] password for emattpoyourebooted:
rmmod i2c_hid
emattpoyourebooted@braswell-setzer:~$ sudo modprobe -rv i2c_hid
emattpoyourebooted@braswell-setzer:~$ sudo modprobe -rv i2c_hid
emattpoyourebooted@braswell-setzer:~$ sudo modprobe -rv elan_i2c
rmmod elan_i2c
emattpoyourebooted@braswell-setzer:~$ sudo modprobe -v elan_i2c
insmod /lib/modules/4.20.7-042007-generic/kernel/drivers/input/mouse/elan_i2c.ko
emattpoyourebooted@braswell-setzer:~$

The touchpad works better, but I still get the error. I am starting to think that I need to edit an ID to make it work correctly...

So, what file holds the drivers? Where is it? What do I change in it?

Also, I remember that I disabled my touchscreen because I thought it had annoyed me with my touchpad, and after I did that, i started getting the errors.

My touchscreen ID is SYTS7508:00, so that could be a problem...

Manfred Hampl (m-hampl) said : #18

The driver file is /lib/modules/4.20.7-042007-generic/kernel/drivers/input/mouse/elan_i2c.ko

The version number looks strange to me. This is not the standard Ubuntu kernel version.
Did you manually download a specific kernel version from somewhere else?
Did you have this problem also with the standard kernel version?

Please provide the output of the commands

uname -a
lsb_release -crid
modinfo elan_i2c

Linux braswell-setzer 4.20.07-042007-generic #201902061234 SMP Wed Feb 6 17:36:40 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I have kernel version 4.20.07, which is the latest kernel. (Nice)

Distributor ID: Ubuntu
Description: Ubuntu 18.10
Release: 18.10
Codename: cosmic

I found the ELAN0000:* driver which is causing problems. I will use nano on the file to fix.

I had the problem with the last kernel.

Manfred Hampl (m-hampl) said : #23

Even if you think that having kernel version 4.20.07 is nice, this is not the standard version delivered by Ubuntu.
You have to be aware that the elan_i2c driver is part of that kernel. And if it is not behaving correctly, then this might be caused by using that foreign kernel version.

I will downgrade, see what that does...

I still have my original kernel, 4.14.29-galliumos, and I am trying that one...

I still have my original kernel, 4.14.29-galliumos, and I am trying that one...

I still have my original kernel, 4.14.29-galliumos, and I am trying that one...

Typing on Mobile is tricky, so expect tons of duplicates until I get the hang of it.

18.10 also came with 4.18, because 4.14 didn’t wanna work with me.

My splash doesn’t wanna work either...

After waiting a while (and surfing the internet for answers) I got my splash working with my login screen. I still get the error on the 4.18 kernel, 4.14 does the same.

Manfred Hampl (m-hampl) said : #32

"4.14.29-galliumos" does not look like being an Ubuntu-provided version of the kernel, but from a foreign source (probably Gallium OS).

What is the output of:

head /etc/apt/sources.list

Thanks

GalliumOS is just Ubuntu but with a different kernel specifically for
Chromebooks.

On Mon, Feb 11, 2019 at 8:02 AM Manfred Hampl <
<email address hidden>> wrote:

> Your question #678393 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/678393
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> "4.14.29-galliumos" does not look like being an Ubuntu-provided version
> of the kernel, but from a foreign source (probably Gallium OS).
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/678393/+confirm?answer_id=31
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/678393
>
> You received this question notification because you asked the question.
>
--
Sincerely,

Erick Pokladowski

# deb cdrom:[GalliumOS 2.1 - Release amd64 (20170228)]/ apt/

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://us.archive.ubuntu.com/ubuntu/ cosmic main restricted
deb-src http://us.archive.ubuntu/ubuntu/ xenial main restricted

## Major bug fix updates produced after the final release of the
## distribution
deb http://us.archive.ubuntu/ubuntu/ cosmic-updates main restricted

Galliumos is not Ubuntu so is not supported by the Ubuntu community in any way.

Its support and community are entirely separate from Ubuntu's. I suggest you post on the Galliumos forum here:
https://wiki.galliumos.org/Community

None of the "Ubuntu based" distributions are supported here.

Thanks

I tried contacting their reddit for help, but no one even said anything. It seems much in need for help, with not enough people to help.

And now I think I accidentally took up the disk space, causing me to not being able to boot up successfully.

The system puts me in TTY 1 and since this error occurs about 1,000 times a second, I can’t even start LightDM through the terminal.

Even if I switch TTYs I still have the error spamming the terminal.

Should I SD boot and clear disk by installing Ubuntu again?

Should I SD boot and clear disk by installing Ubuntu again?

That's what happens. You aren't using Ubuntu so you aren't supported here. Dead simple

Let me explain it: Linux/GNU > Debian > Ubuntu > GalliumOS. It is Ubuntu on the inside, but it looks different.

Let me explain it: Linux/GNU > Debian > Ubuntu > GalliumOS. It is Ubuntu on the inside, but it looks different.

I know all that. I'm a Linux engineer by trade having used Ubuntu since 1999. When you were getting excited about installing Windows XP I was using Linux. What you said isn't news to me and doesn't need explaining to me.

Ubuntu is based on Debian but if you ask for Ubuntu support in the Debian forums they will point you to the Ubuntu support channels because the support for Ubuntu and Debian is separate.

This is the same for Galliumos. You aren't using Ubuntu. There are distribution agnostic forums for Linux distributions but this one is ONLY for official Canonical releases.

Ok. So I just did a reinstall of 18.10, and I still have this error. I wiped the drive in the process because, well, having everything that I have isn’t really needed. My keyboard works, but my touchpad randomly stops working.

Sent from my iPad

> On Feb 12, 2019, at 8:43 AM, actionparsnip <email address hidden> wrote:
>
> Your question #678393 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/678393
>
> actionparsnip proposed the following answer:
> I know all that. I'm a Linux engineer by trade having used Ubuntu since
> 1999. When you were getting excited about installing Windows XP I was
> using Linux. What you said isn't news to me and doesn't need explaining
> to me.
>
> Ubuntu is based on Debian but if you ask for Ubuntu support in the
> Debian forums they will point you to the Ubuntu support channels because
> the support for Ubuntu and Debian is separate.
>
> This is the same for Galliumos. You aren't using Ubuntu. There are
> distribution agnostic forums for Linux distributions but this one is
> ONLY for official Canonical releases.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/678393/+confirm?answer_id=45
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/678393
>
> You received this question notification because you asked the question.

I can make my touchpad work by doing sudo rmmod elan_i2c sudo modprobe elan_i2c. It still stops working though.

Manfred Hampl (m-hampl) said : #49

Re: "sudo rmmod elan_i2c && sudo modprobe elan_i2c":
This is exactly what is written in Bug #1793960

If there is no progress in the bug report, then there is nothing what can be done in this question document.
I recommend that you focus on the bug tracker.

Can you help with this problem?

Provide an answer of your own, or ask Erick Pokladowski for more information if necessary.

To post a message you must log in.