`sensors-detect` finds no sensors 😕

bassamanator · January 31, 2025, 9:45pm

Built a new computer:

Operating System: EndeavourOS 
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.10-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 31.0 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series
Motherboard: ASUS Prime X670E-PRO WiFi

Ran sudo sensors-detect, selected yes on everything, but no sensors are found. The motherboard has the latest non-beta bios, and please note that the board was released roughly 2 years ago.

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

Unfortunately, the linked site is 404.

Not sure how to fix.

Thanks!

thefrog · January 31, 2025, 10:44pm

what happens if you just type
sensors

bassamanator · January 31, 2025, 11:37pm

Interesting. It actually lists some sensors:

mt7921_phy0-pci-0b00
Adapter: PCI adapter
temp1:        +46.0°C

spd5118-i2c-1-51
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1:        +43.5°C  (low  =  +0.0°C, high = +55.0°C)
                       (crit low =  +0.0°C, crit = +85.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +56.1°C
Tccd1:        +42.4°C

amdgpu-pci-0100
Adapter: PCI adapter
vddgfx:      950.00 mV
fan1:         804 RPM  (min =    0 RPM, max = 3200 RPM)
edge:         +50.0°C  (crit = +94.0°C, hyst = -273.1°C)
PPT:          44.03 W  (cap = 175.00 W)

spd5118-i2c-1-53
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1:        +44.2°C  (low  =  +0.0°C, high = +55.0°C)
                       (crit low =  +0.0°C, crit = +85.0°C)

nvme-pci-0200
Adapter: PCI adapter
Composite:    +49.9°C  (low  =  -0.1°C, high = +82.8°C)
                       (crit = +89.8°C)

Looks like a very incomplete lists, however.

bassamanator · January 31, 2025, 11:56pm

I believe this is relevant for me.

I ran sudo modprobe nct6775 acpi_enforce_resources=lax but that doesn’t appear to have done the trick, but maybe I need a reboot.

bassamanator · February 1, 2025, 12:04am

It seems that i need to:

sudo nano /etc/default/grub
# add/replace `GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_enforce_resources=lax"`

sudo grub-mkconfig -o /boot/grub/grub.cfg

Omig · February 1, 2025, 12:06am

You can read this about kernel modules https://wiki.archlinux.org/title/Kernel_module

Stephane · February 1, 2025, 10:25am

can you report , do only enter on for sensors-detect

inxi -Mxx
sudo sensors-detect

is it a kvm install or virtual install ?

r0ckhopper · February 1, 2025, 12:21pm

I can’t see your hard drive temperatures in there. What works for me is:

sudo nano /etc/modules-load.d/drivetemp.conf

and adding tthe following, before saving, closing, and rebooting.

# Load drivetemp at boot
drivetemp

bassamanator · February 1, 2025, 4:57pm

Here’s what I ended up doing based on this thread:

sudo modprobe nct6775 force_id=0xd420, followed by sudo sensors-detect in the same session.
Write sensors to file. Doing this, I was able to detect most of my sensors (1 fan header is missing, for example).
Create /etc/modules-load.d/nct6775.conf with content nct6775. The force_id=0xd420 option is not needed interestingly enough.

Now when I reboot, my sensors show up in CoolerControl (I’m also able to control the detected fans, and RGB headers, etc.) and via sensors. Interestingly though, when I run sensors-detect again, it fails as before, however, the sensors are still being read.

What’s even more interesting though is that even before having done anything, the output from modprobe -c | grep nct6775 was finding the nct6775 module, but I guess I’m too much of a n00b to realize there’s a big difference between nct6775 and nct6775_i2c, for example?

` modprobe -c | grep nct6775` output

alias i2c:nct6106 nct6775_i2c alias i2c:nct6116 nct6775_i2c alias i2c:nct6775 nct6775_i2c alias i2c:nct6776 nct6775_i2c alias i2c:nct6779 nct6775_i2c alias i2c:nct6791 nct6775_i2c alias i2c:nct6792 nct6775_i2c alias i2c:nct6793 nct6775_i2c alias i2c:nct6795 nct6775_i2c alias i2c:nct6796 nct6775_i2c alias i2c:nct6797 nct6775_i2c alias i2c:nct6798 nct6775_i2c alias i2c:nct6799 nct6775_i2c alias of:N*T*Cnuvoton,nct6106 nct6775_i2c alias of:N*T*Cnuvoton,nct6106C* nct6775_i2c alias of:N*T*Cnuvoton,nct6116 nct6775_i2c alias of:N*T*Cnuvoton,nct6116C* nct6775_i2c alias of:N*T*Cnuvoton,nct6775 nct6775_i2c alias of:N*T*Cnuvoton,nct6775C* nct6775_i2c alias of:N*T*Cnuvoton,nct6776 nct6775_i2c alias of:N*T*Cnuvoton,nct6776C* nct6775_i2c alias of:N*T*Cnuvoton,nct6779 nct6775_i2c alias of:N*T*Cnuvoton,nct6779C* nct6775_i2c alias of:N*T*Cnuvoton,nct6791 nct6775_i2c alias of:N*T*Cnuvoton,nct6791C* nct6775_i2c alias of:N*T*Cnuvoton,nct6792 nct6775_i2c alias of:N*T*Cnuvoton,nct6792C* nct6775_i2c alias of:N*T*Cnuvoton,nct6793 nct6775_i2c alias of:N*T*Cnuvoton,nct6793C* nct6775_i2c alias of:N*T*Cnuvoton,nct6795 nct6775_i2c alias of:N*T*Cnuvoton,nct6795C* nct6775_i2c alias of:N*T*Cnuvoton,nct6796 nct6775_i2c alias of:N*T*Cnuvoton,nct6796C* nct6775_i2c alias of:N*T*Cnuvoton,nct6797 nct6775_i2c alias of:N*T*Cnuvoton,nct6797C* nct6775_i2c alias of:N*T*Cnuvoton,nct6798 nct6775_i2c alias of:N*T*Cnuvoton,nct6798C* nct6775_i2c alias of:N*T*Cnuvoton,nct6799 nct6775_i2c alias of:N*T*Cnuvoton,nct6799C* nct6775_i2c alias symbol:nct6775_probe nct6775_core alias symbol:nct6775_reg_is_word_sized nct6775_core alias symbol:nct6775_show_alarm nct6775_core alias symbol:nct6775_show_beep nct6775_core alias symbol:nct6775_store_beep nct6775_core alias symbol:nct6775_update_device nct6775_core

I’m going to undo everything and start from scratch in a bit just to see that I haven’t made any mistakes in the steps.

bassamanator · February 1, 2025, 5:02pm

Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME X670E-PRO WIFI v: Rev 1.xx
    serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 3067
    date: 12/10/2024

# sensors-detect version 3.6.0+git
# Board: ASUSTeK COMPUTER INC. PRIME X670E-PRO WIFI
# Kernel: 6.12.10-arch1-1 x86_64
# Processor: AMD Ryzen 5 7600X 6-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
AMD Family 19h 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'...                                      Yes
Found unknown chip with ID 0x8883
    (logical device 4 has address 0x290, could be sensors)

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: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-1)
Do you want to scan it? (YES/no/selectively):
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
Handled by driver `spd5118' (already loaded), chip type `spd5118'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x53
Handled by driver `spd5118' (already loaded), chip type `spd5118'
    (note: this is probably NOT a sensor chip!)

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

Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-3)
Do you want to scan it? (YES/no/selectively):

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

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

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

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

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

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

