FS#35253 - [linux] 3.9.x - 3.10.x asus laptop function keys not working after kernel upgrade from 3.8

Attached to Project: Arch Linux
Opened by Alfonso (euoar) - Monday, 13 May 2013, 22:43 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 10 October 2013, 10:09 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The laptop: Asus k55v. Function keys don't work after upgrading to the latest kernel (3.9). The same keys functioned well with linux kernel 3.8.

Additional info:
* package version(s): linux-3.9.2-1


Steps to reproduce:

Try to use any of the function keys present in the laptop, like for example the key for adjusting brightness, volume, etc. None of them work.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 10 October 2013, 10:09 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.11.1
Comment by Alfonso (euoar) - Monday, 13 May 2013, 22:54 GMT
This seems to be happening with other asus models too:

https://bbs.archlinux.org/viewtopic.php?pid=1272271#p1272271
Comment by Osman Alperen Elhan (alperenel) - Wednesday, 15 May 2013, 11:22 GMT
i am having the same problem with my asus ux32vd. I had to downgrade linux to 3.8.11
Comment by Sergey Khoroshavin (xop) - Thursday, 16 May 2013, 11:42 GMT
Same problem, asus k73sv. I think this bug is linked to this: https://bugs.archlinux.org/task/35320
Comment by Alfonso (euoar) - Sunday, 19 May 2013, 01:49 GMT
Thanks for the link, Sergey. The solution proposed there by Lachlan (padfoot) works for me ("adding asus-nb-wmi to the modules array in mkinitcpio.conf and running mkinitcpio -p linux"). Keys working now...
Comment by Tobias Powalowski (tpowa) - Tuesday, 30 July 2013, 10:42 GMT
Status on 3.10.x?
Comment by Alfonso (euoar) - Thursday, 01 August 2013, 22:10 GMT
Tested. The issue is still present with kernel 3.10.3-1
Comment by Alfonso (euoar) - Thursday, 01 August 2013, 23:03 GMT
Tested. The issue is still present with kernel 3.10.3-1
Comment by Tobias Powalowski (tpowa) - Friday, 02 August 2013, 09:09 GMT
Please report this upstream that it can be solved.
Thanks.
Comment by Tobias Powalowski (tpowa) - Tuesday, 17 September 2013, 09:55 GMT
Status on 3.11.1?

Loading...