Dynamix - V6 Plugins


Recommended Posts

Redirected here on my question, even though the rules seemed to state very clearly to post a new thread for a new question and not jump on an existing, unrelated, post.  Hopefully this is the right place for the question:

 

I'm unsure if the Dynamix System Temp plug in simply doesn't support my old hardware, or if there is some configuration I need to adjust somewhere.  After installing the plug in, all temps are simply reported as "-48 C" at all times.  

 

Running a Supermicro H8DA3-2 with dual Operon 2435's (six core 2.6GHz)

Unraid version 6.8.0, (though I had this same issue on 6.6.6 previously)

The driver found for the sys temp plug in is: w83627hf

 

This is my first post here, so if I need any other information, let me know.  My server is a rather large mis-match of hardware assembled on the cheap, but I'm not sure that that should matter here.  Over all it's not a huge issue, been running a year with it like this, but just replaced my CPU coolers with some with quieter fans and was curious what they run at now. 

Link to comment

Hello
I changed the hardware a few days ago and after that my Dynamix System Temperature pluign no longer works.
I've searched the forum but can't solve my problem

I have run sensors-detect in cli but get this problem.

 

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): 

To load everything that is needed, add this to one of the system

initialization scripts (e.g. /etc/rc.d/rc.local):

 

#----cut here----

# Chip drivers

modprobe k10temp

modprobe nct6775

/usr/bin/sensors -s

#----cut here----

 

You really should try these commands right now to make sure everything

is working properly. Monitoring programs won't work until the needed

modules are loaded.

 

root @ Tower: ~ # modprobe k10temp
root @ Tower: ~ # modprobe nct6775
modprobe: ERROR: could not insert 'nct6775': No such device
root @ Tower: ~ # / usr / bin / sensors -s
No sensors found!
Make sure you have loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
root @ Tower: ~ #

 

 

My hardware is

M/B: Micro-Star International Co., Ltd. B450M MORTAR MAX (MS-7B89) Version 1.0 - s/n: J916249308

BIOS: American Megatrends Inc. Version 2.50. Dated: 11/07/2019

CPU: AMD Ryzen 5 3600 6-Core @ 3600 MHz

Link to comment
53 minutes ago, trurl said:

If those were the sensors that were working on your old hardware then I wouldn't expect them to be the same on your new hardware.

 

Did you

 

Yes and i got 

I don't really know what to do after I do.

root@Tower:~# sensors-detect
# sensors-detect version 3.6.0
# System: Micro-Star International Co., Ltd. MS-7B89 [1.0]
# Board: Micro-Star International Co., Ltd. B450M MORTAR MAX (MS-7B89)
# Kernel: 4.19.88-Unraid x86_64
# Processor: AMD Ryzen 5 3600 6-Core Processor (23/113/0)

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): 
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 17h thermal sensors...                           Success!
    (driver `k10temp')
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
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): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6797D Super IO Sensors'                   Success!
    (address 0xa20, driver `nct6775')

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): 
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): 

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): 
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus
Module i2c-dev loaded successfully.

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 0 at 26:00.0 (i2c-4)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 1 at 26:00.0 (i2c-5)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 6 at 26:00.0 (i2c-6)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 8 at 26:00.0 (i2c-7)
Do you want to scan it? (yes/NO/selectively): 


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

Driver `k10temp':
  * Chip `AMD Family 17h thermal sensors' (confidence: 9)

Driver `nct6775':
  * ISA bus, address 0xa20
    Chip `Nuvoton NCT6797D Super IO Sensors' (confidence: 9)

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): 
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe k10temp
modprobe nct6775
/usr/bin/sensors -s
#----cut here----

You really should try these commands right now to make sure everything
is working properly. Monitoring programs won't work until the needed
modules are loaded.

Unloading i2c-dev... OK

 

Edited by Johan71
Link to comment
5 hours ago, tasmith88 said:

