From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221583] Lenovo 82KU: keyboard backlight works via Fn+Space but no kbd_backlight LED device exposed
Date: Fri, 05 Jun 2026 00:11:56 +0000 [thread overview]
Message-ID: <bug-221583-215701-8gRQ8BrDo6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221583-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221583
--- Comment #8 from George (george.stafilidis@proton.me) ---
Created attachment 310267
--> https://bugzilla.kernel.org/attachment.cgi?id=310267&action=edit
Keyboard showing up on quick settings
Hey, I'm not very good at writing ASL myself, so I asked Qwen to help. I
managed to get it to a point where the OSD popup was working and the keyboard
button showed up in Quick Settings, but it still wasn't changing the keyboard
backlight.
After some more tinkering, I got it so the Quick Settings button would switch
between Off and Low, but it still wouldn't go to High. At this point, I have no
idea what's going on.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-06-05 0:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 19:47 [Bug 221583] New: Lenovo 82KU: keyboard backlight works via Fn+Space but no kbd_backlight LED device exposed bugzilla-daemon
2026-06-01 17:30 ` [Bug 221583] " bugzilla-daemon
2026-06-01 18:06 ` bugzilla-daemon
2026-06-02 13:44 ` bugzilla-daemon
2026-06-02 20:39 ` bugzilla-daemon
2026-06-03 20:13 ` bugzilla-daemon
2026-06-03 21:19 ` bugzilla-daemon
2026-06-04 19:19 ` bugzilla-daemon
2026-06-05 0:11 ` bugzilla-daemon [this message]
2026-06-05 1:36 ` bugzilla-daemon
2026-06-05 1:40 ` bugzilla-daemon
2026-06-05 1:48 ` bugzilla-daemon
2026-06-05 5:55 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-221583-215701-8gRQ8BrDo6@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.