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/MI30
On 1/8/24 14:21, Germano Massullo wrote:
Il 21/12/23 21:01, Šarūnas ha scritto:
Debian unstable,
kernel 6.6 from experimental,
Which kernel version are you using? 6.6 is a too broad definition
I don't have that setup anymore, but the kernel must have been
$ uname -a
Linux molly 6.6.9-amd64 #
Il 21/12/23 21:01, Šarūnas ha scritto:
Debian unstable,
kernel 6.6 from experimental,
Which kernel version are you using? 6.6 is a too broad definition
___
darktable developer mailing list
to unsubscribe send a mail to dark
Hi,
that sounds like one of the endless AMD GPU stability issues other
people and myself (RX 570, RX 6600 XT, ...) have been having for years.
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
Radeo
Debian unstable,
kernel 6.6 from experimental,
ROCm 6.0,
Radeon RX 7600,
darktable 4.4.2.
OpenCL works 2 out of 3 times between reboots.
~/.cache and ~/.config/darktable are purged between reboots.
When it works, all is fine, no error messages.
When it doesn't (stuck at/before CL kernel compile
Hello, make sure to have a kernel >= 6.6, and make sure to have OpenCL
enabled in darktable. Then, start darktable and check if there are
errors in dmesg
___
darktable developer mailing list
to unsubscribe send a mail to dar
On 12/20/23 17:35, Germano Massullo wrote:
Everyone with an AMD videocard using OpenCL through ROCm on a Linux system with
6.6.x kernel, can you please check if after starting darktable you get this [1]
kind of error messages in dmesg output?
Yes I've been having that error with 6.6.x and a R
