LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 10-25-2023, 12:32 AM   #1
zemerdon
LQ Newbie
 
Registered: Oct 2023
Posts: 3

Rep: Reputation: 0
lm-sensors + Asus X299 SAGE/10G


Good morning,

Little bit of trouble. I have a thermistor on the motherboard T_SENSOR header which is picking up no reading or output in lm-sensors but works in the BIOS (4104).

I also have the Asus fan expansion card (version 1) with 3 fans + 1 thermistor as well which also works in the BIOS but nothing in lm-sensors.

Is there any advice on how to add these devices, or a path to start trying to get Linux (Debian 11 kernel 6.1) to report readings or communicate with these headers/devices?

Any advice would be appreciated.
Code:
SENSORS-DETECT

# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. WS X299 SAGE/10G
# Kernel: 6.1.0-0.deb11.11-amd64 x86_64
# Processor: Intel(R) Core(TM) i9-7920X CPU @ 2.90GHz (6/85/4)
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
Code:
Module cpuid loaded successfully.
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
Code:
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 NCT6796D 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
Code:
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
Using driver `i2c-i801' for device 0000:00:1f.4: Kaby Lake (PCH)
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at 3000 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Code:
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
Next adapter: igb BB (i2c-1)
Do you want to scan it? (YES/no/selectively): yes

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

Next adapter: NVIDIA i2c adapter 6 at 68:00.0 (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes
Code:
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: NVIDIA i2c adapter 7 at 68:00.0 (i2c-7)
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 NCT6796D Super IO Sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
nct6775
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.

Unloading i2c-dev... OK
Unloading cpuid... OK

Code:
SENSORS OUTPUT

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +38.0°C  (high = +100.0°C, crit = +110.0°C)
Core 0:        +38.0°C  (high = +100.0°C, crit = +110.0°C)
Core 1:        +36.0°C  (high = +100.0°C, crit = +110.0°C)
Core 2:        +37.0°C  (high = +100.0°C, crit = +110.0°C)
Core 3:        +37.0°C  (high = +100.0°C, crit = +110.0°C)
Core 4:        +38.0°C  (high = +100.0°C, crit = +110.0°C)
Core 5:        +37.0°C  (high = +100.0°C, crit = +110.0°C)
Core 8:        +38.0°C  (high = +100.0°C, crit = +110.0°C)
Core 9:        +36.0°C  (high = +100.0°C, crit = +110.0°C)
Core 10:       +37.0°C  (high = +100.0°C, crit = +110.0°C)
Core 11:       +37.0°C  (high = +100.0°C, crit = +110.0°C)
Core 12:       +36.0°C  (high = +100.0°C, crit = +110.0°C)
Core 13:       +38.0°C  (high = +100.0°C, crit = +110.0°C)
nvme-pci-0200
Code:
Adapter: PCI adapter
Composite:    +41.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +41.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +45.9°C  (low  = -273.1°C, high = +65261.8°C)

nct6796-isa-0290
Adapter: ISA adapter
Vcore:                    1000.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:                      1000.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:                       3.38 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:                      3.34 V  (min =  +2.98 V, max =  +3.63 V)
in4:                        1.01 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                        0.00 V  (min =  +0.00 V, max =  +0.00 V)
in6:                      600.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:                       3.38 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:                       3.18 V  (min =  +2.70 V, max =  +3.63 V)
in9:                        1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                     600.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                     392.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                       1.01 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                       0.00 V  (min =  +0.00 V, max =  +0.00 V)
in14:                     496.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                     1530 RPM  (min =    0 RPM)
fan2:                      897 RPM  (min =    0 RPM)
fan3:                     2288 RPM  (min =    0 RPM)
fan4:                     2106 RPM  (min =    0 RPM)
fan5:                     1225 RPM  (min =    0 RPM)
fan6:                        0 RPM  (min =    0 RPM)
fan7:                     3199 RPM  (min =    0 RPM)
SYSTIN:                    +44.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
CPUTIN:                    +40.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                   +50.0°C    sensor = thermistor
AUXTIN1:                   +50.0°C    sensor = thermistor
AUXTIN2:                   +68.0°C    sensor = thermistor
AUXTIN3:                   +58.0°C    sensor = thermistor
PECI Agent 0:              +38.0°C  (high = +80.0°C, hyst = +75.0°C)
                                    (crit = +110.0°C)
PECI Agent 0 Calibration:  +40.5°C  
PCH_CHIP_CPU_MAX_TEMP:      +0.0°C  
PCH_CHIP_TEMP:              +0.0°C  
intrusion0:               ALARM
intrusion1:               ALARM
beep_enable:              disabled

i350bb-pci-1a00
Adapter: PCI adapter
loc1:         +50.0°C  (high = +120.0°C, crit = +110.0°C)
 
Old 10-25-2023, 12:12 PM   #2
Arnulf
Member
 
Registered: Jan 2022
Location: Hanover, Germany
Distribution: Slackware
Posts: 270

Rep: Reputation: 89
Temperatures outside of CPU, GPU and NVMe-SSDs and also fan speeds except fans on additional cards e.g. graphics cards should be measured by the "Nuvoton NCT6796D".
Unplug your additional devices (thermistor, "Asus fan expansion card") and check for changes in output of sensors command for nct6796-isa-0290.
 
Old 10-25-2023, 07:14 PM   #3
zemerdon
LQ Newbie
 
Registered: Oct 2023
Posts: 3

Original Poster
Rep: Reputation: 0
Thank you for the reply,

Unfortunately no changes moving a thermal sensor from the expander card to the motherboard header either.

I had already tried to get a differential in sensor reading by moving sensors, removing sensors, removing expander card prior to posting.

looks like the kernel isnt picking anything up? im a bit lost as everything shows up in bios fine but im just unsure how to proceed moving forward, what i would need to do to have Linux start communicating with the device.

I actually feel like its not possible.
 
Old 10-26-2023, 01:44 PM   #4
Arnulf
Member
 
Registered: Jan 2022
Location: Hanover, Germany
Distribution: Slackware
Posts: 270

Rep: Reputation: 89
Try to get information about chips used in your "Asus fan expansion card" and which bus is used for communication with mainboard BIOS.
A missing bus driver in your kernel may cause this problem.
On the other hand, an unsupported hardware monitoring chip may be used.
 
Old 10-28-2023, 04:18 PM   #5
zemerdon
LQ Newbie
 
Registered: Oct 2023
Posts: 3

Original Poster
Rep: Reputation: 0
Would you suggest physically inspecting the card for the chipset model and looking that up then gathering information so see if that particular chipset is supported in Linux?

The expansion card is connected via 4 pin header cable and is it a specifically an 'Asus expansion header' on the mother board for this card only.

I feel like this may be unsupported because of this.

What do you think ?
 
Old 10-28-2023, 06:11 PM   #6
Arnulf
Member
 
Registered: Jan 2022
Location: Hanover, Germany
Distribution: Slackware
Posts: 270

Rep: Reputation: 89
Quote:
Originally Posted by zemerdon View Post
Would you suggest physically inspecting the card for the chipset model and looking that up then gathering information so see if that particular chipset is supported in Linux?
Yes.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] ASUS Prime X299-Deluxe II Motherboard Compatible with Linux? dcsst28 Linux - Hardware 5 07-17-2019 05:23 PM
10G nics not operating at 10G, why? szboardstretcher Linux - Networking 6 06-25-2014 09:42 PM
LXer: McAfee's new security journal: Sage is not sage LXer Syndicated Linux News 0 07-17-2006 12:21 PM
GNOME Sensors Applet says NO SENSORS FOUND! badgerbox76 Linux - Newbie 2 12-24-2005 11:58 AM
lm sensors, no sensors found N_A_J_M Linux - General 3 01-22-2003 05:09 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 05:27 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration