我试图检测传感器，但我不能。首先我安装了lm-sensors。

然后我运行了检测传感器：

# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: HPE ProLiant DL360 Gen10
# Kernel: 4.15.0-52-generic x86_64
# Processor: Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz (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):
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 15h power sensors...                             No
AMD Family 16h power 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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0x0401
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):
Found `IPMI BMC KCS' at 0xca2...                            Success!
    (confidence 8, driver `to-be-written')

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):
Sorry, no supported PCI bus adapters found.


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

Driver `to-be-written':
  * ISA bus, address 0xca2
    Chip `IPMI BMC KCS' (confidence: 8)

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Note: there is no driver for IPMI BMC KCS yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----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 cpuid... OK

但是当我启动 kmod 时，会出现与 coretemp 模块相关的错误：

sudo /etc/init.d/kmod start
[....] Starting kmod (via systemctl): kmod.serviceJob for systemd-modules-load.service failed because the control process exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details.
 failed!

sudo systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-11-10 15:29:50 CET; 41s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 2362 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 2362 (code=exited, status=1/FAILURE)

Nov 10 15:29:50 srvzym01 systemd[1]: Starting Load Kernel Modules...
Nov 10 15:29:50 srvzym01 systemd-modules-load[2362]: Failed to find module 'coretemp'
Nov 10 15:29:50 srvzym01 systemd-modules-load[2362]: Failed to find module 'coretemp'
Nov 10 15:29:50 srvzym01 systemd-modules-load[2362]: Failed to find module 'coretemp'
Nov 10 15:29:50 srvzym01 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Nov 10 15:29:50 srvzym01 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Nov 10 15:29:50 srvzym01 systemd[1]: Failed to start Load Kernel Modules.

我试图加载 coretemp，但我找不到它：

modprobe coretemp
modprobe: FATAL: Module coretemp not found in directory /lib/modules/4.15.0-52-generic

我找到了一些 coretemp 文件，但我不确定它是否与这些有关：

/usr/src/linux-headers-4.15.0-52-generic/include/config/sensors/coretemp.h

也许我必须安装一些东西，因为我没有看到任何与 coretemp 相关的东西

dpkg -L linux-image-4.15.0-52-generic | grep coretemp.ko

我不知道这些是否可以提供更多帮助，但我会提供有关 cpu 的更多信息：

cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 85
model name      : Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz
stepping        : 4
microcode       : 0x200005e
cpu MHz         : 1700.007
cache size      : 8448 KB
physical id     : 0
siblings        : 6
core id         : 0
cpu cores       : 6
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm arat pln pts pku ospke md_clear flush_l1d
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds
bogomips        : 3400.00
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 85
model name      : Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz
stepping        : 4
microcode       : 0x200005e
cpu MHz         : 1700.022
cache size      : 8448 KB
physical id     : 0
siblings        : 6
core id         : 2
cpu cores       : 6
apicid          : 4
initial apicid  : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm arat pln pts pku ospke md_clear flush_l1d
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds
bogomips        : 3400.00
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor       : 2
vendor_id       : GenuineIntel
cpu family      : 6
model           : 85
model name      : Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz
stepping        : 4
microcode       : 0x200005e
cpu MHz         : 1699.999
cache size      : 8448 KB
physical id     : 0
siblings        : 6
core id         : 4
cpu cores       : 6
apicid          : 8
initial apicid  : 8
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm arat pln pts pku ospke md_clear flush_l1d
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds
bogomips        : 3400.00
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor       : 3
vendor_id       : GenuineIntel
cpu family      : 6
model           : 85
model name      : Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz
stepping        : 4
microcode       : 0x200005e
cpu MHz         : 1699.999
cache size      : 8448 KB
physical id     : 0
siblings        : 6
core id         : 1
cpu cores       : 6
apicid          : 2
initial apicid  : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm arat pln pts pku ospke md_clear flush_l1d
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds
bogomips        : 3400.00
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor       : 4
vendor_id       : GenuineIntel
cpu family      : 6
model           : 85
model name      : Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz
stepping        : 4
microcode       : 0x200005e
cpu MHz         : 1700.018
cache size      : 8448 KB
physical id     : 0
siblings        : 6
core id         : 3
cpu cores       : 6
apicid          : 6
initial apicid  : 6
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm arat pln pts pku ospke md_clear flush_l1d
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds
bogomips        : 3400.00
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

