All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 222107] hp-wmi: fan1_input and fan2_input always 0 on OmniBook 7 17-dc (8D9C)
Date: Fri, 09 Oct 2026 14:14:28 +0000	[thread overview]
Message-ID: <bug-222107-215701-p6CAmYMbDv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222107-215701@https.bugzilla.kernel.org/>

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

--- Comment #2 from Krishna Chomal (krishna.chomal108@gmail.com) ---
Hi Jae,

I took a look at your ACPI tables, and they seem consistent with your findings.
The relevant HP WMI methods appear to be stub implementations, which would
explain why the fan-related queries return PASS with a zero payload.

This suggests that the issue is likely on the firmware side rather than a
Linux-specific problem. If the firmware does not implement these methods,
hp-wmi has no meaningful fan-speed data to retrieve through this interface. If
I am not wrong, HP's official software on Windows would also not support fan
read/control behaviour.

For now, it looks like relying on acpi_fan is the best option. Proper support
through hp-wmi would likely require a firmware update from HP that implements
the relevant WMI methods.

Sorry I don't have a better solution!

-- 
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-10-09 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 19:15 [Bug 222107] New: hp-wmi: fan1_input and fan2_input always 0 on OmniBook 7 17-dc (8D9C) bugzilla-daemon
2026-10-08 19:16 ` [Bug 222107] " bugzilla-daemon
2026-10-09 14:14 ` bugzilla-daemon [this message]

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-222107-215701-p6CAmYMbDv@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.