After a good month of researching, I was able to get mine to work by inputting the following in my go file:

 

modprobe nct6775 force_id=0xd120

 

Hopefully this works for you!

Yes it works but now i have to find out witch temp i what.

 

in0:                     1.07 V  (min =  +0.00 V, max =  +1.74 V)
in1:                     1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                     3.42 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                     3.38 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                     1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                   152.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                   768.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                     3.42 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                     3.28 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                     1.85 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                    0.00 V  (min =  +0.00 V, max =  +0.00 V)
in11:                  688.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                    1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                  608.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                    1.53 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                     0 RPM  (min =    0 RPM)
fan2:                  1560 RPM  (min =    0 RPM)
fan3:                   884 RPM  (min =    0 RPM)
fan4:                   852 RPM  (min =    0 RPM)
fan5:                   750 RPM  (min =    0 RPM)
SYSTIN:                 +39.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = CPU diode
CPUTIN:                 +40.0°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN0:                +39.0°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN1:               -128.0°C    sensor = thermistor
AUXTIN2:                +44.0°C    sensor = thermistor
AUXTIN3:                 -2.0°C    sensor = thermistor
SMBUSMASTER 0:          +51.5°C  
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled

 

Link to comment
22 minutes ago, Johan71 said:

Yes it works but now i have to find out witch temp i what.

 


in0:                     1.07 V  (min =  +0.00 V, max =  +1.74 V)
in1:                     1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                     3.42 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                     3.38 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                     1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                   152.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                   768.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                     3.42 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                     3.28 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                     1.85 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                    0.00 V  (min =  +0.00 V, max =  +0.00 V)
in11:                  688.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                    1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                  608.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                    1.53 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                     0 RPM  (min =    0 RPM)
fan2:                  1560 RPM  (min =    0 RPM)
fan3:                   884 RPM  (min =    0 RPM)
fan4:                   852 RPM  (min =    0 RPM)
fan5:                   750 RPM  (min =    0 RPM)
SYSTIN:                 +39.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = CPU diode
CPUTIN:                 +40.0°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN0:                +39.0°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN1:               -128.0°C    sensor = thermistor
AUXTIN2:                +44.0°C    sensor = thermistor
AUXTIN3:                 -2.0°C    sensor = thermistor
SMBUSMASTER 0:          +51.5°C  
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled

 

Once you go to SystemTemp plugin, it should give you the choices you need to choose from.

Edited by tasmith88
Link to comment

I have an ASUS x399a Prime motherboard and a threadripper 2910x processor running unraid 6.8.  I tried to remove the k10temp driver and add the it87 driver but it wont let me detect or even readd the driver.  Ive tried reinstall this plugin as well and this is all i see.  I do have perl install via the nerd pack.

 

Untitled.thumb.png.90ae72f4e94bba1a07e0b9536b77d8ef.png

 

output of sensors and sensors-detect:

 

Untitled.png.a1bacf7eb542f3df144db2fbc05a8da3.png

 

I wanted to change this driver because I am wanting to see more accurate temperatures for my processor.

 

Also this is weird....

 

Untitled.png.8f311e61befca5cca9fc2273cad61749.png

 

There is no Rescan button anywhere on this page but it has a help dropdown right underneath 'Array fan speed:'.

 

So, is there a way to completely uninstall this to somehow reset it or what should I do?  I want to use the it87 driver or something that comes at least close to correct temps for me.  Any help is very much appreciated as I have burned up most of my morning tinkering with this lol 

Edited by danktankk
Link to comment
17 hours ago, gberg said:

Can you please explain how to do that?

After searching for that very answer, I found out the 'go' file in the unRAID /boot/config directory of the flash drive. I also added that line to it, saved the change, then rebooted, but apparently it did not work.
My current understanding is that the chip is too recent (NCT6798D in my case which is just the next one quoted above) and not compatible with the current version of the sensors-detect and sensors present on the latest unRAID. Useful links I found during my searches:

https://wiki.unraid.net/Setting_up_CPU_and_board_temperature_sensing
https://hwmon.wiki.kernel.org/start (replacing the old lm-sensors.org site)

https://github.com/torvalds/linux/commit/0599682b826ff7bbf9d5804fa37bcef36b0c9404 the related issue to this specific chip.

https://forum.level1techs.com/t/temperature-system-monitoring-for-ryzen-3000-and-x570-motherboards-in-linux/145548 Someone with the exact same config as I who apparently managed to patch it up… I'll try to adapt it to unRAID with my little knowledge and see how it goes '-'

Link to comment

Hey guys. I have a problem with the sleep plugin. Under 6.7.2 it work's perfectly. After the upgrade to 6.8 it stopped working. In the logfile is nothing to see what's the problem. the disk's are spinned down, but it doesn't does to sleep. Then I tried a downgrade and it still work's. So the question is, what have you changed in unraid that it doesn't go ? Do you have any solutions ?

Link to comment

Running sensors in CLI results in this:

 

Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced
sensors_init: Can't parse bus name

I've run the 'sensors-detect' first but this still shows up.

Link to comment
On 1/5/2020 at 12:24 PM, danktankk said:

I have an ASUS x399a Prime motherboard and a threadripper 2950x processor running unraid 6.8.1  I tried to remove the k10temp driver and add the it87 driver but it wont let me detect or even readd the driver.  Ive tried reinstall this plugin as well and this is all i see.  I do have perl install via the nerd pack.

 

Untitled.thumb.png.90ae72f4e94bba1a07e0b9536b77d8ef.png

 

output of sensors and sensors-detect:

 

Untitled.png.a1bacf7eb542f3df144db2fbc05a8da3.png

 

I wanted to change this driver because I am wanting to see more accurate temperatures for my processor.

 

Also this is weird....

 

Untitled.png.8f311e61befca5cca9fc2273cad61749.png

 

There is no Rescan button anywhere on this page but it has a help dropdown right underneath 'Array fan speed:'.

 

So, is there a way to completely uninstall this to somehow reset it or what should I do?  I want to use the it87 driver or something that comes at least close to correct temps for me.  Any help is very much appreciated as I have burned up most of my morning tinkering with this lol 

This is still an issue for me.  Can anyone help?

Edited by danktankk
Link to comment

Model: Custom

M/B: Micro-Star International Co., Ltd. MPG X570 GAMING EDGE WIFI (MS-7C37) Version 1.0 - s/n: JA16689981

BIOS: American Megatrends Inc. Version 1.40. Dated: 09/10/2019

CPU: AMD Ryzen 7 3700X 8-Core @ 3600 MHz

HVM: Enabled

IOMMU: Enabled

Cache: 512 KiB, 4096 KiB, 32768 KiB

Memory: 32 GiB DDR4 (max. installable capacity 128 GiB)

 

Dynamix System Temperature is seeing this when i scan. k10temp nct6775

but no available sensors at the bottom. nerd pack is installed and peral is active 

 I runing unraid  Version: 6.8.1 

 

new to unraid any help would be helpful. 
 

Link to comment
23 hours ago, Triplerinse said:

Model: Custom

M/B: Micro-Star International Co., Ltd. MPG X570 GAMING EDGE WIFI (MS-7C37) Version 1.0 - s/n: JA16689981

BIOS: American Megatrends Inc. Version 1.40. Dated: 09/10/2019

CPU: AMD Ryzen 7 3700X 8-Core @ 3600 MHz

HVM: Enabled

IOMMU: Enabled

Cache: 512 KiB, 4096 KiB, 32768 KiB

Memory: 32 GiB DDR4 (max. installable capacity 128 GiB)

 

Dynamix System Temperature is seeing this when i scan. k10temp nct6775

but no available sensors at the bottom. nerd pack is installed and peral is active 

 I runing unraid  Version: 6.8.1 

 

new to unraid any help would be helpful. 
 

i dont think anyone is here....

Link to comment

thanks @tasmith88, but at this point i have deleted the temp app and dont plan on using it anymore until there is better support for it.  None of these apps actually read the true temps anyway..  Its all wonderment and space dust with arbitrary offsets.  Its not even a best guess, its just a guess. 

 

Edited by danktankk
Link to comment
On 1/7/2020 at 10:13 AM, oliveromen said:

Hey guys. I have a problem with the sleep plugin. Under 6.7.2 it work's perfectly. After the upgrade to 6.8 it stopped working. In the logfile is nothing to see what's the problem. the disk's are spinned down, but it doesn't does to sleep. Then I tried a downgrade and it still work's. So the question is, what have you changed in unraid that it doesn't go ? Do you have any solutions ?

I would let you know, that I upgraded yesterday to 6.8.1 and sleep work's now. Thanks 

Link to comment
On 12/23/2019 at 12:00 PM, gberg said:

Ok, so the plugin is supposed to work even after 6.8.0 upgrade? Any ideas what to do to get it working again

Not sure myself, but it was working fine with my old Ryzen 5 2400g. I swapped out to a Ryzen 9 and this stopped working which is super frustrating as I can't manage the temperature well without this.

Link to comment
On 1/6/2020 at 3:47 PM, Yros said:

After searching for that very answer, I found out the 'go' file in the unRAID /boot/config directory of the flash drive. I also added that line to it, saved the change, then rebooted, but apparently it did not work.
My current understanding is that the chip is too recent (NCT6798D in my case which is just the next one quoted above) and not compatible with the current version of the sensors-detect and sensors present on the latest unRAID. Useful links I found during my searches:

https://wiki.unraid.net/Setting_up_CPU_and_board_temperature_sensing
https://hwmon.wiki.kernel.org/start (replacing the old lm-sensors.org site)

https://github.com/torvalds/linux/commit/0599682b826ff7bbf9d5804fa37bcef36b0c9404 the related issue to this specific chip.

https://forum.level1techs.com/t/temperature-system-monitoring-for-ryzen-3000-and-x570-motherboards-in-linux/145548 Someone with the exact same config as I who apparently managed to patch it up… I'll try to adapt it to unRAID with my little knowledge and see how it goes '-'

 

Thanks, I tested this the other day ,when I restarted my UNRAID, and it worked perfectly, now the sensors are back again.

Link to comment
On 1/6/2020 at 3:47 PM, Yros said:

After searching for that very answer, I found out the 'go' file in the unRAID /boot/config directory of the flash drive. I also added that line to it, saved the change, then rebooted, but apparently it did not work.
My current understanding is that the chip is too recent (NCT6798D in my case which is just the next one quoted above) and not compatible with the current version of the sensors-detect and sensors present on the latest unRAID. Useful links I found during my searches:

https://wiki.unraid.net/Setting_up_CPU_and_board_temperature_sensing
https://hwmon.wiki.kernel.org/start (replacing the old lm-sensors.org site)

https://github.com/torvalds/linux/commit/0599682b826ff7bbf9d5804fa37bcef36b0c9404 the related issue to this specific chip.

https://forum.level1techs.com/t/temperature-system-monitoring-for-ryzen-3000-and-x570-motherboards-in-linux/145548 Someone with the exact same config as I who apparently managed to patch it up… I'll try to adapt it to unRAID with my little knowledge and see how it goes '-'

 

On 1/21/2020 at 10:50 AM, gberg said:

 

Thanks, I tested this the other day ,when I restarted my UNRAID, and it worked perfectly, now the sensors are back again.

Hmm, now my sensors are gone again, and I'm not able to select them. I guess the only way is to reboot again, or is it possible to simply run "modprobe nct6775 force_id=0xd120" command from the console?

Link to comment

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.