1 hour ago, i1mran92 said:

i am using a supermicro x11sca-f. though the manufacturer says Enginetech and some where product name. Is it not compatible with this plug in? i'm trying to control the board that is running opnsense on another box. it successfully connected, but no fan control tab show up. when i use override, and choose supermicro x11, it seems to work. i can hear the fans slowed down. i used it to monitor the cpu temps. is there a away without me using the override options?

thanks!

You will need to use override because the board is not reporting as a supermicro board

@SimonFcan you update freeipmi? v 1.6.6 is from 2020, the current version is 1.6.15. https://www.gnu.org/software/freeipmi/

 

https://slackers.it/repository/slackware64-current/freeipmi/freeipmi-1.6.15-x86_64-1cf.txz

 

i have installed it and can confirm it is working as expected

Edited January 25, 20251 yr by spl147

@Edival76 and @xrichnj What do you think?

 

@SimonFi would also like to request the ability to set a temperature in which the cpu temp scale would take over if hdd's are spun up.

 

IE: Hdd's are spinning but temp is 94F, cpu is stressed and running at 145F but fanspeed is using the lower hdd scale, so cpu does not cool properly

 

so if hdds are spinning and cpu reaches X cpu scale kicks in, if cpu temp drops to X and HDDs are still spinning HDD scale kicks in.

 

and label it Override

 

 

Edited January 25, 20251 yr by spl147

11 minutes ago, spl147 said:

@Edival76 and @xrichnj What do you think?

 

@SimonFi would also like to request the ability to set a temperature in which the cpu temp scale would take over if hdd's are spun up.

 

IE: Hdd's are spinning but temp is 94F, cpu is stressed and running at 145F but fanspeed is using the lower hdd scale, so cpu does not cool properly

 

so if hdds are spinning and cpu reaches X cpu scale kicks in, if cpu temp drops to X and HDDs are still spinning HDD scale kicks in.

 

and label it Override

 

 

 

i think that would certainly be handy in a lot of use-cases. 

 

like discussed on the previous page, i think cleaning up the ui and getting everything properly labeled and documented to make the plugin easier and more intuitive to use for all users is more important than new actual features/functionality (even the ones i really need) at this point.

4 minutes ago, xrichnj said:

 

i think that would certainly be handy in a lot of use-cases. 

 

like discussed on the previous page, i think cleaning up the ui and getting everything properly labeled and documented to make the plugin easier and more intuitive to use for all users is more important than new actual features/functionality (even the ones i really need) at this point.

did you look at the labeling changes i made?

 

i added additional in line help text as well:

 

 

2 minutes ago, spl147 said:

did you look at the labeling changes i made?

 

 

yes that is what i was referring to. i think its a step in the right direction. taking it further, i think not having the "override" or "spundown" values even show (or at least grey-ing the options out) unless you have "hdd temperature" selected as your sensor would certainly have helped me when trying to set it up. if i'm not using hdd temp as the monitored temperature sensor, why give me modifiable options that wont have any effect on how the plugin functions?

 

maybe they can "pop out" when you select an option that uses them, like in the appdata backup plugin when you go from "Use Compression":no to "Use Compression":yes, multicore, it pops out another option to select how many cores to use. 

 

Just now, xrichnj said:

 

yes that is what i was referring to. i think its a step in the right direction. taking it further, i think not having the "override" or "spundown" values even show (or at least grey-ing the options out) unless you have "hdd temperature" selected as your sensor would certainly have helped me when trying to set it up. if i'm not using hdd temp as the monitored temperature sensor, why give me modifiable options that wont have any effect on how the plugin functions?

 

maybe they can "pop out" when you select an option that uses them, like in the appdata backup plugin when you go from "Use Compression":no to "Use Compression":yes, multicore, it pops out another option to select how many cores to use. 

 

i have already made that change:

 

 

12 minutes ago, spl147 said:

i have already made that change:

 

 

for a pending future update? this is not the behavior I experience currently

Just now, xrichnj said:

for a pending future update? this is not the behavior I experience currently

i made them locally on my own machine, i have submitted a pull request for them to be added to the next release

4 minutes ago, spl147 said:

i made them locally on my own machine, i have submitted a pull request for them to be added to the next release

 

i think the options limiter and the inline text help will enhance the user-friendliness of the interface a lot. 

17 minutes ago, xrichnj said:

 

i think the options limiter and the inline text help will enhance the user-friendliness of the interface a lot. 

here are the 2 files if you wish to test the changes:

inline help text:

/usr/local/emhttp/plugins/ipmi/ipmifans.page

 

IPMIFans.page

 

fans settings spundown settings:

/usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php

 

