this post was submitted on 17 Oct 2024
75 points (100.0% liked)

Linux Gaming

15494 readers
509 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
monolalia
75
AMD Linux Graphics Driver To Switch To More Aggressive Power Heuristics By Default (www.phoronix.com)
submitted 2 months ago by [email protected] to c/linux_gaming
4 comments fedilink hide all child comments
 

Nice to see this will be finally fixed. You have to make a udev rule to work around this at the moment.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 8 points 2 months ago* (last edited 2 months ago) (1 children)

It's better in the name of performance but with more aggressive ramping of the core/memory clock frequencies it can come with an increase to power use by default.

A Phoronix comment says this increases power draw by more than 10W at idle. That's pretty wasteful for systems that spend most of the day at or near idle. (And AMD's recent GPUs already have a reputation for idling with too much power draw on linux.)

I hope the change comes with an easy to revert it. If they can't figure out how to automatically enter and leave this mode on demand, we need a way for a script or gamemode hook to do it. Efficiency is important even in desktop systems.

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago)

It depends on the GPU I suspect. The 6XXX series doesn't appear to have that issue, at least not in a significant way. But yeah, the 7XXX series having power consumption issues isn't too surprising.

As for the quote, the "more aggressive ramping" is about its behaviour under load, which you probably do want if you're playing games.

You can revert the change in the same way as you can make the change now, with a udev rule. And you can change it on the fly with a script if needed.

Udev rule:

KERNEL=="card0", SUBSYSTEM=="drm", DRIVERS=="amdgpu", ATTR{device/power_dpm_force_performance_level}="manual", ATTR{device/pp_power_profile_mode}="0"

(you might be able to leave the power_dpm_force_performance_level part unset)

You can also try the compute (5) or VR (4) modes which have slightly different behaviour (I use the compute mode on my systems even though they are mostly for gaming).

I believe some of the third party GPU control utilities can also do this, but I don't personally use them.