From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221583] New: Lenovo 82KU: keyboard backlight works via Fn+Space but no kbd_backlight LED device exposed
Date: Wed, 27 May 2026 19:47:27 +0000 [thread overview]
Message-ID: <bug-221583-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221583
Bug ID: 221583
Summary: Lenovo 82KU: keyboard backlight works via Fn+Space but
no kbd_backlight LED device exposed
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: george.stafilidis@proton.me
Regression: No
Laptop: Lenovo 82KU
Distribution: Fedora
Kernel: (paste output of uname -r)
Problem:
Keyboard backlight works correctly using Fn+Space
(Off -> Low -> High), but Linux exposes no keyboard
backlight LED interface.
No device appears under:
/sys/class/leds/
Expected behavior:
A standard LED interface such as:
platform::kbd_backlight
or
ideapad::kbd_backlight
Current result:
GNOME cannot expose keyboard backlight controls because
no LED device exists.
Tested:
* modprobe ideapad_laptop
* reboot
* latest Fedora updates
Outputs:
$ ls /sys/class/leds/
input18::capslock
input18::numlock
input18::scrolllock
input3::capslock
input3::numlock
input3::scrolllock
platform::fnlock
$ sudo dmidecode -s system-manufacturer
LENOVO
$ sudo dmidecode -s system-product-name
82KU
$ uname -r
7.0.10-200.fc44.x86_64
--
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 reply other threads:[~2026-05-27 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 19:47 bugzilla-daemon [this message]
2026-06-01 17:30 ` [Bug 221583] Lenovo 82KU: keyboard backlight works via Fn+Space but no kbd_backlight LED device exposed 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
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@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.