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: Wed, 03 Jun 2026 23:07:49 +0000 [thread overview]
Message-ID: <bug-218901-215701-24SPzYtTmA@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 #70 from tacodog311@gmail.com ---
I think we're making progress. Fn+F1 and Fn+F8 seem to be working, but Fn+F4 no
longer toggles the touchpad.
F1 -> KEY_CONFIG -- Working now
F2 -> Ignored -- still working
F3 -> Ignored -- still working
F4 -> KEY_F21 -- used to work, now "touchpad on" appears on the screen, doesn't
toggle, I suspect it triggers twice (off/on)?
F5 -> Ignored -- still works
F6 -> KEY_F16 and notifying the LED class device -- still no effect
F7 -> KEY_PERFORMANCE -- still no effect
F8 -> KEY_MICMUTE -- Working now
F9 -> KEY_CAMERA_ACCESS_TOGGLE -- still no effect
F10 -> Ignored -- still works
F11 -> Ignored -- still works
F12 -> Ignored -- still works
I also notices that Fn+Esc is supposed to toggle the Fn lock, and that does not
currently work.
This is my evdev:
Fn+F1:
Event: time 1780527642.116637, type 4 (EV_MSC), code 4 (MSC_SCAN), value
f070002
Event: time 1780527642.116637, type 1 (EV_KEY), code 171 (KEY_CONFIG), value 1
Event: time 1780527642.116637, -------------- SYN_REPORT ------------
Event: time 1780527642.116658, type 1 (EV_KEY), code 171 (KEY_CONFIG), value 0
Event: time 1780527642.116658, -------------- SYN_REPORT ------------
Fn+F4:
Event: time 1780527664.185518, type 4 (EV_MSC), code 4 (MSC_SCAN), value 74
Event: time 1780527664.185518, type 1 (EV_KEY), code 191 (KEY_F21), value 1
Event: time 1780527664.185518, -------------- SYN_REPORT ------------
Event: time 1780527664.185529, type 1 (EV_KEY), code 191 (KEY_F21), value 0
Event: time 1780527664.185529, -------------- SYN_REPORT ------------
Fn+F6:
Event: time 1780527716.168356, type 4 (EV_MSC), code 4 (MSC_SCAN), value
10000000
Event: time 1780527716.168356, type 1 (EV_KEY), code 186 (KEY_F16), value 1
Event: time 1780527716.168356, -------------- SYN_REPORT ------------
Event: time 1780527716.168372, type 1 (EV_KEY), code 186 (KEY_F16), value 0
Event: time 1780527716.168372, -------------- SYN_REPORT ------------
Fn+F7:
Event: time 1780527729.707137, type 4 (EV_MSC), code 4 (MSC_SCAN), value
30010051
Event: time 1780527729.707137, type 1 (EV_KEY), code 701 (?), value 1
Event: time 1780527729.707137, -------------- SYN_REPORT ------------
Event: time 1780527729.707147, type 1 (EV_KEY), code 701 (?), value 0
Event: time 1780527729.707147, -------------- SYN_REPORT ------------
Fn+F8:
Event: time 1780527743.793305, type 4 (EV_MSC), code 4 (MSC_SCAN), value
40020001
Event: time 1780527743.793305, type 1 (EV_KEY), code 248 (KEY_MICMUTE), value 1
Event: time 1780527743.793305, -------------- SYN_REPORT ------------
Event: time 1780527743.793320, type 1 (EV_KEY), code 248 (KEY_MICMUTE), value 0
Event: time 1780527743.793320, -------------- SYN_REPORT ------------
Fn+F9:
Event: time 1780527761.607632, type 4 (EV_MSC), code 4 (MSC_SCAN), value
40020000
Event: time 1780527761.607632, type 1 (EV_KEY), code 589
(KEY_CAMERA_ACCESS_TOGGLE), value 1
Event: time 1780527761.607632, -------------- SYN_REPORT ------------
Event: time 1780527761.607655, type 1 (EV_KEY), code 589
(KEY_CAMERA_ACCESS_TOGGLE), value 0
Event: time 1780527761.607655, -------------- SYN_REPORT ------------
Fn+Esc:
Event: time 1780527879.303527, type 4 (EV_MSC), code 4 (MSC_SCAN), value
40030001
Event: time 1780527879.303527, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 1
Event: time 1780527879.303527, -------------- SYN_REPORT ------------
Event: time 1780527879.303550, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 0
Event: time 1780527879.303550, -------------- SYN_REPORT ------------
Event: time 1780527879.456554, type 4 (EV_MSC), code 4 (MSC_SCAN), value
30010001
Event: time 1780527879.456554, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 1
Event: time 1780527879.456554, -------------- SYN_REPORT ------------
Event: time 1780527879.456569, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 0
Event: time 1780527879.456569, -------------- SYN_REPORT ------------
--
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 prev parent reply other threads:[~2026-06-03 23:07 UTC|newest]
Thread overview: 79+ 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 [this message]
2026-06-04 8:25 ` bugzilla-daemon
2026-06-04 10:24 ` bugzilla-daemon
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
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-24SPzYtTmA@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.