Description of problem: Keyboard backlight worked until upgrading to FC34. The Fn 5 key toggled the keyboard backlight on and off. In researching the new method to expose the Fn keys to the user I found that there is no input/input5. The input/input3 is configured. lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::capslock -> ../../devices/platform/i8042/serio0/input/input3/input3::capslock lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::numlock -> ../../devices/platform/i8042/serio0/input/input3/input3::numlock lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::scrolllock -> ../../devices/platform/i8042/serio0/input/input3/input3::scrolllock lrwxrwxrwx 1 root root 0 Jul 10 16:30 phy0-led -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/leds/phy0-led Version-Release number of selected component (if applicable): 5.14.11-200.fc34.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: A script or kernel option that builds the /sys/class/leds/input/input5 hierarchy. Additional info: If the input5 exists then simply changing the brightness value should turn on the keyboard backlight.
I found that my laptop uses the backlight class as in /sys/class/backlight/amdgpu_bl0. This is the systemctl output: systemctl status systemd-backlight@backlight ○ systemd-backlight - Load/Save Screen Backlight Brightness of backlight Loaded: loaded (/usr/lib/systemd/system/systemd-backlight@.service; static) Active: inactive (dead) Docs: man:systemd-backlight@.service(8) It appears that there are a couple of issues. 1) The brigthness numbers get converted to 5 digits instead of 3 which is not valid. https://bugzilla.kernel.org/show_bug.cgi?id=203905 2) There is a bug in the admgpu kernel driver that enables it even if the backlight device is controlled by AUX. https://unix.stackexchange.com/questions/616371/backlight-control-not-working-on-lenovo-ideapad-gaming-3-with-renoir-amdgpu/637154#637154 #1 is a kernel fix and it might be quite awhile before this gets fixed. Are there any workarounds?
I found this kernel patch (below) that addressed the keyboard backlight. It was developed in 3rd qtr of 2020 for Asus. It was just included in the Asus 5.14.9 kernel release only a couple of weeks ago. I am using kernel 5.14.11 fc34. I can only assume this patch is yet to make its way into Fedora. https://lab.retarded.farm/zappel/asus-rog-zephyrus-g14/-/raw/master/kernel_patches/5.8/5.8.6/0001-HID-asus-add-support-for-ASUS-N-Key-keyboard-v5.8.patch
On occasion and several times the keyboard backlight will come on. The only correlation is that it occurs after the power management wakes up from sleep. The backlight stays on for a couple minutes but as I type "some" key turns it back off. I don't believe it is a character key. More likely return, tab, backspace, etc. This has occurred maybe 4 times in 8 months. Many laptops make the backlight control part of the BIOS settings HP is not one that does. Finally, after witnessing this occasional backlight turning on, I thought could it be a lose connector. I disassembled the laptop to where I could access the 2 keyboard motherboard connectors and found both tightly locked in. I am using the MATE desktop. I believe this issue is in the MATE Power Management code. What steps are necessary to switch to the GNome desktop (Power Management) that would allow me to test this?
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.