graphics: Check LLVMpipe for Linux software render#202
Conversation
|
This seems fine. Just to confirm, there isn't really any kind of generic article/guide that could be linked or written on common issues here? It's just a bit too environment specific? |
|
None that I know of no. llvmpipe is just the fallback software renderer. I don't think a KB article would make sense here. It really only happens in the mentioned scenarios, one of which we don't support anyway. edit:
|
|
Doesn't seem necessary, was more just curious if there was a "most of you will have to do this:" kind of thing. If there isn't, this is fine as-is. |
Description
Adds a check for the
Mesa llvmpipesoftware-rendering on Linux. Also adds a potential solution for Flatpak users.Not sure on the wording, feedback welcome.
Motivation and Context
This comes up fairly regularly in linux-support on Discord. The most common cause is an updated NVIDIA driver kernel module. On native packages this also updates the userland libraries, but this is not the case for Flatpak. Running
flatpak updatewill sync the userland libraries for the Flatpak runtime, after which OBS runs on the GPU again.Another cause can be virtualised or containerised environments, which are not supported.
How Has This Been Tested?
Grabbed a log from Discord (truncated to the relevant parts) and ran it through the analyzer:
Types of changes
Checklist: