Dynamix - V6 Plugins


Recommended Posts

I have been using the system temps plugin on my intel-based server for a while and it worked flawlessly (unraid 6.10.3, fresh install). I recently upgraded to a 3950x with Crosshair viii hero motherboard, and some awkward behavior showed up. The first time I detect drivers, the processor temp and mainboard temp and even fan speed of my kraken AIO shows up properly, but after I click save on drivers, all the temps goes away, and regardless what I do (load drivers, unload, rescan) no temperature would show up. Any input on this problem would be appreciated!

Link to comment

Used Fan speed / system temp fine on old system, swapped out motherboard to an ASUS ROG CROSSHAIR VIII HERO (AMD X570)
However now I only get CPU/Mobo temp, no other sensors or fan speeds show up.

Wondering if anyone could take a squiz and see what might be going on..
Bios shows all this info fine, so I presume unraid just isn't picking up one of the sensors
sensors-detect doesn't bring any new information either

Appreciate it!

minerva-diagnostics-20220701-0945.zip

Edited by FlippinTurt
Link to comment

Hi all.

 

Maybe a bit dumb on my part but I have just installed unraid 6.10.3 (previously I was on 6.9) and now system temp plugin seems to be broke.

 

when i go into the plugin settings page everything seem to be greyed out, tried rebooting the server a few times but doesn't help

 

any idea?

 

image.thumb.png.52561941e5004cf88696785564f76302.png

Link to comment
13 hours ago, FlippinTurt said:

Anyone have an update on X570 boards and system fan / system temp plugins?

 

You need to identify the Super I/O chip, which is separate from the main chipset. It won't be made by AMD. Likely manufacturers include ITE and Nuvoton. You need a driver for that chip and it needs to be loaded at boot time. Have you tried running the sensors-detect command, as @bastl did a few messages up on this page? It might need the id of the chip to be overridden and you might need to do some web searching once you've determined what chip your motherboard actually uses. For example, I have a Gigabyte X370 motherboard that uses an ITE chip. All I had to do was add

 

modprobe it87

 

to my /boot/config/go file. YMMV, of course.

  • Like 1
Link to comment
1 hour ago, John_M said:

 

You need to identify the Super I/O chip, which is separate from the main chipset. It won't be made by AMD. Likely manufacturers include ITE and Nuvoton. You need a driver for that chip and it needs to be loaded at boot time. Have you tried running the sensors-detect command, as @bastl did a few messages up on this page? It might need the id of the chip to be overridden and you might need to do some web searching once you've determined what chip your motherboard actually uses. For example, I have a Gigabyte X370 motherboard that uses an ITE chip. All I had to do was add

 

modprobe it87

 

to my /boot/config/go file. YMMV, of course.

Found I have a Nuvoton chip, needed to add this to boot; acpi_enforce_resources=lax
Seems I have all my temps and fan speeds again 😍

Link to comment
On 7/17/2022 at 9:12 PM, John_M said:

 

That is the current version. More information is needed about your problem though. I haven't experienced it for five years.

I only need telegram notifications.

How can I completely disable email authorization and notifications?

There is no "disable" option. If i choose custom then all fields must be filled.

If i leave it at "google" then it spam in logs about unsuccessful authorization. Even if all "email" box is unchecked.

image.thumb.png.82e82a0954e778c6db74b7ed5b7da4e9.png

 

image.thumb.png.931120e687cce32fe93a2d1586b4018c.png

Edited by Nuke
  • Upvote 1
Link to comment

SYSTEM TEMP PLUGIN

Hardware: Asus ROG STRIX Z490-i

Unraid: 6.10.3

 

The System temp plugin recognizes the CPU temp of my system but it doesn't seem to find the motherboard temp:

82394536_ScreenShot2022-07-26at2_53_56PM.thumb.png.8f0c85462ef60e6922ed71b017615d40.png

 

It also doesn't detect my fans:

602926331_ScreenShot2022-07-26at2_54_02PM.png.a6679ba1c193ba179b1df188877c69b8.png

 

The "sensors" command showed the following output:

amdgpu-pci-0300
Adapter: PCI adapter
vddgfx:      725.00 mV 
edge:         +49.0°C  (crit = +100.0°C, hyst = -273.1°C)
                       (emerg = +105.0°C)
junction:     +49.0°C  (crit = +110.0°C, hyst = -273.1°C)
                       (emerg = +115.0°C)
mem:          +46.0°C  (crit = +105.0°C, hyst = -273.1°C)
                       (emerg = +110.0°C)
slowPPT:      10.00 W  (cap = 170.00 W)

