-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[Bug]: Unable to use OpenGL ES backend with ANGLE #23042
Comments
I've been doing some more research on this and running |
Unsure if it's related but
but |
It seems that |
@licy183 commenting that line out, doesn't fix the issue for me. I tried commenting the other overrides out as well and it errors out in every case
|
Oh you were responding to my first post. Thank you, that does fix my issue. The OpenGL ES backend is working perfectly now. Any idea what is causing the second error? |
The vendored OpenGL driver shipped for Mali GPU doesn't work out of box with |
Does it work for Adreno GPUs? If it does, could support theoretically be added for Mali GPUs to work out of the box with |
It is theoretically possible, but issues about running virgl directly over Mali's OpenGL is much difficult to resolve.
|
Great information, thank you. One last question. Is it possible to use WebGL with llvmpipe? I tried on both Firefox and Chrome, but both think there is no OpenGL support. The commands I used using the xfce4 script were |
IIRC both |
Chrome says "Your browser supports WebGL" but fails to show the cube and the WebGL Aquarium demo errors out. The console logs: Firefox says "Your browser supports WebGL" and shows the cube spinning, but the WebGL Aquarium demo fails to run. The console logs: output from working get.webgl.org WebGL Aquarium works on both browsers when using ANGLE. Firefox with |
@licy183 looking back over this, you say here the Mali GPU vendored driver doesn't work out of the box with Also, I realized I made a mistake and the initial fix actually does not work for me. |
So to recap:
If I'm wrong about any of this, or this is the wrong place to open up an issue for any of these, please let me know. |
I'm not sure what the script
It is answered by the comments about
I'm confirming why this happens. |
It's a pretty small script located here. The equivalent minimal and reproducible code is included with 2. For example, This fails
But this still works somehow
Does Chromium somehow have a way to use vendored drivers that
Ah gotcha, so it was not intended to be used this way, even though it happens to work when
If the problem is there is no vendored Mali GPU support, why does Chromium seem to work with vendored Mali GPU support? Is it using
Sounds good, ty. Appreciate the help. |
I personally think that the reason is the way Chromium calls OpenGL doesn't make Virgl over Mali's OpenGL fail. If Mali's OpenGL is used as virgl, it is recommended to pass
No. It will use the system OpenGL (maybe over ANGLE bundled in chromium). If you're using chromium with |
Problem description
Running OpenGL applications with the OpenGL ES backend provided by
angle-android
causes an error even though it's supported by my GPU.What steps will reproduce the bug?
~/vgl use-angle
,~/vgl angle=gl
, and finally~/vgl glmark2
What is the expected behavior?
glmark2 is able to run its benchmark without issue
System information
The text was updated successfully, but these errors were encountered: