MangoHUD uses the wrong CPU temperature sensor on CachyOS (Ryzen 9 3900)

Issue description

Since updating to MangoHUD 0.8.1-1, I’ve noticed that the CPU temperature is either not shown correctly or uses the wrong sensor. The system correctly detects all sensors, but MangoHUD ignores the proper one (k10temp-pci-00c3) and instead reads from asusec-isa-000a, which reports the motherboard or chipset temperature, not the actual CPU temperature.

️ System information

OS: CachyOS (Arch Linux)

Kernel: (output of uname -r)

CPU: AMD Ryzen 9 3900

GPU: NVIDIA RTX 4070 Ti

MangoHUD version: 0.8.1-1+

Graphics driver: (e.g. NVIDIA 555.xx or Mesa 24.xx)

Observed behavior

The sensors command shows:

asusec-isa-000a CPU: +37.0°C ... k10temp-pci-00c3 Tctl: +46.0°C Tccd1: +46.5°C Tccd2: +37.5°C

However, MangoHUD seems to read from asusec-isa-000a instead of k10temp-pci-00c3, which leads to an incorrect CPU temperature being displayed.

Even forcing the sensor in the configuration:

cpu_temp=1 cpu_temp_sensor=k10temp

does not fix the issue — MangoHUD continues to use the wrong source. This suggests that MangoHUD either fails to recognize k10temp as a valid sensor or does not properly apply the manual override.

⚙️ Steps to reproduce

On a CachyOS or Arch Linux system with a Ryzen CPU (e.g., 3900X or 3900), install MangoHUD 0.8.1.

Verify that both asusec and k10temp sensors are visible with sensors.

Launch any game or app with:

DXVK_ASYNC=1 DXVK_HUD=0 gamemoderun mangohud %command%

Observe that the CPU temperature displayed by MangoHUD does not match the k10temp readings.

✅ Expected behavior

MangoHUD should read the temperature from the k10temp sensor (e.g., Tctl) or allow users to manually select it with the cpu_temp_sensor configuration option.