May 17, 20179 yr Hi all, I am hoping someone may be able to share some knowledge with me as I am scratching my head. I am no linux guru and tend to get non-standard things working via trial and error, so please know that if I ask a question it is not to annoy you, its likely I have no idea! I do however work in IT and so understand the premise of what I am trying to do, just not the implementation. So, my end goal is to setup array temperature based fan control, using the Dynamix plugin. The issue I am fighting at the moment is getting the PWM fan controller to be detected. My motherboard is an Asus Z170M-Plus. The board itself definitely has PWM support as I have configured PWM fan curves within the BIOS, but am obviously only able to have that track the CPU or motherboard temperature. Whether or not this is able to be passed up to the OS is unknown to me. The SystemAutoFan plugin see's no fan controller present. After spending a few hours following links from google to this very support forum, I have hit a bit of a brick wall. A summarised/compressed list of what I have done so far is: 1. Installed SystemAutoFan - found no pwm controller 2. Googled, found out about sensors-detect. Ran this found the config at the bottom of the post. Shows an Intel sensor for CPU/motherboard. Also shows an unknown sensor from Nuvoton 3. Looked up about Nuvoton drivers/modules for Unraid and found this - https://forums.lime-technology.com/topic/30414-need-driver-for-new-motherboard-super-io-chip/ This appeared to be for v5 and so when attempted to load using modprobe/insmod the module is not compatible and receive error - nsmod: ERROR: could not insert module /boot/custom/nct6775.ko: Invalid module format Again, I want to reiterate that I am no Linux guru, so this may have been a stupid thing to do! 4. Attempted to run pwmconfig and received this error - /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed To me this would mean I need to load a module of some kind, as attempted in step 3. 5. Attempted to run ipmitool -c sdr and it errors. Have seen other peoples output of this and it lists all of the fan details. I am open to ideas as to how to solve this and will really appreciate some peoples opinions on this problem I am experiencing. Thanks in advanced (below is the sensors-detect output) Sam root@WAITING:~# sensors-detect # sensors-detect revision 6284 (2015-05-31 14:00:33 +0200) # Board: ASUSTeK COMPUTER INC. Z170M-PLUS # Kernel: 4.9.19-unRAID x86_64 # Processor: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (6/94/3) 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): YES 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 15h power sensors... No AMD Family 16h power 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): YES Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found unknown chip with ID 0xd121 (logical device B has address 0x290, could be sensors) 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): YES 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): YES 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): YES Found unknown SMBus adapter 8086:a123 at 0000:00:1f.4. Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at f040 (i2c-0) Do you want to scan it? (YES/no/selectively): YES Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Probing for `EDID EEPROM'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No 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
Archived
This topic is now archived and is closed to further replies.