[Bug 221149] New: hp-wmi: Fan control fails and RPM always reads as zero on HP OMEN 16-wf1xxx (Board 8C76)

bugzilla-daemon
2026-02-27T10:16:50Z

Bug ID: 221149
Summary: hp-wmi: Fan control fails and RPM always reads as zero
on HP OMEN 16-wf1xxx (Board 8C76)
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: Jie7172585@gmail.com
Regression: No

Created attachment 309484
--> https://bugzilla.kernel.org/attachment.cgi?id=309484&action=edit
log of OMEN Gaming Hub

I am opening this new bug report to track the fan control issues for the HP
OMEN 16-wf1xxx (Board ID: 8C76)

The primary issue is that the manual fan control completely fails, and the fan
speed is always reported as zero.

Description:
While the hp-wmi driver successfully exposes the hwmon nodes, attempting to
write to the pwm1_enable node (e.g., setting it to 0 for max fan speed) has no
physical effect on the fans. Furthermore, reading the fan speed (e.g., cat
fan1_input) constantly returns 0 RPM, even when the fans are physically
spinning under heavy CPU/GPU load. The commands seem to be rejected at the
firmware level.

Errors from dmesg:
The underlying WMI communication is failing, producing the following ACPI
errors in dmesg when trying to query/set thermal states:

hp_wmi: query 0x4c returned error 0x6
ACPI BIOS Error (bug): Attempt to CreateField of length zero
(20251212/dsopcode-133)
ACPI Error: Aborting method \_SB.WMID.WQBC due to previous error
(AE_AML_OPERAND_VALUE)
ACPI Error: Aborting method \_SB.WMID.WQBE due to previous error
(AE_AML_OPERAND_VALUE)
ACPI Error: Aborting method \_SB.WMID.WHCM due to previous error
(AE_AML_OPERAND_VALUE)
ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error
(AE_AML_OPERAND_VALUE)

Hardware details:
- Laptop: OMEN by HP Gaming Laptop 16-wf1xxx
- DMI Board ID: 8C76
- BIOS Version: F.15

EC dump:

$ sudo xxd /sys/kernel/debug/ec/ec0/io
00000000: 0000 0000 0001 48aa 0f84 fa71 0ffa 1c01 ......H....q....
00000010: 0129 251e ff00 ffff ffff ffff 00fa ac24 .)%............$
00000020: 0000 0000 0000 f900 350f 2000 0036 4b59 ........5. ..6KY
00000030: 5844 304b 3831 4a38 324a 5400 0100 00ff XD0K81J82JT.....
00000040: ffff ff01 00ff ffff ff4c 494f 4e00 0000 .........LION...
00000050: 0009 ffff 3100 000f 4301 2d41 0000 0000 ....1...C.-A....
00000060: 0080 1620 3333 332d 4143 2d31 322d 4100 ... 333-AC-12-A.
00000070: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000080: 0000 0000 0b00 0000 0000 0000 0000 0000 ................
00000090: 3333 332d 4143 2d31 3257 4b30 3630 3833 333-AC-12WK06083
000000a0: 0001 00d8 4500 004c 0000 0008 642a 0078 ....E..L....d*.x
000000b0: 4d4d 3c5b 4100 3232 008c 0800 f242 1111 MM<[A.22.....B..
000000c0: 0000 7e1b 8505 0c32 3c2d 6c20 7e1b 6421 ..~....2<-l ~.d!
000000d0: 0000 0000 0000 7e1b bf02 5b11 0000 e000 ......~...[.....
000000e0: 0000 00af 10ad 10af 1000 0083 430b 0080 ............C...
000000f0: 0009 0200 0000 0000 5000 0061 580b 0000 ........P..aX...

I have attached the OMEN Gaming Hub logs from my Windows partition to this bug
report.