Skip to content

Conversation

@refi64
Copy link
Collaborator

@refi64 refi64 commented Aug 4, 2023

Chromium needs to load the drivers before entering the BPF sandbox, but it loads them from the merged driver mount point, which results in mesa's attemts to load them from the extension-specific mount point failing. To fix this, set dri-search-path to match the merged mount point, so that mesa will always look there by default.

Chromium needs to load the drivers before entering the BPF sandbox, but
it loads them from the merged driver mount point, which results in
mesa's attemts to load them from the extension-specific mount point
failing. To fix this, set dri-search-path to match the merged mount
point, so that mesa will always look there by default.
@orowith2os
Copy link
Owner

LGTM at first glance, anything other than testing for a reason why this is a draft?

@refi64
Copy link
Collaborator Author

refi64 commented Aug 4, 2023

Definitely just testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants