Bug 201323 - Integrated keyboard not working since linux 4.18 on Acer chromebook Cyan
Summary: Integrated keyboard not working since linux 4.18 on Acer chromebook Cyan
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: Intel Linux
: P1 blocking
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-04 11:56 UTC by Mildred
Modified: 2018-10-07 17:47 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.18.10
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Mildred 2018-10-04 11:56:06 UTC
Since upgrading from kernel 4.17.3 to 4.18.10 (on Fedora) the integrated keyword is not working any more while the trackpad continues to work.

This model aleady had issues with input devices since resolved, see https://bugzilla.kernel.org/show_bug.cgi?id=194945 except the symptoms are different: the touchpad is working and the keystrokes don't seem to be registered at all.
Comment 1 Mildred 2018-10-04 19:32:12 UTC
The touchscreen is not working, neither the keyboard. But the touchpad works. Kernel logs shows:

oct. 04 19:16:40 elayna kernel: elants_i2c i2c-ELAN0001:00: Failed to register interrupt
oct. 04 19:16:40 elayna kernel: elants_i2c: probe of i2c-ELAN0001:00 failed with error -22

full log:

oct. 04 19:16:40 elayna kernel: chromeos ramoops using acpi device.
oct. 04 19:16:40 elayna kernel: elants_i2c i2c-ELAN0001:00: i2c-ELAN0001:00 supply vcc33 not found, using dummy regulator
oct. 04 19:16:40 elayna kernel: elants_i2c i2c-ELAN0001:00: i2c-ELAN0001:00 supply vccio not found, using dummy regulator
oct. 04 19:16:40 elayna kernel: elan_i2c i2c-ELAN0000:00: i2c-ELAN0000:00 supply vcc not found, using dummy regulator
oct. 04 19:16:40 elayna kernel: proc_thermal 0000:00:0b.0: can't derive routing for PCI INT A
oct. 04 19:16:40 elayna kernel: proc_thermal 0000:00:0b.0: PCI INT A: no GSI
oct. 04 19:16:40 elayna kernel: proc_thermal 0000:00:0b.0: No auxiliary DTSs enabled
oct. 04 19:16:40 elayna kernel: dw_dmac INTL9C60:00: DesignWare DMA Controller, 8 channels
oct. 04 19:16:40 elayna kernel: dw_dmac INTL9C60:01: DesignWare DMA Controller, 8 channels
oct. 04 19:16:40 elayna kernel: input: Elan Touchscreen as /devices/platform/808622C1:00/i2c-0/i2c-ELAN0001:00/input/input6
oct. 04 19:16:40 elayna kernel: elants_i2c i2c-ELAN0001:00: Failed to register interrupt
oct. 04 19:16:40 elayna kernel: elants_i2c: probe of i2c-ELAN0001:00 failed with error -22
oct. 04 19:16:40 elayna kernel: elan_i2c i2c-ELAN0000:00: Elan Touchpad: Module ID: 0x002a, Firmware: 0x0007, Sample: 0x000b, IAP: 0x0009
oct. 04 19:16:40 elayna kernel: input: Elan Touchpad as /devices/platform/808622C1:05/i2c-2/i2c-ELAN0000:00/input/input7
Comment 2 Mildred 2018-10-04 19:48:04 UTC
The same dmesg logs from kernel 4.17.3

[   10.422401] chromeos ramoops using acpi device.
[   10.442262] elants_i2c i2c-ELAN0001:00: i2c-ELAN0001:00 supply vcc33 not found, using dummy regulator
[   10.442463] elants_i2c i2c-ELAN0001:00: i2c-ELAN0001:00 supply vccio not found, using dummy regulator
[   10.444927] elan_i2c i2c-ELAN0000:00: i2c-ELAN0000:00 supply vcc not found, using dummy regulator
[   10.455107] proc_thermal 0000:00:0b.0: can't derive routing for PCI INT A
[   10.455112] proc_thermal 0000:00:0b.0: PCI INT A: no GSI
[   10.460400] proc_thermal 0000:00:0b.0: No auxiliary DTSs enabled
[   10.466411] dw_dmac INTL9C60:00: DesignWare DMA Controller, 8 channels
[   10.490390] dw_dmac INTL9C60:01: DesignWare DMA Controller, 8 channels
[   10.534047] input: Elan Touchscreen as /devices/platform/808622C1:00/i2c-0/i2c-ELAN0001:00/input/input4
[   10.562117] elan_i2c i2c-ELAN0000:00: Elan Touchpad: Module ID: 0x002a, Firmware: 0x0007, Sample: 0x000b, IAP: 0x0009
[   10.568274] input: Elan Touchpad as /devices/platform/808622C1:05/i2c-2/i2c-ELAN0000:00/input/input5

(the difference in input device numbers comes from the fact that I booted kernel 4.18 with an external keyboard)
Comment 3 Mildred 2018-10-04 20:15:50 UTC
/proc/interrupts shows two interrupts missing: https://gist.github.com/mildred/76851161886b75e9b74c006f0c042416

 182:          0          0          0       5096  chv-gpio   17  i8042
 184:          0          0          0          0  chv-gpio   19  ELAN0001:00

Those are most probably the keyboard and the touchscreen.
Comment 4 Dmitry Torokhov 2018-10-04 23:13:56 UTC
Is this with original firmware, or alternative one? What does dmidecode show?
Comment 5 Mildred 2018-10-07 17:47:59 UTC
Unfortunately, I cannot provide you with dmidecode, because I now flashed MrChromebox EFI firmware.

The chromebook device was booted in BIOS mide using standard chromeos firmware with RW_LEGACY, a build of MrChromebox dated of 2016. I can provide you with the firmware dump though.

Booted with EFI, there is no keyboard issue. Unfortunately this require removibg a write protection screw, and prevents from dual booting ChromeOS.

Note You need to log in before you can comment on or make changes to this bug.