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
- GitLab takes down Nintendo Switch emulator suyu due to the DMCA
- Horizon Forbidden West Complete Edition out now on Steam - works on Steam Deck
- AMD FSR 3.1 announced with Vulkan support, upscaling quality improvements
- Founder of Baldur's Gate 3 developer blasts publisher greed
- Proton 9.0 (Beta16) brings more regression fixes, updated Steamworks SDK
- > See more over 30 days here
-
SDL 3 will prefer Wayland Over X11, if certain protocol…
- drjoms -
SDL 3 will prefer Wayland Over X11, if certain protocol…
- fenglengshun -
Swordhaven: Iron Conspiracy from the ATOM RPG team has …
- Trias -
The Triple-i Initiative gaming showcase is coming April…
- pb -
Take-Two Interactive buying Gearbox from Embracer, more…
- Salvatos - > See more comments
Latest Forum Posts
- How to find out if a game is native for sure?
- CatKiller - Probably quite slow for the next 9 days
- Ehvis - Logitech G29 steering wheel - Snowrunner support
- njasd2w - Weekend Players' Club 3/22/2024
- Pengling - Nintendo-style gaming, without Nintendo!
- Linux_Rocks - See more posts
You might be right that this only happens if you use multiple display outputs (or a specific single output). I'm using the HDMI only.
View PC info
I have an ASRock one too. Have you read the smallprint before downloading and upgrading to the latest BIOS? For my model they don't recommend upgrading the bios past a certain version for some AMD CPUs.
View PC info
View PC info
I saw some edid progams available in Ubuntu (read-edid, parse-edid???) but couldn't get them working in Fedora. Getting properly functioning monitors shouldn't be this complicated.
Last edited by m2mg2 on 4 April 2020 at 3:04 am UTC
View PC info
[ 6.954609] amdgpu: [powerplay] failed send message: PowerDownJpeg (46) param: 0x00000000 response 0xffffffc2
[ 6.954653] [drm:amdgpu_dpm_enable_jpeg [amdgpu]] *ERROR* Dpm disable jpeg failed, ret = -62.
[ 9.171323] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 9.171364] [drm:amdgpu_dpm_enable_uvd [amdgpu]] *ERROR* Dpm disable uvd failed, ret = -62.
"PowerDownJpeg"?
[ 13.262325] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 15.730846] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 17.949442] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 20.427404] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 22.908628] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 25.392032] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 27.875584] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 30.355106] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 32.571936] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 35.052594] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 37.531160] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 40.013514] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 42.117738] amdgpu: [powerplay] Msg issuing pre-check failed and SMU may be not in the right state!
[ 42.117740] amdgpu: [powerplay] SMU11 attempt to set divider for DCEFCLK Failed!
...and then it boots as if nothing ever has happened.
Well, the problem has been known for months now:
https://gitlab.freedesktop.org/drm/amd/issues/929
View PC info
Last edited by m2mg2 on 15 April 2020 at 5:03 pm UTC
uname -r
5.5.0-1-amd64
glxinfo | grep "OpenGL renderer\|OpenGL version"
OpenGL renderer string: AMD Radeon RX 5700 XT (NAVI10, DRM 3.36.0, 5.5.0-1-amd64, LLVM 9.0.1)
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.3.3
ls /lib/firmware/amdgpu/ | grep navi10
navi10_asd.bin
navi10_ce.bin
navi10_gpu_info.bin
navi10_me.bin
navi10_mec2.bin
navi10_mec.bin
navi10_pfp.bin
navi10_rlc.bin
navi10_sdma1.bin
navi10_sdma.bin
navi10_smc.bin
navi10_sos.bin
navi10_ta.bin
navi10_vcn.bin
Last edited by nolddor on 15 April 2020 at 9:57 pm UTC
View PC info
What does dmesg say? No powerplay in red? As far as firmware goes - hashes are more interesting, since the files don't vary in name and hardly vary in size. Next point: How many displays attached? Finally: It works most of the time, which means I can get 10 boots in a row without any hiccups, then 2 boots with a plethora of errors during boot, then back to normal.
View PC info
No I haven't generated any edid files. And for f*ck's sake I don't want to. Because...
I am completely aware that maybe a custom edid file could solve my problems. But this was the intention of this thread all along: That you don't get a "mildly pleasant" OOTB experience with an RX 5700. Sure, I can setup edid files, try these and that mesa versions, throw in some BIOS files, pick a mainline kernel, do some distro hopping, or draw a pentagram and sacrifice my hamster (redheads are way too scarce nowadays). It's just not something I expect to do in 2020.
View PC info
If you look at my previous post on this thread before the one quoted, I had many of those same complaints. The OOTB experience with amdgpu is garbage, unless you're really lucky and have the right monitor on the right display connector. This is deeper than just the 5700. I had these issues on all 3 of my amdgu compatible cards with three different monitors. How can amdgpu not do something as basic as read edid settings? On my primary gaming set up with 2 monitors neither one had a functional display OOTB.
I didn't have to mess with any BIOS versions, jump distro's, deal with kernel or mesa versions. The only things I had to do were generate the xorg.conf, create and force the edid settings (I put the edid in the initrd but I'm not sure that is needed). BUT, it took me way too long to get there and that is way too much!!!
Overall I'm happy with my functionality and that I don't have to deal with a proprietary module every kernel update but Linux can do better. At the very least we need a utility that can read the edid settings properly, put a file in the firmware folder and add the kernel parameters to force them to be used.