mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-25 16:45:53 +03:00
[GH-ISSUE #424] What registers affect fan speed on startup? (HP Probook 650 G1/G2 Win 10) #384
Labels
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nbfc-hirschmann#384
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Daniol71 on GitHub (Jan 17, 2018).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/424
Hey, really impressed with the software so far even if it's not the easiest to use.
I have managed to set up my HP Probook 650 G2 using one of the configs for it here on GitHub (although it can be noted it also works with the 650 G1 config provided in the install).
My problem is: On startup and (sometimes) wake from sleep, the fans reset (perhaps to the system fan profile?) and I have to manually drag the slider to a low value (around 5%) then set the slider back to Auto to get the desired fan behaviour back. I think it might be related to the Register Write Configuration which is the only setting I haven't played around with.
Additionally: if you could give me the EC model numbers for the HP Probook 650 G1/G2 that would be highly appreciated, I haven't had any luck finding them myself. Then I could play around with the registers.
If I solve the issue I'll buy you a beer ;)
EDIT: Couldn't find the log files that are referenced here:
https://github.com/hirschmann/nbfc/wiki/Files-and-directories-overview
so I made my own using Process Monitor. Hopefully it's of some use.
Logfile - Copy.txt
@github-actions[bot] commented on GitHub (Dec 4, 2019):
This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed