问题[temperature](ubuntu)

我最近将我的 CPU 和 MOBO 更改为安装在技嘉 B660M DS3H DD4 主板上的 i5-12400。从那时起，我一直有错误的motd温度读数：

Welcome to Ubuntu 21.10 (GNU/Linux 5.13.0-28-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  System information as of Fri Feb 18 11:25:17 AM CET 2022

  System load:    1.26      Processes:                        450
  Usage of /home: unknown   Users logged in:                  0
  Memory usage:   10%       IPv4 address for xxx:             yyy
  Swap usage:     0%        IPv4 address for xxx:             yyy
  Temperature:    46.0 C    IPv4 address for xxx:             yyy

更改后，我执行了lm-sensors程序并从中sensors得到：

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)
temp2:        +27.8°C  (crit = +105.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +38.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:        +36.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:        +34.0°C  (high = +80.0°C, crit = +100.0°C)
Core 2:        +35.0°C  (high = +80.0°C, crit = +100.0°C)
Core 3:        +34.0°C  (high = +80.0°C, crit = +100.0°C)
Core 4:        +34.0°C  (high = +80.0°C, crit = +100.0°C)
Core 5:        +34.0°C  (high = +80.0°C, crit = +100.0°C)

为了确定哪个读数正确，我快速重启到 UEFI 并显示 38.0°C。当系统motd再次启动时显示46.0 C。

这是我可以解决的问题吗？

我正在尝试提高戴尔 Inspiron 7460 笔记本电脑的 CPU 温度，这是这台特定机器在承受合理压力时的常见问题（小机箱、通风口放置不当、cpu 和 gpu 的单一冷却器）。Windows 允许我简单地将 i5 7200U 的最大速度从 3.1GHz 降低到 2.8GHz 或 2.5GHz，虽然我同意这不是最好的解决方案，但它对我来说很好用。

那么 Ubuntu 20.04.1 有什么办法可以做到这一点吗？另外我是 Linux 新手，终端命令对我来说通常是未知的，但我正在努力学习，而且我经常更喜欢使用它们。

我试图检测传感器，但我不能。首先我安装了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)

我最近在我的 Thinkpad T490 上安装了 Ubuntu 20.04，我注意到 Ubuntu 上的 CPU 温度与 Windows 相比有些奇怪和不同。

我不知道为什么，但在启动时风扇旋转得非常快（可能是由于 CPU 温度高），而这在 Windows 10 上从未发生过。

有人知道为什么吗？我也试过“thinkfan”，但我认为最好使用 BIOS 默认配置来控制风扇（我认为这是 Lenovo Vantage 应用程序使用的配置）。

我想提高我的风扇速度，让我的电脑运行得更冷一些，所以我下载了“fancontrol”包并运行了传感器检测和 pwmconfig 程序。但即使在阅读了“fancontrol”的手册页之后，我也不知道某些参数的实际数值是什么。

例如，有“MINSTART”和“MINSTOP”参数设置“风扇开始旋转的最低速度。你应该使用一个安全的值来确保它工作，即使风扇变老了”和“最低速度风扇仍在旋转。在这里也使用一个安全的值。但是“MINSTART”和“MINSTOP”的度量单位是什么？

然后它说“MINPWM”和“MAXPWM”是分别在温度低于 MINTEMP 或高于 MAXTEMP 时使用的“PWM”值。它确实说“当未定义“MINPWM ...速度）。”但是当我运行“pwmconfig”并选择“详细关联”选项时，我可以看到 255不是最大速度；相反，它大约是速度的一半（是的，我试过等待几分钟让风扇旋转，因此这种行为不仅仅是开始测试和测量之间的滞后时间的产物），然后 210 的值是在“

    PWM 255 FAN 1066
    PWM 240 FAN 974
    PWM 225 FAN 1366 (probably incorrect)
    PWM 210 FAN 1650 (probably incorrect)
    PWM 195 FAN 1558 (probably incorrect)
    PWM 180 FAN 1442 (probably incorrect)
    PWM 165 FAN 1323 (probably incorrect)
    PWM 150 FAN 1198 (probably incorrect)
    PWM 135 FAN 1066
    PWM 120 FAN 976
    PWM 105 FAN 974
    ... some output omitted (PWM values under 150 consistently produce slow speeds)....
    Warning: slow font initialization    Hit return to continue...qt_processTermEvent received a GE_fontprops event. This should not have happened

风扇一直旋转到全速，然后我开始这个阶段的测试，然后风扇速度立即下降，然后加速，然后再次下降。（这是针对“hwmon1/pwm1”传感器的。对于“hwmon1/pwm3”传感器来说，有一个更加戏剧性和看似随机的效果。）（最后的错误信息是新的。）

无论如何，当我使用 fancontrol 程序（使用默认配置或“pwmconfig”生成的配置）时，它肯定会影响风扇的速度，但很难说在后台运行 fancontrol 服务是否会更快，或者没有它。

那么“PWM”数字是什么意思呢？从漫不经心的谷歌上搜索，它似乎与风扇的电脉冲周期有关，这就引出了一个问题：哪个 PWM 数字真的是最大速度？我假设 190 到 220 之间的数字会产生一个波形，使电机旋转得更快，但这个数字的真正含义是什么？以及如何将风扇配置为按需以更高的速度运行？

有时，在将我的笔​​记本电脑从睡眠状态（Ubuntu 18.04 上的联想 Thinkpad T440）唤醒后，lm-sensors将无法读取 temp1，因此thinkfan似乎认为温度很低并且没有启动风扇。传感器中还有其他温度读数，我看到一些温度读数高达 80C。重新启动 PC 通常不能解决问题，但关闭它并重新打开它通常会解决问题。有人遇到过这种问题吗？这就是传感器的输出然后看起来像这样

    coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +43.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +41.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +42.0°C  (high = +100.0°C, crit = +100.0°C)

thinkpad-isa-0000
Adapter: ISA adapter
fan1:           0 RPM
temp1:         N/A
temp2:         +0.0°C
temp3:         +0.0°C
temp4:         +0.0°C
temp5:         +0.0°C
temp6:         +0.0°C
temp7:         +0.0°C
temp8:         +0.0°C

编辑：

$ ps auxc | grep -i therm
root       154  0.0  0.0      0     0 ?        I<   May26   0:00 acpi_thermal_pm
root       956  0.0  0.0 186996   420 ?        Ssl  May26   0:01 thermald

我安装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重新启动，但没有任何好处。

我尝试了许多不同风格的 Ubuntu，所有这些都使我的笔记本电脑的底部比 Windows 更热。我正在使用 i3-7100U CPU 构建的 3-4 岁笔记本电脑上运行。

UPD：空闲时，CPU 温度为 50 度。随着工作量的增加（观看视频、Minecraft、Hotline Miami、Half-life 等轻游戏），它爬升到 60-70 度，我也能感觉到从风扇格子里冒出的热气。

是 Ubuntu 的问题，还是我必须清洁笔记本电脑的风扇并重新涂抹导热膏？