While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations: 
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
Patreon. Plain Donations: PayPal.This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Unofficial PC port of Zelda: Majora's Mask, 2 Ship 2 Harkinian has a big new release out
- Steam Controller 2 is apparently a thing and being 'tooled for a mass production' plus a new VR controller
- Half-Life: Blue Shift remake mod Black Mesa: Blue Shift - Chapter 5: Focal Point released
- Linux kernel 6.12 is out now with real-time capabilities, more gaming handheld support
- Steam Deck OLED: Limited Edition White and Steam Deck Australia have launched
- > See more over 30 days here
-
Kathy Rain 2: Soothsayer announced and there's a demo a…
- Raaben -
War Thunder adds stealth tech, ray tracing and graphics…
- Pikolo -
Steam Controller 2 is apparently a thing and being 'too…
- FutureSuture -
Dungeon Clawler will grab hold of your free time now it…
- USteppin -
War Thunder adds stealth tech, ray tracing and graphics…
- chr - > See more comments
- Weekend Players' Club 11/22/2024
- Pengling - Our own anti-cheat list
- Liam Dawe - Spare gog keys
- on_en_a_gros - What do you want to see on GamingOnLinux?
- dpanter - Nintendo-style gaming, without Nintendo!
- Talon1024 - See more posts
View PC info
Got my Sapphire Pulse RX 5700 this October (I wanted a quiet custom design) and I was well aware that I required a 5.3 kernel, manually copied firmware and 19.2 Mesa drivers.
I set up a brand new Ubuntu 19.10 on my rig - a X570 board with 3700X and 32Gig RAM - added the firmware (wasn't there upon default install) and the Oibaf-PPA.
Outcome: A constant flow of
amdgpu: [powerplay] Failed to send message ...or
amdgpu: [powerplay] Failed to export SMU metrics table!Result: An unusable desktop which crashes hard after a few minutes.
Back to my trusty 18.04, added mainline kernel, added firmware, added Oibaf. This interestingly works. A dmesg shows nothing disturbing. Well, kinda works. It crashes hard every now and then, but not too often. Crashing games I can live with, but a crashing browser is more of an annoyance.
Googling and finding threads like that
https://bugs.freedesktop.org/show_bug.cgi?id=111481
I heartily have to agree to one of the posters there which states
because I don't get the feeling that this is going to be fixed anytime soon. After all the RX 5700 was introduced about 4 months ago... (He got reprimanded for "name calling" though I found he had put it "rather mildly".)
Next thing: OpenCL. I wasn't aware that the open source drivers lack that entirely. Extracting binaries from the proprietary packages and manually placing them appropriately fixed that too.
I'm all for Open Source but at this point I can only recommend NVidia graphic cards with their proprietary drivers. They just "work". I've always considered the attacks of Windows users claiming "hardware problems with Linux" as unfounded. And I was right - never had them. Till I came across the RX 5700. Now you really "have to compile kernels and drivers" and "do everything in a shell, typing cryptic commands".
On the bright side: Doing some Vulkan benchmarks yielded spectacular frame rates when compared to my previous GTX1060:
View PC info
I can only hope that this is during transition
to the new architecture and will be sorted out soon.
So far I'm more than pleased with AMD's politics and support.
Yet, I don't have one of the new cards.
I can fully understand your anger.
[freedesktop.org is down?]
View PC info
AMD truly made a huge turnover regarding their Linux drivers, but it can be expected to lag behind somewhat. Although I don't have problems with the AMD cards I have or with the ones my friends own, I wouldn't recommend one which is younger than half a year because of the support. That's sad, but currently not much can be done. AMD's Linux team has great people, but the upper management and the communication inside the company is still lacking in this regard.
So the most I can suggest is to try again the "flawless experience" sometime later, when it will be ready, like for older AMD cards.
Last edited by tuxintuxedo on 3 November 2019 at 12:24 pm UTC
View PC info
The Linux team has surely great people and absolutely
love the FOSS drivers / documentation available.
I currently only see one major problem with it,
that might cause problems like described by the OP.
Mesa has a release cycle. So unless you're able to build the stack yourself,
this means sometime waiting 3-6 month for a release that (properly) supports the new hardware.
In particular, if there is a major architecture change.
Now, why not simply push the new code earlier?
Well, products that are not released (probably announced) but have no official specs yet,are understandably a problem for AMD by means that they don't want to expose details early,that gives competition a major advantage. Be it simply to have an existing products ready that's at least competitive in the bang for buck target regime.
While I'm sure that AMD has an internal review process for the patches,
they have to undergo another review when they are pushed to Mesa.
Hence, this can't be simply done right before a release.
If you think exposing information early isn't a problem, then you have missed the many
news sites (not Linux related) that tried to speculate about upcoming AMD GPUs just by
some commits to Mesa. So this is a problem.
And while this stuff sometimes looks hard to read, people that are really interested
in those bits (read competitors) DO KNOW how to extract valuable information from it.
This is a true dilemma.
That could maybe just be resolved if Mesa would allow for private code reviews (including NDA),
which they probably won't consider for other good reason.
Last edited by sub on 3 November 2019 at 3:05 pm UTC
View PC info
The power consumption of 30W when idling should be addressed by kernel 5.4. Hopefully...
Phoronix had benchmarks up and running by the end of July (yes, everything was bleeding edge then)
https://www.phoronix.com/scan.php?page=article&item=rx-5700-july&num=1
but three months later I don't think I'm asking too much when I ask for a somewhat stable driver. (Or at least guidelines which will yield a stable system.)
With the Oibaf PPA I am on the most recent Mesa stack. But there are several firmware versions floating around and the kernel has to be recent enough (with an 18.04 Ubuntu you will get the official 5.3 kernel next spring).
And then we look to the Green Side: Get a GTX2060, get pretty much any of their drivers readily available in repositories (they had RTX support in their drivers the same day they released the hardware), and - it works.
Whether withholding information will yield competitive advantages is questionable. For fellow Linux users I just can't recommend AMD cards. By the time the issues for the RX5700 are ironed out, the next generation is ready to launch. And the reports about bugs and problems might also bleed into the Windows world, fueling a general perception of AMD being sub-par.
Well, I just got carried away. I was pissed. Writing these posts helped :)
MESA's code reviews aren't the reason Navi still has major bugs and missing functionality that were basically only discovered when a customer tried running a popular game or application on a popular distribution. AMD simply doesn't have a big enough Linux driver team to properly test and support a new consumer hardware architecture in a timely fashion.
All that said, my next GPU will most likely be AMD again. I'm rarely in a hurry to buy the latest and greatest anyway. I have been thinking about the 5700, but I don't think I'll take a serious look until Christmas.
I'm not a Linux Poweruser so installing the latest Kernel-Rc then finding that it lacks the firmware and installing it, building the latest mesa-git, the one that is bugged with the game you're actually playing, filing a bug, waiting for the patch to be merged, re-building mesa to actually use your hardware is really really tedious for a product that is almost 5 months old. And you're right when you say it's exactly how Windows users describes us.
Heck, if I've gone the nvidia way : Unplug the old card, plug the new one, better than Windows.
I'm rendering some stuff on Blender and like you I need OpenCl, so right now my GTX 970 is better with her old working cuda cores.
Right now I'm satisfied, it's working well and I'm sorry to learn that you're crashing cause I don't have this problem, but tomorrow ? I feel like it's working but with duct tape and zip ties holding everything together and one wrong update or upgrade could mess it all really quickly.
Last edited by TobyGornow on 3 November 2019 at 6:48 pm UTC
View PC info
View PC info
Depending on your resolution and refresh rate, it's not addressed.
See: https://bugs.freedesktop.org/show_bug.cgi?id=111482
There is conflicting info on that. Some claim that for high resolution / high refresh rate. GDDR6 needs 30W (and they observe it on Windows as well) so it's not a bug, it simply differs from HBM2 which can handle it with less.
However others say, that it's possible to run it with less (see suspend resume sequence example). I tested that and indeed it's possible. So something is clearly missing here.
See also #amd-navi-linux chat room on matrix.org for active discussion.
Last edited by Shmerl on 4 November 2019 at 5:21 am UTC
I have a computer with an AMD GPU. It hangs hard any time from 5 seconds to 5 minutes after booting the system. I don't use it much.
View PC info
Well 5.4 should be out in two or three weeks. I'll try it once it becomes stable. After all, I have to work on the machine, too...