processor       : 5
vendor_id       : GenuineIntel
cpu family      : 6
model           : 85
model name      : Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz
stepping        : 4
microcode       : 0x200005e
cpu MHz         : 1700.014
cache size      : 8448 KB
physical id     : 0
siblings        : 6
core id         : 5
cpu cores       : 6
apicid          : 10
initial apicid  : 10
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm arat pln pts pku ospke md_clear flush_l1d
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds
bogomips        : 3400.00
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

如果有人可以提供帮助，我正在尝试获取 cpu 的温度。

我也尝试过使用 hardinfo，但对传感器没有结果：

hardinfo -rma devices.so
Sensors
-------

-Sensors-

非常感谢你，伯塔

我对命令如何sensors工作感到有些困惑？

我的 CPU 型号是Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz

当我打开笔记本电脑时，它显示我的平均温度为 50 摄氏度，如果我在 Android Studio 中构建一个项目，它会立即升高到 80+，而当构建完成时它又会立即下降到 50？怎么可能在一秒钟之内如此迅速地上升和下降温度？

它是显示准确的温度还是根据正在运行的进程进行猜测？

是否有终端命令以简单的方式在单个屏幕中显示使用的内存、温度度和 GPU 使用的摘要？

我想在终端中以使用内存（而不是交换等）、GPU 使用（百分比）和温度度的摘要方式向我提供信息 - CPU 有多热？

现在，我必须使用三个不同的终端命令：

watch free -m    # For Memory use
watch sensors    # For Temperature
watch ndivia-smi # For GPU use

有没有办法在一个屏幕上显示这些信息？这些命令会产生很多人可能不需要的信息。

第一行可能显示内存使用情况。第二行可能显示 GPU 使用情况。第三行可能显示温度。

我想从free -m“可用”。例如，我想从nvidia-smi“Volatile GPU-Util”和sensors所有温度百分比中显示它们的限制（从那个到那个）

Available memory    5500000          

Volatile GPU-Util  20% 

CPUtemp1           40oC
Fantemp1           41oC
FanTemp2           42oC
etc... 

那可能吗？

示例输出：

free -m输出

$ free -m
              total        used        free      shared  buff/cache   available
Mem:           7815        1938        3548         188        2328        5391
Swap:          2047          57        1990

nvidia-smi输出

$ nvidia-smi
Fri Jul 31 18:35:45 2020       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 390.138                Driver Version: 390.138                   |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GT 1030     Off  | 00000000:01:00.0  On |                  N/A |
| 32%   44C    P8    N/A /  30W |    220MiB /  1998MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
    +-----------------------------------------------------------------------------+
    | Processes:                                                       GPU Memory |
    |  GPU       PID   Type   Process name                             Usage      |
    |=============================================================================|
    |    0      1770      G   /usr/lib/xorg/Xorg                            82MiB |
    |    0      8182      G   /usr/bin/krunner                               6MiB |
    |    0      8184      G   /usr/bin/plasmashell                          55MiB |
    |    0     26370      G   ...AAAAAAAAAAAACAAAAAAAAAA= --shared-files    74MiB |
    +-----------------------------------------------------------------------------+

sensors输出

