Blender crashes on Fedora, AMD Radeon RX 6700 XT build #121079

Closed
opened 2024-04-25 16:26:52 +02:00 by Danny-59 · 3 comments

System Information
Operating system: Linux-6.8.7-300.fc40.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI
Graphics card: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 17.0.6, DRM 3.57, 6.8.7-300.fc40.x86_64) AMD 4.6 (Core Profile) Mesa 24.0.5 (git-7737614720)

Blender Version
Broken: version: 4.1.1, branch: blender-v4.1-release, commit date: 2024-04-15 15:11, hash: e1743a0317bc
Worked: (newest version of Blender that worked as expected)

Short description of error
Blender crashes on launch since switching to AMD GPU on Linux (Fedora 40, Wayland)

Exact steps for others to reproduce the error

Ever since switching from an NVidia GPU to an AMD GPU (Radeon RX 6700 XT) on my linux build, blender crashes on launch; the only method that runs blender is oddly through the terminal (flatpak run org.blender.Blender; any other means of launching the application fails) - but when doing so, the GPU is not recognized by Blender (e.g. in the preferences > system > cycles render devices, there is no option available under HIP). Notably, other applications recognize the GPU; only Blender does not. Lastly, uninstalling and reinstalling Blender from other repos (Fedora flatbaks, Fedora RPMs) does not resolve this issue

**System Information** Operating system: Linux-6.8.7-300.fc40.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI Graphics card: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 17.0.6, DRM 3.57, 6.8.7-300.fc40.x86_64) AMD 4.6 (Core Profile) Mesa 24.0.5 (git-7737614720) **Blender Version** Broken: version: 4.1.1, branch: blender-v4.1-release, commit date: 2024-04-15 15:11, hash: `e1743a0317bc` Worked: (newest version of Blender that worked as expected) **Short description of error** Blender crashes on launch since switching to AMD GPU on Linux (Fedora 40, Wayland) **Exact steps for others to reproduce the error** Ever since switching from an NVidia GPU to an AMD GPU (Radeon RX 6700 XT) on my linux build, blender crashes on launch; the only method that runs blender is oddly through the terminal (flatpak run org.blender.Blender; any other means of launching the application fails) - but when doing so, the GPU is not recognized by Blender (e.g. in the preferences > system > cycles render devices, there is no option available under HIP). Notably, other applications recognize the GPU; only Blender does not. Lastly, uninstalling and reinstalling Blender from other repos (Fedora flatbaks, Fedora RPMs) does not resolve this issue
Danny-59 added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2024-04-25 16:26:53 +02:00
Member

The flatpak and Fedora RPM Blender versions are not maintained by the Blender foundation and the Blender foundation can not garuntee they work properly. For future testing, please use versions of Blender from the Blender founadtion: https://www.blender.org/download/

Does clearing your Blender config help with this issue? To do this, go to $HOME/.config/ and rename the folder blender to something like blender-backup then try opeing Blender.

The flatpak and Fedora RPM Blender versions are not maintained by the Blender foundation and the Blender foundation can not garuntee they work properly. For future testing, please use versions of Blender from the Blender founadtion: https://www.blender.org/download/ Does clearing your Blender config help with this issue? To do this, go to `$HOME/.config/` and rename the folder `blender` to something like `blender-backup` then try opeing Blender.
Alaska added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-04-25 17:36:36 +02:00
Author

Thank you for the prompt reply!

I was not aware that the RPM and Flatpaks were not officially maintained. That being said, I have experimented with a few things:

  1. Downloading and running the official Linux Blender 4.1.1 build from https://www.blender.org/download/ does successfully open the app without crashing, but the GPU is still not recognized. In practice, it seems to originally behave the same as running the Flatpak through the terminal ("flatpak run org.blender.Blender").

  2. Clearing the Blender config file from $Home/.config/ (either by renaming it or by deleting it) did not resolve the issue - this is true for both the official Blender build and the Flatpak.

  3. Interestingly, in the Flatpak permissions, if I remove the Blender Flatpak's permission for "Direct Graphic Rendering", the Flatpak runs like in bullet (1), i.e. like running the official Blender build or running the Flatpak through the terminal ("flatpak run org.blender.Blender").

  4. I'm not sure if this is the direct solution or a temporary fix, but following the instructions on https://fedoraproject.org/wiki/SIGs/HC to install HIP on Fedora:

sudo dnf install rocm-hip
sudo dnf install rocm-hip-devel

allows the official Blender build to recognize the GPU, and seems to work in most cases. However, the Flatpak running with the "direct graphic rendering" setting turned off, nor the Flatpak running through the terminal ("flatpak run org.blender.Blender"), recognizes the GPU.

In summary: it seems the only use case that works is installing HIP as in bullet (4) above, and then running the official Blender build; only then does Blender run without crashing, and recognize/uses the GPU.

I'm still not entirely certain about the exact cause of the issue, as other applications or video games can utilize the GPU without any of the steps above; so far only Blender has had these limitations.

Thank you for the prompt reply! I was not aware that the RPM and Flatpaks were not officially maintained. That being said, I have experimented with a few things: 1. Downloading and running the official Linux Blender 4.1.1 build from https://www.blender.org/download/ _does_ successfully open the app without crashing, but the GPU is still not recognized. In practice, it seems to originally behave the same as running the Flatpak through the terminal ("flatpak run org.blender.Blender"). 2. Clearing the Blender config file from $Home/.config/ (either by renaming it or by deleting it) did not resolve the issue - this is true for both the official Blender build and the Flatpak. 3. Interestingly, in the Flatpak permissions, if I remove the Blender Flatpak's permission for "Direct Graphic Rendering", the Flatpak runs like in bullet (1), i.e. like running the official Blender build or running the Flatpak through the terminal ("flatpak run org.blender.Blender"). 4. I'm not sure if this is the direct solution or a temporary fix, but following the instructions on https://fedoraproject.org/wiki/SIGs/HC to install HIP on Fedora: ``` sudo dnf install rocm-hip sudo dnf install rocm-hip-devel ``` allows the official Blender build to recognize the GPU, and seems to work in most cases. However, the Flatpak running with the "direct graphic rendering" setting turned off, nor the Flatpak running through the terminal ("flatpak run org.blender.Blender"), recognizes the GPU. **In summary**: it seems the only use case that works is installing HIP as in bullet (4) above, and then running the official Blender build; only then does Blender run without crashing, and recognize/uses the GPU. I'm still not entirely certain about the exact cause of the issue, as other applications or video games can utilize the GPU without any of the steps above; so far only Blender has had these limitations.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2024-04-28 03:44:58 +02:00
Danny-59 reopened this issue 2024-04-28 03:45:09 +02:00
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2024-04-28 03:45:11 +02:00
Member

Since installing the HIP package (which is required to use HIP in Blender) and running the official Blender version resolves the issue, then this issue is resolved and I will be closing it.

The issues with the flatpak and RPM versions of Blender should be brought up with the maintainers of those packages.

Since installing the HIP package (which is required to use HIP in Blender) and running the official Blender version resolves the issue, then this issue is resolved and I will be closing it. The issues with the flatpak and RPM versions of Blender should be brought up with the maintainers of those packages.
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2024-04-28 03:54:39 +02: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
2 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#121079
No description provided.