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: Sun, 02 Jun 2024 15:04:08 +0000 [thread overview]
Message-ID: <bug-218901-215701-RGgojzrGZN@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 #15 from Agathe Boutmy (agathe@boutmy.com) ---
(In reply to Armin Wolf from comment #12)
> Did you unload the old module first?
yes
> Or does dmesg show any ACPI errors?
There is one that was already present before that I didn't mention because
after a little research it seemed to be unrelated, I'll post it here just in
case:
[ 10.843998] ACPI Error: No handler for Region [XIN1] (00000000f9e347f6)
[UserDefinedRegion] (20240322/evregion-130)
[ 10.844003] ACPI Error: Region UserDefinedRegion (ID=143) has no handler
(20240322/exfldio-261)
[ 10.844007] ACPI Error: Aborting method \_SB.PC00.LPCB.H_EC.DPTF.SNRD due to
previous error (AE_NOT_EXIST) (20240322/psparse-529)
[ 10.844010] ACPI Error: Aborting method \_SB.IETM.SEN2._TMP due to previous
error (AE_NOT_EXIST) (20240322/psparse-529)
> I made a mistake when calling the ACPI methods, can you try again?
It works!
(I think, I now longer have an input output error on battery care limit and I
have been able to set it to 80% and it seems to stop properly charging if I
believe what the power management service included with Manjaro is saying)
The other files are also correctly readable.
The 3 FN keys FN-F1, FN-F6, FN-F9 don't seem to do anything but strangely FN-F5
works (which it did before) maybe it's handled differently by the driver.
--
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:[~2024-06-02 15:04 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 [this message]
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
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-RGgojzrGZN@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.