Technology

37717 readers

408 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

AMD continues to lock down AMDGPU features (www.phoronix.com)

submitted 8 months ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

Well, apparently, after just a few years the ability to control GPU operation in Linux will slide down considerably.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 8 months ago

🤖 I'm a bot that provides automatic summaries for articles:

Click here to see the summary

This has allowed AMD Radeon Linux users to limit their GPU power draw when desiring for power/efficiency reasons.

But since Linux 6.7 they've begun enforcing a lower-power limit set by the respective graphics card BIOS.

But since Linux 6.7 and the plan moving forward is to honor this power limit bounding box -- matching the behavior of the AMD Radeon Windows driver.

AMD and the Linux Direct Rendering Manager subsystem maintainers have decided this will be the intended behavior to avoid risking any user hardware issues and potential damage -- granted, the likelihood for damage is more often on the upper power limit, but still limiting the GPU power use too low can lead to undefined behavior or other hard to diagnose problems.

It was confirmed today in this bug report that: "This has been discussed on the amd-gfx M/L, and the conclusion was that under-powering outside of the bounding box is potentially dangerous and might damage the hardware.

That stems from a lengthy mailing list discussion and confirmation from AMD that this matches the Windows driver behavior and that there is the risk when running outside of the validated power ranges to see undefined behavior and potentially hardware damage.This change is frustrating some AMD Linux users with some graphics cards reportedly having very conservative pre-defined lower power limits and thus no longer being able to run on the lower-end outside of that imposed range even though they could successfully do so on prior kernels.

Saved 32% of original text.