All of lore.kernel.org
 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: Tue, 17 Nov 2026 07:26:52 +0000	[thread overview]
Message-ID: <bug-222275-215701-06YVeFUwHP@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 #2 from daxter1992@gmail.com ---
I tested the patch "platform/x86: lg-laptop: Fix input of super key"
on my LG gram 16UD55U-G.AX85BN (BIOS GP115, kernel 7.3.4-300.fc45).
The KEY_UNKNOWN events are gone and the Super key works correctly in GNOME
without any workaround.

Tested-by: daxter1992@gmail.com

Regarding the keyboard backlight issue, which is still open, when loading
lg_laptop I see:

  lg_laptop: product: 16UD55U-G.AX85BN  year: 2022
  lg_laptop: Cannot get handle

The year detection seems wrong (this is a 2026 model), so the driver
may be using old-generation methods, and one ACPI handle is not found.
This could explain why kbd_backlight has no effect. acpidump is attached
to this bug. Happy to test further patches.

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

  parent reply	other threads:[~2026-11-17  7:26 UTC|newest]

Thread overview: 5+ 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 [this message]
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-06YVeFUwHP@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.