Next adapter: AMDGPU DM aux hw bus 1 (i2c-10)
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.

Please note that this output is from a session where I’m made the changes mentioned in my previous post.

bassamanator · February 14, 2025, 6:39pm

Update

What I’ve learned

I have to start without having made any changes to the kernel modules.

sudo modprobe nct6775 id=0xd420
sudo sensors-detect and save the found sensors.
sudo nano /etc/modules-load.d/nct6775.conf with content nct6775.

Upon reboot:

Running sudo sensors-detect will not find any sensors.
However, running sensors will accurately display sensor data.

I’ve tried passing the option id=0xd420 via

sudo nano /etc/modprobe.d/nct6775.conf, content options nct6775 id=0xd420.
sudo nano /etc/default/grub and editing GRUB_CMDLINE_LINUX_DEFAULT="quiet nct6775.id=0xd420" followed by sudo grub-mkconfig....

but I don’t think either method works because sudo sensors-detect doesn’t find sensors.

My question now is

Am I passing the option correctly?

Thanks!

sfflatwhite · March 1, 2025, 3:18am

Hi! (new guy here, intend to stay… :))

Ill be sorting these out soon tonight too… Will start a new thread in a bit if I cannot solve it on my own, but this thread seems super helpful, as I’m looking to solve for my mobo (x870 Asrock Pro Rs).

Did you manage to solve your issue?

bassamanator · March 1, 2025, 6:49am

sensors does display data, but running sensors-detect does not find any, which doesn’t seem right to me.

Having said that, I am getting sensor data and am able to control fans and rgb via coolercontrol and openrgb.

sfflatwhite · March 1, 2025, 4:25pm

Thanx! This thread is a good starting point for me. I just finished troubleshooting and making good the CoolerControl to work. Due to our different mobo, I just need to make slight tweaks. And to make it permanent (for reboots/restarts), I need only need to add nct6775 to /etc/modules-load.d/nct6775.conf. I didn’t need to edit the grub file.