Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

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

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#59441 - [linux] ASUS GL502VMK Keyboard backlight no longer working after system upgrade

Attached to Project: Arch Linux
Opened by happy times (happy-times) - Wednesday, 25 July 2018, 04:53 GMT
Last edited by Toolybird (Toolybird) - Sunday, 28 May 2023, 06:41 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After running a full system update (# pacman -Syu)from linux-4.16.8-1-x86_64 to linux-4.17.8-1-x86_64 on July 22 2018, and my system's keyboard backlight stopped responding to commands from their corresponding built-in function keys after rebooting. This had previously never been an issue, and I have never had to touch anything regarding this feature (it just worked). Anyways, the little toggle bar for keyboard backlight appears when the keys are pressed, and it does indeed raise or lower the backlight level according to that toggle bar, but the keyboard does not respond at all (always off). I attempted to change my backlight via a python script that attempts to interface directly with the kbd_backlight dbus and set/retrieve values from there. While the script works perfectly (it does successfully fetch a value for the kbd_backlight from the dbus interface, and that value does change accurately either via the script or via use of the fn keys. This put me at a bit of a loss, but a friend of mine pointed out it could be a kernel bug (he seemed fairly sure of it), and that if that's the case I should reach out to you.

My laptop is an ASUS GL502VMK (16GB RAM, Nvidia Gtx 1060, 1TB hd, 123GB SSD). I've attached an output from dmesg (dmesg-output). The two firmware bugs located here:

//-> [ 306.712716] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x201] vs fed40080 f80
//-> [ 306.713402] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x201] vs fed40080 f80

Have existed on the system since it's initial install, so I don't think they are related. I also am receiving nothing via systemctl --failed.

I've also attached a copy of the aforementioned python script I was utilizing to attempt to change the keyboard brightness levels (kblight).

I've

If this isn't a you issue, and it's actually a me issue, please just let me know and I'll probably just end up starting a new build of Arch. But if possible, I would really love to keep this one.

Thank you so much for your time, and hard work!


Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:

Use an ASUS GL502VMK with linux-4.17.8-1-x86_64, and attempt to change the keyboard backlight brightness via any method (fn keys, cli, etc). None work on my machine.
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 28 May 2023, 06:41 GMT
Reason for closing:  No response
Additional comments about closing:  Plus it's old and stale. If still an issue, please report upstream.
Comment by happy times (happy-times) - Saturday, 28 July 2018, 00:31 GMT
UPDATE:

I dropped my kernel back to linux-4.16.8-1, and they keyboard backlight works as it used to again. Pretty sure this means it's a kernel bug, yes?
Comment by loqs (loqs) - Saturday, 28 July 2018, 19:30 GMT
Assuming it is a kernel bug do you have a patch for it that has been accepted by upstream that the linux package maintainers can apply?
Or something in the PKGBUILD or config that needs changing? Otherwise it would be an upstream issue that would need to be fixed upstream.
Try linux 4.18-rc6 / 4.18-rc7 if the issue has not been fixed in that release report it upstream to the relevant subsystem preferably
after performing a git bisection to locate the causal commit.
Comment by happy times (happy-times) - Saturday, 28 July 2018, 22:26 GMT
UPDATE:

I dropped my kernel back to linux-4.16.8-1, and they keyboard backlight works as it used to again. Pretty sure this means it's a kernel bug, yes?
Comment by loqs (loqs) - Saturday, 28 July 2018, 23:13 GMT
https://bugs.archlinux.org/task/59441#comment171598 is none responsive to https://bugs.archlinux.org/task/59441#comment171592 and has already been answered in detail.
Please do not expect any action to result from this bug report beyond it being assigned to the kernel package maintainers.
Comment by happy times (happy-times) - Sunday, 29 July 2018, 03:35 GMT
Comment by Maksim (DragonX256) - Monday, 10 September 2018, 06:10 GMT
All the same happened on ASUS UX310UQ.
Comment by mattia (nTia89) - Monday, 28 February 2022, 16:42 GMT
I cannot reproduce the issue. Is it still valid for you?

Loading...