CkChong

Hi @BL76 , new version is out! It should fix the issue you reported — let me know if anything else comes up. Thanks again for the feedback!

Hi, First of all, that script you ran is actually for AMD (k10temp) systems. Your motherboard looks like Intel, so it’s normal that it didn’t show anything under k10temp. Let’s check a few things step-by-step: Did you install the System Temp plugin and click Detect and Load Driver? In your BIOS, are the fan headers set to PWM / Manual, not Smart or Auto mode? Just to confirm — in FanCtrl Plus, you can see PWM controllers in the dropdown list, but the Identify button doesn’t make the fans react, right? (or are the PWM options completely missing?) If System Temp is loaded correctly and BIOS is already in PWM/manual mode, please share the outputs of the following safe diagnostic commands (these won’t change fan speeds): echo "=== hwmon devices ===" grep -H . /sys/class/hwmon/hwmon*/name echo "" echo "=== Available PWM controllers (safe check) ===" for d in /sys/class/hwmon/hwmon*; do name=$(cat "$d/name" 2>/dev/null) echo "-- $d ($name) --" ls "$d"/pwm* 2>/dev/null done That will help confirm which hwmon chip exposes the PWM interfaces (usually it86xx or nct6xxx for Gigabyte boards). Once we know which one actually has PWM entries, we can test Identify safely from there.

Hi — FanCtrl Plus doesn’t read or control GPU fans; it only works with the motherboard PWM headers (CPU_FAN / CHA_FAN). For PWM2 and PWM7: if Identify shows no response, they’re most likely unused headers. Your board exposes 8 PWM channels and you’ve connected 6 (one CPU fan + five case fans), so that matches. If nothing is connected to PWM2/7, it’s fine to leave them unassigned.

Thanks for the feedback. I found a typo in the .plg. You can ignore this error for now—it doesn’t affect usage. I’ll release an update soon (today or in the next few days) with the fix.

Thanks for the output. It shows your board only has auto mode, no real PWM control. So sadly both FanCtrl Plus and AutoFan can’t adjust the fans on this system.

Please take a look back at the previous few posts above. I already explained this there, and this feature is on the roadmap.

Since you already have System Temp installed and it does detect your Array Fan, it looks like the chip may only support reading RPM, not controlling PWM. Have you tried Dynamix AutoFan before — were you able to actually control the fans with it? If not sure, could you also paste the output of this so we can double check if any PWM controls are exposed? ls /sys/class/hwmon/hwmon*/pwm*

I’ll add an “Always keep fan minimum speed” option to the roadmap. Once I have some time to implement and test it, I’ll include it in a future release.

Yes, that’s actually how the current logic works — when all selected disks are spun down and there’s no active temperature source, the fan will stop completely (or just fall back to your hardware’s own minimum speed). I might consider adding an extra option in the future like “Always keep fans at minimum speed” so that they won’t fully stop. For now, if you’d like to keep them spinning at least at your defined minimum, here are two possible workarounds: 1. Also include an NVMe or SSD in your selection (since those drives don’t spin down), though of course the fan curve will then follow that device too. 2. Enable CPU temperature as an additional source. If this fan doesn’t actually need to follow CPU temps, you can simply set the CPU min–max range to something unrealistically high (e.g. 75 °C – 80 °C). That way, when all disks are spun down, the fan will still see CPU as a source and keep running at your minimum (e.g. 45%).

Thanks a lot for the detailed explanation. Right now FanCtrl Plus uses a linear control curve, so in most cases hysteresis isn’t really needed. But I’ll definitely keep it in mind and consider it in the future if more use cases come up. Also, you can give FanCtrl Plus a try — if the curves are set up properly, you normally shouldn’t run into the ping-pong on/off behavior.

Hello @alturismo , and thanks a lot for the kind words. FanCtrl Plus doesn’t have a hysteresis setting. The way it works is simple: you define a min–max temperature range and a min–max fan speed range, and the plugin automatically scales PWM smoothly between those points. I’m curious — for the hysteresis you mentioned, what would you mainly use it for? Maybe I can learn from your use case.

Thanks for the feedback! 🙏 You can also try enabling the new FCP Airflow option and let me know how it works for you. For more details, check the How to use section under Identify PWM Controller.

Try going into the plugin settings page, click Stop and then Start again. If PWM% still doesn’t show, please paste the output of: ls -l /var/tmp/fanctrlplus

Hi, Just released v1.3.2, which now supports multiple Identify Modes — including Pause, Max Speed, and Pulse. This should make it easier to tell which fan is being controlled, even on boards where fans don’t fully stop. Feel free to update and give it a try.

Yeah, sometimes hardware just acts weird and it’s hard to pin down. If possible, try swapping the two fans between headers — if the issue follows the fan, then it’s the fan itself. If the same header misbehaves again, it’s more likely the motherboard/BIOS side taking control back.