Page 2 of 2

Re: Brand new hardware ... and OpenCL

Posted: 19 May 2019 13:09
by ilu
Yes, it is. 4th Gen GCN. ... eneration). All AMD graphics since 2012 use GCN architecture. Or did I get your question wrong?

Edit: Actually there are mistakes in your list, Arjen. I'm working on it. And I've moved it to a separate topic, because I think we've figured out amnesix' hardware and he can move on to the openCL problem.

The confusion results from the fact that Radeon 570 and 580 essentially use the same Polaris 10 chip as the 470 and 480 - just produced differently (14nm) - and as such can identify themselves as Ellesmere and as Polaris. The kernel driver identifies them as "same" 67df.
"Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580]" would be better but for Ellesmere that's only in the subsystem line of your last lspci comand and it's probably too much hassle to adapt line 176.

@Amnesix, if you look up the code [1002:67df] given by the lspci command you'll see that it's your card. So it's just the name that's wrong and I don't think that matters. And if you look up 67df in the kernel driver database you'll find "Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]" - so all of them use the same driver. I don't think we need to worry about names here.

Amnesix, please always include the command with the output, don't post just the output!

Re: AMD graphics: radeon, amdgpu, amdgpu-pro

Posted: 01 Jul 2019 18:32
by amnesix
I have a late question : I've found this debian page which tells me how to install amdgpupro, and it seems (for me) quite complicated, but I'm going to try. The link is here : ... d%20Buster

Now the question : what happens when the time comes for a new kernel ?

Re: Brand new hardware ... and OpenCL

Posted: 01 Jul 2019 22:28
by ilu
I've moved your post to your original topic to keep the context.
amnesix wrote: Now the question : what happens when the time comes for a new kernel ?
That could be problematic, you'll have to try. Since the guy is not patching the kernel but the driver that should work. dkms usually cares for things to work. If after a kernel update things don't compile anymore you'll have to reboot with the previously working kernel and wait for the guy to update his patch.