You are not logged in.
Hello I am having trouble with getting Blender working on my PowerColor Fighter RX 6600. I have debugged it and Blender hangs when trying to use hip in the settings of blender. I am at a completely loss. no idea what to do and I'm pulling hair out at this point any help would be appreciated
hw-probe: https://linux-hardware.org/?probe=fee42ea005
gdb output: https://pastebin.com/MitGqppv
blender log: https://pastebin.com/LeDprcfP
Last edited by Ozzy_Helix_ (2024-02-02 19:40:18)
Offline
Is the hip-runtime-amd package installed?
What does this say
/opt/rocm/bin/rocminfoJin, Jîyan, Azadî
Offline
hip-runtime-amd is installed and this is the output of /opt/rocm/bin/rocminfo
https://pastebin.com/iLT7BBhs
Offline
Looks like you'll need the AMDGPU-PRO driver for this. The interface reports that driver "version 22.10 or newer" is needed, which refers to the blobs. Shame. I'm very disappointed about this myself because I've just bought a laptop with a discrete card and I'm very fond of path tracing.
I'm going to see if I can get Mitsuba or PBRT working on the GPU when I have the time. Perhaps try those instead?
Jin, Jîyan, Azadî
Offline
after installing AMDGPU PRO drivers from the instructions on the wiki the system hangs when trying to enable hip on blender
https://wiki.archlinux.org/title/AMDGPU_PRO
Offline
when I say it hangs mouse and keyboard input stop and the screen appears to freeze
Offline
from the testing I just did blender hangs when hip is enabled in the settings but it is random if it takes the system down with it sometimes blender will crash without taking the system down but will cause other apps like latte dock and the kde desktop to become unresponsive to the point I have to force restart the machine
Offline
The amdgpu-pro components useful for Blender and other programs are already in ROCm, there should be no need to install them. I have convinced myself that the problem is an incompatibility between the 6.6 kernel and ROCm 5.7, but I don't have the expertise to find it. Try putting in the LTS kernel, it should work.
Offline
I rebooted into the LTS kernel but now blender can't find a hip device it doesn't crash on the LTS kernel but it can't find the hip device either
Offline
The amdgpu-pro components useful for Blender and other programs are already in ROCm, there should be no need to install them. I have convinced myself that the problem is an incompatibility between the 6.6 kernel and ROCm 5.7, but I don't have the expertise to find it. Try putting in the LTS kernel, it should work.
It is, it seems like there is an issue since October about it.
Last edited by Luciddream (2023-12-20 18:57:55)
Offline
I will try using downgrade to downgrade the linux-zen and linux-zen-headers to 6.1.12 to see if that fixes the issue I doubt it tho
Offline
ok when I downgrade the kernel to before 6.6.7 it can't even detect there is a hip device there
Offline
its the same result as running the LTS 6.1 kernel
Offline
I am trying other kernels but I feel it will likely be the same result either nothing or a crash
Offline
I've discovered going back to any version of 6.5 gets me further along but it still crashes it now displays Hip info in blender before terminating/crashing
Offline
I ended up making a comment on this issue on gitlab I guess I'm just hoping this is fixed in 6.7
Offline
I looked into it and this describes my issue perfectly
https://lists.freedesktop.org/archives/ … 00298.html
Offline
I downloaded the source code for the Zen Kernel version 6.6.8 and compiled it but I patched
drivers/gpu/drm/amd/amdkfd/kfd_flat_memory.cit seems a commit was made to the kernel between 6.5 and 6.6 that made Linux lock up when running blender due to an incompatiblity between rocm and amdgpu this gitlab thread talks about it and provides changes to the kernel that fix the issue it's just bisecting a commit in particular
96c211f1f9ef82183493f4ceed4e347b52849149Offline
the issue appears to be resolved in Linux 6.7.2 but idk if the issue will reappear in the future.
I use the Zen kernel but its fixed in that
Last edited by Ozzy_Helix_ (2024-02-02 18:11:09)
Offline
I've requested that this thread be archived but I get the feeling this issue will reappear in the future I worry this kernel bug will rear its ugly head again at some point in the future
Offline