Radeon ROCm 3.5 Released With New Features But Still No Navi Support

[69Y69]

I'll double-check, but I thought the HW support list was all Polaris & Vega dGPUs with Navi in the pipe, ie pretty much everything we have been selling in the last few years.

Sorry, but it's been almost 11 months since the Navi product line launched. It has been 11 months and AMD customers are still waiting for a compute support. The same 11 months have been their Navi cards useless for compute.

Here goes the hard truth - any customer buying a GPU/product expects a SW support on the very day when he/she made the purchase. With AMD this is not really the case.

Sorry, but AMD's SW support is still a hobbyist project. Nobody serious would consider that. Forward this memo to your manager. Thanks

[birdie]

This is getting ridiculous...

Fuck NVIDIA, right?

Oh wait, NVIDIA does fully support OpenCL 1.2 on all its current GPUs for Linux while God-blessed AMD does neither support OpenCL, nor HW video decoding acceleration for Navi.

[TemplarGR]

I think the best solution for AMD consumers would be the MESA OpenCL implementation. Now that it seems it is picking up support, it might become viable soon. The majority of people just need OpenCL support, they don't care about the more advanced features ROCm brings. I personally just want to be able to run some OpenCL stuff without having to rely on the binary module.

[_r00t-]

It's a good card. Your biggest mistake is probably not doing your homework before buying

No time for homework mate..... ok it's a good card but even opensource drivers doesn't work properly yet(lots of GPU resets...etc). Also still no OpenCL support yet and some programs won't work even with combination of opensource drivers + OpenCL from AMDGPU-PRO.

[TemplarGR]

Fuck NVIDIA, right?

Oh wait, NVIDIA does fully support OpenCL 1.2 on all its current GPUs for Linux while God-blessed AMD does neither support OpenCL, nor HW video decoding acceleration for Navi.

You shill, AMD supports OpenCL through a binary module too, and higher than 1.2.... ROCm is not the only OpenCL software AMD has, and ROCm is far more advanced that the Nvidia implementation of OpenCL...

Now go back to Nvidia to get your shekels, you earned them.

[birdie]

One of my biggest mistakes in my life that i bought Radeon RX 5600 XT..... pitty

Any AMD fan will tell you AMD GPUS ARE THE BEST EVAR, AMD CPUs ARE THE BEST EVAR (despite not fully supporting Linux), NVIDIA AND INTEL SUCK ASS.

[_r00t-]

Give it to me then

I wish i could but i will have to buy another one and i have other priorities currently. :P

[birdie]

You shill, AMD supports OpenCL through a binary module too, and higher than 1.2.... ROCm is not the only OpenCL software AMD has, and ROCm is far more advanced that the Nvidia implementation of OpenCL...

Now go back to Nvidia to get your shekels, you earned them.

Binary module? Heresy!!!!!!!!!!!!! Burn with fire!!!!!

NVIDIA SUCKZ, INTEL SUCKZ, AMD IS THE SECOND COMING OF CHRIST.

Also, f you, I am now rocking a piece of crap called RX 5600 XT - the most unstable GPU I've ever owned, with the most drivers issues I've ever had.

[Laughing1]

Binary module? Heresy!!!!!!!!!!!!! Burn with fire!!!!!

NVIDIA SUCKZ, INTEL SUCKZ, AMD IS THE SECOND COMING OF CHRIST.

Also, f you, I am now rocking a piece of crap called RX 5600 XT - the most unstable GPU I've ever owned, with the most drivers issues I've ever had.

Run Mesa-git and the latest kernel, problem solved...

[blacknova]

What problems are you having installing on a recent distro ? We split the packages and dependency hierarchy to make it easy to install ROCm userspace on the distro's existing kernel and drivers, and have covered that in the install instructions for almost a year.

Thanks, let me check again, last time I've tried to install ROCm I was on Fedora 31 with latest kernel from Fedora's repo to the moment and RX480 GPU. Installation instructions, which I found, were not very clear on what one need to do to setup ROCm with in kernel kfd.

I'll double-check, but I thought the HW support list was all Polaris & Vega dGPUs with Navi in the pipe, ie pretty much every dGPU we have been selling in the last few years. I think it was even working on the KabyLake G parts (which had an AMD dGPU). We do need to get Navi support finished but getting the transition from HCC to hip-clang done (part of 3.5) will make that easier.

We have been making some changes to APU support (using GPUVM-based dGPU code paths rather than the original APU-specific ATC/IOMMUv2 paths) in order to let APUs be a better development platform for dGPUs and you should see that code start to fetch up soon as well.

I still have a number of GCN1.0 gpus on hand including R9 280X, which should be very good at least at OpenCL 1.x, but it is not supported and would not be supported by ROCm.