From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 222275] New: lg_laptop: LG gram 16UD55U - kbd_backlight has no effect, unknown WMI scancodes on Super key
Date: Mon, 16 Nov 2026 10:10:20 +0000 [thread overview]
Message-ID: <bug-222275-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=222275
Bug ID: 222275
Summary: lg_laptop: LG gram 16UD55U - kbd_backlight has no
effect, unknown WMI scancodes on Super key
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: daxter1992@gmail.com
Regression: No
Created attachment 311472
--> https://bugzilla.kernel.org/attachment.cgi?id=311472&action=edit
dmesg and acpidump attached
Hardware: LG gram 16UD55U-G.AX85BN (board 16U55U), AMD Ryzen AI 7 445, BIOS
GP115
Kernel: 7.3.3-300.fc45 (also tested 7.4.0-rc2)
1) Keyboard backlight
lg_laptop loads and creates /sys/class/leds/kbd_backlight, but writing
to brightness has no effect: the value stays at 0 and the keyboard
does not light up. Fn+F8 does nothing either.
2) Unknown WMI key events
Each press of the Super key makes the "LG WMI hotkeys" device send
KEY_UNKNOWN with scancodes 0x30020000 (press) and 0x30020001 (release).
This breaks the GNOME overlay key, because it sees another key between
Super press and release. Remapping via hwdb does not work (unknown
sparse-keymap entries). Workaround: LIBINPUT_IGNORE_DEVICE=1 on
"LG WMI hotkeys". These scancodes should probably be added to the
keymap as ignored.
dmesg and acpidump attached. Happy to test patches.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2026-11-16 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 10:10 bugzilla-daemon [this message]
2026-11-17 1:40 ` [Bug 222275] lg_laptop: LG gram 16UD55U - kbd_backlight has no effect, unknown WMI scancodes on Super key bugzilla-daemon
2026-11-17 7:26 ` bugzilla-daemon
2026-11-17 7:29 ` bugzilla-daemon
2026-11-17 22:15 ` 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-222275-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.