58
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Feb 2026
58 points (100.0% liked)
Linux
12991 readers
301 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
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.
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
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!
Someone on the github issue thread has been asking for clinfo output on affected systems, theorising that client issues are caused by issues with vendor detection.
This is a bit of an ask, but if it's quick to jump forward and back between ROCm releases on your setup, would you be able to pass your clinfo output from 7.2.0 into the ticket linked above? No worries if not
More than happy to, though it might be later today thing
no hurry at all, thanks a bunch!
Posted, I also had an error on the output
Memory access fault by GPU node-1 (Agent handle: 0x5a020e3bce10) on address 0x7f86a34eb000. Reason: Page not present or supervisor privilege. Aborted (core dumped)
can you tell me which device this is with?
edit: nvm i saw you posted it directly into the thread - gfx1103 = 780M iirc
Framework 13 AMD 7640U
hey, hope you're doing well. Can you confirm if ROCm 7.2.1 fixes the issue for you?
Last I tried to download it for Ubuntu last night. The file wasn’t there, will check again when I can
huh, weird. I'll check in with that and see what's going on.
Found the driver, amdgpu-install_7.2.1.70201-1_all.deb.
Downloaded and installed. And while it doesn't immediately crash, it's still crashing before the main page loads. Just after the fairlight page. Will see if there is any Davinci updates and report back
Looks like they copies 7.2 folder when the updated to 7.2.1. Only REHL and another distro has March files, the rest are dated Jan.
Just finished installing DaVinci_Resolve_Studio_20.3.2_Linux.
With amdgpu-install_7.2.1.70201-1_all.deb the app does start and the splash screen shows. But the app crashes before the main menu appears. I presume there's still issues in the OpenCL implementation. Not sure if it's a Davinci issue or a Driver issue. Old driver still works.
Updating the issue myself, but yeah let me know if you want me to check anything else.
Thank you for checking in with this. Strangely it seems to work fine for other people using different distros. Will follow up internally.
I am also running an edge case with an iGPU and a Laptop. Let me know if you want me to run or try anything else.