mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-26 00:56:01 +03:00
[GH-ISSUE #1461] Explain practical function of config settings #1256
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#1256
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 @SirYavin on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/1461
The current documentation as to creating or modifying a config for a notebook not included in the pre-installed list of configs is unclear and not elaborated upon. Trial-and-error should never be required for something controlling a notebook's physical hardware--nor should uncertainty.
Please elaborate as to the actual function and practical result of each of the various config settings in a plain-word context in the config guide, rather than exclusively describing each config setting as a mathematical equation dependent on other config settings that are themselves described only as mathematical equations.
Normally I'd try to elaborate as to the specific settings that are dubiously described or unclear--but in this case, I'd be listing every single setting, because none of them correspond to actual measurements; they all appear to be assigned to arbitrary ranges, and don't appear to even be locked to those ranges (such as insisting my current fan speed is 142%). There is no relevant documentation for instances like this, and the guide--in it's current form--offers no guidance as to which setting would affect or correct this.
I cannot stress enough that a program of this nature is explicitly unsafe to use without knowing what it is doing, and what you are telling it to do as a user. Therefore, it is critical that the documentation instructing users on proper usage of this program be reasonably understandable to even the average user. Unfortunately, it is not.