graphics: Check LLVMpipe for Linux software render#202
Open
mihawk90 wants to merge 1 commit into
Open
Conversation
Member
|
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? |
Contributor
Author
|
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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: