FW13 AMD 7840u thermal throttle at much lower temperature

Framework Laptop 13 Linux
21

hmm, active looks much better. I’ll keep watching it.

22

I found that it’s reasonable for Framework to not to use full power. Here are two 65W power supplies, one can deliver 3.25A the other has trouble at 3A

PXL_20241213_094025728
PXL_20241213_0940257282040×1536 503 KB

PXL_20241213_093033871
PXL_20241213_0930338711920×1446 233 KB

1 Like
23

which one, may I ask?

This might also have to do with the un-grounded connection – 2-prong chargers technically have a floating voltage, since the charger don’t have a 0V (ground) reference. which can cause erractic readings if you are comparing it to gorund

24

so bad. I have a LM5175 + IP2736 buck-boost DC-DC adapter, it can do 12V input, 20V 5A output no problem. And I am designing a new one.

25

I had exactly the same issue you describe @Terrance_Hendrik on my FW16 with Ryzen 9 : Very low frequency despite heavy load AND low temperatures :-/

I’m glad I have resolved it by switching the power-management from Gnome power-profiles-daemon (Nixos default option) to using auto-cpufreq.

I’m using NixOS, so here is what I’ve added to my configuration.nix :

# https://nixos.wiki/wiki/Laptop
services.power-profiles-daemon.enable = false;
services.tlp.enable = false;
services.auto-cpufreq = {
  enable = true;
  settings = { # https://github.com/AdnanHodzic/auto-cpufreq
    battery = {
       governor = "powersave";
       turbo = "never";
    };
    charger = {
       governor = "performance";
       turbo = "auto";
    };
  };
};

It works beautifully now !

1 Like
26

Oh ! And also I use the Framework recommanded configuration with

imports = [
    <nixos-hardware/framework/16-inch/7040-amd>
  ];

from GitHub - NixOS/nixos-hardware: A collection of NixOS modules covering hardware quirks.

27

wow! I still have this issue occasionally with amd_pstate=active, guess I am going back to amd_pstate=guided and try this auto-cpufreq.

also amd_pstate=active does not fully obey my command, it always steps to high freq than scaling_max_freq