I went ahead and installed Blender 3.2.1 from updates-testing, along with all 6 ROCm packages. I rebooted and checked for my GPU in blender under Edit > Preferences > Cycles Render Devices > HIP. However, Blender reported that “No compatible GPUs” were found:
Hey there! I wanted this exact same thing! I had to do a little work and research to get there, but Blender now uses HIP on my Fedora 36 install. Here’s a post I wrote about the process. Hope it helps!
Taking a high level approach … kernel programming model is used in several C++ extension frameworks being HIP, Cuda or DPC++ supported by AMD, NVidia or Intel with enormous stake as thought to be ideal tool for AI neural network. Red Hat/CentOS/Fedora implement SELinux, a National Security Agency program and you find information at Fedora Docs/F36/System Administrator Guide/Kernel, Module and Driver Configuration about signed/tainted kernel modules. NVidia, Google Coral, Intel Altera, AMD Xilinx, … all send you to Ubuntu as liberal with closed source software and Canonical only commercial support of Blender software massively used in industry. You can implement in Fedora, can be complicated, no sure of the pertinence of specific point of view … not Fedora vs Ubuntu but global approach to open source concept.
When DPC++ came out, it targeted heterogeneous environment being CPU, GPU and FPGA with SYCL replacing OpenCL. Works with Altera devices. AMD made noise so opened to them being an open source sort of thing, look up about it. Cuda is specific to NVidia devices, HIP to AMD devices moving from Vivado to Vitis for Xilinx devices. The DPC++ project is fascinating as you program a project on a mix, the compiler choosing where, when, how device by device.
AI is hot topic now using neural networks similar to those used for computer vision. That is where you are cornered between Blender and the rest …
Which packages listed in that post are proprietary? According to AMD, amdgpu-install is for installing their All-Open stack.
Also, I was under the impression while that HIP & OpenCL serve similar purposes, neither depends on the other.
You may be better qualified to make those distinctions than I am. It was my impression that the packages were proprietary because they aren’t apart of the regular mesa libraries (again, I’m not an expert!).
As far as the HIP vs OpenCL is concerned, you may be onto something there where the opencl portion of the install is not necessary, but since I was following a guide from Reddit, I thought it best to stick to what got it working for the writer at the time. It’s totally possible that on step 5 that you can omit the opencl portion of the install and just include the hip portion.
This statement makes sense! Call me superstitious, but again I blindly followed the guide from Reddit which I simply regurgitated on the Fedora forum (with links to the original).
I very much hope that this kind of work around isn’t necessary forever (the one I linked to) and that something like what you’ve mentioned here will become a mainstay for us instead!
Let me know if you have any further questions or need more detail!
Please also check out this user’s input. They got HIP under Blender to work (the rpm from Fedora’s repo) via a slightly different method. I’ve tested it and found it to be more stable than the method I detailed above. The latest comments discuss the alternate (and more stable in my opinion) approach.
Something else … HIP is only compatible with AMD Radeon 6000 series, with Blender probably only high end with sufficient memory. You can install drivers but if incompatible HIP/Blender you will get no message or minimal mention in logs. HIP/Blender is still experimental, AMD trying to catch up on NVidia Grace Hopper hardware architecture.
HIP is only compatible with AMD Radeon 6000 series
While only certain CDNA & RDNA2 cards are officially supported by ROCm, others have gotten HIP to (mostly) work with older cards & Blender Cycles. See the image texture bug link at the start of this thread.