-
Notifications
You must be signed in to change notification settings - Fork 195
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
chromium-ozone-wayland: eglCreateContext: Requested version is not supported #849
Comments
As mentioned in e.g. OSSystems#849, `--use-gl=egl` doesn't work any more. We can replace it with `--use-gl=angle --use-angle=gles-egl`, or just `--use-angle=gles-egl` as ANGLE is the default.
It might be related to Angle. Please see https://issues.chromium.org/issues/326752458 . I wonder what happens if you try use desktop implementation via --use-angle=gl-egl |
With |
Can you try #850 ? |
Yes I can only run with Angle now. So I only have Hardware acceleration works for the most part when using Angle. See the report: |
Can you try |
Interesting, with
But when I check the report: I can see that Angle still decided to use the OpenGL ES Mesa driver instead of regular GL. Now when I try to display the WebGL aquarium demo, I'll get the following error on the console:
The webpage itself will display:
So if I understand it correctly, it seems that Angle decided to use the Mesa OpenGLES driver instead of the regular GL driver. The question I have it, why didn't it select the regular GL driver instead:
Perhaps the supported version GL version 2.1 is not sufficient for Angle/WebGL ? |
Yeah that's probably it. I've switched to the proprietary binary driver from ARM which unfortunately only supports OpenGLES 3.1 on X11 and WebGL is working just fine when running on the Ozone X11 platform. So the reason for the So I can confirm that the change in PR #850 works across both X11 and Wayland. |
As mentioned in e.g. #849, `--use-gl=egl` doesn't work any more. We can replace it with `--use-gl=angle --use-angle=gles-egl`, or just `--use-angle=gles-egl` as ANGLE is the default.
Does https://webglsamples.org/aquarium/aquarium.html work for you? afaict that's using WebGL 1, and that should only require OpenGL ES 2.0 according to MDN. |
That was the exactly the demo I was trying. Then when I open the aquarium demo, the webpage will display: That's why I think Angle will fail to initialize the WebGL backend, because I don't have OpenGL(ES) 3.x or higher. |
Hi @msisov , |
When I run chromium-ozone-wayland on my armv7 board using the Panfrost mesa drivers, I always get the following error:
The browser runs fine otherwise and seems fully accelerated except for WebGL.
Is it possible I could get more verbose information regarding the above error?
My chromium flags:
--ozone-platform=wayland --enable-wayland-ime --use-gl=angle --use-angle=gles-egl --use-cmd-decoder=passthrough --ignore-gpu-blocklist --ignore-gpu-blacklist --enable-accelerated-video-decode --enable-features=VaapiVideoDecoder,VaapiVideoEncoder --gtk-version=4 --disable-gpu-memory-buffer-video-frames
By the way:
--use-gl=egl
doesn't seem to work anymore and needs to be replaced with:--use-gl=angle --use-angle=gles-egl
or--use-gl=angle --use-angle=gl-egl
The text was updated successfully, but these errors were encountered: