Dynamix - System Temp


Recommended Posts

@bonienl any way to have the Nuvoton NCT6797D present on a lot of X570 motherboards of Ryzen 3000-series ? Detect doesn’t detect it, but the driver exist. 

 

Ok, I downloaded the latest lm-sensors from GitHub and was able to use the most recent « sensors-detect ».  Here is what it found for my board (ASUS WS Pro X570-ACE).  I wonder how can i load that driver ?? :

 

Found `Nuvoton NCT6796D Super IO Sensors'                   Success!
    (address 0x290, driver `nct6775')


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

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

Attached is the Syslog.  I can see the driver trying to load, but I think it give an error just after (?) 

 

 

tower-syslog-20190718-0009.zip

Edited by Pducharme
Link to comment
On 6/6/2019 at 7:11 PM, p0xus said:

Im having the same problem as some others on this forum. I have a Supermicro X10DAL-i with dual Xeon E5-2678s and when I say detect drivers, it says "coretemp nct7904", but there are no sensors in the list. I think I remember seeing them right before I saved which sensor was which, but the lists have been blank ever since. 

I am new to UnRAID, but will do my best to send any diagnostic info you want. Ive tried reinstalling the plugin, but no difference.

 

If not this plugin, is there any other way to see CPU temps in unraid? It concerns me greatly that I have no idea how hot they are. I havn't wanted to stress them without knowing.

 

I'm having this same problem. Just happened 20 minutes ago or so.

 

 

filesvr-diagnostics-20190719-1020.zip

Link to comment
  • 2 months later...
On 7/19/2019 at 3:22 AM, GHunter said:

 

I'm having this same problem. Just happened 20 minutes ago or so.

 

 

filesvr-diagnostics-20190719-1020.zip 127.29 kB · 0 downloads

Same here. Supermicro running unraid 6.7.2 getting coretemp nct7904, and when I first installed last night I saw options in the three drop downs. I selected them and then hit apply and done yet it didn't apply to the footer. Then I refreshed the page and the settings disappeared. I tried uninstalling and reinstalling and still it detects the driver but I cant get any sensors listed no matter what process I use or hitting rescan. 

Link to comment

The lm-sensors version of the unraid installation is 3.5.

root@Tower:~# sensors -v
sensors version 3.5.0 with libsensors version 3.5.0

lm-sensors 3.6 version support some motherboards sensors such as z370 ,x570 with Nuvoton NCT6793D Super IO Sensors.The driver ofNuvoton NCT6793D Super IO Sensors is nct6775.

 

This is lm-sensors 3.5 detected result:

Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0xd121
    (logical device B has address 0x290, could be sensors)
Probing for Super-I/O at 0x4e/0x4f

This is 3.6 version:

Found `Nuvoton NCT6793D Super IO Sensors'    Success! 

(address 0x290, driver `nct6775') Probing for Super-I/O at 0x4e/0x4f

So we need update the latest lm-sensors version

 

My configuration information:

# sensors-detect version 3.6.0+git

# Board: ASUSTeK COMPUTER INC. TUF Z370-PLUS GAMING

# Kernel: 5.3.6-Unraid x86_64

# Processor: Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz (6/158/10)

#Unraid version: 6.8.0 rc3

Edited by Young_Max
  • Like 1
Link to comment
  • 4 weeks later...

Hi all

 

Have a problem with the plugin in combination with the Ryzen 2700X and a AsRock X470 Taichi Ultimate (bios P3.30). 

The temperature displayed do not make sense as most of them are in the negative area. Temperatures I have found in the motherboard seem to be correct. Has someone any experience and hopefully a solution for that issue?

1.png.6ebf47a0c03f395eed066dc2bde247b2.png

 

Has someone an idea where I could start troubleshooting or at least gather more information?

 

Thanks in advance!

Georg

Link to comment

Sorry i did not get that you have answered. 

 

On 11/16/2019 at 6:42 PM, itimpi said:

What makes you think those are negative temperatures?    Isn’t it just a case of a dash being used as a separator?

Could be but then the separator is not always transferred:
image.png.cd3660d7eb6e5ebc72592d03f35c8618.png

(I have set the CPU as cpu temp and the smbus master as MB temp)

 

Also the bios states different temperatures.

Even if I read it wrong it does not move at all. From right after the start to continues loads of 50% it always says -62.5 C. 

 

Also because of: 

image.png.9e42e976f586c394b579d4a172dfb5ee.png

 

I understand that maybe not all the sensors are connected/ used but the CPU one?

 

In the system is also an Avago SAS 9300-i16 card. I was not able to find out if it has a temp sensor or how it is called. 

Does someone know something?

 

Thanks a lot,

Georg

Link to comment
  • 2 weeks later...
2 hours ago, atoaster said:

@Georg did you ever get this figured out? Mine is the exact same way with -62.50 temp on my 3700x

Unfortunately not. I don't even know where to start...
From what I have read in forums and all, it gives me the impression that it appears  if Linux (unraid) and a X version of a Ryzen processor come together. Please keep me up do to date in case you find a solution.

It kinda makes me worried whether the CPU gets sufficient cooling. As the MB reads them correct, I guess the fan is not affected.

Link to comment
  • 1 month later...
  • 4 weeks later...

Hello, today I upgraded my MOBO to  PRIME X470-PRO. with the latest BIOS update, can't get all core temp and fans speed only CPU and MB with this driver k10temp, also Fan Auto Control didn't detect PWM fan. I added diagnostics also, I have read that there is no driver yet for IT8665E. I'd appreciate it if anyone can help. Thanks

 

here is the output of sensors-detect

 

