X86 platform drivers
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218901] LG Gram Laptop Extra Features not working on 2024 models (16Z90S)
Date: Thu, 04 Jun 2026 10:24:51 +0000	[thread overview]
Message-ID: <bug-218901-215701-URQ01I52v9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218901-215701@https.bugzilla.kernel.org/>

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

--- Comment #72 from Quaternion (4966508hayk@gmail.com) ---
In my evtest, KEY_PERFORMANCE and KEY_CAMERA_ACCESS_TOGGLE are present. Maybe
the Fn+F4 has something to do with the settings? The combination started
toggling twice after you fixed settings. As a possible workaround, I can
mention that the touchpad state can be easily toggled inside settings.

Here is the new dmesg response (I omit the Fn key press/release event):

Fn+Esc:
[  978.268869] LG Gram Laptop Support LGEX0820:00: Received event 130
(1073938433)
Fn+F1:
[  411.436702] LG Gram Laptop Support LGEX0820:00: Received event 130
(252116994)
Fn+F2:
[  413.325769] LG Gram Laptop Support LGEX0820:00: Received event 128 (0)
Fn+F3:
[  414.323986] LG Gram Laptop Support LGEX0820:00: Received event 128 (0)
Fn+F4:
[  421.565755] LG Gram Laptop Support LGEX0820:00: Received event 128 (116)
Fn+F5:
Ignored
Fn+F6:
[  425.480991] LG Gram Laptop Support LGEX0820:00: Received event 128
(268435456)
Fn+F7:
[  427.640268] LG Gram Laptop Support LGEX0820:00: Received event 130
(805371985)
Fn+F8:
[  428.620331] LG Gram Laptop Support LGEX0820:00: Received event 130
(1073872897)
Fn+F9:
[  429.512356] LG Gram Laptop Support LGEX0820:00: Received event 130
(1073872896)
Fn+F10:
[  429.976413] LG Gram Laptop Support LGEX0820:00: Received event 128 (120)
Fn+F11:
[  430.509555] LG Gram Laptop Support LGEX0820:00: Received event 128 (0)
Fn+F12:
[  431.333337] LG Gram Laptop Support LGEX0820:00: Received event 128 (0)

I use the lgfnlock.sh script from

https://github.com/leoomi/LinuxLGGramScripts

to get the Fn lock working.

-- 
You may reply to this email to add a comment.

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

  parent reply	other threads:[~2026-06-04 10:24 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 16:48 [Bug 218901] New: LG Gram Laptop Extra Features not working on 2024 models (16Z90S) bugzilla-daemon
2024-05-27 20:05 ` [Bug 218901] " bugzilla-daemon
2024-05-28  7:20 ` bugzilla-daemon
2024-05-28  7:25 ` bugzilla-daemon
2024-05-28 13:36 ` bugzilla-daemon
2024-05-28 16:17 ` bugzilla-daemon
2024-05-30  9:48 ` bugzilla-daemon
2024-05-30 19:31 ` bugzilla-daemon
2024-05-30 21:56 ` bugzilla-daemon
2024-06-01 20:29 ` bugzilla-daemon
2024-06-01 20:30 ` bugzilla-daemon
2024-06-02 13:15 ` bugzilla-daemon
2024-06-02 14:02 ` bugzilla-daemon
2024-06-02 14:08 ` bugzilla-daemon
2024-06-02 14:37 ` bugzilla-daemon
2024-06-02 15:04 ` bugzilla-daemon
2024-06-02 15:06 ` bugzilla-daemon
2024-06-02 15:21 ` bugzilla-daemon
2024-06-02 15:26 ` bugzilla-daemon
2024-06-02 15:37 ` bugzilla-daemon
2024-06-02 15:39 ` bugzilla-daemon
2024-06-02 16:02 ` bugzilla-daemon
2024-06-02 16:50 ` bugzilla-daemon
2024-06-02 16:58 ` bugzilla-daemon
2024-06-02 16:59 ` bugzilla-daemon
2024-06-02 17:02 ` bugzilla-daemon
2024-06-02 17:04 ` bugzilla-daemon
2024-06-02 18:41 ` bugzilla-daemon
2024-06-02 22:12 ` bugzilla-daemon
2024-06-04 11:31 ` bugzilla-daemon
2024-06-04 13:24 ` bugzilla-daemon
2024-06-04 13:25 ` bugzilla-daemon
2024-06-04 14:43 ` bugzilla-daemon
2024-06-04 14:49 ` bugzilla-daemon
2024-06-04 14:54 ` bugzilla-daemon
2024-06-04 14:59 ` bugzilla-daemon
2024-06-04 15:04 ` bugzilla-daemon
2024-06-04 15:08 ` bugzilla-daemon
2024-06-04 15:10 ` bugzilla-daemon
2024-06-04 15:19 ` bugzilla-daemon
2024-06-04 15:37 ` bugzilla-daemon
2024-06-05  8:44 ` bugzilla-daemon
2024-06-06  5:01 ` bugzilla-daemon
2024-06-06  5:02 ` bugzilla-daemon
2024-06-06  5:03 ` bugzilla-daemon
2024-06-06 12:09 ` bugzilla-daemon
2024-06-06 12:46 ` bugzilla-daemon
2024-06-06 12:48 ` bugzilla-daemon
2024-06-24 12:22 ` bugzilla-daemon
2024-07-23 21:39 ` bugzilla-daemon
2024-07-23 21:46 ` bugzilla-daemon
2024-07-24 10:27 ` bugzilla-daemon
2024-08-05 13:18 ` bugzilla-daemon
2024-08-07 18:01 ` bugzilla-daemon
2024-08-07 18:15 ` bugzilla-daemon
2026-05-30 17:06 ` bugzilla-daemon
2026-05-30 21:53 ` bugzilla-daemon
2026-05-30 22:20 ` bugzilla-daemon
2026-05-30 23:50 ` bugzilla-daemon
2026-05-31  0:11 ` bugzilla-daemon
2026-05-31  6:42 ` bugzilla-daemon
2026-05-31  6:44 ` bugzilla-daemon
2026-06-02  4:34 ` bugzilla-daemon
2026-06-02 10:08 ` bugzilla-daemon
2026-06-02 13:49 ` bugzilla-daemon
2026-06-02 15:43 ` bugzilla-daemon
2026-06-02 15:55 ` bugzilla-daemon
2026-06-03 10:23 ` bugzilla-daemon
2026-06-03 10:27 ` bugzilla-daemon
2026-06-03 10:38 ` bugzilla-daemon
2026-06-03 23:07 ` bugzilla-daemon
2026-06-04  8:25 ` bugzilla-daemon
2026-06-04 10:24 ` bugzilla-daemon [this message]
2026-06-04 10:41 ` bugzilla-daemon
2026-06-04 10:56 ` bugzilla-daemon
2026-06-04 11:29 ` bugzilla-daemon
2026-06-04 15:43 ` bugzilla-daemon
2026-06-04 16:16 ` bugzilla-daemon
2026-06-04 19:33 ` bugzilla-daemon
2026-06-05  1:26 ` bugzilla-daemon
2026-06-05 20:45 ` bugzilla-daemon
2026-06-05 20:47 ` bugzilla-daemon
2026-06-06  4:00 ` bugzilla-daemon
2026-06-06  9:31 ` bugzilla-daemon
2026-06-10 20:40 ` 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-218901-215701-URQ01I52v9@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