nvme-pci-0700
Adapter: PCI adapter
Composite:    +37.9°C  (low  = -20.1°C, high = +74.8°C)
                       (crit = +79.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +119.0°C)

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +30.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:       +31.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:       +28.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:       +29.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:       +28.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:       +30.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:       +27.0°C  (high = +82.0°C, crit = +100.0°C)
Core 6:       +29.0°C  (high = +82.0°C, crit = +100.0°C)
Core 7:       +29.0°C  (high = +82.0°C, crit = +100.0°C)

nvme-pci-0400
Adapter: PCI adapter
Composite:    +30.9°C  (low  = -20.1°C, high = +74.8°C)
                       (crit = +79.8°C)

 

 

I also ran sensor detect (answered "yes" to everything) and got the following output:

 

root@B-List:~# sensors-detect
# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. ROG STRIX Z490-I GAMING
# Kernel: 5.15.46-Unraid x86_64
# Processor: Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (6/165/5)

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
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal 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): yes
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 NCT6798D 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): 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...       Success!
    (confidence 6, driver `lm78')
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
Found unknown SMBus adapter 8086:06a3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at efa0 (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)

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

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

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

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

Next adapter: AUX B/DDI B/PHY B (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x4a
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Client found at address 0x4b
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `Analog Devices ADT7481'...                     No

Next adapter: AUX C/DDI C/PHY C (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU SMU (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-8)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-9)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-10)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-11)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM aux hw bus 0 (i2c-12)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM aux hw bus 1 (i2c-13)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AMDGPU DM aux hw bus 2 (i2c-14)
Do you want to scan it? (yes/NO/selectively): yes


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 NCT6798D Super IO Sensors' (confidence: 9)

Do you want to overwrite /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

 

Unfortunately, I don't know what to do with any of this information since I am new to Unraid. Any suggestions on what I can do to get my motherboard temps and the fans to show up?

Link to comment
On 7/17/2022 at 10:20 PM, FlippinTurt said:

Found I have a Nuvoton chip, needed to add this to boot; acpi_enforce_resources=lax
Seems I have all my temps and fan speeds again 😍

@FlippinTurt I seem to have the Nuvoton NCT6798D chip and I only get CPU temps but not the Motherboard temp or fan speeds. I assume I may have the same issue as you

 

Could you tell me where and how exactly I would need to enter "acpi_enforce_resources=lax"? You mention you added this to boot but I'm new to Unraid so I'm not exactly sure that this means. ;)

Link to comment

Hi...

Upgraded to 6.10.3 and it seems that the Network Stats, under Stats, is no longer displaying.  It just shows broken graphic icons.

 

I uninstalled and reinstalled STATS and still the same. (See attached)


Any guidance would be appreciated.

Thank you.

David

screenshot_3491.png

screenshot_3492.png

Edited by David Bott
Link to comment
5 hours ago, venicenerd said:

@FlippinTurt I seem to have the Nuvoton NCT6798D chip and I only get CPU temps but not the Motherboard temp or fan speeds. I assume I may have the same issue as you

 

Could you tell me where and how exactly I would need to enter "acpi_enforce_resources=lax"? You mention you added this to boot but I'm new to Unraid so I'm not exactly sure that this means. ;)

image.thumb.png.6a08c0fd5b01794d414a7e5a2319b229.png
If you click on your 'Main' tab, click on 'Flash' and it will take you to the Flash device settings.  Scroll down till you see syslinux config, and add it to the end of the current commands there (Leaving a space after the last command) :)
After that give it a reboot and should be all good

Link to comment
6 hours ago, FlippinTurt said:

image.thumb.png.6a08c0fd5b01794d414a7e5a2319b229.png
If you click on your 'Main' tab, click on 'Flash' and it will take you to the Flash device settings.  Scroll down till you see syslinux config, and add it to the end of the current commands there (Leaving a space after the last command) :)
After that give it a reboot and should be all good

 

Thanks @FlippinTurt. It still just lets me choose the CPU temp, though. Nothing in mainboard temp:

687612608_ScreenShot2022-07-27at3_53_18AM.png.186604275e7d99b35c5ccacb99fbc59a.png

 

I think I did it right?

1663370109_ScreenShot2022-07-27at3_50_09AM.png.eedcab2ba415f3d48513569fbd057e8d.png

 

Are you able to see the motherboard temp on your end? Do I have anything else set wrong?

Link to comment

Hi...

 

System Temp and Fan Control
unRAID 6.10.3  (Note that going to this ver of unRAID also broke the NEt Stats screen.  I mentioned this also above. Sadly no reply.)

 

Motherboard: Gigabyte Z690i ADRUS ULTRA LITE DDR4

 

The System Temp can only see the CPU (and cores) , Motherboard Temp and NVMe temps.  It can not find the FAN's at all. 

I have tried a few things just to try to resolve it from reading above.  I have tried adding "acpi_enforce_resources=lax" to the boot with no luck (hey you never know.)  I also tried adding "modprobe it87" to the GO file again just to try something.  

 

