From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221523] [BUG] hp-wmi: OMEN 16-ap0xxx (8E35) - fan control not available (no PWM)
Date: Sat, 16 May 2026 00:33:45 +0000 [thread overview]
Message-ID: <bug-221523-215701-rAYZvGhipW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221523-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221523
--- Comment #5 from Ahmet Özt (sivasli-ahmet@gmx.de) ---
(In reply to Krishna Chomal from comment #3)
> Hi Ahmet,
>
> Your device ID 8E35 was not present in any whitelist, which caused platform
> profile switching and fan control to fail.
>
> Could you please apply the patch (attachment 310134 [details]) and test the
> following:
>
> 1. Check dmesg for successful registration message:
> "hp_wmi: Registered as platform profile handler"
>
> 2. Verify that fan RPM is readable and controllable via sysfs
> (/sys/devices/platform/hp-wmi/hwmon/*).
>
> 3. Verify that on changing platform profile, and it does physically change
> the amount of power drawn in the CPU/GPU.
Hi Krishna,
I was now able to update the hp_wmi with dkms. The board is now detected by
hp_wmi. But I cannot control the PWMs.
--
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-05-16 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 10:51 [Bug 221523] New: [BUG] hp-wmi: OMEN 16-ap0xxx (8E35) - fan control not available (no PWM) bugzilla-daemon
2026-05-15 10:53 ` [Bug 221523] " bugzilla-daemon
2026-05-15 10:53 ` bugzilla-daemon
2026-05-15 14:02 ` bugzilla-daemon
2026-05-15 14:06 ` bugzilla-daemon
2026-05-15 23:06 ` bugzilla-daemon
2026-05-16 0:33 ` bugzilla-daemon [this message]
2026-05-16 0:49 ` 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-221523-215701-rAYZvGhipW@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.