Hi! There have been some changes on this topic in the last few months so here are my updates:
Recently I decided to upgrade the ROCm version to 5.7 because I needed it for other project. I was curious to see if it would break blender again. Weirdly, it didn’t break at all. The behavior is still what I described previously. So now I’m starting to think that maybe there was an issue with ROCm on 5.7 that got fixed at some point.
As of today I’ve tested with 3 different Blender versions with the different versions of ROCm on the lastest Fedora 39 kernel (6.7.6-200.fc39.x86_64) and this are the results:
| Blender Version | ROCm 5.6 | ROCm 5.7 |
|---|---|---|
| 3.6 | Detects devices and renders | Detects devices and renders |
| 4.0 | Detects devices but crashes on render | Detects devices but crashes on render |
| 4.1 | Didn’t test | Detects devices and renders |
So, this leads me to believe that the issue is with Blender 4.0 and we also had bad timing with other bug from ROCm that got fixed.
For my use case and interests the issue is fixed. I can just use the 4.1 beta or 3.6 for stability. Sadly the 4.0 release is borked but I understand that it will be soon replaced by 4.1.