# Framework 13 AMD cpu temps?

**URL:** <https://community.frame.work/t/framework-13-amd-cpu-temps/59699>\
**Category:** Linux\
**Created:** [October 28, 2024, 8:37pm UTC](https://community.frame.work/t/framework-13-amd-cpu-temps/59699 "2024-10-28T20:37:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrjpaxton](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mrjpaxton/32/29649_2.png) [@mrjpaxton](https://community.frame.work/u/mrjpaxton)\
**Post date:** [October 28, 2024, 8:37pm UTC](https://community.frame.work/t/framework-13-amd-cpu-temps/59699/1 "2024-10-28T20:37:10Z")

</div>

Hey everyone,

I use one of those status bars with a WM on Linux, and I’m trying to configure CPU temps specifically in my shell script. When I use this command:

```auto
$ cat /sys/class/thermal/thermal_zone*/type
acpitz
acpitz
acpitz
acpitz

```

It just shows that they all use ACPI. When I run the `acpi -t` command:

```auto
$ acpi -t
Thermal 0: ok, 47.8 degrees C
Thermal 1: ok, 55.8 degrees C
Thermal 2: ok, 45.8 degrees C
Thermal 3: ok, 44.8 degrees C

```

It’s also not very enlightening, since it just shows “Thermal 0, 1, 2, 3”. How can I figure out which one is CPU, HDD, etc…?

---

<div class="post-metadata">

**Author:** ![mrjpaxton](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mrjpaxton/32/29649_2.png) [@mrjpaxton](https://community.frame.work/u/mrjpaxton)\
**Post date:** [October 28, 2024, 9:00pm UTC](https://community.frame.work/t/framework-13-amd-cpu-temps/59699/2 "2024-10-28T21:00:58Z")

</div>

Oh, I just saw this thread - [[RESOLVED] Monitoring AMD Temperature from Linux](http://community.frame.work/t/resolved-monitoring-amd-temperature-from-linux/39980)

Didn’t show up before!

However, when looking at the output of `sensors` from the `lm-sensors` package…

```auto
acpitz-acpi-0
Adapter: ACPI interface
temp1: +45.8°C  
temp2: +48.8°C  
temp3: +44.8°C  
temp4: +55.8°C 

<...>

k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +55.6°C  

amdgpu-pci-c100
Adapter: PCI adapter
vddgfx: 929.00 mV 
vddnb: 650.00 mV 
edge: +53.0°C  
PPT: 10.18 W (avg = 8.05 W)

```

I noticed “temp4” does not line up exactly accurately to these other two. I wonder why? Well, it seems like that one _could likely_ be the CPU die temp.

---

<div class="post-metadata">

**Author:** ![JL\_Framework](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/jl_framework/32/28846_2.png) [@JL\_Framework](https://community.frame.work/u/JL_Framework)\
**Post date:** [October 29, 2024, 1:08am UTC](https://community.frame.work/t/framework-13-amd-cpu-temps/59699/3 "2024-10-29T01:08:04Z")

</div>

You can compare [the approach that I used](https://github.com/brndnmtthws/conky/issues/2051#issuecomment-2392517631). I’m unsure it is the same approach that you are using (but in making that - vague - judgement, I’m being lazy).

---

<div class="post-metadata">

**Author:** ![kirelagin](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/kirelagin/32/16165_2.png) [@kirelagin](https://community.frame.work/u/kirelagin)\
**Post date:** [January 25, 2025, 5:52pm UTC](https://community.frame.work/t/framework-13-amd-cpu-temps/59699/4 "2025-01-25T17:52:51Z")

</div>

The `cros_ec` module re-exports the same values with the following names:

- `temp1` → `local_f75303@4d`
- `temp2` → `cpu_f75303@4d`
- `temp3` → `ddr_f75303@4d`
- `temp4` → `cpu@4c`

In my stress-testing, the `temp4` value seems to be the most responsive to CPU load, with `temp2` lagging noticeably behind. `temp3` appears to be pretty well correlated to memory load and the `spd5118` readings that I am getting. Not sure about the rest.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/1X/64c81a89f963ddb07633887baceb642a4b056046.png) [@system](https://community.frame.work/u/system)\
**Post date:** [July 24, 2025, 5:53pm UTC](https://community.frame.work/t/framework-13-amd-cpu-temps/59699/5 "2025-07-24T17:53:24Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.