X86 platform drivers
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 222275] lg_laptop: LG gram 16UD55U - kbd_backlight has no effect, unknown WMI scancodes on Super key
Date: Fri, 20 Nov 2026 08:53:12 +0000	[thread overview]
Message-ID: <bug-222275-215701-DsMzpppl1K@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222275-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=222275

--- Comment #7 from daxter1992@gmail.com ---
Tested on LG gram Book 16UD55U-G.AX85BN, kernel 7.3.4-300.fc45.x86_64:

The kbd_backlight LED device is no longer registered (confirmed with
ls /sys/class/leds/ — only tpad_led remains). The other hotkeys
(volume, brightness, mic mute, fan mode, etc.) still work fine.

Relevant dmesg output:
  lg_laptop: product: 16UD55U-G.AX85BN  year: 2022
  lg_laptop: Cannot get handle
  input: LG WMI hotkeys as /devices/platform/LGEX0820:00/input/input54

As confirmed by LG's official spec page for this model, there is no
keyboard backlight on the LG gram Book line.

Tested-by: daxter1992@gmail.com

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-11-20  8:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 10:10 [Bug 222275] New: lg_laptop: LG gram 16UD55U - kbd_backlight has no effect, unknown WMI scancodes on Super key bugzilla-daemon
2026-11-17  1:40 ` [Bug 222275] " bugzilla-daemon
2026-11-17  7:26 ` bugzilla-daemon
2026-11-17  7:29 ` bugzilla-daemon
2026-11-17 22:15 ` bugzilla-daemon
2026-11-18  8:28 ` bugzilla-daemon
2026-11-19  4:51 ` bugzilla-daemon
2026-11-20  8:53 ` bugzilla-daemon [this message]
2026-11-20 19:26 ` bugzilla-daemon
2026-11-20 19:27 ` bugzilla-daemon
2026-11-20 21:00 ` 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-DsMzpppl1K@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox