Dynamix - V6 Plugins


bonienl

3122 posts in this topic Last Reply

Recommended Posts

noob questions here.
 
I Cant seem to find this "PERL" plugin that I need.... could I be pointed to the right direction?
 
thank you

Yea, I always felt it should be installed automatically as it is required by the plugin
Link to post
  • Replies 3.1k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

It has been some time since I visited the Unraid forums. Due to health issues I had to take a break, and unfortunately this break took way longer than anticipated. But I am back and will sta

Notice: You must be running unRAID version 6.1 or later to use these plugins The easiest way of installing plugins is thru Community Applications. This is an apps installation manager develope

Today has been a productive day   I have updated several Dynamix plugins, mainly bug fixes. Please check your plugins to get the updates.

Posted Images

56 minutes ago, spl147 said:


Yea, I always felt it should be installed automatically as it is required by the plugin

To be fair, it's a system-wide thing.  If you had several plugins using PERL (say, Speedtest), and you uninstalled one of them, would you expect PERL to still be there?

Link to post
3 hours ago, Cessquill said:

To be fair, it's a system-wide thing.  If you had several plugins using PERL (say, Speedtest), and you uninstalled one of them, would you expect PERL to still be there?

yes if other installed plugins required it, like wize if you uninstall a plugin and no other installed plugins require it. then it should be removed

Link to post
1 hour ago, spl147 said:

yes if other installed plugins required it, like wize if you uninstall a plugin and no other installed plugins require it. then it should be removed

How should that be coordinated? How would the plugin know if anything else needs it?

Link to post

The plugin purposely doesn't install PERL to avoid multiple instances and/or different installed versions.

 

Instead 'one source' is used, which is the Nerd pack to install additional packages.

 

Also keep in mind that PERL is only needed to run the detection script, once sensors are known, there is no need for PERL.

 

Link to post
Posted (edited)

still unable to get the Fan Control to work right

whats the purpose of the Minutes interval?

i do set up  0 PWM  so the fans wont run    and set the temp 30 low  40 high  but how does  it work on a rising curve?

so 200rpm at 30   and 40 runs at 7500rpm for the fan  or my other fan  200rpm at 30  and 6000rpms on 40  but run in between

 

or in the end  do you have to run  Windows VM  and use the Fancontrol from the motherboard manufacture 

to get it to run right?  its an ASUS motherboard TUF x570

as i find the fans dont come on when they supposed to

 

even if i set to LOW 40  and HIGH 50  and not do exclude of any of the HDS 

it will not come on when 1 hard drive hits   41.5 degrees 

so it seems it doesnt wanna work 100% right least with Asus boards X570

 

also i not sure where the fan control is getting its numbers from for RPM

 

when the Fan is at 0rpms   it shows its running at 2800rpms  so i not sure how this is working its not accurate..   is it because its a X570 board

Edited by comet424
Link to post

hello,

First -  Welcome back and hoping for a fast recovery for you. 

second - I'm a noob, to unraid that is. basic linux understanding, proficient in hardware.

here is my issue-  i am trying to get the systems temps to work, have unraid 6.9.2 pro - IBM x3650 M3 latest bios- upon installing system temp, it might see sensors and then go away, even tried several times to flush the config and re-install including perl. and then it shows nothing for senstors or hard drive temps and never showed anything for fan controller.

i noticed this however upon re-installing the plugin again: (highlighted in RED- unraid version too high?)

has this been addressed with a work around prior ? as of 6/2/21 this is the error i get re-installing

 

 

plugin: installing: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.system.temp.plg
plugin: downloading https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.system.temp.plg
plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.system.temp.plg ... done
plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.system.temp.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz
+==============================================================================

Verifying package dynamix.system.temp.txz.
Installing package dynamix.system.temp.txz:
PACKAGE DESCRIPTION:
Package dynamix.system.temp.txz installed.
plugin: skipping: sensors-detect - Unraid version too high, requires at most version 6.7.2
plugin: skipping: sensors-detect - Unraid version too high, requires at most version 6.7.2


-----------------------------------------------------------
Plugin dynamix.system.temp is installed.
This plugin requires Dynamix webGui to operate
Copyright 2021, Bergware International
Version: 2021.05.20a
-----------------------------------------------------------

plugin: dynamix.system.temp.plg installed

 

then looking at the plugin i see just this:

image.png.98523b7c78a3026e991c530c1fdcf950.png

 

and this :

 

image.png.4ca6afaf72ffb40914c4d7d7ca18373b.png

 

and then the same for system and cpu temps:

 

image.png.f6c4bad569755db09a31118797291551.png

Link to post

as a followup:

I ran sensors-detect and this is the full result. now if someone could point me in the correct direction for the proper name of the driver i need to use, maybe i can manually load it and see if it detects:

 

image.thumb.png.08684454d04fdbcf4e7e5eda21861321.png

 

any help greatly appreciated. :)

-Bill

Link to post

a more complete copy of the script that ran, I have stripped out the negative responses:

 

# sensors-detect version 3.6.0
# System: IBM System x3650 M3 -[7945D2U]- [00]
# Board: IBM 90Y4784
# Kernel: 5.10.28-Unraid x86_64
# Processor: Intel(R) Xeon(R) CPU X5690 @ 3.47GHz (6/44/2)

 

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

Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel 5500/5520/X58 thermal sensor...                       Success!
    (driver `i5500_temp')

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
 

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
Found `IPMI BMC KCS' at 0xca2...                            Success!
    (confidence 8, driver `to-be-written')

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
 

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 ICH10
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at 3000 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x18
Handled by driver `jc42' (already loaded), chip type `jc42'
Client found at address 0x19
Handled by driver `jc42' (already loaded), chip type `jc42'
Client found at address 0x1b
Handled by driver `jc42' (already loaded), chip type `jc42'
Client found at address 0x1c
Handled by driver `jc42' (already loaded), chip type `jc42'
Client found at address 0x1e
Handled by driver `jc42' (already loaded), chip type `jc42'
Client found at address 0x1f
Handled by driver `jc42' (already loaded), chip type `jc42'
Client found at address 0x2e
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x51
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x53
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 `to-be-written':
  * ISA bus, address 0xca2
    Chip `IPMI BMC KCS' (confidence: 8)

Driver `jc42':
  * Bus `SMBus I801 adapter at 3000'
    Busdriver `i2c_i801', I2C address 0x18
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at 3000'
    Busdriver `i2c_i801', I2C address 0x19
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at 3000'
    Busdriver `i2c_i801', I2C address 0x1b
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at 3000'
    Busdriver `i2c_i801', I2C address 0x1c
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at 3000'
    Busdriver `i2c_i801', I2C address 0x1e
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at 3000'
    Busdriver `i2c_i801', I2C address 0x1f
    Chip `jc42' (confidence: 6)

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Driver `i5500_temp':
  * Chip `Intel 5500/5520/X58 thermal sensor' (confidence: 5)

Note: there is no driver for IPMI BMC KCS yet.
Check https://hwmon.wiki.kernel.org/device_support_status 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-dev... OK

Link to post

Found `IPMI BMC KCS' at 0xca2...                            Success!
    (confidence 8, driver `to-be-written')

 

Note: there is no driver for IPMI BMC KCS yet.

 

your fans are controlled via the IPMI BMS KCS, but there is NO driver for it currently. so you cannot control your fans via the fanspeed plugin!

Link to post
Posted (edited)

I'm also having trouble with my motherboard and the AutoFan plugin not being able to detect a PWM controller.

 

My motherboard is a MSI X470 Gaming Pro Carbon. I appreciate that this is a work in progress, but is this something that can work or might ever be able to work? Thanks 🙂

fan auto control.png

 

SOLVED - had to reboot the Unraid server for something else, after reboot the PWM controllers are listed and the airflow data shows on the dashboard. Weird.

Edited by TangoEchoAlpha
Reboot sorted it
Link to post

As of 7 hours ago, I'm getting the following alert pinged to me via email from Unraid:

/bin/sh: line 1: 28292 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

 

This is occurring every 25-30 minutes or so. The Unraid GUI is broken a bit now too; I can navigate between pages, but the syslog won't load, sometimes the Main tab won't load areas, the Docker and VMs tab won't load at all, and I cannot update Plugins.

The day before, Unraid became unresponsive around 1:00am, and was no longer displaying an output, so I had to hard reset it. It is currently finishing up the parity check it initiated due to this.

 

It's obviously a dynamix plugin causing this issue, but not sure which one uses the "monitor" script. I have not added, updated or removed any plugins in over 4 weeks, so seems odd that this is occurring now. The only thing that has changed in my machine is I added some new sticks of RAM, but that was 2 weeks ago. The more I write this, the more it sounds like it's a hardware fault, and not software, seeing as the OS is running in RAM.

 

Unfortunately, I tried to get Diagnostic logs, but it's hanging (it's been running for over an hour now). I've attached all of the Dyanmix plugins that I currently have. Running on Unraid 6.9.1.

image.thumb.png.7bc06a791d0748026fbac376d7224460.png

 

I'll try pulling the extra RAM I added, and guess I'll have to monitor it for a few weeks to see if this happens again.

Link to post
Posted (edited)

Hi,

 

I have a Gigabyte GA-Z87X-UD3H inside a 24 HDD chassis with 3 middle, 2 back and 2 cpu fans.

 

The fans are connected as follows:

- CPU_FAN: cpu fans 1-2

- CPU_OPT: back fans 1-2

- SYS_FAN3: middle fans 1-3

 

When I installed Unraid several months ago, I tried to manually setup this to auto control the fans but it seemed not to detect everything correctly (not sure, atm) and I found out that the dynamix plugin is or was based on this manual setup but with several tweaks/bugfixes, I guessed. So, I have installed the plugin (without removing anything I did before with the manual setup) and wondered which sensors etc. are correct. So, I sat next to my open server and looked while checking the settings.

 

- PWM Controller it8728 - pwm1: active, /sys/devices/platform/it87.2608/hwmon/hwmon2/fan5_input

- PWM Controller it8728 - pwm2: inactive, none detected

- PWM Controller it8728 - pwm3: active, /sys/devices/platform/it87.2608/hwmon/hwmon2/fan4_input

 

So, it looked good, the disk temperatures were around 32-43° C.

 

Now, I have received the several warnings by mail, the disk temperatures are up to 55° C (!!!) and after looking inside the server, there are 3 fans that are not active:

- 1 of the cpu fans

- 1 of the back fans

- 1 of the middle fans

 

This is especially strange as all of these fans are not connected solely but with a fan that works.

 

So, what is wrong here? How can I check?

 

The log says it adjusts the RPM:

Jun  6 00:31:57 godsbane autofan: Highest disk temp is 41C, adjusting fan speed from: 202 (79% @ 1753rpm) to: 186 (72% @ 1626rpm)
Jun  6 00:31:57 godsbane autofan: Highest disk temp is 41C, adjusting fan speed from: 202 (79% @ 0rpm) to: 186 (72% @ 0rpm)
Jun  6 00:37:03 godsbane autofan: Highest disk temp is 42C, adjusting fan speed from: 186 (72% @ 1634rpm) to: 202 (79% @ 1748rpm)
Jun  6 00:37:03 godsbane autofan: Highest disk temp is 42C, adjusting fan speed from: 186 (72% @ 0rpm) to: 202 (79% @ 0rpm)
Jun  6 00:38:43 godsbane emhttpd: spinning down /dev/sdf
Jun  6 00:40:55 godsbane emhttpd: read SMART /dev/sdf
Jun  6 01:12:11 godsbane autofan: Highest disk temp is 41C, adjusting fan speed from: 202 (79% @ 0rpm) to: 186 (72% @ 0rpm)
Jun  6 01:12:11 godsbane autofan: Highest disk temp is 41C, adjusting fan speed from: 202 (79% @ 1735rpm) to: 186 (72% @ 1630rpm)
Jun  6 01:16:06 godsbane emhttpd: spinning down /dev/sdc
Jun  6 01:19:44 godsbane emhttpd: read SMART /dev/sdc
Jun  6 01:22:18 godsbane autofan: Highest disk temp is 42C, adjusting fan speed from: 186 (72% @ 0rpm) to: 202 (79% @ 0rpm)
Jun  6 01:22:18 godsbane autofan: Highest disk temp is 42C, adjusting fan speed from: 186 (72% @ 1626rpm) to: 202 (79% @ 1748rpm)
Jun  6 01:22:43 godsbane emhttpd: read SMART /dev/sdh
Jun  6 01:23:10 godsbane emhttpd: read SMART /dev/sdj
Jun  6 01:37:59 godsbane emhttpd: read SMART /dev/sdk
Jun  6 01:53:12 godsbane emhttpd: spinning down /dev/sdj
Jun  6 02:00:57 godsbane emhttpd: read SMART /dev/sdl
Jun  6 02:01:09 godsbane emhttpd: read SMART /dev/sdj
Jun  6 02:01:23 godsbane emhttpd: read SMART /dev/sdg
Jun  6 02:02:28 godsbane autofan: Highest disk temp is 43C, adjusting fan speed from: 202 (79% @ 0rpm) to: 218 (85% @ 0rpm)
Jun  6 02:02:28 godsbane autofan: Highest disk temp is 43C, adjusting fan speed from: 202 (79% @ 1739rpm) to: 218 (85% @ 1854rpm)
Jun  6 02:03:27 godsbane emhttpd: shcmd (3179161): /usr/local/sbin/mover &> /dev/null &
Jun  6 02:03:43 godsbane emhttpd: read SMART /dev/sdd
Jun  6 02:03:43 godsbane emhttpd: read SMART /dev/sde
Jun  6 02:05:40 godsbane emhttpd: read SMART /dev/sdm
Jun  6 02:07:34 godsbane autofan: Highest disk temp is 44C, adjusting fan speed from: 218 (85% @ 0rpm) to: 234 (91% @ 0rpm)
Jun  6 02:07:34 godsbane autofan: Highest disk temp is 44C, adjusting fan speed from: 218 (85% @ 1849rpm) to: 234 (91% @ 1950rpm)
Jun  6 02:07:44 godsbane kernel: mdcmd (64): set md_write_method 1
Jun  6 02:07:44 godsbane kernel: 
Jun  6 02:12:39 godsbane autofan: Highest disk temp is 45C, adjusting fan speed from: 234 (91% @ 0rpm) to: FULL (100% @ 0rpm)
Jun  6 02:12:39 godsbane autofan: Highest disk temp is 45C, adjusting fan speed from: 234 (91% @ 1973rpm) to: FULL (100% @ 2109rpm)

 

Now, I manually activated PWM Controller it8728 - pwm2 without corresponding fan (as none is detected) and the log shows:

 

Jun  6 11:19:19 godsbane ool www[32242]: /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/rc.autofan 'start'
Jun  6 11:19:19 godsbane autofan: autofan process ID 406 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2608/hwmon/hwmon2/pwm1 -f /sys/devices/platform/it87.2608/hwmon/hwmon2/fan5_input
Jun  6 11:19:19 godsbane autofan: autofan process ID 443 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2608/hwmon/hwmon2/pwm2 -f /sys/class/hwmon/hwmon2/fan1_input
Jun  6 11:19:19 godsbane autofan: autofan process ID 483 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2608/hwmon/hwmon2/pwm3 -f /sys/devices/platform/it87.2608/hwmon/hwmon2/fan4_input
Jun  6 11:19:25 godsbane autofan: Highest disk temp is 53C, adjusting fan speed from: 70 (27% @ 0rpm) to: FULL (100% @ 0rpm)

 

But this changed nothing - the 3 fans are still not working. By the way, all fans have been brought together.

 

I will shutdown the server after the mover is done and will observe, if those fans are working when I reboot.

Edited by tardezyx
Link to post

The fan control plugin will only control 1 header.

Your middle and rear fans should be combined with a powered fan splitter and connecter to 1 system header and set to full speed in the bios. Cpu fans should be configured to auto in bios based on cpu temp.

Run sensors detect, then load discovered drivers, in the fan speed plugin click detect then select the correct pwm output

Link to post

After deactivating the PWM controls in the plugin and re-activating with re-detecting (the 2 it has detected before), it seems to work now, again.

38 minutes ago, spl147 said:

The fan control plugin will only control 1 header.

It should be able to handle 3 controllers. Unfortunately, it detects only 2 here - so ye: I think I will leave the cpu fans set by BIOS only.

Link to post
3 hours ago, tardezyx said:

After deactivating the PWM controls in the plugin and re-activating with re-detecting (the 2 it has detected before), it seems to work now, again.

It should be able to handle 3 controllers. Unfortunately, it detects only 2 here - so ye: I think I will leave the cpu fans set by BIOS only.

im telling you it only controls 1!

 

 

Screen Shot 2021-06-06 at 5.22.02 PM.png

Link to post
Posted (edited)
12 minutes ago, spl147 said:

im telling you it only controls 1!

Nope, you can switch through the PWM controllers and set (activate/deactivate) every one of them each on their own. It even shows in your unraid system log different autofan process IDs:

 

Jun  6 23:34:30 godsbane autofan: autofan process ID 5315 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2608/hwmon/hwmon2/pwm1 -f /sys/devices/platform/it87.2608/hwmon/hwmon2/fan5_input
Jun  6 23:34:30 godsbane autofan: autofan process ID 5350 started, To terminate it, type: autofan -q -c /sys/devices/platform/it87.2608/hwmon/hwmon2/pwm3 -f /sys/devices/platform/it87.2608/hwmon/hwmon2/fan4_input
Jun  6 23:34:35 godsbane autofan: Highest disk temp is 38C, adjusting fan speed from: FULL (100% @ 2265rpm) to: 189 (74% @ 1748rpm)
Jun  6 23:34:35 godsbane autofan: Highest disk temp is 38C, adjusting fan speed from: FULL (100% @ 1708rpm) to: 189 (74% @ 1662rpm)

 

Edited by tardezyx
Link to post
2 minutes ago, tardezyx said:

Nope, you can switch through the PWM controllers and set (activate/deactivate) every one of them each on their own. It even shows in your unraid system log different autofan process IDs.

currently it only works if you have a single config file and a single controller! it's a known issue.

Link to post
2 minutes ago, spl147 said:

currently it only works if you have a single config file and a single controller! it's a known issue.

What!? Is there a manual for how to correctly set this up?

Link to post
Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `jc42':
  * Bus `SMBus I801 adapter at f040'
    Busdriver `i2c_i801', I2C address 0x18
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at f040'
    Busdriver `i2c_i801', I2C address 0x19
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at f040'
    Busdriver `i2c_i801', I2C address 0x1a
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at f040'
    Busdriver `i2c_i801', I2C address 0x1b
    Chip `jc42' (confidence: 6)

Driver `it87':
  * ISA bus, address 0xa30
    Chip `ITE IT8728F Super IO Sensors' (confidence: 9)

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): Y
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

Now, how do I proceed?

Link to post
2 minutes ago, tardezyx said:

Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `jc42':
  * Bus `SMBus I801 adapter at f040'
    Busdriver `i2c_i801', I2C address 0x18
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at f040'
    Busdriver `i2c_i801', I2C address 0x19
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at f040'
    Busdriver `i2c_i801', I2C address 0x1a
    Chip `jc42' (confidence: 6)
  * Bus `SMBus I801 adapter at f040'
    Busdriver `i2c_i801', I2C address 0x1b
    Chip `jc42' (confidence: 6)

Driver `it87':
  * ISA bus, address 0xa30
    Chip `ITE IT8728F Super IO Sensors' (confidence: 9)

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): Y
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

Now, how do I proceed?

from command line run "modprobe jc42 it87 coretemp" or install the system temp plugin and the neardpack and from neardpack install pearl, the in the system temp plugin click detect

 

Link to post
Posted (edited)
35 minutes ago, spl147 said:

from command line run "modprobe jc42 it87 coretemp" or install the system temp plugin and the neardpack and from neardpack install pearl, the in the system temp plugin click detect

 

I had already installed the temp plugin, nerdpack and pearl and clicked detect which now still shows me this:

grafik.png.76b8e75907267f9114589e54e80b97b4.png

grafik.png.6b3b73e8336570cf9d67c3c8f26381ef.png

grafik.png.16627d23f7988eb856bea9f210f8e105.png

I am not sure about the correct sensors (if I remember correctly, I had once renamed those "CPU Temp" and "MB Temp" sensors a while back - i think, remembered wrongly 😄).

 

In Fan Auto Control I have these options:

grafik.thumb.png.ef2b7c89d3e3aa7dc008ae02c0a7cad6.png

 

I guess, I need to open the case and connect back & middle fans to one MB fan connector, as you said, and then just try & error which one of these three is the correct one. Is this correct?

Edited by tardezyx
Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.