ASUS PRIME X670-P WiFi (No Sensor Data)

@Querzion what is the output from sensors-detect (open up a Terminal from Unraid, run "sensors-detect" and press ENTER a few times) and please post your Diagnostics.

21 hours ago, ich777 said:

@Querzion what is the output from sensors-detect (open up a Terminal from Unraid, run "sensors-detect" and press ENTER a few times) and please post your Diagnostics.

I did as you said. Added <sensors> & <sensors-detect> to the post and made a pastebin in the process, before I noticed there was a <> code feature. 
 

sensors-detect output on pastebin >> https://pastebin.com/qXStSqSR

 

Edited July 21 by Querzion
Deleted data from the answer, added it to the post.

2 hours ago, Querzion said:

sensors-detect output on pastebin

Your Diagnostics are still missing.

 

Do you know what I/O chip is on the Motherboard?

17 hours ago, ich777 said:

Your Diagnostics are still missing.

 

Do you know what I/O chip is on the Motherboard?

 

I have no idea actually. "/ 

This is basically the only information that I can get a hold of about the card. "/ 
https://dlcdnets.asus.com/pub/ASUS/mb/Socket AM5/PRIME X670-P WIFI/E20185_PRIME_X670-P_WIFI_UM_WEB.pdf?model=PRIME X670-P WIFI

 

5 hours ago, Querzion said:

I have no idea actually. "/ 

According to that picture that I found online:

 

You have a Nuvoton chip as Super I/O controller.

 

Please go to the CA App and install the Nuvoton plugin and run sensors-detect again and see if you got more output and if the sensors are listed afterwards:

1 hour ago, ich777 said:

...

Please go to the CA App and install the Nuvoton plugin and run sensors-detect again ...

 

It seems I got the same output as before, I might need to reboot the computer for it to fully work. . ?

 

root@VMC:~# sensors
corsairpsu-hid-3-8
Adapter: HID adapter
v_in:        230.00 V  
v_out +12v:   12.00 V  (crit min =  +8.41 V, crit max = +15.59 V)
v_out +5v:     5.08 V  (crit min =  +3.50 V, crit max =  +6.50 V)
v_out +3.3v:   3.33 V  (crit min =  +2.31 V, crit max =  +4.30 V)
psu fan:        0 RPM
vrm temp:     +45.2°C  (crit = +70.0°C)
case temp:    +45.0°C  (crit = +70.0°C)
power total: 220.00 W  
power +12v:  174.00 W  
power +5v:    23.00 W  
power +3.3v:  10.00 W  
curr +12v:    14.50 A  (crit max = +112.50 A)
curr +5v:      4.56 A  (crit max = +40.00 A)
curr +3.3v:    3.12 A  (crit max = +40.00 A)

nvme-pci-6500
Adapter: PCI adapter
Composite:    +30.9°C  (low  = -273.1°C, high = +69.8°C)
                       (crit = +79.8°C)
Sensor 1:     +30.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +30.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 5:     +45.9°C  (low  = -273.1°C, high = +65261.8°C)

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +56.4°C  
Tccd1:        +51.4°C  
Tccd2:        +52.1°C  

root@VMC:~# sensors-detect
# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. PRIME X670-P WIFI
# Kernel: 6.8.12-Unraid x86_64
# Processor: AMD Ryzen 9 7900X 12-Core Processor (25/97/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): 
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...                             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'...               Yes
Found unknown chip with ID 0xd802
    (logical device B has address 0x290, could be sensors)
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): 
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): 
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x28
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM96080'...             No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Nuvoton NCT7802Y'...                           No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                No
Client found at address 0x49
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 `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
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               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
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

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 1 at 0b20 (i2c-2)
Do you want to scan it? (YES/no/selectively): 

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.

 

 

I submitted something for my board (same chip I believe) a while back but no luck. We may need to wait for a new kernel but as far as I can tell the current one in unraid has the proper drivers so not sure what gives. 

On 7/23/2024 at 7:49 PM, Jclendineng said:

I submitted something for my board (same chip I believe) a while back but no luck. We may need to wait for a new kernel but as far as I can tell the current one in unraid has the proper drivers so not sure what gives. 

I always want to try out the newest hardware at times. It's my own damn fault for not thinking clearly. I could have just bought two GPU's a set of new drives, a 5950X and had a really good time, but I decided to build a whole new computer instead. "/ Stupid of me. "/ Sooner or later it's going to register everything, I just hope it's not going to be a problem hardware wise, In that case I might need to stop using unRAID for a while, which isn't really what I want to do. "/

You can ignore sensors-detect which no sensor found. Your sensors result show k10temp reading, then you can ref. below post to create drivers.conf file to make reading show in Unraid.

 

 

On 7/22/2024 at 2:45 PM, Querzion said:

Found unknown chip with ID 0xd802
    (logical device B has address 0x290, could be sensors)

https://forums.gentoo.org/viewtopic-p-8788027.html?sid=3619453445bb2d184b0f305f513539d7

You may try modprobe nct6775 force_id=0xd420 and check does superio got the reading.

 

Edited July 25 by Vr2Io

https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/commit/?h=hwmon-next&id=aee395bb190564a3fa22aa65c60812c25410e94a

Driver should be in Linux 6.5

https://github.com/lm-sensors/lm-sensors/pull/480

 

looks like there is a request for lm-sensors to be updated and its probably not going to be. Asus's new boards apparently don't use WMI so we may just not be able to use them with unraid unless they can figure out how to get that driver integrated.  

I think I fixed mine actually.

https://github.com/trulyspinach/SMCAMDProcessor/commit/673ba36183fd18a2864221a58993e08869ae3564

 

Find your chip ID here:
 

#define CHIP_NCT6796DR 0xD42A

#define CHIP_NCT6797D 0xD451

#define CHIP_NCT6798D 0xD42B

#define CHIP_NCT6799D 0xD802

 

modprobe nct6775 force_id=0xD802 is what I used

sensors now shows everything

 

touch /boot/config/modprobe.d/nct6799.conf

nano /boot/config/modprobe.d/nct6799.conf

options nct6775 force_id=0xD802 0 Edit doesn't load on startup

Edit: the modprobe.d doesn't work, does someone know the correct format? Or else we can load on startup via user scripts. 

Edited July 25 by Jclendineng