-
Notifications
You must be signed in to change notification settings - Fork 18
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
freeimpi fan control and more? #60
Comments
Hello! Going back to ipmi. I tried to install it, but kept on getting the following error: root@pve:~# ipmi-sensors
Caching SDR repository information: /root/.freeipmi/....
ipmi_sdr_cache_create: internal IPMI error During the investigation of the issue, I found several comments mentioning that it requires that the motherboard supports ipmi. That it is a feature that is only available on enterprise/server grade hardware. Looking up your motherboard, IPMI is mentioned as a feature. So that could confirm my assumption. If that is a correct assumption, that means all the current users of the scripts are using consumer hardware and that also implies it's not an either or case. Both ways of retrieving data must be working. The output of ipmi-sensors is also quite different, though much easier to parse. The current parser is for json and I don't find a json output mentioned in their docs: https://www.gnu.org/software/freeipmi/manpages/man8/ipmi-sensors.8.html. @eremem I'd like get your view on this as well. Thanks. |
@Meliox based on your analysis the support for IPMI with all of the adjustments/changes that would be required in the current solution seems not really to be the justified development direction. |
So I suppose if we could have some sort of plugin-like architecture where there are data sources (e.g. Also I'd like to argue in favor of using both "data sources" at the same time, but their update intervals would most likely differ due to IPMI making requests to the IPMI/BMC rather than just reading raw chip values (like e.g. |
This could be a possible approach but it would also mean that the current "architecture" had to be fundamentally reworked and the whole solution would most likely have to be incomparably more complex.
Yes, I can also see both tools used in tandem for providing sensor readings. I would expect though that both programs (as soon as they can read anything usable) provide redundant rather than complementary information. |
First of all: thank you very much for building these scripts!
Is your feature request related to a problem? Please describe.
I have the ASRockRack W680D4U-2L2T/G5 motherboard and I am running Proxmox on it.
Long story short: the default NCT6798D chip does not deliver fan speeds along with quite a bunch of other stuff. Manually enabling the kernel module doesn't help - most if not all of the relevant values are broken.
A proper IPMI driver is also not found by
lm-sensors
/sensors
.Describe the solution you'd like
Use
freeipmi
- or rather:ipmi-sensors
- to retrieve RPM values of the fans. I am not sure how to go about the configuration though.Alternatively
ipmitool
could be used, but in my experience so far (though I only tried it on this one motherboard) it's every so slightly slower.Describe alternatives you've considered
I considered making a separate script rather than modifying
pve-mod-gui-sensors.sh
, but I feel it would be a better idea to include it in the original script, because one really would only need any values fromipmi-sensors
if the regularsensors
did not manage to deliver them for whatever reason.Additional context
None yet, but I can expand and perhaps I could even help with a PR if you would consider the PR to be merged.
Sensors output
ipmi-sensors
outputThe text was updated successfully, but these errors were encountered: