Add HIP and HIPRT Support for GFX1037 (AMD Radeon 610M iGPU) #111019

Closed
opened 2023-08-10 19:11:27 +02:00 by Argo-Tegar · 9 comments

System Information
Operating system: Windows 10 IoT LTSC 21H2 (19044.2846)
Graphics card: AMD Radeon 610M (Mendocino) (GFX1037) with the latest 23.7.2 driver.

Blender Version
Broken: All versions that I know of, including the latest 4.0.0 Alpha build.
Worked: None, that I know of.

Short description of error
There seems to be no HIP kernels for the Mendocino iGPU which is based on the RDNA2 microarchitecture. I was unable to use Cycles with the integrated GPU selected, it would throw a message saying "HIP binary kernel for this graphics card compute capability (10.3) not found".

Exact steps for others to reproduce the error

  1. Install the 23.7.2 driver after doing a DDU.
  2. Install Blender 3.6.1.
  3. Download the Classroom demo file.
  4. Open it, open the Preferences menu, go to System, select the iGPU as the HIP render device.
  5. Select Cycles as the render engine, then select GPU compute.
  6. Render -> Render Image.
**System Information** Operating system: Windows 10 IoT LTSC 21H2 (19044.2846) Graphics card: AMD Radeon 610M (Mendocino) (GFX1037) with the latest 23.7.2 driver. **Blender Version** Broken: All versions that I know of, including the latest 4.0.0 Alpha build. Worked: None, that I know of. **Short description of error** There seems to be no HIP kernels for the Mendocino iGPU which is based on the RDNA2 microarchitecture. I was unable to use Cycles with the integrated GPU selected, it would throw a message saying "HIP binary kernel for this graphics card compute capability (10.3) not found". **Exact steps for others to reproduce the error** 1. Install the 23.7.2 driver after doing a DDU. 2. Install Blender 3.6.1. 3. Download the Classroom demo file. 4. Open it, open the Preferences menu, go to System, select the iGPU as the HIP render device. 5. Select Cycles as the render engine, then select GPU compute. 6. Render -> Render Image.
Argo-Tegar added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-08-10 19:11:27 +02:00
Author

Additional screenshot from the latest 4.0.0 Alpha daily builds.
image

Additional screenshot from the latest 4.0.0 Alpha daily builds. ![image](/attachments/d0ef47f6-4d26-4b27-a875-dd8e69e86298)
YimingWu added
Status
Needs Info from Developers
Interest
Cycles
and removed
Status
Needs Triage
labels 2023-08-11 04:17:42 +02:00
Member

Hi, thanks for the report. As far as I know, RDNA2 architecture GPUs are supported but I'm not seeing this GPU series listed in: https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html#hip-amd

@BrianSavery , can you check?

Hi, thanks for the report. As far as I know, RDNA2 architecture GPUs are supported but I'm not seeing this GPU series listed in: https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html#hip-amd @BrianSavery , can you check?
Author

Hi, thanks for the report. As far as I know, RDNA2 architecture GPUs are supported but I'm not seeing this GPU series listed in: https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html#hip-amd

Yes, it isn't listed under the discrete GPU section since it's an APU/integrated GPU. It is still fairly new and I thought it would be supported since I saw someone running HIP with the 680M, but apparently it's a different RDNA2 revision (GFX1035).

Just to be sure I tested the same alpha build on my mini PC with the 5600G (Vega 7 GFX90c) and it works perfectly even with HIPRT enabled.

> Hi, thanks for the report. As far as I know, RDNA2 architecture GPUs are supported but I'm not seeing this GPU series listed in: https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html#hip-amd > Yes, it isn't listed under the discrete GPU section since it's an APU/integrated GPU. It is still fairly new and I thought it would be supported since I saw someone running HIP with the 680M, but apparently it's a different RDNA2 revision (GFX1035). Just to be sure I tested the same alpha build on my mini PC with the 5600G (Vega 7 GFX90c) and it works perfectly even with HIPRT enabled.
Pratik Borhade added the
Module
Render & Cycles
label 2023-08-11 09:10:14 +02:00

Yes, the list of "supported" vs enabled hardware is somewhat non-intuitive so it's worth recapping.

AMD's official supported hardware for ROCm / HIP is here: https://rocm.docs.amd.com/en/latest/release/windows_support.html (and the linux page)

You'll notice that there are actually more GPUs enabled in Blender than is on those list (for example the 680M and APUs mentioned before.) We do our best to make as many gpus work in Blender as we can but I can't officially say something like an RX 5700 is supported because the ROCm compiler guys don't officially support it.

That said, in practice a lot of cards actually just work. The list of possible targets to compile to is here: https://www.llvm.org/docs/AMDGPUUsage.html#processors which you will notice there isn't even a target for gfx1037 in the compiler (and it's not mentioned in the SDK anywhere). So for this APU, sorry it doesn't look like this is possible right now. Not sure if you want to keep the issue open or close or just check back when there is a future version of the SDK.

Yes, the list of "supported" vs enabled hardware is somewhat non-intuitive so it's worth recapping. AMD's official supported hardware for ROCm / HIP is here: https://rocm.docs.amd.com/en/latest/release/windows_support.html (and the linux page) You'll notice that there are actually more GPUs enabled in Blender than is on those list (for example the 680M and APUs mentioned before.) We do our best to make as many gpus work in Blender as we can but I can't officially say something like an RX 5700 is supported because the ROCm compiler guys don't officially support it. That said, in practice a lot of cards actually just work. The list of possible targets to compile to is here: https://www.llvm.org/docs/AMDGPUUsage.html#processors which you will notice there isn't even a target for gfx1037 in the compiler (and it's not mentioned in the SDK anywhere). So for this APU, sorry it doesn't look like this is possible right now. Not sure if you want to keep the issue open or close or just check back when there is a future version of the SDK.
Author

That said, in practice a lot of cards actually just work. The list of possible targets to compile to is here: https://www.llvm.org/docs/AMDGPUUsage.html#processors which you will notice there isn't even a target for gfx1037 in the compiler (and it's not mentioned in the SDK anywhere). So for this APU, sorry it doesn't look like this is possible right now. Not sure if you want to keep the issue open or close or just check back when there is a future version of the SDK.

I booted my linux install on the Mendocino machine and it seems that the RadeonSI driver (which uses LLVM) recognized the iGPU as "raphael_mendocino", and is loading the GFX1036 (Raphael) instruction set as evidenced by glxinfo.

Another interesting thing is that the Geeks3D vulkan RT demo works, though it is slow, about 6-12fps, to be expected with only two RAs but I feel like there's still potential for HIPRT accel for Blender here.

I think (from the perspective of a non-programmer here) that you guys can tackle implementing Raphael's (desktop Ryzen 7000) iGPU as well as Mendocino in one go. If this feels like enough information then I'll gladly close it.

> That said, in practice a lot of cards actually just work. The list of possible targets to compile to is here: https://www.llvm.org/docs/AMDGPUUsage.html#processors which you will notice there isn't even a target for gfx1037 in the compiler (and it's not mentioned in the SDK anywhere). So for this APU, sorry it doesn't look like this is possible right now. Not sure if you want to keep the issue open or close or just check back when there is a future version of the SDK. I booted my linux install on the Mendocino machine and it seems that the RadeonSI driver (which uses LLVM) recognized the iGPU as "raphael_mendocino", and is loading the GFX1036 (Raphael) instruction set as evidenced by glxinfo. Another interesting thing is that the Geeks3D vulkan RT demo works, though it is slow, about 6-12fps, to be expected with only two RAs but I feel like there's still potential for HIPRT accel for Blender here. I think (from the perspective of a non-programmer here) that you guys can tackle implementing Raphael's (desktop Ryzen 7000) iGPU as well as Mendocino in one go. If this feels like enough information then I'll gladly close it.

We recently enabled gfx1036 here: #110907 (comment)

You can try that. Not sure why one is reporting gfx1037

We recently enabled gfx1036 here: https://projects.blender.org/blender/blender/pulls/110907#issuecomment-995693 You can try that. Not sure why one is reporting gfx1037
Author

Is there any CI builds for that specific branch or should I be compiling it myself? I'll take a look after upgrading to Win11 IoT in a bit.

Is there any CI builds for that specific branch or should I be compiling it myself? I'll take a look after upgrading to Win11 IoT in a bit.

It’s in the link look for “download here”

It’s in the link look for “download here”
Author

I can confirm that HIPRT now works perfectly without crashing with the latest alpha build (seems to be build f04bd961fd) and driver 24.2.1 (24019.1006).
image

I can confirm that HIPRT now works perfectly without crashing with the latest alpha build (seems to be build f04bd961fd1e) and driver 24.2.1 (24019.1006). ![image](/attachments/ba7a5881-c504-419b-be2c-a431f9da872c)
521 KiB
Blender Bot added
Status
Archived
and removed
Status
Needs Info from Developers
labels 2024-02-28 04:09:25 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#111019
No description provided.