Jump to content
bonienl

Dynamix - V6 Plugins

2296 posts in this topic Last Reply

Recommended Posts

Posted (edited)

I was just trying to get my motherboard working (MSI X470 Gaming Pro Carbon) with the fan controller and seem to have figured it out. Here's what I did (being verbose in case it helps others troubleshoot their own motherboard in the future):

  1. Used sensors-detect to figure out that my board has a `VIA/Winbond/Nuvoton/Fintek' chip reported at ID 0xd352.
  2. Did a bunch of googling to find out that my board specifically has the Nuvoton NCT 6795D chip.
  3. More googling to find the supported devices: https://hwmon.wiki.kernel.org/device_support_status_n_o
  4. More googling to figure out that the nct6775 driver may also support the nct6795D.
  5. Tried 'modprobe nct6775 0xd352' (not sure if I was supposed to use force_id=0xd352, but it worked without it) and surprising, it worked and now the Fan Auto Control plugin shows my 6 nct6795 PWM controllers!

So @Taddeusz maybe try 'modprobe nct6775 0xd423' (with or without force_id=) and see if that works for you.

 

My only complaint now is that I'd like to be able to control more than one of my 6 PWM controllers. 

 

EDIT: Also worth pointing out that while detect doesn't work in the System Temp plugin, manually entering 'nct6775' as the driver and hitting save does. Enables me to see/select the temps and fans.

 

Edited by shooga

Share this post


Link to post

Oh, cool! Thank you so much! That driver worked. I now have two fans and a whole bunch more temps.

Share this post


Link to post

Glad to hear it worked! I'm usually the one asking the questions, so it's nice to be able to help. I think you'll need to add that command to your go file in order for the functionality to survive a reboot.

Share this post


Link to post
8 minutes ago, shooga said:

Glad to hear it worked! I'm usually the one asking the questions, so it's nice to be able to help. I think you'll need to add that command to your go file in order for the functionality to survive a reboot.

For me it actually works fine without specifying the hardware I’d so I added it to the plugin’s driver list.

Share this post


Link to post

Are you using Fan Auto Control too? Or just System Temp? Were you able to get both working without using modprobe?

Share this post


Link to post

No, I’m just using the Dynamix System Temperature plugin.

Share this post


Link to post

Ok, got it. If you want to use Fan Auto Control, which I really like because it uses the drive temps instead of CPU or system temp, then you may need the modprobe command. There doesn't seem to be a way to manually enter the driver there.

Share this post


Link to post
20 minutes ago, shooga said:

Ok, got it. If you want to use Fan Auto Control, which I really like because it uses the drive temps instead of CPU or system temp, then you may need the modprobe command. There doesn't seem to be a way to manually enter the driver there.

No, if u load the drivers via system temp, you dont need to also load it in any other program, its system wide enabled then.

Share this post


Link to post

I wonder what i have to do to get my pwm fan CHA running,

 


# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# Board: ASRock B85M DASH/OL R2.0
# Kernel: 4.18.20-unRAID x86_64
# Processor: Intel(R) Core(TM) i3-4370 CPU @ 3.80GHz (6/60/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): y
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): y
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 `Nuvoton NCT5573D/NCT5577D/NCT6776F Super IO Sensors' Success!
    (address 0x290, driver `nct6775')
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): y
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): y
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): y
Using driver `i2c-i801' for device 0000:00:1f.3: Intel Lynx Point (PCH)
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at f040 (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
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 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
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)
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: i915 gmbus ssc (i2c-1)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus vga (i2c-2)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus panel (i2c-3)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpc (i2c-4)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpb (i2c-5)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpd (i2c-6)
Do you want to scan it? (yes/NO/selectively): y


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 `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT5573D/NCT5577D/NCT6776F Super IO Sensors' (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

Could it have someting to do with 

 

Using driver `i2c-i801' for device 0000:00:1f.3: Intel Lynx Point (PCH)
Module i2c-dev loaded successfully.

 

Share this post


Link to post
On 11/18/2018 at 4:38 PM, bonienl said:

I haven't done any updates (yet) on the dynamix s3 sleep plugin.

Is there a plan to fix this bug?

I am also affected.

Share this post


Link to post
Posted (edited)
On 1/3/2019 at 12:09 PM, bonienl said:

The plugin relies on what your motherboard reports about pwm controllers.

 

You can check manually what is available under "/sys/devices/platform" and fill in the correct path under  pwm fan.

You were right!

 

It seems like my Mainboard doesnt report PWM speed back, still i can control the speed of the fans.

 

I just manually changed the setting from PWM2 (/sys/devices/platform/nct6775.656/hwmon/hwmon1/fan2_input) to PWM1 and /sys/devices/platform/nct6775.656/hwmon/hwmon1/fan1_input

 

And it works!

 

Still i have the problem that my CPU fan goes crazy, always like full speed. Thats my settings:

 

Settings for hwmon1/pwm2:
  Depends on hwmon0/temp1_input
  Controls hwmon1/fan2_input
  MINTEMP=60
  MAXTEMP=75
  MINSTART=150
  MINSTOP=0
  MINPWM=0
  MAXPWM=255

 

But it only works when i manually run fancontrol.. is there a automated way like could i simply make a user script run at array start: "fancontrol" ?

 

Would be cool if you could control multiple fans with your script ?! Like a GUI for the functions of fancontrol. Or atleast a way to select which sensor it should use. So we could use ur plugin (install multiple times) for CPU, also.

Edited by nuhll

Share this post


Link to post
Posted (edited)

I came up with this


#!/bin/bash
killall -15 fancontrol
echo "fancontrol gekillt"
rm -f /etc/fancontrol
echo "/etc/fancontrol gelöscht"
echo "# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/nct6775.656
DEVNAME=hwmon0=coretemp hwmon1=nct6776
FCTEMPS=hwmon1/pwm2=hwmon0/temp1_input
FCFANS= hwmon1/pwm2=hwmon1/fan2_input
MINTEMP=60 hwmon1/pwm2=60
MAXTEMP=75 hwmon1/pwm2=75
MINSTART=150 hwmon1/pwm2=20
MINSTOP=0 hwmon1/pwm2=15
MINPWM=0 hwmon1/pwm2=15
MAXPWM=255 hwmon1/pwm2=255" > /etc/fancontrol
echo "/etc/fancontrol/ neu geschrieben"
fancontrol

 

any ideas? Ive set it to "on startup of array".

 

edit:

slightly better version which i run every hour now, so if it crashs it restarts.

 

#!/bin/bash

###  Check if script already run 
if [[ -f "/var/run/fancontrol.pid" ]]; then
echo "fancontrol läuft bereits."
exit

else
echo "starte fancontrol"

fi

killall -15 fancontrol
echo "fancontrol gekillt"
rm -f /etc/fancontrol
echo "/etc/fancontrol gelöscht"
echo "# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/nct6775.656
DEVNAME=hwmon0=coretemp hwmon1=nct6776
FCTEMPS=hwmon1/pwm2=hwmon0/temp1_input
FCFANS= hwmon1/pwm2=hwmon1/fan2_input
MINTEMP=60 hwmon1/pwm2=60
MAXTEMP=75 hwmon1/pwm2=75
MINSTART=150 hwmon1/pwm2=20
MINSTOP=0 hwmon1/pwm2=15
MINPWM=0 hwmon1/pwm2=15
MAXPWM=255 hwmon1/pwm2=255" > /etc/fancontrol
echo "/etc/fancontrol neu geschrieben"
fancontrol
Edited by nuhll

Share this post


Link to post
Posted (edited)
2 hours ago, f@llo said:

Is there a plan to fix this bug?

I am also affected.

Yeah would be cool if this could be finally fixed.

It is a small fix which i have documented here in line 233-236: https://pastebin.com/knv869Aq

Matter of seconds.

 

 

Edited by darkside40

Share this post


Link to post

I am using Unraid Stable 6.6.6 but unable to install Dynamix System Stats

plugin: installing: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg
plugin: downloading https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg
plugin: downloading: https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.system.stats.plg ... done
plugin: installed Unraid version is too low, require at least version 6.7.0-rc0i
 

Share this post


Link to post

You need to wait until the new version of Unraid is released. Coming soon (tm).

Share this post


Link to post
11 minutes ago, bonienl said:

You need to wait until the new version of Unraid is released. Coming soon (tm).

Well. That’s interesting.😎

Bet I’ll be updating my server later today.

Share this post


Link to post
25 minutes ago, mrbilky said:

Has the genie been let out of the bottle?

1937194943_ScreenShot2019-01-12at8_14_42AM.thumb.png.7808eda874863d0abbd6ed21cda4ef21.png

 

1 hour ago, bonienl said:

You need to wait until the new version of Unraid is released. Coming soon (tm).

Kinda looks that way.

Share this post


Link to post

sysstat-12.1.2 was release Dec 14. will this be included in next update?

Share this post


Link to post

Hello,

 

I am running UR: 6.6.6 and attempted to update "Dynamix System Statistics" and received the following error:
plugin: updating: dynamix.system.stats.plg
plugin: installed Unraid version is too low, require at least version 6.7.0-rc0i

 

I was unable to locate a ver 6.7.0 (and quite frankly would love to get off 6.6.6 but even RC shows 6.6.0-RC4 to me.).

 

Is this a bug or am I missing a RC release somehow?

Share this post


Link to post
1 minute ago, fmp4m said:

Hello,

 

I am running UR: 6.6.6 and attempted to update "Dynamix System Statistics" and received the following error:
plugin: updating: dynamix.system.stats.plg
plugin: installed Unraid version is too low, require at least version 6.7.0-rc0i

 

I was unable to locate a ver 6.7.0 (and quite frankly would love to get off 6.6.6 but even RC shows 6.6.0-RC4 to me.).

 

Is this a bug or am I missing a RC release somehow?

Several reports of this, including just 2 posts up from yours on this thread. Apparently that update of the plugin must wait on the new release, which is anticipated.

Share this post


Link to post
3 minutes ago, fmp4m said:

Hello,

 

I am running UR: 6.6.6 and attempted to update "Dynamix System Statistics" and received the following error:
plugin: updating: dynamix.system.stats.plg
plugin: installed Unraid version is too low, require at least version 6.7.0-rc0i

 

I was unable to locate a ver 6.7.0 (and quite frankly would love to get off 6.6.6 but even RC shows 6.6.0-RC4 to me.).

 

Is this a bug or am I missing a RC release somehow?

I have no idea how to respond to this. I'm truly mystified. I can't even.

Share this post


Link to post
2 minutes ago, trurl said:

Several reports of this, including just 2 posts up from yours on this thread. Apparently that update of the plugin must wait on the new release, which is anticipated.

 

Welp,  thats what I get for getting Lasik.   Totally replied to page 1 thinking I was on  the last not seeing any reports.  

Share this post


Link to post

@bonienl Just tried to have a look at the cache dir settings but the page wont load, i get the following error in my logs, could be another issue with my machine but all other sections in settings are fine. I have not restarted my server yet.

Jan 14 10:17:41 Server php-fpm[6702]: [WARNING] [pool www] server reached max_children setting (20), consider raising it

 

Jan 14 10:19:11 Server nginx: 2019/01/14 10:19:11 [error] 6545#6545: *759590 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.3, server: , request: "GET /Settings/FolderCachingSettings HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "6be638aa6cf91355b8a5263599baf5fedf9b833f.unraid.net", referrer: "https://6be638aa6cf91355b8a5263599baf5fedf9b833f.unraid.net/Settings"

 

Edited by Lebowski

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now