Bug 195027 - Touchpad not working, FN keys and keyboard backlight on ASUS g752VS
Summary: Touchpad not working, FN keys and keyboard backlight on ASUS g752VS
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Platform (show other bugs)
Hardware: x86-64 Linux
: P1 blocking
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-24 17:44 UTC by Pedro
Modified: 2017-05-23 14:25 UTC (History)
5 users (show)

See Also:
Kernel Version: 4.8.0-42 generic
Tree: Mainline
Regression: No


Attachments
linux 4.8.0 kernel .config file (194.89 KB, text/x-mpsub)
2017-03-24 17:44 UTC, Pedro
Details
dmesg output file (65.41 KB, text/plain)
2017-03-24 17:45 UTC, Pedro
Details
acpidump file (1020.67 KB, text/plain)
2017-03-24 17:46 UTC, Pedro
Details
grep . /sys/firmware/acpi/interrupts/* (7.35 KB, text/plain)
2017-03-24 17:47 UTC, Pedro
Details
/proc/interrupts (4.89 KB, text/plain)
2017-03-24 17:47 UTC, Pedro
Details
dmidecode (12.19 KB, text/plain)
2017-03-24 17:48 UTC, Pedro
Details
ls -latr /sys/class/leds/ (2.30 KB, text/plain)
2017-03-24 17:49 UTC, Pedro
Details
lsmod (6.23 KB, text/plain)
2017-04-04 22:03 UTC, Pedro
Details

Description Pedro 2017-03-24 17:44:42 UTC
Created attachment 255505 [details]
linux 4.8.0 kernel .config file

I'm dualbooting Windows 10 and Ubuntu 16.0.4.2, tried Ubuntu 17.04 live cd with kernel 4.10.13 too, fedora 25, and all of these problems persist.

Can't manage to have the backlight keyboard working, 

The fn keys for brightness, keyboard light, switch displays, which are f1 through f9 don't have any use.

And most importantly the Touchpad doesn't function at all.

~$ xinput --list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ ASUS ROG SICA                           	id=10	[slave  pointer  (2)]
⎜   ↳ ASUS ROG SICA                           	id=11	[slave  pointer  (2)]
⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey      	id=14	[slave  pointer  (2)]
⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey      	id=15	[slave  pointer  (2)]
⎜   ↳ ELAN1203:00 04F3:301E Touchpad          	id=16	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Asus Wireless Radio Control             	id=7	[slave  keyboard (3)]
    ↳ Video Bus                               	id=8	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam                    	id=12	[slave  keyboard (3)]
    ↳ ASASTeK COMPUTER INC. ROG MacroKey      	id=13	[slave  keyboard (3)]
    ↳ Asus WMI hotkeys                        	id=17	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=18	[slave  keyboard (3)]
Comment 1 Pedro 2017-03-24 17:45:45 UTC
Created attachment 255507 [details]
dmesg output file
Comment 2 Pedro 2017-03-24 17:46:25 UTC
Created attachment 255509 [details]
acpidump file
Comment 3 Pedro 2017-03-24 17:47:05 UTC
Created attachment 255511 [details]
grep . /sys/firmware/acpi/interrupts/*
Comment 4 Pedro 2017-03-24 17:47:38 UTC
Created attachment 255513 [details]
/proc/interrupts
Comment 5 Pedro 2017-03-24 17:48:30 UTC
Created attachment 255515 [details]
dmidecode
Comment 6 Pedro 2017-03-24 17:49:15 UTC
Created attachment 255517 [details]
ls -latr /sys/class/leds/
Comment 7 nnmware 2017-03-25 22:27:05 UTC
This problems with many new ASUS notebooks(see bugs 191651, 112531) :( Very bad then Asus don't want help linux community solve this problems, but linux acpi developers, which can solve this-don't have time/etc. :(
Comment 8 Zhang Rui 2017-03-28 06:15:14 UTC
TBH, this sounds like we are missing driver support for some Asus laptop devices, and this should be a vendor driver issue.

And I don't think Linux ACPI developers have the knowledge to fix this.

Reassign to platform drivers.
Comment 9 Pedro 2017-03-28 19:44:13 UTC
Ok, I changed to drivers, platform, is that more adequate now? Thank you Zhang Rui
Comment 10 Darren Hart 2017-04-04 21:52:05 UTC
Hi Pedro,

The Asus drivers rely heavily on DMI match to enable some of these features. If you have the ability to build and test kernels, it will be much easier for us (the Platform Driver X86 team) to help get your laptop supported. Is that something you can do?

Something that would be helpful for us is to get an ACPI dump (acpica-tools) and a dmidecode dump from you.

$ sudo dmidecode > dmidecode.log

$ mkdir acpi
$ cd acpi
$ acpidump -b
$ iasl -d *.dat
$ rm *.dat
$ cd ..
$ tar cjf acpi.tar.bz2 acpi

Then attach the dmidecode.log and the acpi.tar.bz2 files here. We probably only need dsdt.dsl if you don't want to post it all, but we may have to come back to you for the more.
Comment 11 Darren Hart 2017-04-04 21:58:26 UTC
Also, please provide the output of "lsmod" to list which drivers are loaded.
Comment 12 Pedro 2017-04-04 22:03:34 UTC
Created attachment 255763 [details]
lsmod

lsmod
Comment 13 Pedro 2017-04-04 22:06:06 UTC
I had added already dmidecode and acpi tables but they have all the acpi information, some that concerned me it may have private information or device specific, however I had them marked obsolete since I couldn't edit or delete them.

Thank you for your help.
Comment 14 Darren Hart 2017-04-04 22:52:00 UTC
OK, so the _WDG buffer contains the ASUS_BM_WMI_EVENT_GUID, so we should be able to support it by figuring out which quirks are right for your laptop, and then adding an entry matching your DMI data to the asus_quirks[] table - at a minimum. It's possible it will also need a new quirk. I'm going to review with Corentin for the best way to go about testing changing. We'll pick this up on list.
Comment 15 Darren Hart 2017-04-04 23:15:10 UTC
Aha, looking at those other bugs, we need to first determine how these keys are connected. Since I don't have this laptop in front of me, can you enumerate which keys exist, and which keys work (if any) already. I'm beginning to think this is not an asus_nb_wmi hotkey issue, but rather an asus_hid and elan touch issue, as noted in the other bugs.
Comment 16 Pedro 2017-04-05 11:06:46 UTC
I can't make the combo keys fn + f1,f2,...,f9. They are not recognised.

f1 - sleep,
f2 - airplane mode,
f3 and f4 - keyboard backlight,
f5 and f6 - screen brightness,
f8 - display mode,
f9 - touchpad on and off

Thank you.
Comment 17 gonzalo 2017-05-23 14:25:03 UTC
The new kernel fixed all of my FN keys on a G752VS, however the Elantech 1203 touchpad is still dead. The following lines appear while booting:

[6.110760] i2c_designware i2c_designware.1: controller timed out
[6.110768] i2c_hid i2c-ELAN1203:00: hid_descr_cmd failed

Once booted I no longer see this in xinput:

ELAN1203:00 04F3:301E Touchpad id=15 [slave pointer (2)] 

With the previous kernel 4.10 this was still present in xinput.

Also when I press the FN key F9 to enable/disable touchpad, the system displays only disable.

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