Touch screen not working on Acer Chromebook R11, CONFIG_TOUCHSCREEN_ELAN not enabled on mainline 4.7 kernel

[Timo Jyrinki]

Touch screen seems to be identified as far as I can see, but there's no working input. I've tried among else xinput test-xi2, reattach command but it seems simply non-functional for whatever reason.

It works on the ChromeOS side.

The machine is Acer Chromebook R11 (codename CYAN).

WORKAROUND: Enable CONFIG_TOUCHSCREEN_ELAN manually via a recompilation, and use mainline kernel 4.7+.

---
ApportVersion: 2.20.3-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
InstallationDate: Installed on 2016-07-22 (13 days ago)
InstallationMedia:

Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: GOOGLE Cyan
Package: linux-image-4.4.0-33-generic 4.4.0-33.52
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-33-generic N/A
 linux-backports-modules-4.4.0-33-generic N/A
 linux-firmware 1.159
Tags: yakkety
Uname: Linux 4.4.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/20/2016
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: GOOGLE
dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
dmi.product.name: Cyan
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7

[Timo Aaltonen (tjaalton)]

it is a kernel bug, closing for xorg

[Timo Jyrinki (timo-jyrinki)]

No change on 4.7 mainline kernel.

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

apport information

[Timo Jyrinki (timo-jyrinki)]

Actually there was a change: with mainline 4.7 kernel there is no trace of the touchscreen anymore in dmesg or xinput.

[Timo Jyrinki (timo-jyrinki)]

The actual problem/bug is that for some reason the mainline Ubuntu 4.7 kernel lacks CONFIG_TOUCHSCREEN_ELAN. In 4.4 Ubuntu kernel CONFIG_TOUCHSCREEN_ELAN is defined, but the touchscreen doesn't work.

However with mainline Ubuntu kernel sources, and CONFIG_TOUCHSCREEN_ELAN enabled manually via a recompilation, touch screen now works! That means the touchscreen does work with mainline kernel but Ubuntu config is wrong for 4.7.

[penalvch (penalvch)]

Timo Jyrinki, the next step is to fully reverse commit bisect from kernel 4.4 to 4.7 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Thank you for your help.