root@Tower:~# sensors-detect --auto
# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. PRIME X470-PRO
# Kernel: 4.19.98-Unraid x86_64
# Processor: AMD Ryzen 5 1600 Six-Core Processor (23/1/1)

Running in automatic mode, default answers to all questions
are assumed.

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

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


Now follows a summary of the probes I have just done.

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

Driver `to-be-written':
  * ISA bus, address 0x290
    Chip `ITE IT8665E Super IO 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.

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK

 

 

 

BBBB.png.0c22564e3a589f5cd79de6a4b901d253.png

 

 

i have tried this as a way around modprobe it87 force_id=0x8620

 

root@Tower:~# modprobe it87 force_id=0x8620
modprobe: ERROR: could not insert 'it87': Device or resource busy

 

and the logs show

 

Tower kernel: it87: Found IT8620E chip at 0x290, revision 6
Tower kernel: it87: Beeping is supported
Tower kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.HWM) (20180810/utaddress-204)
Tower kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

 

 

 

 

 

 

 

tower-diagnostics-20200210-2133.zip

Link to comment

I've got a question to which I think that answer is a faulty sensor but thought I'd post here to see if anyone has other suggestions.

 

I followed SpaceInvader One's guide for installing everything and this is what I'm seeing. Which ones should I be selecting for the CPU and motherboard temperatures? The CPU ones are close enough that it seems I should just be using "coretemp - Package id 0," right? The other values for the values for the motherboard temperature is where I'm more confused.

 

I used to think that SYSTIN was the motherboard temperature but it's showing as 118 degrees.  That can't be right.  Pretty sure my rig wouldn't be running for a long as it has it's at 118 degrees.  

 

Also AUXTIN is my power supply right? There's something weird going on there right?  There are 3 values over 100 and AUXTIN0 at 31 degrees.

 

SysTmp.PNG.bcc946abedaaed530a4c7987f4485801.PNG

 

This may or not be related but of my three fan headers (1 cpu & 2 case), one of the fans is highly erratic. The CPU fan 1 governed but the CPU temp, and the other two fans are governed but the motherboard temp. The profiles (quiet, perfomance,...) are the same for all of them. One of the motherboard fans runs pretty steady at ~950rpm, but the other ranges anywhere from 1,400rpm  to 70,000+rpm (I did not mistype this number).  

 

Any help would be greatly appreciated.

 

My build on PCPP.

Unraid v6.8.2

Dynamix System Temperature v2019.11.03

 

 

 

 

 

Link to comment
On 10/18/2019 at 4:19 PM, gtosnipey said:

Same here. Supermicro running unraid 6.7.2 getting coretemp nct7904, and when I first installed last night I saw options in the three drop downs. I selected them and then hit apply and done yet it didn't apply to the footer. Then I refreshed the page and the settings disappeared. I tried uninstalling and reinstalling and still it detects the driver but I cant get any sensors listed no matter what process I use or hitting rescan. 

Me too! No luck at all. I'm running Nvidia Unraid version 6.8.2. I'm adding my Diagnostic as well. Maybe this will help?

plexunraid-diagnostics-20200215-1314.zip

Link to comment
  • 1 month later...

I wonder if anyone managed to get module nct6775 working for NCT6791D chip? (this chip is what the sensors-detect output showing)

I did `modprobe nct6775` and `modprobe nct6775 0x290` at the command line to no effect.

The other command `modprobe coretemp` did result in sensors reporting the CPU temperature (only).
 

Link to comment
  • 2 weeks later...

My ASRock X570 Taichi worked fine with this app. However, when I upgraded to the ASRock X570 Creator it quit working. The x570 creator detects the k10temp nct6683 drivers (which is different from the taichi). I save and load the new detected drivers, and save again only to see "not used" in the three temp slots. Any ideas to get the creator to work with nct6683 drivers?

Link to comment

I had the same issues some of you guys are having that is it was working perfectly fine then I messed around with it and my drop down list became empty.

 

I finally got it fixed by deleting sensors.conf in /etc/sensors.d/ and then reinstalling dynamix. Then I ran into another problem where coretemp wasn't showing up in the list and I unloaded and reloaded the driver and that seem to have done the trick. 

Link to comment

Hi I have a Supermicro - X7SB4/E, (Unraid version 6.8.3) after installing the plugin and loading the drivers (coretemp w83627hf w83793) the pull down's where populated.

After selecting the appropriate sensors and applying them the pull down's where empty and unable to detect them anymore.

this can be resolved by removing /etc/sensors.d/ensors.config and rescanning, but i'm still not able to save the sensors.

 

unraid error log says:

Apr  8 04:18:28 Tower kernel: w83793 0-002f: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
Apr  8 04:18:28 Tower kernel: w83793 0-002f: Registered watchdog chardev major 10, minor: 130

Is there a fix for this ?

Edited by Jos Visser
added some extra essential information
Link to comment

Howdy

 

Think I have things working but I thought there there would be a screen where I could see all my server temps and voltages

 

Might have missed something not sure

 

Currently CPU1, MB temps and fans are on GUI.  In drop downs of plugin most of the stuff I want is in there with lables I created

 

Thanks

Link to comment

when I had the MSI x570 Gaming board the tricks to get the sensors to work.. worked.. but when I switched  to the Asus TUF Gaming X570  the trick  has stopped working and I no longer get sensors  

 

running  sensors-detect --auto    shows I have sensors

when I run  modprobe k10temp 

                modprobe nct6775

likt it tells me to..  and when I run sensors

tells me I have no sensors  so I guessing it cant read asus  boards   😞

 

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.