-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for MSI B350 Gaming Plus #1
Comments
There really isn't much of a guideline. For an introductory guide you can reference this: And the sensors.conf example file: First thing you'd want to do is run Inside the file you need to state which sensor your config applies to Next we will start correlating the voltages and temps etc for a system that's under load and idle. Because that's where scaling factors come in. The best approach there is to monitor voltage jumps between idle and load under windows or to look at the little jumps that voltages do in the BIOS. Observe voltage differences. The voltage "jumps" are multiples of the scaling factors, which you then can use to map inX with the respective voltages and to calculate the scaling factors. For understanding the various parameters you can read In my case I happened to have a datasheet available to determine the resistor values for the voltage dividers used on the voltage sensors I documented this in the sensor config file itself
In addition a big help was using output from existing software such as hwinfo under windows. |
@mchwalisz If so you can send me what you have and I'll try put something together. |
I have started on my fork https://github.com/mchwalisz/sensor_config/tree/master . Have only the fan info figured out for now. Don't have windows so it is kind of hard to figure out the rest. |
I would like to get/add support for MSI B350 Gaming Plus. I plan to take your X350 config and see what I need to change to make it work.
What I could really use is some kind of guide / guidelines how to provide such support.
The text was updated successfully, but these errors were encountered: