AMD's Initial Graphics Updates For Linux 5.3 Include PowerPlay Improvements, HMM Usage

[skeevy420]

No, end users shouldn't do that. Distributors should. They have the QA pipeline in place to test if the whole thing causes issues with other tweaks and patches they have.

No, they shouldn't. But that is what we have to do to get our brand new AMD GPUs and APUs to work on Linux if we buy them on day one. It sucks, but that is the position that AMD puts their Linux users who buy early in.

[wizard69]

It is sad that the noisy gamers spend so much time criticizing AMD for delivering balanced GPU performance. Not everybody using AMD GPUs is a gamer guys, some of us don’t give a rate ass about how well the GPU supports the latest games.

What we do care about is good balance performance across a number of workloads and open and reliable software. AMD might come up short with respect to reliable but they are not that much worse than the competition.

What im hoping for from AMD is that Navi is a success so that they can continue to expand production of software and hardware variants. In the end guys that is what is needed to solve the software issues, strong sales that will lead to expanded software development teams.

[Space Heater]

It is sad that the noisy gamers spend so much time criticizing AMD for delivering balanced GPU performance. Not everybody using AMD GPUs is a gamer guys, some of us don’t give a rate ass about how well the GPU supports the latest games.

Why do you believe it is only "noisy gamers" that want their newly-bought AMD graphics card to work? It would be great if someone from AMD could confirm that Navi will run properly on 5.1.x or at least 5.2.x kernels. If we have to wait for 5.3+ this is going to be another bad launch for AMD graphics on Linux, regardless of use case.

[dwagner]

Will be interesting to see if the "refactoring clk mgr" mentioned in https://cgit.freedesktop.org/~agd5f/...2efbefe9e2a87e will some day put an end to the arbitrary and erratic seeming relationship between display refresh rates and the minimum shader and memory clocks - which have been changing time and again with code updates.

[bridgman]

It would be great if someone from AMD could confirm that Navi will run properly on 5.1.x or at least 5.2.x kernels.

Agree it would be great, but Navi is going to require either a 5.3 kernel or DKMS-installed kernel drivers.

We were aiming for 5.2 with a good safety margin but IP review and approvals took a lot longer than expected.

[nuetzel]

Agree it would be great, but Navi is going to require either a 5.3 kernel or DKMS-installed kernel drivers.

We were aiming for 5.2 with a good safety margin but IP review and approvals took a lot longer than expected.

Sad to hear, but thanks for info!

[Panda_Wrist]

It is not known what patches AMD has in private repository. AMD have had open source drivers ready since A8-7600 launch. Some bugs of course but they will fix them fast.

Intel provides code far enough in advance that most operating systems will have support for the hardware on day one. --Intel is killing desktop linux.

AMD may or may not have patches in a private repository. Only releasing said code on day one of hardware release, thus requiring compiling the kernel and mesa to get it working. --AMD is saving desktop linux.

*not actually hating on AMD, just hating on debianxfce dumb logic. Code for new Intel hardware is available much sooner than new AMD hardware, that is sadly a true fact, one that I hope changes in the future.

[Termy]

Agree it would be great, but Navi is going to require either a 5.3 kernel or DKMS-installed kernel drivers.

We were aiming for 5.2 with a good safety margin but IP review and approvals took a lot longer than expected.

Can you say anything about if Mesa needs adjustment and if 19.2 is going to work?

[bridgman]

Can you say anything about if Mesa needs adjustment and if 19.2 is going to work?

Yes, Mesa will need changes as well. I expect they will go out after the kernel changes, ie week of June 10-14 or later.

[Termy]

Yes, Mesa will need changes as well. I expect they will go out after the kernel changes, ie week of June 10-14 or later.

That sounds good - lets hope it doesn't get delayed and misses the 19.2 merge window ^^