$ sensors
it8620-isa-0a30
Adapter: ISA adapter
in0:          +0.01 V  (min =  +0.00 V, max =  +3.06 V)  ALARM
in1:          +2.05 V  (min =  +0.00 V, max =  +3.06 V)
in2:          +2.00 V  (min =  +0.00 V, max =  +3.06 V)
in3:          +2.02 V  (min =  +0.00 V, max =  +3.06 V)
in4:          +0.01 V  (min =  +0.00 V, max =  +3.06 V)
in5:          +1.74 V  (min =  +0.00 V, max =  +3.06 V)
in6:          +1.50 V  (min =  +0.00 V, max =  +3.06 V)
3VSB:         +3.38 V  (min =  +0.00 V, max =  +6.12 V)
Vbat:         +3.05 V  
fan1:        2986 RPM  (min =    0 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
temp1:        +47.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:       -128.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = disabled
temp3:        +35.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = Intel PECI
temp4:        +45.0°C  
temp5:        +42.0°C  
temp6:        +45.0°C  
intrusion0:  ALARM

acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8°C  (crit = +97.0°C)
temp2:        +29.8°C  (crit = +97.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +45.0°C  (high = +86.0°C, crit = +92.0°C)
Core 0:        +43.0°C  (high = +86.0°C, crit = +92.0°C)
Core 1:        +44.0°C  (high = +86.0°C, crit = +92.0°C)
Core 2:        +42.0°C  (high = +86.0°C, crit = +92.0°C)
Core 3:        +40.0°C  (high = +86.0°C, crit = +92.0°C)

我安装lm-senosrs并运行sudo sensors-detect. 这是我得到的：

# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Gigabyte Technology Co., Ltd. Z390 GAMING X [Default string]
# Board: Gigabyte Technology Co., Ltd. Z390 GAMING X-CF
# Kernel: 5.3.0-42-generic x86_64
# Processor: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (6/158/12)

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
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 15h power sensors...                             No
AMD Family 16h power 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 0x8688
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:a323 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

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

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

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

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

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

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

Next adapter: NVIDIA i2c adapter 9 at 1:00.0 (i2c-6)
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)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----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 cpuid... OK

当我跑步时，sensors我得到：

No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

我试图重新启动，但它没有帮助。跑步/etc/init.d/kmod start也无济于事。

我试过psensors了，但似乎看不到 CPU 核心温度。Python我还尝试使用名为的库读取温度，psutil但它也看不到 CPU。

>>> import psutil
>>> psutil.sensors_temperatures()
{'acpitz': [shwtemp(label='', current=16.8, high=18.8, critical=18.8), shwtemp(label='', current=27.8, high=119.0, critical=119.0)]}

我还尝试注释掉blacklist i2c_i801并/etc/modprobe.d/blacklist.conf重新启动，但没有任何好处。

我不确定使用包sensors提供的命令探索的检测到的传感器列表。lm-sensors

正如这个包的wiki所说：

lm_sensors（Linux 监控传感器）是一个免费的开源应用程序，提供用于监控温度、电压和风扇的工具和驱动程序。

我有点怀疑：

• 它是否仅限于/仅限于属于计算机的所有内部传感器，或者它也可以检测连接到计算机的外部传感器（如接近传感器、温度、湿度等）？

我已经阅读了手册man sensors，sensors --help但没有找到明确的解释。

我想读取我的 ryzen 2600 的 CPU 温度值。这个 askubuntu回答说“只是加载it87”。但是我该如何it87安装呢？我正在运行主线5.0.0-36-generic，所以我希望内核模块在某处可用，因为 18.04.1 默认情况下应该有它并与 kernel 打包4.15。

github repo对我来说是一个死链接。所以我不能只编译它并手动加载它。

更新

我的主板是 x470 芯片组华硕 ROG Strix x470-F 游戏。它有一个 IT8665E。

我已经it87安装在/lib/modules/$(uname -r)/kernel/drivers/hwmon/it87.ko. 当我使用加载它时

sudo modprobe it87

结果：

modprobe：错误：无法插入“it87”：没有这样的设备

lm-sensors结果：

Trying family `ITE'...                                      Yes
Found unknown chip with ID 0x8665
    (logical device 4 has address 0x290, could be sensors)

并迫使问题导致：

sudo modprobe --verbose it87 force_id=0x8665
insmod /lib/modules/5.0.0-36-generic/kernel/drivers/hwmon/it87.ko force_id=0x8665
modprobe: ERROR: could not insert 'it87': No such device

我想获得 AMD Ryzen 3900x 的 CPU 温度/有趣的速度监视器。

在这个问题中我发现，我需要激活 it87 模块才能使用 如何在 Ubuntu 18.04 上监控 Ryzen 温度？

但后来我尝试这样做，我得到错误：

$ sudo modprobe it87
modprobe: ERROR: could not insert 'it87': No such device

如何设置这个？ubuntu 19.10 版，linux 5.3，lsmod 输出：

$ lsmod
Module                  Size  Used by
snd_usb_audio         241664  2
snd_usbmidi_lib        36864  1 snd_usb_audio
btrfs                1257472  0
xor                    24576  1 btrfs
zstd_compress         167936  1 btrfs
raid6_pq              114688  1 btrfs
ufs                    81920  0
qnx4                   16384  0
hfsplus               110592  0
hfs                    61440  0
minix                  36864  0
ntfs                  106496  0
msdos                  20480  0
jfs                   188416  0
xfs                  1273856  0
libcrc32c              16384  2 btrfs,xfs
cpuid                  16384  0
edac_mce_amd           32768  0
snd_hda_codec_hdmi     61440  1
nvidia_uvm            913408  0
kvm                   643072  0
nvidia_drm             49152  8
irqbypass              16384  1 kvm
nvidia_modeset       1122304  15 nvidia_drm
nls_iso8859_1          16384  1
nvidia              19517440  744 nvidia_uvm,nvidia_modeset
snd_hda_codec_realtek   114688  1
snd_hda_codec_generic    81920  1 snd_hda_codec_realtek
ledtrig_audio          16384  2 snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_intel          49152  6
snd_hda_codec         131072  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core           90112  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_ctxfi             114688  4
snd_hwdep              20480  2 snd_usb_audio,snd_hda_codec
snd_pcm               106496  6 snd_ctxfi,snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core
crct10dif_pclmul       16384  1
snd_seq_midi           20480  0
crc32_pclmul           16384  0
snd_seq_midi_event     16384  1 snd_seq_midi
ghash_clmulni_intel    16384  0
snd_rawmidi            36864  2 snd_seq_midi,snd_usbmidi_lib
uvcvideo               98304  0
input_leds             16384  0
videobuf2_vmalloc      20480  1 uvcvideo
videobuf2_memops       20480  1 videobuf2_vmalloc
videobuf2_v4l2         24576  1 uvcvideo
videobuf2_common       53248  2 videobuf2_v4l2,uvcvideo
aesni_intel           372736  0
drm_kms_helper        184320  1 nvidia_drm
snd_seq                69632  2 snd_seq_midi,snd_seq_midi_event
videodev              208896  3 videobuf2_v4l2,uvcvideo,videobuf2_common
aes_x86_64             20480  1 aesni_intel
crypto_simd            16384  1 aesni_intel
snd_seq_device         16384  3 snd_seq,snd_seq_midi,snd_rawmidi
wmi_bmof               16384  0
cryptd                 24576  2 crypto_simd,ghash_clmulni_intel
mc                     53248  5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common
glue_helper            16384  1 aesni_intel
snd_timer              36864  2 snd_seq,snd_pcm
drm                   491520  11 drm_kms_helper,nvidia_drm
ipmi_devintf           20480  0
ipmi_msghandler       102400  2 ipmi_devintf,nvidia
fb_sys_fops            16384  1 drm_kms_helper
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
snd                    86016  38 snd_hda_codec_generic,snd_ctxfi,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi
soundcore              16384  1 snd
ccp                    94208  0
mac_hid                16384  0
sch_fq_codel           20480  2
parport_pc             40960  0
ppdev                  24576  0
lp                     20480  0
parport                53248  3 parport_pc,lp,ppdev
ip_tables              32768  0
x_tables               40960  1 ip_tables
autofs4                45056  2
hid_generic            16384  0
usbhid                 57344  0
hid                   126976  2 usbhid,hid_generic
i2c_piix4              28672  0
ahci                   40960  6
libahci                32768  1 ahci
r8169                  81920  0
realtek                20480  1
wmi                    32768  1 wmi_bmof

我有一台双启动的华硕 TP301UJ 笔记本电脑，我的风扇一直很响。我正在尝试在 Ubuntu 中配置我的风扇速度（我在 Windows 10 中很容易做到），但我遇到了问题。

这是我所做的：

1. 我安装了lm-sensors、psensor和fancontrol。psensor运行良好，并读取了风扇速度和所有温度。

2. Ransudo sensors-detect只说我需要将coretemp添加到/etc/modules. coretemp已经在模块中，所以我什么也没做。

3. 重新启动。跑sudo pwmconfig，它输出：

   找到以下设备：
   hwmon0 is acpitz
   hwmon1 is coretemp
   hwmon2 is asus

   找到以下 PWM 控件：
   hwmon2/pwm1 当前值：0

   hwmon2/pwm1 当前设置为自动速度控制。
   一般来说，自动模式比手动模式更受欢迎，因为它更有效并且反应更快。您确定要将此输出设置为手动控制吗？(n)

4. 输入“y”，输出为：

   给粉丝一些时间来达到全速...

   发现以下风扇传感器：
   hwmon2/fan1_input 当前速度：0 ... 跳过！
   没有工作风扇传感器，所有读数均为 0。

   确保连接了 3 线风扇。
   您可能还需要增加风扇除数。
   有关更多信息，请参阅 doc/fan-divisors。

所以我的风扇进入“手动模式”并开始全速运行但pwmconfig退出，让我的风扇全速运行。将数字/sys/class/hwmon/hwmon2/pwm1_enable从 1 更改回 2，使其再次自动。

这是我的问题（我认为）：当我的风扇处于“手动模式”时，sensors显示-1为它的速度。它没有被检测到！但是在自动模式下，完全没有问题。这使我无法使用pwmconfig.

我已经尝试添加acpi_enforce_resources=lax到 grub 文件中的变量GRUB_CMDLINE_LINUX_DEFAULT。结果是一样的。

我应该怎么办？

我有一台 HP Pavilion Power 台式机，最近在 Windows 10 旁边安装了 Ubuntu 18.04 LTS。到目前为止一切都很好，除了当我启动 ubuntu 时，我的风扇（我只有一个风扇）会立即全速运转，尽管事实上有没有资源密集型进程正在运行。我安装了 lm 传感器，我的核心温度在 30-40 摄氏度左右，这不是保证风扇一直运行的温度。在 Windows 10 上运行时我没有这个问题，所以我认为 ubuntu 缺少一种控制风扇的好方法。

我首先检查了 BIOS 中是否有任何选项，但没有关于风扇的选项。（没有，我至少找到了）。

所以我安装了 lm-sensors 并让它检测我的硬件，但它添加到 etc/modules 的只是一条信号线“coretemp”，据我了解，它只是我的主要 CPU 内核的模块。但是它确实检测到我的风扇并向我显示它正在运行多少 RPM。

第一张图：传感器输出

如您所见，风扇大约在运行。始终保持 2000 转/分。

我尝试运行 pwm-config，它还成功检测到我在 hwmon1 下的风扇（您可以在第一张图片中看到我的风扇在“nouveau-pci-0100”下运行，在第二张图片中您可以看到“nouveau” " 与 hwmon1) 相关联。但是，当它试图加快速度时，它就不起作用了。

第二张图：pwmconfig 输出

输出表明，pwm 输出与结果速度之间没有相关性。有没有我做错的配置？还是我的风扇根本不支持 pwm？如果是这种情况，是否有任何其他选项可以手动控制我的风扇速度或防止它们一直全速运行？

我正在尝试控制连接到我的 Asrock J5005-ITX 主板的风扇。我已经确定它包含负责该问题的 Nuvoton NCT6796D 芯片组。我被困在我想sensors-detect检测它的地方。从这个linux 驱动程序文件中，我了解到我需要加载nct6775模块。不幸的是，有些事情是不对的：

userName@Server:/$ sudo modprobe nct6775
userName@Server:/$ sudo sensors-detect
# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# Board: ASRock J5005-ITX
# Kernel: 4.18.0-25-generic x86_64
# Processor: Intel(R) Pentium(R) Silver J5005 CPU @ 1.50GHz (6/122/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
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 15h power sensors...                             No
AMD Family 16h power 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): 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'...               Yes
Found unknown chip with ID 0xd423
    (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): 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
Found unknown SMBus adapter 8086:31d4 at 0000:00:1f.1.
Sorry, no supported PCI bus adapters found.

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

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

Next adapter: i915 gmbus misc (i2c-2)
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: y

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----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)y
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 cpuid... OK

未找到该模块。我究竟做错了什么？