Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#58183 - [linux] 4.13 breaks keyboard on Cherryview devices (Asus C300S Chromebook)

Attached to Project: Arch Linux
Opened by William Osler (LibreWulf) - Tuesday, 10 April 2018, 04:56 GMT
Last edited by Jan Steffens (heftig) - Friday, 25 May 2018, 07:58 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


Description: Upgrading from 4.12 to 4.13 broke the keyboard on my Asus C300S Chromebook, and from what I've read when searching online, other Cherryview based devices. This is because support for this platform was reworked in 4.13. The solution is to enable CONFIG_PINCTRL_CHERRYVIEW=y. Currently, it is set to CONFIG_PINCTRL_CHERRYVIEW=m, which will cause it to load late, which in this case means not working at all. I have confirmed this fix works on 4.15.15-1 by making this change (and changing nothing else), rebuilding the linux package, and installing it.

For more information, see the upstream bug report here:

Additional info:
* linux 4.15.15-1

Steps to reproduce:
* Install any version of the linux package > 4.13
* Boot the system
* Keyboard doesn't work both in early boot nor post boot
This task depends upon

Closed by  Jan Steffens (heftig)
Friday, 25 May 2018, 07:58 GMT
Reason for closing:  Fixed
Additional comments about closing:  linux 4.16.2-2
Comment by Luke V (Wulfsta) - Thursday, 12 April 2018, 05:19 GMT
I can confirm that this happens on the Asus C301SA. These are both reported as TERRA machines by dmidecode.
Comment by William Osler (LibreWulf) - Friday, 25 May 2018, 05:41 GMT
Hi, any updates here, or anything that you need for me? I'd really like to get this change merged in, as right now upgrading the kernel manually is a huge pain, and there are some security related patches that have landed recently in mainline.
Comment by Jan Steffens (heftig) - Friday, 25 May 2018, 07:57 GMT
This was fixed in linux 4.16.2-2.