To find the starting speed, you have to work upwards from 0. Find the minimum fan start speedįans have momentum – because pwmconfig was working down from the highest-to-lowest speed, it found the lowest speed it would keep spinning after it was already moving. your case fan stopped spinning, not your CPU fan). You should also physically check that this shut off the fan you expect it to (i.e. Replace the bold text below with the fan you want to control: echo 0 > /sys/class/hwmon/ cat /sys/class/hwmon/h wmon2/fan1_input From the command line, you can assign a value to a fan to directly control the speed. In order to make sure that you pick the right fan, I recommend doing a quick check. One of them is probably your CPU fan, which I’d recommend leaving under the control of your BIOS (it’s safer that way). You likely have two sets of fans (at least) that show up in the output. The setting (PWM) at which the fan stopped spinning.Above that I can see that hwmon2/pwm1 is correlated to hwmon2/fan1_input. Above the fan I want is controlled by hwmon2/pwm1 Would you like to generate a detailed correlation (y)? y It appears that fan hwmon2/fan1_input is controlled by pwm hwmon2/pwm1 The output will be long. What you’re looking for are the following things. When prompted to set up the configuration file, say “no”. When prompted, answer “yes” to generating a detailed correlation. To run it, SSH into your machine and run: pwmconfig The pwmconfig tool runs through all of your fan headers and vary the power output to find out which fans are controlled by each header. Next up, you’ll need to figure out which device controls what fan, as well as the minimum power that needs to be applied for a given fan to keep spinning.įans are controlled in Linux by assigning a value between 0 and 255 to the Pulse Width Modulated (PWM) fan header (0 is off, 255 is max power). (Or, alternatively, you can run the modprobe commands from the command line to load the kernel modules without rebooting).Īfter you reboot (or run the modprobe commands), you can run the sensors command from a command prompt which should show you the status of all the temperature sensors your machine knows about. Do not add in the ‘/user/bin/sensors -s’ line. Take the lines that start with modprobe from the sensors-detect output and add them to your ‘go’ file.Open up your unRAID ‘go’ file in an editor.But we want to make sure they run each time you boot your machine – to do that unRAID, we have to modify the ‘go’ file that runs each time your machine starts. The modprobe commands will load the specific kernel modules for your hardware enabling your computer to detect, read, and control these fans. #-cut here- Load the kernel modules at each boot Copy this block of text – you’ll need it in the next step.
The output will be pretty long, and result in the something that looks like the following. From the prompt, run sensors-detect. Answer “Yes” (by pressing Enter) to every question except the last prompt- you do not need to automatically generate the config file.
#DYNAMIX LOCAL MASTET PLUGIN UNRAID SETUP INSTALL#
It’s the easiest way to install Perl which is needed to discover your sensors. Discover your fan sensor kernel modulesīy default, it’s likely that you don’t have the kernel modules installed to give the system access to your fan speed sensors. These instructions are specific to unRAID v6, but may be useful for other Linux installations. But it wasn’t straight forward to get it operating, so I thought I’d post the steps I followed to get it running. In reading through several forum posts, I found a shell script that many people use to control their case fans based on their hard drive temperatures. There is a plugin ( Dynamix System AutoFan) that is supposed to do this, but it didn’t work for me.
When switching to unRAID, I wanted to fix this. The only reason they’re there is to cool my hard drives – which aren’t in use half the time. I’ve always been annoyed that the fans in my server spin all the time (wasting power, making noise) when they’re not needed.
0 kommentar(er)