ipmi_helpers.php

Edited January 25, 20251 yr by spl147

57 minutes ago, spl147 said:

did you look at the labeling changes i made?

 

Was thinking that the Sensor could be changed i.e. the following

 

First sensor, followed by a comparison option. 1. None, 2. Spundown(HDD) 3. Max 4. Average

 

For options 3 and 4 would work in conjunction of the secondary sensor. Override values would only be show for spindown.

 

Thoughts.

 

I will look at freeipmi version. You testing on 7, will need to check which versions it supports.

1 minute ago, SimonF said:

Was thinking that the Sensor could be changed i.e. the following

 

First sensor, followed by a comparison option. 1. None, 2. Spundown(HDD) 3. Max 4. Average

 

For options 3 and 4 would work in conjunction of the secondary sensor. Override values would only be show for spindown.

 

Thoughts.

 

I will look at freeipmi version. You testing on 7, will need to check which versions it supports.

yes i am testing on 7

2 minutes ago, SimonF said:

Was thinking that the Sensor could be changed i.e. the following

 

First sensor, followed by a comparison option. 1. None, 2. Spundown(HDD) 3. Max 4. Average

 

For options 3 and 4 would work in conjunction of the secondary sensor. Override values would only be show for spindown.

 

Thoughts.

 

I will look at freeipmi version. You testing on 7, will need to check which versions it supports.

i have submitted pull requests for the changes i have made

6 hours ago, spl147 said:

yes i am testing on 7

I have compiled my own package, does not work on 6.12 so will have to make conditional. I look to merge and create new package tomorrow.

I have released 2025.01.26 but is not showing as an update yet on my systems.

 

Works fine if I do a manual download.

 

https://raw.githubusercontent.com/SimonFair/IPMI-unRAID/refs/heads/master/plugin/ipmi.plg

1 hour ago, SimonF said:

I have released 2025.01.26 but is not showing as an update yet on my systems.

 

Works fine if I do a manual download.

 

https://raw.githubusercontent.com/SimonFair/IPMI-unRAID/refs/heads/master/plugin/ipmi.plg

still seeing this in the log:

HDD Spundown using Temp(104 °F)

1 hour ago, SimonF said:

I have released 2025.01.26 but is not showing as an update yet on my systems.

 

Works fine if I do a manual download.

 

https://raw.githubusercontent.com/SimonFair/IPMI-unRAID/refs/heads/master/plugin/ipmi.plg

still hasn't shown for me yet either. will report when it does and i install!

Hey all - I'm unable to install the update, which I think broke my Dell IDRAC fan controller docker container as it's complaining about not being able to send RAW command.

 

Error when trying to update / install this plugin:

 

plugin: installing: ipmi.plg
Executing hook script: pre_plugin_checks
plugin: downloading: ipmi.plg ... done

plugin: downloading: freeipmi-1.6.6-x86_64-1.txz ... done

plugin: bad file MD5: /boot/config/plugins/ipmi/freeipmi-1.6.15-x86_64-1_SBo.tgz
Executing hook script: post_plugin_checks

 

22 minutes ago, spl147 said:

still seeing this in the log:

HDD Spundown using Temp(104 °F)

Did you restart fan control?

2 minutes ago, SimonF said:

Did you restart fan control?

yes

15 minutes ago, SimonF said:

Did you restart fan control?

i found the issue, even though it says the plugin updated, the ipmifan script did not have the code change in it. i manually changed it and can confirm it is fixed.

 

curious as to why the update did not work properly?

 

UPDATE: just looked and the plugin has reverted to the 1.21.25 release

Edited January 26, 20251 yr by spl147

8 minutes ago, spl147 said:

i found the issue, even though it says the plugin updated, the ipmifan script did not have the code change in it. i manually changed it and can confirm it is fixed.

 

curious as to why the update did not work properly?

Try 26b I made an error in the new package load.

26 minutes ago, tslamars said:

Hey all - I'm unable to install the update, which I think broke my Dell IDRAC fan controller docker container as it's complaining about not being able to send RAW command.

 

Error when trying to update / install this plugin:

 

plugin: installing: ipmi.plg
Executing hook script: pre_plugin_checks
plugin: downloading: ipmi.plg ... done

plugin: downloading: freeipmi-1.6.6-x86_64-1.txz ... done

plugin: bad file MD5: /boot/config/plugins/ipmi/freeipmi-1.6.15-x86_64-1_SBo.tgz
Executing hook script: post_plugin_checks

 

Try 26b Should show normally as an update now.

 

https://raw.githubusercontent.com/SimonFair/IPMI-unRAID/refs/heads/master/plugin/ipmi.plg