Hello, I am only now reading your reply cause the message was in the
spam folder, due darktable domain wrong settings
https://github.com/darktable-org/darktable/issues/15906
ROCm is simply not reliable on consumer cards and never has been. ROCm
6.0 officially only supports the MI100/MI200/MI300 data center GPUs,
the Radeon Pro W7900/W6800/V620/VII and the Radeon RX 7900/VII on at
most kernel 6.2 (Ubuntu 22.04.3). Everything else is unsupported.
Indeed I have another Radeon card which is a RX480 and it is a second
class citizen since it is not supported by rocm. It does not even have
HDCP support so I am forced to watch video streaming with a very low
resolution
When the drm/amdgpu errors started appearing, I would usually have at
most 20 minutes until the whole machine would lock itself up.
My Radeon 680M suffered till recently of this 1 year old bugreport
https://gitlab.freedesktop.org/drm/amd/-/issues/2220
For me the situation became so unbearable last year, I ended up
plugging in an Intel Arc A770 GPU besides my RX 6600 XT. The A770 only
does OpenCL (not just for darktable), the RX 6600 XT only graphics
(ROCm is not installed). I would maybe be able to get my hand on an
MI100, but they're passively cooled and don't fit into a standard ATX
case.
Have you ever tried to unpack propertary AMD OpenCL drivers somewhere
and exposing them to darktable with a command like
OPENCL_VENDOR_PATH=/home/user/amd_opencl/etc/OpenCL/vendors/
LD_LIBRARY_PATH=/home/user/amd_opencl/opt/amdgpu-pro/lib64/ darktable
it works for my old RX480
P.S. Not just using a different/recent kernel can break a working
setup, but also changing the firmware files (usually installed in
/lib/firmware/amdgpu/). An update of the firmware package might
therefore also break a previously working kernel.
Yes you're 100% right
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
