From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220926] HP ENVY 16-h1xxx (Hayden): hp_wmi platform_profile fails to read/write
Date: Thu, 20 Aug 2026 09:37:12 +0000 [thread overview]
Message-ID: <bug-220926-215701-wguLNY7zB6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220926-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220926
--- Comment #4 from Gibs (gibs23@proton.me) ---
(In reply to Suryansh Singh from comment #2)
> (In reply to Gibs from comment #1)
> > I have the same problem on same platform on kernel 7.1.8.
> > Changing profiles does change fan behavior, but RPM reads 0 with hp-wmi.
> >
> > Package power also seems to max at 40W no matter the profile. On Windows I
> > have peaks of 115W and then drops at 55W after a short while.
> >
> > I also tried mapping my board ID to Omen or Victus configs but doesn't work,
> > the ENVY seems to be different.
>
> Hi,
>
> Could you please provide your board ID, or clarify if it is the same as
> Andres?
>
>
> Are you sure you've tried out all Omen or Victus configs? The latest branch
> for the platforms/x86 subsystem (pdx86/for-next) has an expanded driver
> scope compared to the current upstream version of the kernel you're running,
> so consider using the code on that branch for mapping your board ID to
> specific driver data in hp_wmi_feature_boards[]
>
>
> In case none of the existing parameters apply to your ENVY laptop, the EC
> behavior and specific quirks required to get it working will have to be
> reverse engineered and patched into the code, rather than the regular patch
> of mapping the board ID under predefined parameters.
> You may contact me at my mail if that happens to be true, I'll be glad to
> help in the whole process if it gets that complex.
I tried the version from the next branch but still no results. With
&omen_v1_no_ec_thermal_params I get a kernel panic, and with the others the
driver fails to load with hp-wmi hp-wmi: probe with driver hp-wmi failed with
error -22.
For one of them I got an extra:
hp_wmi: Unknown EC layout for board 8BE5. Thermal profile readback will be
disabled. Please report this to platform-driver-x86@vger.kernel.org
--
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-08-20 9:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 2:23 [Bug 220926] New: HP ENVY 16-h1xxx (Hayden): hp_wmi platform_profile fails to read/write bugzilla-daemon
2026-08-16 11:21 ` [Bug 220926] " bugzilla-daemon
2026-08-18 12:49 ` bugzilla-daemon
2026-08-19 19:45 ` bugzilla-daemon
2026-08-20 9:37 ` bugzilla-daemon [this message]
2026-08-21 2:01 ` bugzilla-daemon
2026-08-21 10:44 ` bugzilla-daemon
2026-08-21 10:45 ` bugzilla-daemon
2026-08-21 10:45 ` bugzilla-daemon
2026-08-21 10:50 ` bugzilla-daemon
2026-08-21 10:50 ` bugzilla-daemon
2026-08-21 10:50 ` bugzilla-daemon
2026-08-21 10:51 ` bugzilla-daemon
2026-08-21 10:51 ` bugzilla-daemon
2026-08-21 10:52 ` bugzilla-daemon
2026-08-21 10:55 ` bugzilla-daemon
2026-08-21 11:10 ` 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-220926-215701-wguLNY7zB6@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