September 19, 20241 yr 1 hour ago, ChirpyTurnip said: I have fans that will only run at 100%, but I can see the sensor rpm data etc...I just cannot control them and this might be a answer I need. 🙂 may just try the following command in unraid terminal pwmconfig and check if its able to control the pwn fans then you can look upper in the post for manually control them if wanted ... and you have to be aware, you need pwm fans (4 pins) and pwm should be enabled in the BIOS too (just to make sure)
September 19, 20241 yr 2 hours ago, ChirpyTurnip said: Are you able to provide a link to this post? Nope... Without Diagnostics it is hard to say what is wrong or why it's not working on your system... However if you've got the driver plugin installed for your chip (if needed) then everything should work, you could also try what I described here:
September 19, 20241 yr I have been chasing my tail for a week or more. It seems that with PWM fans and Gigabyte board this is not uncommon. I have followed many guides and forum posts....but always I come up empty handed. I will summarise my problem (if that is possible) and provide some logs data for you. I have installed the Dynamix Temperature and Fan Control plugins and neither gave me anything fan-control related until I also installed the IT87 plugin. Now at least I have data and I can see my four fans: CPU = CPU (Unraid detected as FAN1) CPU_OPT = Not used SYS_FAN1 = Drive Bay Rear (Unraid detected as FAN2) SYS_FAN2 = Drive Bay Front Lower (Unraid detected as FAN3) SYS_FAN3 = Drive Bay Front Upper (Unraid detected as FAN4) PUMP = Unused I have verified this verified by finger-braking the fans and seeing the changing values come through - so I know the fans are right and the speed is right. The fans are also all PWM fans (e.g NOCTUA 140mm NF-A14 PWM 1500RPM Case Fan) and they are controlled to the fan motherboard headers. The BIOS has been told that these fans should be set to PWM (not auto). If I run sensors-detect I get this: # sensors-detect version 3.6.0 # System: Gigabyte Technology Co., Ltd. Z790M AORUS ELITE AX # Kernel: 6.1.106-Unraid x86_64 # Processor: Intel(R) Core(TM) i7-14700K (6/183/1) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found unknown chip with ID 0x8689 Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (YES/no): Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Found unknown SMBus adapter 8086:7a23 at 0000:00:1f.4. Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at efa0 (i2c-0) Do you want to scan it? (YES/no/selectively): Client found at address 0x49 Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Analog Devices ADT7410/ADT7420'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... No Probing for `National Semiconductor LM73'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Probing for `SMSC EMC1023'... No Probing for `SMSC EMC1043'... No Probing for `SMSC EMC1053'... No Probing for `SMSC EMC1063'... No Client found at address 0x4b Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Analog Devices ADT7410/ADT7420'... No Probing for `Analog Devices ADT7411'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Probing for `Analog Devices ADT7481'... No Client found at address 0x51 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Next adapter: i915 gmbus dpa (i2c-1) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus dpb (i2c-2) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus dpc (i2c-3) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc1 (i2c-4) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc2 (i2c-5) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc3 (i2c-6) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc4 (i2c-7) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc5 (i2c-8) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus tc6 (i2c-9) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AUX USBC2/DDI TC2/PHY C (i2c-10) Do you want to scan it? (yes/NO/selectively): yes Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. Unloading i2c-dev... OK And running sensors gives me this: acpitz-acpi-0 Adapter: ACPI interface temp1: +16.8°C (crit = +20.8°C) MB Temp: +27.8°C (crit = +105.0°C) nvme-pci-0600 Adapter: PCI adapter Composite: +44.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +44.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +51.9°C (low = -273.1°C, high = +65261.8°C) nvme-pci-0700 Adapter: PCI adapter Composite: +47.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +47.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +53.9°C (low = -273.1°C, high = +65261.8°C) it8689-isa-0a40 Adapter: ISA adapter in0: 1.46 V (min = +0.00 V, max = +3.06 V) in1: 1.98 V (min = +0.00 V, max = +3.06 V) in2: 2.02 V (min = +0.00 V, max = +3.06 V) in3: 2.00 V (min = +0.00 V, max = +3.06 V) in4: 144.00 mV (min = +0.00 V, max = +3.06 V) in5: 1.81 V (min = +0.00 V, max = +3.06 V) in6: 1.99 V (min = +0.00 V, max = +3.06 V) 3VSB: 3.36 V (min = +0.00 V, max = +6.12 V) Vbat: 3.12 V fan1: 1735 RPM (min = 10 RPM) fan2: 1439 RPM (min = 0 RPM) fan3: 1161 RPM (min = 0 RPM) fan4: 1188 RPM (min = 0 RPM) temp1: +35.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +44.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp3: +59.0°C (low = +127.0°C, high = +127.0°C) sensor = Intel PECI temp4: +41.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp5: +47.0°C (low = +0.0°C, high = -124.0°C) sensor = thermistor temp6: +32.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor intrusion0: ALARM coretemp-isa-0000 Adapter: ISA adapter CPU Temp: +64.0°C (high = +80.0°C, crit = +100.0°C) Core 0: +64.0°C (high = +80.0°C, crit = +100.0°C) Core 4: +54.0°C (high = +80.0°C, crit = +100.0°C) Core 8: +56.0°C (high = +80.0°C, crit = +100.0°C) Core 12: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 16: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 20: +56.0°C (high = +80.0°C, crit = +100.0°C) Core 24: +56.0°C (high = +80.0°C, crit = +100.0°C) Core 28: +56.0°C (high = +80.0°C, crit = +100.0°C) Core 32: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 33: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 34: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 35: +55.0°C (high = +80.0°C, crit = +100.0°C) Core 36: +58.0°C (high = +80.0°C, crit = +100.0°C) Core 37: +58.0°C (high = +80.0°C, crit = +100.0°C) Core 38: +58.0°C (high = +80.0°C, crit = +100.0°C) Core 39: +58.0°C (high = +80.0°C, crit = +100.0°C) Core 40: +53.0°C (high = +80.0°C, crit = +100.0°C) Core 41: +53.0°C (high = +80.0°C, crit = +100.0°C) Core 42: +53.0°C (high = +80.0°C, crit = +100.0°C) Core 43: +53.0°C (high = +80.0°C, crit = +100.0°C) nvme-pci-0900 Adapter: PCI adapter Composite: +47.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +47.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +51.9°C (low = -273.1°C, high = +65261.8°C) So far, so good, BUT, since playing with this stuff my fans are also jammed up at 100% which is a real pain because that's loud. Previously they were BIOS managed and unless the CPU was running hot they were quiet - now they are full noise all of the time except when the machine is not running Unraid or Unraid hasn't full started. As soon as the array is started we got to full noise and we stay there! Running pwmconfig also achieves nothing: # pwmconfig version 3.6.0 This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. Found the following devices: hwmon0 is nvme hwmon1 is nvme hwmon2 is nvme hwmon3 is coretemp hwmon4 is acpitz hwmon5 is it8689 Found the following PWM controls: hwmon5/pwm1 current value: 57 hwmon5/pwm2 current value: 63 hwmon5/pwm2 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm3 current value: 79 hwmon5/pwm4 current value: 63 hwmon5/pwm4 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm5 current value: 79 hwmon5/pwm6 current value: 63 hwmon5/pwm6 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) Giving the fans some time to reach full speed... Found the following fan sensors: hwmon5/fan1_input current speed: 1739 RPM hwmon5/fan2_input current speed: 1436 RPM hwmon5/fan3_input current speed: 1159 RPM hwmon5/fan4_input current speed: 1186 RPM hwmon5/fan5_input current speed: 0 ... skipping! hwmon5/fan6_input current speed: 0 ... skipping! Warning!!! This program will stop your fans, one at a time, for approximately 5 seconds each!!! This may cause your processor temperature to rise!!! If you do not want to do this hit control-C now!!! Hit return to continue: Testing pwm control hwmon5/pwm1 ... hwmon5/fan1_input ... speed was 1739 now 1730 no correlation hwmon5/fan2_input ... speed was 1436 now 1439 no correlation hwmon5/fan3_input ... speed was 1159 now 1161 no correlation hwmon5/fan4_input ... speed was 1186 now 1188 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm1, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) This lack of result is also I think why in the Dynamix Fan Controller software hitting 'DETECT' can result in random results as it simply can't find which PWM input controls which fan. But if if just let it do it's thing I can at least see in the logs that it is trying to control the fans: Sep 12 17:39:42 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1149rpm) to: 57 (22% @ 1101rpm) Sep 12 17:39:42 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1439rpm) to: 79 (30% @ 1436rpm) Sep 12 17:39:42 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1182rpm) to: 79 (30% @ 1184rpm) Sep 12 17:41:48 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1436rpm) to: 79 (30% @ 1439rpm) Sep 12 17:41:48 Svalbard autofan: Highest disk temp is 36C, adjusting fan speed from: FULL (100% @ 1186rpm) to: 79 (30% @ 1188rpm) It just keeps running at 100%....all the time. 😞 So, in the post I quoted where you said to check a script if something was set to 1 I was interested. If this refers to setting for example pwm2_enable in order to allow control, and then similarly using an echo command to set a fan speed (e.g. echo 50 > pwm2) then sadly I cannot get that to go either.... The only this is is good at is 100%. It is very good at that. svalbard-diagnostics-20240919-1818.zip
September 19, 20241 yr 1 hour ago, ChirpyTurnip said: Running pwmconfig also achieves nothing: if pwmconfig cant control the fans ... you are "out of luck" ... pwmconfig actually does nothing else to test, set 1 for manual control, make steps by editing the value's ... so 1st, you need to either figure a way to control them, or ... - keep it on BIOS only (uninstall autofan ... will may set fan to 1 and without any control always run 100 %) - - > no HDD Temp Control possible ... - get some external controller ... which you can use in Linux ... nothing more i can help here, exept ... dont buy GB Boards sorry ... (i dont like them ...) may @ich777 has other ideas left ...
September 19, 20241 yr 2 hours ago, ChirpyTurnip said: The only this is is good at is 100%. It is very good at that. Have you read my post on how to interact with the fans directly by issuing the commands from the linked post? There is no real script that I made, this was just a simple entry in the go file specificly for my motherboard to: Set the fans to manual mode Set the fan speed
September 19, 20241 yr Yes. Less than ideal... The bit I can't figure out is why Unraid (somehow) seizes control of the fans and ramps them up to 100%. Like control them, or don't.....but don't force them to 100% and then pretend that you can't talk to the fans. The CPU fan changes speed all the time, so BIOS is controlling that just fine - but the other fans, which are also pegged to the CPU in BIOS, don't change at all, they just stay at 100%. And before I started messing with the fan stuff they didn't run at 100% either. So there's definitely something going on... I could create a new Unraid usb stick but it's have to figure out how to migrate my config without migrating any fan stuff....
September 19, 20241 yr 1 minute ago, ChirpyTurnip said: Yes. Less than ideal... The bit I can't figure out is why Unraid (somehow) seizes control of the fans and ramps them up to 100%. That‘s usually done by the BIOS and not by Unraid, have you yet tried to uninstall the FAN controll plugin and see if the fans also ramp to 100%? I assume that the Gigabyte BIOS enforces something or at least that the fans spin at 100%
September 19, 20241 yr 1 minute ago, ich777 said: Have you read my post on how to interact with the fans directly by issuing the commands from the linked post? There is no real script that I made, this was just a simple entry in the go file specificly for my motherboard to: Set the fans to manual mode Set the fan speed This is what I'm trying to find! The simple entry in the go file and how to set the fan a speed. I've looked in the thread but I cannot find this post....I can find lots of other things but not that part. If you could share that with me that would be super helpful. :-)
September 19, 20241 yr If it helps my current go file is this: #!/bin/bash # Chip drivers modprobe coretemp /usr/bin/sensors -s # Start the Management Utility /usr/local/sbin/emhttp
September 19, 20241 yr 38 minutes ago, ChirpyTurnip said: If you could share that with me that would be super helpful. 🙂 I linked it above, just click the little arrow (the second post on this site).
September 19, 20241 yr 42 minutes ago, ChirpyTurnip said: This is what I'm trying to find! The simple entry in the go file and how to set the fan a speed. i cant imagine you ll get it to work as pwm... cant control it. but short, check if your fans are already on manual control set (return 1), if return is 0 ... controlled by BIOS replace the it<your_controller_here> with your actual controller, ls -l /sys/devices/platform/ cat /sys/devices/platform/it<your_controller_here>/hwmon/hwmon5/pwm*_enable if the are set to 1 (manual control), good, if not, enable manual control, sample fan3 (may 2 ...) echo 1 > /sys/devices/platform/it<your_controller_here>/hwmon/hwmon5/pwm3_enable then try to set the speed manually, sample again, will set fan3 (may 2 ...) to value 150 (0-255), so should throttle down ... some fans need higher values to startup, so not any fan will start at 10 ... some needs 30, some 50, ... 150 is a sure value to look if it works or not echo 150 > /sys/devices/platform/it<your_controller_here>/hwmon/hwmon5/pwm3 good luck, still ... as pwm doesnt work, i cant imagine this will
September 19, 20241 yr Then I think I have followed those instructions? I think this in one where you say to put this in the go file: # Chip drivers modprobe coretemp /usr/bin/sensors -s But this I already have....I even have added this now: # Chip drivers modprobe it87 force_id=0x8689 modprobe coretemp /usr/bin/sensors -s And it is happy: it8689-isa-0a40 Adapter: ISA adapter in0: 1.44 V (min = +0.00 V, max = +3.06 V) in1: 1.98 V (min = +0.00 V, max = +3.06 V) in2: 2.00 V (min = +0.00 V, max = +3.06 V) in3: 2.00 V (min = +0.00 V, max = +3.06 V) in4: 504.00 mV (min = +0.00 V, max = +3.06 V) in5: 1.81 V (min = +0.00 V, max = +3.06 V) in6: 1.99 V (min = +0.00 V, max = +3.06 V) 3VSB: 3.36 V (min = +0.00 V, max = +6.12 V) Vbat: 3.12 V fan1: 1523 RPM (min = 10 RPM) Array Fan: 1439 RPM (min = 0 RPM) Array Fan: 1178 RPM (min = 0 RPM) Array Fan: 1198 RPM (min = 0 RPM) temp1: +37.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: +44.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp3: +60.0°C (low = +0.0°C, high = +127.0°C) sensor = Intel PECI temp4: +42.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp5: +48.0°C (low = +0.0°C, high = -124.0°C) sensor = thermistor temp6: +32.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor intrusion0: ALARM It is like crazy - here I run pwmconfig immediately after a reboot - you can see the fan speeds are slower at the start of the test....like the even sort of seem to respond! But by the end of the test they are racing again and the definitely do not want to play with me: # pwmconfig version 3.6.0 This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. Found the following devices: hwmon0 is nvme hwmon1 is nvme hwmon2 is nvme hwmon3 is coretemp hwmon4 is acpitz hwmon5 is it8689 Found the following PWM controls: hwmon5/pwm1 current value: 66 hwmon5/pwm1 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm2 current value: 63 hwmon5/pwm2 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm3 current value: 63 hwmon5/pwm3 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm4 current value: 63 hwmon5/pwm4 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm5 current value: 66 hwmon5/pwm5 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm6 current value: 63 hwmon5/pwm6 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) There are no usable PWM outputs. root@Svalbard:~# pwmconfig # pwmconfig version 3.6.0 This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. Found the following devices: hwmon0 is nvme hwmon1 is nvme hwmon2 is nvme hwmon3 is coretemp hwmon4 is acpitz hwmon5 is it8689 Found the following PWM controls: hwmon5/pwm1 current value: 66 hwmon5/pwm1 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) hwmon5/pwm2 current value: 63 hwmon5/pwm2 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon5/pwm3 current value: 63 hwmon5/pwm3 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon5/pwm4 current value: 63 hwmon5/pwm4 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon5/pwm5 current value: 66 hwmon5/pwm5 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon5/pwm6 current value: 63 hwmon5/pwm6 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y Giving the fans some time to reach full speed... Found the following fan sensors: hwmon5/fan1_input current speed: 1638 RPM hwmon5/fan2_input current speed: 1380 RPM hwmon5/fan3_input current speed: 1144 RPM hwmon5/fan4_input current speed: 1167 RPM hwmon5/fan5_input current speed: 0 ... skipping! hwmon5/fan6_input current speed: 0 ... skipping! Warning!!! This program will stop your fans, one at a time, for approximately 5 seconds each!!! This may cause your processor temperature to rise!!! If you do not want to do this hit control-C now!!! Hit return to continue: Testing pwm control hwmon5/pwm2 ... hwmon5/fan1_input ... speed was 1638 now 1400 no correlation hwmon5/fan2_input ... speed was 1380 now 1149 no correlation hwmon5/fan3_input ... speed was 1144 now 919 no correlation hwmon5/fan4_input ... speed was 1167 now 933 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm2, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) Did you see/hear a fan stopping during the above test (n)? Testing pwm control hwmon5/pwm3 ... hwmon5/fan1_input ... speed was 1638 now 1496 no correlation hwmon5/fan2_input ... speed was 1380 now 1205 no correlation hwmon5/fan3_input ... speed was 1144 now 982 no correlation hwmon5/fan4_input ... speed was 1167 now 1001 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm3, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) Did you see/hear a fan stopping during the above test (n)? Testing pwm control hwmon5/pwm4 ... hwmon5/fan1_input ... speed was 1638 now 1537 no correlation hwmon5/fan2_input ... speed was 1380 now 1436 no correlation hwmon5/fan3_input ... speed was 1144 now 1175 no correlation hwmon5/fan4_input ... speed was 1167 now 1194 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm4, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) Did you see/hear a fan stopping during the above test (n)? Testing pwm control hwmon5/pwm5 ... hwmon5/fan1_input ... speed was 1638 now 1516 no correlation hwmon5/fan2_input ... speed was 1380 now 1436 no correlation hwmon5/fan3_input ... speed was 1144 now 1175 no correlation hwmon5/fan4_input ... speed was 1167 now 1196 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm5, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) Did you see/hear a fan stopping during the above test (n)? Testing pwm control hwmon5/pwm6 ... hwmon5/fan1_input ... speed was 1638 now 1555 no correlation hwmon5/fan2_input ... speed was 1380 now 1433 no correlation hwmon5/fan3_input ... speed was 1144 now 1171 no correlation hwmon5/fan4_input ... speed was 1167 now 1196 no correlation No correlations were detected. There is either no fan connected to the output of hwmon5/pwm6, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) Did you see/hear a fan stopping during the above test (n)? Testing is complete. If I re-run the test there is no longer any change - 100% only!
September 19, 20241 yr 9 minutes ago, alturismo said: i cant imagine you ll get it to work as pwm... cant control it. but short, check if your fans are already on manual control set (return 1), if return is 0 ... controlled by BIOS replace the it<your_controller_here> with your actual controller, ls -l /sys/devices/platform/ cat /sys/devices/platform/it<your_controller_here>/hwmon/hwmon5/pwm*_enable if the are set to 1 (manual control), good, if not, enable manual control, sample fan3 (may 2 ...) echo 1 > /sys/devices/platform/it<your_controller_here>/hwmon/hwmon5/pwm3_enable then try to set the speed manually, sample again, will set fan3 (may 2 ...) to value 150 (0-255), so should throttle down ... some fans need higher values to startup, so not any fan will start at 10 ... some needs 30, some 50, ... 150 is a sure value to look if it works or not echo 150 > /sys/devices/platform/it<your_controller_here>/hwmon/hwmon5/pwm3 good luck, still ... as pwm doesnt work, i cant imagine this will Thanks for your help 🙂 Yes, this path I have followed....my controller is it87.2624... * All but pwm1 are set to 1. * All can be set to any value (e.g. 100 or 150) but nothing changes and the values are not overwritten... Might be time to look for an external controller....because right now I cannot control fan via BIOS or via Unraid and that is driving me crazy.
September 19, 20241 yr 1 minute ago, ChirpyTurnip said: .because right now I cannot control fan via BIOS or via Unraid and that is driving me crazy. sure BIOS will always work, but as monitor its system temp or cpu temp only ... no hdd temps. and as soon you set the pwm_enable to 1 ... its OS controlled, so fans will then always runn 100 % as long as they are not throttled, what actually doesnt work on your system ... sadly. so, remove all autofan etc stuff, dont set anything, then it keeps BIOS controlled by fan curves or whatever you setted up in BIOS.
September 19, 20241 yr So that is the crazy thing - when I remove the it87 driver, the auto fan, the go file changes, and reboot....the fans behave the same way. If I boot off a live Linux DVD and muck around there for an hour or more then everything is nice and quiet....always quiet. BUT If I boot into Unraid again then for the first minute everything is normal and quiet....and then the fans get louder and then nothing but 100% fan again....even if the CPU is idle and just 50C, fans go nuts....and only the fans I tried to control! The CPU fan I haven't controlled, that does not go 100%....if goes up and down like normal.... Like seriously....this is only happening in Unraid. I swear there is something in the config that has changed after starting to try the fan control and now Unraid *is* doing something, just not what I want. 😞 I would cry, except that I must go to bed. It is late...and the alarm clock will show me no mercy in the morning.
September 20, 20241 yr 21 hours ago, ChirpyTurnip said: If I boot off a live Linux DVD and muck around there for an hour or more then everything is nice and quiet....always quiet. But keep in mind that they might have some monitoring/drivers in place which Unraid doesn't have right OOB. 21 hours ago, ChirpyTurnip said: Like seriously....this is only happening in Unraid. I swear there is something in the config that has changed after starting to try the fan control and now Unraid *is* doing something, just not what I want. 😞 Sorry, I really can't help with that because all my systems work as expected even my one system where the it87 driver is needed. Have you yet tried to leave Unraid as is without the driver and without the fan plugin and assign the temperature from the fans that you try to control to the CPU? On my systems I usually set the fans to a fixed speed in the BIOS or through the go script and they stay there.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.