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.
this post was submitted on 14 Feb 2026
56 points (100.0% liked)
Linux
12388 readers
358 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
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
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
Update: Turns out that this is happening because the update of opencl-amd package, the newest ROCm 7.2 drivers appear to not be compatible with DaVinci, I installed rocm-opencl-runtime from the extra repo since it still on 7.1.1 and now its working again.. It also doesn't work with opencl-mesa, it crashes launching a project
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
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
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:
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