That’s really interesting! Good find
Small correction, it’s not about even or odd horizontal resolution, the horizontal resolution has to be a multiple of 128. Tested 128, 256, 384, 512, 768, 1024, 1536, 1664, 2048 and 4096, all worked. Any horizontal resolution I’ve tested below 128 crashed, as did 192 for example (128+64), or anything else that wasn’t a multiple of 128. The vertical resolution can be anything.
2 Likes
Thanks I’ll add that info. Will greatly help us!
Just a heads up 3.2 doesn’t appear to work on arch any more with just the opencl-amd package, it appears it needs the rocm-llvm package to build a kernel the first time it runs (took 35 sec on a 5900X).
If you use arch and want to use repo.radeon use opencl-amd and opencl-amd-dev. Only downside is the 10 GB install size, however I think amdgpu-install users still have a 4GB install size?
@Luciddream
What do you think about separating openCL and HIP aur packages for those that don’t want to compile? It would also slightly better align with the amdgpu-install packages.
| aur package | purpose | aur dependencies | repo.radeon dependencies |
|---|---|---|---|
| opencl-hip-amd | common to OpenCL and HIP | current stuff from opencl-amd | rocm-language-runtime, rocm-core, rocm-device-libs, comgr, hsa-rocr, has-rocr-dev, hsakmt-roct-dev |
| opencl-amd | unique OpenCL stuff | opencl-hip-amd | rocm-opencl-runtime, rocm-opencl, rocm-ocl-icd |
| hip-amd | unique HIP stuff | opencl-hip-amd | rocm-hip-runtime, rocminfo, rocm-llvm, hip-runtime-amd |
No idea what to do with the other 6GB of files from opencl-amd-dev once you remove rocm-llvm.
Can I install rocm on the open source driver? Which one has better performance than the dedicated driver on the official website
@L_S I’m open to discussing it but lets transfer this discussion to the AUR package page. But, I doubt we can find a middle ground. Every user will have a different need for his GPU. The only easy way to cover all cases is to include the whole amdgpu stack (which is what opencl-amd and opencl-amd-dev does)
However it would be helpful to understand why Blender 3.2 needs rocm-llvm but the previous versions didn’t, so we can make the better decision.
I think amdgpu-install users still have a 4GB install size?
I’m not at my PC now but I think amdgpu-install is about 16GB+. Maybe someone using Ubuntu and amdgpu stack can verify.
It’s a problem with Arch’s Blender package I believe. I ran into the same issue, the official binaries from blender.org worked just fine with opencl-amd. I guess the official package ships with precompiled kernels while the Arch package doesn’t.
2 Likes
Thanks for the info you are 100% correct! I removed opencl-amd-dev and the official packaged blender 3.2 version renders in Cycles fine without kernel compilation (also deleted the kernel the arch packaged blender made).
Any news on Vega support and broken HIP kernels on Arch in 3.3 Alpha?
HIP on Vega linux hasn’t been addressed yet but as noted in the meeting notes, Vega (And Vega II aka Radeon 7) support is looking good for 3.3 on windows. We’ll push a change in a week or two.
1 Like
That’s good news for any Windows users out there.
What about Vega on Linux and HIP kernel build issues with Rocm 5.1.3? Vega is unsupported with proprietary drivers as well.
1 Like
So basically, polaris architecture has HIP supporte but Cycles doesn’t support polaris architecture, right? If polaris support doesn’t happen, it means that we’re stuck in Blender 2.93 until we made a GPU upgrade? just trying to understand fr
1 Like
You are correct.
However, it is important to point out something. Polaris supports HIP, but it is no longer officially supported in recent versions of HIP, like the one used by Blender/Cycles. And as such I believe it is unlikely that the Blender foundation will enable Polaris support in Cycles.
Man this is devastating to hear, I spent all the money I saved on an RX 580! What a day to be alive LOL, anyway, thanks for the clarification
1 Like
Vega support for Linux and Windows has been added here: ⚙ D15242 Enable Vega GPU/APU for Cycles HIP
Seeing that this requires a new HIP SDK, do we also need a new driver to utilize it?
1 Like
We’ve tested on the AMD side with the latest already released drivers. Not sure if they would work with earlier ones.
1 Like
Will these new drivers also contain a fix for the RDNA1 texture bug (see: ⚓ T97591 Cycles HIP error with image textures on Linux and RDNA1)?
If you subscribe to that issue, you’ll be notified when there is a fix in the driver.
This is really sad news 
It’ll be some years untill I’ll be able to invest into a new gpu card. I hope the landscape will be different and whatever I buy has support for more years.
4 Likes