-
-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Temperatures reading issue #545
Comments
Hi, I have the same issue on my system because Could you do me a favor and enter the following commands into your terminal and posting the results?
|
|
Great, I will work on a fix |
System information:
Linux distro: EndeavourOS rolling rolling
Linux kernel: 6.4.12-zen1-1-zen
Processor: AMD Ryzen 7 5800H with Radeon Graphics
Cores: 16
Architecture: x86_64
Driver: acpi-cpufreq
------------------------------ Current CPU stats ------------------------------
CPU max frequency: 3200 MHz
CPU min frequency: 1200 MHz
Core Usage Temperature Frequency
CPU0 1.0% 43 °C 4374 MHz
CPU1 0.0% 43 °C 2566 MHz
CPU2 10.1% 43 °C 3901 MHz
CPU3 1.0% 43 °C 3513 MHz
CPU4 2.0% 43 °C 1200 MHz
CPU5 1.0% 43 °C 1790 MHz
CPU6 2.0% 43 °C 3513 MHz
CPU7 6.1% 43 °C 2848 MHz
CPU8 1.0% 43 °C 3503 MHz
CPU9 0.0% 43 °C 1197 MHz
CPU10 2.0% 43 °C 1200 MHz
CPU11 0.0% 43 °C 1200 MHz
CPU12 5.0% 43 °C 1198 MHz
CPU13 1.0% 43 °C 1200 MHz
CPU14 4.0% 43 °C 4374 MHz
CPU15 2.0% 43 °C 4374 MHz
CPU fan speed: 2331 RPM
auto-cpufreq version: 1.9.9 (git: 71ebc3e)
Python: 3.11.5
psutil package: 5.9.5
platform package: 1.0.8
click package: 8.1.7
distro package: 1.8.0
Computer type: Notebook
Battery is: charging
auto-cpufreq system resource consumption:
cpu usage: 0.0 %
memory use: 0.22 %
Total CPU usage: 4.4 %
Total system load: 0.90
Average temp. of all cores: 42.85 °C
Currently using: schedutil governor
Currently turbo boost is: on
Basically, the CPU temperatures read by auto-cpufreq differ from temperatures read by other software like Psensor (I think the correct ones are the letters) and this leads to high fan speeds in daily usage workload.

The text was updated successfully, but these errors were encountered: