You are not logged in.
❯ cpupower frequency-info
analyzing CPU 1:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
energy performance preference: balance_performance
hardware limits: 404 MHz - 4.79 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 1.10 GHz and 4.79 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.32 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
amd-pstate limits:
Highest Performance: 166. Maximum Frequency: 4.79 GHz.
Nominal Performance: 111. Nominal Frequency: 3.20 GHz.
Lowest Non-linear Performance: 38. Lowest Non-linear Frequency: 1.10 GHz.
Lowest Performance: 14. Lowest Frequency: 400 MHz.
Preferred Core Support: 1. Preferred Core Ranking: 191.
❯ watch -n1 sensors
Every 1.0s: sensors arch: Mon 15 Jun 2026 11:49:44 AM IST
in 0.040s (0)
spd5118-i2c-19-51
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +60.0°C (low = +0.0°C, high = +55.0°C) ALARM (HIGH)
(crit low = +0.0°C, crit = +85.0°C)
hp-isa-0000
Adapter: ISA adapter
fan1: 3327 RPM
fan2: 2986 RPM
pwm1: N/A
amdgpu-pci-0600
Adapter: PCI adapter
vddgfx: 1.32 V
vddnb: 1.04 V
edge: +71.0°C
PPT: 30.00 W
sclk: 933 MHz
BAT0-acpi-0
Adapter: ACPI interface
in0: 12.92 V
power1: 0.00 W
mt7921_phy0-pci-0300
Adapter: PCI adapter
temp1: +66.0°C
spd5118-i2c-19-50
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +62.5°C (low = +0.0°C, high = +55.0°C) ALARM (HIGH)
(crit low = +0.0°C, crit = +85.0°C)
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +97.2°C
nvme-pci-0500
Adapter: PCI adapter
❯ nvidia-smi
Mon Jun 15 11:44:31 2026
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.159.04 Driver Version: 580.159.04 CUDA Version: 13.0 |
+-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 3070 ... On | 00000000:01:00.0 On | N/A |
| N/A 64C P0 38W / 80W | 1140MiB / 8192MiB | 1% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 1284 G /usr/lib/Xorg 373MiB |
| 0 N/A N/A 11725 C+G ghb 574MiB |
| 0 N/A N/A 134668 G alacritty 10MiB |
| 0 N/A N/A 135849 G ...rack-uuid=3190708988185955192 102MiB |
| 0 N/A N/A 136478 G alacritty 10MiB |
| 0 N/A N/A 136950 G alacritty 10MiB |
| 0 N/A N/A 137594 G alacritty 10MiB |
+-----------------------------------------------------------------------------------------+usually at this temps i would see fans spinning at 5000rpm but that is not happening anymore after the I updated my system. I am using handbrake right now.
Offline
Do you run any userspace https://wiki.archlinux.org/title/Fan_speed_control or are the fans controlled by the firmware (UEFI)?
Does the CPU eventually rather clock down rather than the fans keeping it < 100°C?
Offline
Fan speeds are controlled by uefi.
❯ watch -n1 sensors
Every 1.0s: sensors arch: Tue 16 Jun 2026 02:08:21 PM IST
in 0.052s (0)
spd5118-i2c-19-51
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +43.8°C (low = +0.0°C, high = +55.0°C)
(crit low = +0.0°C, crit = +85.0°C)
hp-isa-0000
Adapter: ISA adapter
fan1: 2826 RPM
fan2: 2619 RPM
pwm1: N/A
amdgpu-pci-0600
Adapter: PCI adapter
vddgfx: 890.00 mV
vddnb: 1.04 V
edge: +46.0°C
PPT: 9.02 W
sclk: 2 GHz
BAT0-acpi-0
Adapter: ACPI interface
in0: 13.12 V
power1: 23.60 W
mt7921_phy0-pci-0300
Adapter: PCI adapter
temp1: +54.0°C
spd5118-i2c-19-50
Adapter: SMBus PIIX4 adapter port 0 at 0b00
temp1: +43.2°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: +47.9°C
nvme-pci-0500
Adapter: PCI adapter
Composite: +36.9°C (low = -0.1°C, high = +79.8°C)
❯ cpupower frequency-info
analyzing CPU 1:
driver: amd-pstate-epp
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
energy performance preference: balance_performance
hardware limits: 404 MHz - 4.79 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 1.10 GHz and 4.79 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 3.04 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
amd-pstate limits:
Highest Performance: 166. Maximum Frequency: 4.79 GHz.
Nominal Performance: 111. Nominal Frequency: 3.20 GHz.
Lowest Non-linear Performance: 38. Lowest Non-linear Frequency: 1.10 GHz.
Lowest Performance: 14. Lowest Frequency: 400 MHz.
Preferred Core Support: 1. Preferred Core Ranking: 191.
❯ nvidia-smi
Tue Jun 16 14:08:53 2026
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.159.04 Driver Version: 580.159.04 CUDA Version: 13.0 |
+-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 3070 ... On | 00000000:01:00.0 On | N/A |
| N/A 42C P8 18W / 80W | 353MiB / 8192MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 1293 G /usr/lib/Xorg 208MiB |
| 0 N/A N/A 616125 G ...rack-uuid=3190708988185955192 103MiB |
| 0 N/A N/A 618725 G alacritty 10MiB |
+-----------------------------------------------------------------------------------------+This is current right now. I am not running handbrake and not doing anything CPU intensive.
Offline
❯ fancontrol
Loading configuration from /etc/fancontrol ...
Error: Can't read configuration file
❯ sudo pwmconfig
[sudo] password for shobhit:
# pwmconfig version 3.6.2
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
/usr/bin/pwmconfig: There are no pwm-capable sensor modules installed
❯ fancontrol
Loading configuration from /etc/fancontrol ...
Error: Can't read configuration file
❯ sensors-detect
You need to be root to run this script.
❯ sudo sensors-detect
# sensors-detect version 3.6.2
# System: HP OMEN by HP 16.1 inch Gaming Laptop PC (laptop)
# Board: HP 8A44
# Kernel: 7.0.12-arch1-1 x86_64
# Processor: AMD Ryzen 7 6800H with Radeon Graphics (25/68/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):
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'... Yes
Found unknown chip with ID 0x5570
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 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.
Client at address 0x2c can not be probed - unload all client drivers first!
Next adapter: AMDGPU DM i2c hw bus 0 (i2c-1)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 1 (i2c-2)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 2 (i2c-3)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 3 (i2c-4)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 4 (i2c-5)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 5 (i2c-6)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 6 (i2c-7)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 7 (i2c-8)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM i2c hw bus 8 (i2c-9)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 0 (i2c-10)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 1 (i2c-11)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 2 (i2c-12)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 3 (i2c-13)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 4 (i2c-14)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 5 (i2c-15)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 6 (i2c-16)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 7 (i2c-17)
Do you want to scan it? (yes/NO/selectively):
Next adapter: AMDGPU DM aux hw bus 8 (i2c-18)
Do you want to scan it? (yes/NO/selectively):
Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-19)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x48
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
Probing for `SMSC EMC1023'... No
Probing for `SMSC EMC1043'... No
Probing for `SMSC EMC1053'... No
Probing for `SMSC EMC1063'... No
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 0x50
Handled by driver `spd5118' (already loaded), chip type `spd5118'
(note: this is probably NOT a sensor chip!)
Client found at address 0x51
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-20)
Do you want to scan it? (YES/no/selectively):
Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-21)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x4e
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... No
Probing for `Maxim MAX1617A'... No
Probing for `Maxim MAX1668'... No
Probing for `Maxim MAX1805'... No
Probing for `Maxim MAX1989'... No
Probing for `Maxim MAX6642'... No
Probing for `Maxim MAX6655/MAX6656'... No
Probing for `TI THMC10'... No
Probing for `National Semiconductor LM84'... No
Probing for `Genesys Logic GL523SM'... No
Probing for `Onsemi MC1066'... No
Probing for `Maxim MAX1618'... No
Probing for `Maxim MAX1619'... No
Probing for `National Semiconductor LM82/LM83'... No
Probing for `Maxim MAX6654'... No
Probing for `Maxim MAX6690'... No
Probing for `Maxim MAX6659'... No
Probing for `Maxim MAX6647'... No
Probing for `Maxim MAX6680/MAX6681'... No
Probing for `Maxim MAX6695/MAX6696'... No
Probing for `Texas Instruments TMP400'... No
Probing for `Texas Instruments TMP411C'... No
Probing for `Texas Instruments TMP421'... No
Probing for `Texas Instruments TMP422'... No
Probing for `Texas Instruments TMP435'... No
Probing for `Texas Instruments TMP441'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `National Semiconductor LM95234'... No
Probing for `National Semiconductor LM64'... No
Probing for `National Semiconductor LM73'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Probing for `Fintek F75121R/F75122R/RG (VID+GPIO)'... No
Probing for `Fintek F75111R/RG/N (GPIO)'... No
Probing for `ITE IT8201R/IT8203R/IT8206R/IT8266R'... No
Client found at address 0x73
Probing for `FSC Poseidon I'... No
Probing for `FSC Poseidon II'... No
Probing for `FSC Scylla'... No
Probing for `FSC Hermes'... No
Probing for `FSC Heimdal'... No
Probing for `FSC Heracles'... No
Probing for `FSC Hades'... No
Probing for `FSC Syleus'... No
Probing for `FTS Teutates'... No
Client found at address 0x77
Probing for `Asus Mozart-2'... No
Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-22)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-23)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter 6 at 1:00.0 (i2c-24)
Do you want to scan it? (yes/NO/selectively):
Sorry, no sensors were detected.
This is relatively common on laptops, where thermal management is
handled by ACPI rather than the OS.
❯
❯ sudo pwmconfig
# pwmconfig version 3.6.2
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
/usr/bin/pwmconfig: There are no pwm-capable sensor modules installed
❯ fancontrol
Loading configuration from /etc/fancontrol ...
Error: Can't read configuration fileOffline
Assuming you aren't dualbooting, have you tested how it runs on the Arch live ISO?
If its working fine on the live system but not on your installed Arch then it probably is something running that is attempting to control fan speed.
If you have the same issue in the live environment then it points to either a UEFI/BIOS issue or hardware issue.
I would also go into the UEFI/BIOS if you haven't already and check the fan settings to see if they are what you are expect them to be.
Ryzen 7 9850X3D | AMD 7800XT | KDE Plasma
Offline
Does the CPU eventually rather clock down rather than the fans keeping it < 100°C?
Also test the behavior w/ a synthetic multithread stresser, eg. https://wiki.archlinux.org/title/Stress_testing#stress
Offline
# System: HP OMEN by HP 16.1 inch Gaming Laptop PC (laptop)
*sigh
why so many people just don't get it to mention in thier first post "hey, I'm on a laptop, btw"
Online