Arch Linux

Soyman

Member

Registered: 2017-06-23

Posts: 27

High idle fan speed on Legion Pro 7 16IRX8H

My laptop has 3 hardware defined fan presets. The https://aur.archlinux.org/packages/leno … nlinux-git package is installed (as well as the dkms version) but does not support the fan curve system on my laptop. The fans idle at around 2100 RPM on all the presets. They ramp up as they should under load, and the fan presets work, giving more aggressive fan speeds at the balanced, and performance presets, than the quiet one, as would be expected. The main issue is that the fan never ramps down by itself, below 2100 RPM. When switching presets, the fan slows down, but ramps back up to at least 2100 after ~10 seconds.

I don't recall this being an issue after purchasing the laptop, around a year ago. The issue is present on both Arch with linux 6.12.1 and LTS 6.6.63. The issue is not present on a manjaro live USB running linux 6.10.

I'm not sure how best to go about troubleshooting this in lieu of this information.

jl2

Member

From: 47° 18' N 8° 34' E

Registered: 2022-06-01

Posts: 489

Website

Re: High idle fan speed on Legion Pro 7 16IRX8H

IDK if this is the right direction but what are your CPU/GPU temps? One way you can read them is with the "sensors" command (requires the lm_sensors package), but any other monitoring tool will do.

Last edited by jl2 (2024-11-27 20:20:21)

---

Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...

Soyman

Member

Registered: 2017-06-23

Posts: 27

Re: High idle fan speed on Legion Pro 7 16IRX8H

IDK if this is the right direction but what are your CPU/GPU temps? One way you can read them is with the "sensors" command (requires the lm_sensors package), but any other monitoring tool will do.

It's a valid suggestion. They hover around 55-60 when idle, although the cores themselves and the discreet gpu are colder at around 40-45.

I haven't looked at the sensors in manjaro, but the fans don't have the issue there.

To be clear, the issue occurs when the cpu is idle and I've verified that there is no load on it.