I ran the sensors-detect and the output is below.  Can't seem to find the chip or driver that is needed that I can tell.

Anyone have any ideas on what I may be able to do to get this MB readings for the FAN's so I then can control them? (they are 4 pin headers so they are controllable and they do show up in the BIOS.)  There are only 2 case fans and 1 CPU fan...None show.  :(  

Thank you for your time.
 

 

root@Server:~# sensors-detect
# sensors-detect version 3.6.0
# System: Gigabyte Technology Co., Ltd. Z690I A ULTRA LITE D4 [-CF]
# Kernel: 5.15.46-Unraid x86_64
# Processor: 12th Gen Intel(R) Core(TM) i5-12600K (6/151/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
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...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal 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): YES
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'...                                      Yes
Found unknown chip with ID 0x8689
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): 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
Found unknown SMBus adapter 8086:7aa3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at efa0 (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)

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
 

screenshot_3511.png

Link to comment

I am having trouble adding my NZXT Kraken x62 fan to the fan array in this plugin. When I go to the plug in settings and open the drop down it shows the kraken fan and pump but when I select the fan and click apply it wipes out all of the values set and none of the dropdowns have any options available.

 

Before selecting the fan:

image.thumb.png.5a377446a30f9d6ce8fa74976cefe178.png

 

After selecting the fan:

image.thumb.png.cdaa3beed68bd05d4f7cad1a6ccda138.png

 

If I run

sensors

I get the error

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

 

Checking /etc/sensors.d/sensors.conf I see the Kraken is listed on that line.

image.thumb.png.ec4c62b8bea672e870817ead55c7917b.png

 

If I comment it out and rescan in the plug in I get the sensor options back. 

 

Is there a way to get this fan sensor to play nice with Unraid?

Link to comment

Having issues with System Temp not showing any sensors after detection. This worked previously, but I upgraded my rig and am now using an ASRock Z590 Steel Legend which isn’t providing proper sensor detection.

A799BD0B-86FE-4CD2-AA33-A56504257B84.thumb.jpeg.f4858c08fd446877d79c021bfca62525.jpeg

 

 This is my sensors detected…

E72D855A-5057-4526-BFF5-C3B9028C2904.thumb.jpeg.436445b5424dd700915f702832ed8005.jpeg


…and this is my sensors config.

599D39AE-F95D-46EF-BBCB-B3CF82CFC2EF.thumb.jpeg.d6b8e5a74358e71425d9870e160dc85c.jpeg
 

The detected “coretemp nct6775” provides no numbers at all, so I tried plugging in “coretemp nct6779” to match the config file but that wouldn’t load the drivers. Using just “coretemp” works to show the CPU temp, but not the motherboard temps or array fan speeds. Any idea what I can try next?
 

Edit:

Editing my flash boot option to…

kernel /bzimage

append initrd=/bzroot acpi_enforce_resources=lax

…fixed my issue after restarting!

Edited by Krolitian
Link to comment
On 8/3/2022 at 8:58 AM, jdiacobbo said:

I am having trouble adding my NZXT Kraken x62 fan to the fan array in this plugin. When I go to the plug in settings and open the drop down it shows the kraken fan and pump but when I select the fan and click apply it wipes out all of the values set and none of the dropdowns have any options available.

 

Before selecting the fan:

image.thumb.png.5a377446a30f9d6ce8fa74976cefe178.png

 

After selecting the fan:

image.thumb.png.cdaa3beed68bd05d4f7cad1a6ccda138.png

 

If I run

sensors

I get the error

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

 

Checking /etc/sensors.d/sensors.conf I see the Kraken is listed on that line.

image.thumb.png.ec4c62b8bea672e870817ead55c7917b.png

 

If I comment it out and rescan in the plug in I get the sensor options back. 

 

Is there a way to get this fan sensor to play nice with Unraid?

I updated /ect/sensors.d/sensors.conf.save to also remove the two kraken lines and now everything is working properly. 

Edited by jdiacobbo
Link to comment

I have an ASUS Prime X370 Pro and I'm having trouble with the fan control. There are six fan headers on the board and only two are detected. I ran sensors-detect and got this:

 

Quote

root@BigNAS:~# sensors-detect
# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. PRIME X370-PRO
# Kernel: 5.15.46-Unraid x86_64
# Processor: AMD Ryzen 5 1500X Quad-Core Processor (23/1/1)

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 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): 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'...               No
Trying family `ITE'...                                      Yes
Found `ITE IT8665E Super IO Sensors'                        Success!
    (address 0x290, driver `to-be-written')
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-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): y
Client found at address 0x1a
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1618'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `Maxim MAX6654'...                              No
Probing for `Maxim MAX6690'...                              No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `Maxim MAX6695/MAX6696'...                      No
Probing for `Texas Instruments TMP400'...                   No
Probing for `Texas Instruments AMC6821'...                  No
Probing for `ST STTS424'...                                 No
Probing for `ST STTS424E'...                                No
Probing for `ST STTS2002'...                                No
Probing for `ST STTS3000'...                                No
Probing for `NXP SE97/SE97B'...                             No
Probing for `NXP SE98'...                                   No
Probing for `Analog Devices ADT7408'...                     No
Probing for `IDT TS3000/TSE2002'...                         No
Probing for `IDT TSE2004'...                                No
Probing for `IDT TS3001'...                                 No
Probing for `Maxim MAX6604'...                              No
Probing for `Microchip MCP9804'...                          No
Probing for `Microchip MCP9808'...                          No
Probing for `Microchip MCP98242'...                         No
Probing for `Microchip MCP98243'...                         No
Probing for `Microchip MCP98244'...                         No
Probing for `Microchip MCP9843'...                          No
Probing for `ON CAT6095/CAT34TS02'...                       No
Probing for `ON CAT34TS02C'...                              No
Probing for `ON CAT34TS04'...                               No
Probing for `Atmel AT30TS00'...                             No
Probing for `Giantec GT30TS00'...                           No
Client found at address 0x1b
Probing for `ST STTS424'...                                 No
Probing for `ST STTS424E'...                                No
Probing for `ST STTS2002'...                                No
Probing for `ST STTS3000'...                                No
Probing for `NXP SE97/SE97B'...                             No
Probing for `NXP SE98'...                                   No
Probing for `Analog Devices ADT7408'...                     No
Probing for `IDT TS3000/TSE2002'...                         No
Probing for `IDT TSE2004'...                                No
Probing for `IDT TS3001'...                                 No
Probing for `Maxim MAX6604'...                              No
Probing for `Microchip MCP9804'...                          No
Probing for `Microchip MCP9808'...                          No
Probing for `Microchip MCP98242'...                         No
Probing for `Microchip MCP98243'...                         No
Probing for `Microchip MCP98244'...                         No
Probing for `Microchip MCP9843'...                          No
Probing for `ON CAT6095/CAT34TS02'...                       No
Probing for `ON CAT34TS02C'...                              No
Probing for `ON CAT34TS04'...                               No
Probing for `Atmel AT30TS00'...                             No
Probing for `Giantec GT30TS00'...                           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)
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: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (YES/no/selectively): y

Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-2)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x4e
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6642'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1618'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `Maxim MAX6654'...                              No
Probing for `Maxim MAX6690'...                              No
Probing for `Maxim MAX6659'...                              No
Probing for `Maxim MAX6647'...                              No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `Maxim MAX6695/MAX6696'...                      No
Probing for `Texas Instruments TMP400'...                   No
Probing for `Texas Instruments TMP411C'...                  No
Probing for `Texas Instruments TMP421'...                   No
Probing for `Texas Instruments TMP422'...                   No
Probing for `Texas Instruments TMP435'...                   No
Probing for `Texas Instruments TMP441'...                   No
Probing for `Texas Instruments AMC6821'...                  No
Probing for `National Semiconductor LM95234'...             No
Probing for `National Semiconductor LM64'...                No
Probing for `National Semiconductor LM73'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `Fintek F75121R/F75122R/RG (VID+GPIO)'...       No
Probing for `Fintek F75111R/RG/N (GPIO)'...                 No
Probing for `ITE IT8201R/IT8203R/IT8206R/IT8266R'...        No

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

Next adapter: NVIDIA i2c adapter 6 at 9:00.0 (i2c-4)
Do you want to scan it? (yes/NO/selectively): y
\
Next adapter: NVIDIA i2c adapter 7 at 9:00.0 (i2c-5)
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 `to-be-written':
  * ISA bus, address 0x290
    Chip `ITE IT8665E Super IO Sensors' (confidence: 9)

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

Note: there is no driver for ITE IT8665E Super IO Sensors yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): ^C
Unloading i2c-dev... OK

 

When running the command 'modprobe IT87' it does detect the CPU and MB temps correctly, and recognizes two of the fans, which I can also control. So what about the other four fans?

 

When I go to the fan control settings it seems to recognize that there are indeed six fan headers:

image.png.bcb3218b91a3602600f6d134619a9731.png

 

However, if I try to detect PWM3-6 I get this error:

Quote

<br /><b>Warning</b>:  file_put_contents(): Only -1 of 3 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>43</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 3 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>46</b><br /><br /><b>Warning</b>:  file_put_contents(): Only -1 of 4 bytes written, possibly out of free disk space in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>49</b><br />/sys/devices/platform/it87.656/hwmon/hwmon1/fan1_input

 

I'm stumped.

Edited by BreakfastPurrito
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.