Hey Guys,
i have so many Problems with the HIP for Blender under Linux (UBUNTU LTS 20.04).
I installed the Driver 22.10 for Ubuntu LTS... correctly, Blender is listing my 6900XT. All is alright then i start the Renderviewport. I can move the Camera and all is fast and it renders but if i change a Material or switch HDRI maps, the Display freezes, short Blackscreen and Display is back but i can't do anything. Music or Videos playing further but i can't do anything on the Desktop i have to reset the Workstation or switch to another TTY to reboot the System.
Is there any Troubleshooting?
I love your Cards guys, i really do, but the Support for Linux is a Total Mess. Please guys do something about that.
Best Regards
Sebastian
From SBL-Multimedia
im having the same issue here, if i try to switch to cycles with HIP enabled i will work for a little bit then crashes the whole display driver and i have to reboot
im using manjaro KDE
I have the same in Ubuntu 22.04 HIP works for me only in the official standalone version from the official site does not work with Flatpak, for example. But also there are problems with viewport. Was it somehow possible to solve the problem? Do you think they will fix it in the new version of Blender 3.5? Or is there a better way to install the driver?
you can ask at AMD Forum's Radeon Pro Render that has a discussion for Blender issues: https://community.amd.com/t5/blender-discussions/bd-p/blender-discussions
Hi,
a few people have this issue on their 6900XT and 6800XT, but so far official help was refused, because only a few -mostly Enterprise Distros like RHEL/SLES- are actually officially supported by ROCm (the part of the AMD Driver you need for HIP in Blender).
We have talked about the issue here:
https://devtalk.blender.org/t/cycles-amd-hip-device-feedback/21400
https://discussion.fedoraproject.org/t/blender-amd-and-opencl/40199/21
This is the issue-ticket on the official driver-gitlab - I invite anyone to join and share their experience so this issue gets more traction and official attention:
No Ubuntu 20.04 and 22.04 is officially is officially suppoprted but it doesn't work. I think that AMD do not care of their customers whant they got the money from them.
Why do many developers do this to us Linux non enterprise users? they neglect the general Linux users and stick to obscure Linux distros. That aside, what's the story for windows then? I tried the very same project file in windows blender and it still crashed the same way, Although not windows but just the gpu driver instead.
It's probably just easier for the devs to support just the Enterprise distros because they are the most stable and don't change software package-versions and kernel versions that often.
Most of the time "general" Linux-users still profit from bug-fixes meant for enterprise-distros though - (that's why I reopened the bug report again when I was able to replicate the issue on SUSE-Linux-Enterprise-Desktop(SLED).
I'm pretty sure if they fix it for the Enterprise-Distros (Ubuntu,SLED,RHEL) it will work with something like Kubuntu/OpenSUSE(Leap)/maybe fedora) too.
Do you have an RDNA2 GPU too? If so you might very well have a very similar issue on windows and it would most likely warrant a separate bug-report from mine (although I have no idea where you could open the ticket for the windows driver)
I'm asking about the GPU, because I remember a separate bug that was reported on RDNA1 GPUs that should be fixed in the newest ROCm as far as I know.
i Hope they get this sorted out for you guys, i went back to Nvidia now, i got work I need to get done.
I have exactly the same problem in viewport with HIP rendering enabled. Do you guys think this will be fixed in the upcoming version of Blender 3.5?
I think they've got us somewhere in the back. I now, bare instalation on Manjaro, Blender 3.5.0, HW AMD 7 5800X, 64GB DDR4, AMD RX5700XT or AMD RX6800XT. Result the same. I move the texture colors, move the scene for a while, it freezes, goes black then the old VESA screen and error message about wrong directory rights to save the error message appears and restarts Manjaro from the password. All tested 8-apr to 10-apr-2023,. Not working Flatpak distribution, Manjaro comunitni, build from AUR, just directly downloaded from Blender site with softwareGL but it can't be used.
at the moment a workaround for the problem is to disable the overlay in the blender preview panel. After my short tests it seems to work, the preview in viewport works and does not crash the system. At the moment there is no better solution. Some stubborn user has even made a simple addon to Blender to disable overlay automatically in cycles preview. https://gitlab.freedesktop.org/drm/amd/-/issues/2145?fbclid=IwAR3TeAwpQ-1vqrH0AHEaqWqH9CJSzg2ZpE8oBr....
There is a link and an exemption at the bottom of this forum. AMD it's time for you to make your move. We are really looking forward to improvement and approaching Linux users the same way as the rest of us. We are the same customers as everyone else. Blender will soon become the industry standard for frelancers. If you don't want to lose this group then it's time to act. It would be silly if Intel was the first to release RT support for its cards in Blender.
Absolutely. This behaviour is completely ununderstandable. Maybe the idea is to force users to switch to windows since the pro drivers are really fast ?
Is there any new news regarding viewport crashing when rendering GPU from HIP? I have the latest ROCm 5.6 on Ubuntu and nothing has changed. for a while it looked like the viewport was not crashing, but when it first happened it now freezes the gpu after a short while every time. This forum thread has been going on since 2021. What is the reason that this problem cannot be fixed for such a long time? After all, it makes it impossible to use the program normally. This is how AMD is losing its reputation among Open Souce users.
Since version 5.5, everything works without errors. I work in Manjaro, I have no problem anymore. I mean since May 2023
I am writing this as a warning. Unfortunately, the information that viewport currently works well with Radeon cards on Linux is incorrect. Unfortunately it continues to be unstable. with more advanced scenes the system crashes after a while, some sample demo scenes do not render at all. I'm very much rooting for AMD in their way to make the best GPUs but for 3 years they can't or won't fix this problem. It's sad and frustrating.
I will attempt to add as much information as I can as I've had this issue for multiple versions of Blender in linux not utilizing my GPU and the problem is always following what AMD says I should do to make it work.
CPU:3600
GPU:7600
RAM:16GB
latest mobo bios
Linux Mint 21 6.5 kernels and quite a few of the older ones as well.
back with blender3.5+ I've been trying to get my radeon used by blender. I've downloaded rocm, cleared the previous nvidia settings as I switched over from a PNY P2200. I'm knowledgeable enough to play around in root and install things from tars in the terminal and the like. It will just take me a little longer than others just because that's how my brain works with these things.
That said, I've gotten multiple things working in here such as wine for my older games and data recovery for a friends harddrive their computer wouldn't read.
If i clear the config file and start blender fresh it opens, runs and all of that. As soon as I try to look at the preferences, Blender crashes and sometimes it crashes my entire os. Trying to switch to cycles appears to do the same thing.
I have no crashing issues while using my other main 3d software; which is Cura.
rocm on my system is version 6.0.2
multiple times I've followed the documentation for installing rocm and getting the dependencies set up for radeon, I've even paired back my installation to barebones and started from scratch to make sure things were installed as stated and as I type right now I have blender frozen in my other window after trying to toggle HIP choices.
I would suggest someone grab a test bench pc, give it a fresh Linux install (because I've seen people with various Linux flavours reporting this in various forums) and then install blender. Do nothing else and run blender with some form of test file then try to run GPU rendering, or cpu+gpu rendering. It doesn't seem like whoever is in charge of implementing code changes and whatnot has done this. Not everyone using linux is Wendel or Phoronix, we're trying to learn and learn we do but I feel like a vast majority of the issues that are reported by people could be cut off before release if someone from AMD would just try to install and use the hardware like general people would and then put that into the documentation. I get it, this costs time and money and apparently the linux base is small enough to be deemed inconsequential, however my rebuttal is Nvidia does everything they can to make sure their cards work with little extra steps from users that's part of the reason for their market share.
Listen I'm just trying to start a new project and this issue really brought an axe down on my thought space sorry that i'm coming off as annoying and entitled.