I've got an Asus e403SA notebook with the same elan touchpad. My experiences are different from the others. I'm on Ubuntu 15.10 with stock 4.2.x kernel. The touchpad works as a ps/2 mouse without multitouch and recognised as ELAN1000:xxx. With 4.3 or 4.4 kernel everything works fine (recognision, multitouch) but after a while (minutes, sometimes hours) the touchpad freezes.
In the syslog appears these:
Jan 5 20:55:27 darkslide-notebook kernel: [ 1531.867948] i2c_designware 808622C
1:03: Unknown Synopsys component type: 0x00000000
Jan 5 20:55:27 darkslide-notebook kernel: [ 1531.893399] i2c_designware 808622C
1:03: timeout in enabling adapter
Jan 5 20:55:28 darkslide-notebook kernel: [ 1532.892319] i2c_designware 808622C
1:03: controller timed out
Jan 5 20:55:28 darkslide-notebook kernel: [ 1532.892334] i2c_designware 808622C
1:03: Unknown Synopsys component type: 0x00000000
Jan 5 20:55:28 darkslide-notebook kernel: [ 1532.892343] elan_i2c i2c-ELAN1000:00: failed to read report data: -110
Do I need to submit a new ticket or is my problem is because of the same driver bug?
I've got an Asus e403SA notebook with the same elan touchpad. My experiences are different from the others. I'm on Ubuntu 15.10 with stock 4.2.x kernel. The touchpad works as a ps/2 mouse without multitouch and recognised as ELAN1000:xxx. With 4.3 or 4.4 kernel everything works fine (recognision, multitouch) but after a while (minutes, sometimes hours) the touchpad freezes.
In the syslog appears these:
Jan 5 20:55:27 darkslide-notebook kernel: [ 1531.867948] i2c_designware 808622C
1:03: Unknown Synopsys component type: 0x00000000
Jan 5 20:55:27 darkslide-notebook kernel: [ 1531.893399] i2c_designware 808622C
1:03: timeout in enabling adapter
Jan 5 20:55:28 darkslide-notebook kernel: [ 1532.892319] i2c_designware 808622C
1:03: controller timed out
Jan 5 20:55:28 darkslide-notebook kernel: [ 1532.892334] i2c_designware 808622C
1:03: Unknown Synopsys component type: 0x00000000
Jan 5 20:55:28 darkslide-notebook kernel: [ 1532.892343] elan_i2c i2c-ELAN1000:00: failed to read report data: -110
Do I need to submit a new ticket or is my problem is because of the same driver bug?