Bug 119531

Summary:	Asus keyboard backlight broken
Product:	Drivers	Reporter:	Antoine Bolvy (antoine.bolvy)
Component:	Other	Assignee:	drivers_other
Status:	RESOLVED CODE_FIX
Severity:	low	CC:	antoine.bolvy, regressions
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	4.7-rc1	Subsystem:
Regression:	No	Bisected commit-id:

Description Antoine Bolvy 2016-06-02 19:39:29 UTC

Hello,

I have an Asus laptop (ROG-G501VW) running Arch Linux, with the mainline kernel from this package: https://aur.archlinux.org/packages/linux-mainline/

Since the release of the 4.7-rc1, the backlight of the keyboard is not controllable anymore.

/sys/class/leds/asus::kbd_backlight is not there anymore

Right now I'm on 4.5 and it works fine, and I'm pretty sure 4.6 works too.

This is my first bug report, so please excuse anything that I could have forgotten to mention, please ask if you need more details.

Comment 1 The Linux kernel's regression tracker (Thorsten Leemhuis) 2016-06-17 11:16:38 UTC

Can you confirm is this bug is still present with rc3 or later? And if yes can you please check which asus driver provided /sys/class/leds/asus::kbd_backlight earlier? There are a few afaics (my Fedora kernel install has asus_atk0110 asus-laptop asus-nb-wmi asus-wireless asus-wmi). Once you figure that out could you make sure that driver is present in the arch package you use?
 Sincerely, your regression tracker for Linux 4.7 (http://bit.ly/28JRmJo )

Comment 2 Antoine Bolvy 2016-06-17 14:14:07 UTC

Hi,

I just confirmed this bug is not present anymore with rc3.

Thanks!

Comment 3 The Linux kernel's regression tracker (Thorsten Leemhuis) 2016-06-19 12:29:00 UTC

(In reply to Antoine Bolvy from comment #2)
> I just confirmed this bug is not present anymore with rc3.

Thx; can you please close this bug? I'm lacking permission to do so; you should have it, as you are the reporter

Comment 4 Antoine Bolvy 2016-06-19 12:54:26 UTC

(In reply to Thorsten Leemhuis from comment #3)
> can you please close this bug?

I closed it as PATCH_ALREADY_AVAILABLE, but I'm not really sure it's the right thing to do tbh ; afaik it's not a duplicate, or is it?
Is there a more appropriate status?

Comment 5 The Linux kernel's regression tracker (Thorsten Leemhuis) 2016-06-19 13:06:21 UTC

I guess "RESOLVED -> CODE_FIX" would be better, but I don't think anybody cares much (and if there is anybody that cares please speak up! ;-) )