-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Pipelined Rendering] "Unable to find a GPU" on ChromeOS w/ Crostini/Pengin/Linux (maybe GL related) #3023
Comments
Minor updates. Have since pulled the latest
This is on this commit: c5af133 |
Can you attach a debugger and get a backtrace where it crashes? |
Update: Tried again on 09706cd Still segfaults. I'll look and see how to attach a debugger. |
Can confirm that I'm also having this issue, running on a chromebook, I wanted to try some development using bevy but the examples won't work in crostini (Linux on Chromebooks) because of lack of Vulkan support. Not sure if having an OpenGL fallback would be possible but it'd be nice. |
I get a different kind of error on Crostini.
No stack trace, even with Also, note this is very clearly due to lack of a proper Vulkan driver, which so far, there is not an official one for most Chromebooks. It sounds like others are having similar issues, but these issues are not necessarily bevy's fault (aside from lack of OpenGL support, which is already tracked as #841). Perhaps error handling could be improved, but other than that, I'm not sure what bevy could do about this. The responsibility is primarily on ChromeOS to supply a working copy of the Venus driver for Crostini, or on us as users to try adding it DIY style. |
Bevy version
Pipelined Rendering branch - 432ce72 and also main - 6a8a8c9
Operating system & version
ChromeOS w/ Penguin: Version 94.0.4606.97 (Official Build) beta (64-bit)
ASUS Chromebook C425
What you did
WGPU_BACKEND
togl
, and tried running the pipelined examples, got different errors.What you expected to happen
The examples would run correctly, if the renderer was forced to use GL backend.
What actually happened
Bevy examples paniced due to GPU issues, regardless of graphics backend.
Additional information
Currently Vulkan support is really shoddy on ChromeOS due to running Linux inside of a VM. OpenGL seems to be work much better. I am able to run the current main branch of wgpu examples with no problem (other than some warning about keyboard and caps lock... lol). I'm also able to run other things using OpenGL such as macroquad examples.
This machine does not support Vulkan, as vulkaninfo returns nothing.
Failed to find GPU errors on
pipelined_texture_atlas
exampleDifferent error with wgpu_backend set to gl
Clearly the
wgpu_backend
env var is doing something, but not enough to get the examples to run.The text was updated successfully, but these errors were encountered: