PSA for those using DaVinci Resolve with AMD GPUs, don't install ROCM 7.2, stay on 7.1.1
Been fighting this bug for a while now, but since I updated rocm to 7.2 DaVinci resolve died.
Took me a while to track down that it was rocm until I ran across an endeavour os post about it. But if you’ve noticed that resolve stopped loading and not showing errors, Try downgrading rocm and trying again.
Endevour OS Post: https://forum.endeavouros.com/t/can-t-use-davinci-resolve-studio-crash-to-desktop/77870/11
AUR post which the Endevour OS post was referring to: https://aur.archlinux.org/packages/davinci-resolve-studio#comment-1058336
If you need to downgrade your amdgpu-install package, AMD's repo link is here https://repo.radeon.com/amdgpu-install/
How is 7.2 newer than 7.11?
Spoiler: It's 7.1.1, actually
You need to be more careful. Misplaced decimal point can kill a diabetic.
fixed, I couldn't remember if it was 11 or 1.1 and I wrote the post on my phone.
ROCm has got to be the worst software I've ever dealt with.
An unfortunate evil if you have AMD and need open cl
On my main rig I am using Nvidia RTX3060 12G, I was considering AMD, but this is putting that into question.
My laptop is using AMD for CPU and GPU which is why I ran into this. Was concerned that it was an issue with Linux Mint. So happy it isn't.
Can you share the post here? Does it elaborate on what's failing?
I'll also add it to the main post, but here is the link i was referring too
https://forum.endeavouros.com/t/can-t-use-davinci-resolve-studio-crash-to-desktop/77870/11
and here is the AUR comment thread it was linking too
https://aur.archlinux.org/packages/davinci-resolve-studio#comment-1058336
Sadly it's above my head.
Thank you for linking these. The second one suggests the following
I'll dig through to see what can be done about it.
I am curious if it's a Davinci issue or a AMD one. Would love to hear the results.
have filed this to the ROCm team, hope to get someone looking into this tomorrow.
Thank you, hopefully it’s something small
We'll find out. It's filed to the public issue tracker, which is a nice change of pace. Hope you can stay appraised of the progress from the following link:
https://github.com/ROCm/ROCm/issues/5970
Good news, seems there's an existing internal ticket covering this defect. It's an application-side issue pertaining to libProResRAW.so.
I believe we're shipping a workaround at the ROCm framework side in 7.2.1
That is fantastic to hear!
I don't suspect it's davinci resolve. This is likely due to rocm-opencl.
It's a long weekend, so I likely won't hear back from my colleagues until Tuesday at the earliest