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: Sun, 07 Jun 2026 07:53:46 +0000 [thread overview]
Message-ID: <bug-221583-215701-ydm822C33h@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 #37 from George (george.stafilidis@proton.me) ---
Created attachment 310279
--> https://bugzilla.kernel.org/attachment.cgi?id=310279&action=edit
Applied the patch
Hey Ron,
I’ve applied the patch and attached an MP4 so you can see what’s happening.
When I press Fn + Space, the OSD message appears correctly, and the quick
settings menu shows the keyboard button with Off / Low / High options. However,
the High setting doesn’t seem to have any effect.
Should this keyboard control button even be visible in this case, or did I mess
something up again?
--
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-07 7:53 UTC|newest]
Thread overview: 45+ 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
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
2026-06-05 17:10 ` bugzilla-daemon
2026-06-05 17:14 ` bugzilla-daemon
2026-06-05 17:18 ` bugzilla-daemon
2026-06-05 17:33 ` bugzilla-daemon
2026-06-05 17:44 ` bugzilla-daemon
2026-06-05 18:17 ` bugzilla-daemon
2026-06-05 18:17 ` bugzilla-daemon
2026-06-05 18:17 ` bugzilla-daemon
2026-06-05 18:18 ` bugzilla-daemon
2026-06-05 18:23 ` bugzilla-daemon
2026-06-05 18:47 ` bugzilla-daemon
2026-06-05 18:58 ` bugzilla-daemon
2026-06-05 20:01 ` bugzilla-daemon
2026-06-05 21:08 ` bugzilla-daemon
2026-06-05 21:09 ` bugzilla-daemon
2026-06-06 17:40 ` bugzilla-daemon
2026-06-06 17:43 ` bugzilla-daemon
2026-06-06 17:51 ` bugzilla-daemon
2026-06-06 18:11 ` bugzilla-daemon
2026-06-06 18:26 ` bugzilla-daemon
2026-06-06 18:31 ` bugzilla-daemon
2026-06-06 19:28 ` bugzilla-daemon
2026-06-06 19:37 ` bugzilla-daemon
2026-06-06 20:58 ` bugzilla-daemon
2026-06-07 7:53 ` bugzilla-daemon [this message]
2026-06-07 7:54 ` bugzilla-daemon
2026-06-07 10:49 ` bugzilla-daemon
2026-06-07 10:51 ` bugzilla-daemon
2026-06-07 11:00 ` bugzilla-daemon
2026-06-07 11:18 ` bugzilla-daemon
2026-06-07 11:21 ` bugzilla-daemon
2026-06-07 11:29 ` 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-ydm822C33h@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.