Fan Control - Master Thread

[Helloguys]

Sorry if this already exists.  But I was trying to consolidate the information on the form into one thread to make it more helpful for other users.

 

The Problem:

After installing DSM on non-Synology hardware (Xpenology), you might notice that the fan is running at full speed and noisy.  It doesn't matter what "fan speed mode" you set in "DSM > Control Panel > Hardware & Power".  The reason is - DSM use a proprietary circuit on Synology hardware for fan control.  On non-Synology hardware, this circuit does not exist, therefore DSM "fan speed mode" setting won't be able to control the fan speed.

 

Solutions:

There seems to be different solutions:

Option 1: Utilize the DSM GUI.  This solution uses a modified version of /usr/syno/bin/scemd so that the "fan speed mode" settings in DSM is redirected to your own fan speed control logic instead of Synology's proprietary circuit.  This seems to be a more elegant solution as it retain the features of the DSM.  Reference: https://github.com/NyaMisty/scemd_fanspeed_hook

Option 2: Ignore the DSM GUI.  This solution uses the /etc/fancontrol file to control the fan speed based on temperature.

References:

 

Please note: Either of the above solutions requires you to install hardware specific driver, which is usually missing from the 3rd-party loader.  Otherwise, you'll get message like below:

/opt/sbin/pwmconfig: There are no pwm-capable sensor modules installed

 

I'm not a Linux guru.  Can someone write a good document on how to load the sensor drivers?  For your reference, this is an output of "sensors-detect" command:

root@Q870:~# sensors-detect

sensors-detect revision 5946 (2011-03-23 11:54:44 +0100)
System: To be filled by O.E.M. Synoden
Board: INTEL Corporation MAHOBAY
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
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM 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'...                   No Trying family SMSC'... No
Trying family VIA/Winbond/Nuvoton/Fintek'...               Yes Found Fintek F71869A Super IO Sensors' Success!
(address 0xa20, driver to-be-written') Probing for Super-I/O at 0x4e/0x4f Trying family National Semiconductor'... 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
Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)
Module i2c-i801 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'...                                 Yes (confidence 8, not a hardware monitoring chip) 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'... Yes
(confidence 8, not a hardware monitoring chip)

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)
Driver `to-be-written':

ISA bus, address 0xa20
Chip `Fintek F71869A Super IO Sensors' (confidence: 9)
Note: there is no driver for Fintek F71869A Super IO Sensors yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.

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-i801... failed

 

[Fox Mulder]

How exactly do I run this from the DSM gui?