FreedomX wrote:Do I understand correctly that you fixed this by compiling the latest mainline MesaGL and use this to update your system?
Well I traced the issue and wrote the patch and then submitted it upstream to be included, so that it is now included in the git master and will eventually trickle down to all packages although that could take a while ...
The issue is really dumb, Resolve requests an "OpenGL 3 Core" context and then checks if that extension ARB_texture_border_clamp is available. But the thing is that in a "Core" context, that extension is not optional, it's mandatory and so MESA wasn't including it in the list of "extensions" (since it's mandatory and would always be present in such a context).
You could try to set the env variable MESA_EXTENSION_OVERRIDE=GL_ARB_texture_border_clamp but I'm not sure that would work ... it's not supported for all extensions.
As for the packages, I'm not even sure what distribution you use but the package version (20.x) are quite old ... like 2020 ...
The `amdgpu` ones are the ones installed by drivers from AMD AFAIK, but I didn't know you even needed those, I thought the RX6600 would work with the default mesa and ROCm stack.
In any case, those might appear as different "packages" but they all from the same source mesa tree and must all be updated (see their "version" is all the same since they all come from the same source tree and must stay in sync).
Also the mesa version with the fix isn't going to be packaged for a while, but maybe you can just build it from source and start resolve pointing at it without the need for a global system update.
Not sure how that would play with amdgpu though. What opencl stack is used in your system for the RX6600 ?
Resolve Studio - Ryzen 5800X3D - AMD RX6600 / NVidia RTX 4070 (switching between the 2) - Linux