-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
Could not resolve EGL procedure eglCreatePlatformWindowSurface #328
Comments
Yep that could be the case. Can you try the |
Hi Thank you, I have tried the branch. For me, it looks like it still tries to resolve the Do I need to change something in the Header file to "force" it into another GL "mode"? Can I somehow provide more debug informations?
|
You can compile flutter-pi in debug mode: The error is actually not that it can't resolve I just pushed a some commits that makes it fall back to EDIT: Also, does kmscube work for you? |
With the branch updated, I now Interestingly get a Segmentation fault. Will try the other things you suggested tomorrow:
|
Interesting. Have you already configured debug mode yet with Btw, in this repo, it seems like there's multiple variants of libmali for different window systems. Can you make sure you're linking against the |
Oops, didn't notice that assertion is just active in Debug, sorry (logical, no question) So with debug, we indeed get a assert:
The same build without debug runs into a Segmentation fault:
After removing the assert on :501 also the debug build runs into a Segmentation fault. Running it with gdb results in this:
Both tested with commit be323fc. kmscube seems to run:
Need to double check the results later.. |
Ah, I know what's going on. Seems like your GPU doesn't support modifiers. In that case the whole The code in Lines 1331 to 1365 in be323fc
|
Just wanted to push the fix, but github seems to have problems 🤷♂️ https://www.githubstatus.com/ |
Can you try: 599d5d6 |
Wow, thank you, you are lightning fast! Looks like this commit runs fine. Unfortunately, I don't have access to the device/screen right now to check if it also displays something useful.. Will check tomorrow.
|
Only sometimes 😄
sounds good 👍 |
It seems to work, also with way better performance than Software rendering. But something is weird, I was just able to get it displaying something when lightdm runs at the same time. Not yet sure if this is a weird thing of this Rockchip BSP or where this behavior is coming from. I will check later if I can further narrow that down. (Just tested with running the flutter app in debug, still need to test it with a release flutter app build) |
does it log any errors when it doesn't display something? can you do |
Hello
A you said, I used |
@AndroidDesigner yep that's the final solution for this issue. I'll merge Though, just for reference, what board are you using? Btw, since it's DSI and the display does not have dimensions set, flutter-pi just assumes it's official Raspberry Pi 7inch display and uses those dimensions ( Those are obviously wrong in your case so it's best to specify the correct dimensions via command-line |
I'm using this debian 10 touch panel (aarach64)
My Touch Panel is 1280*800 and the rendering is good. But as I said here, I don't know why the touch does not work correctly (although touch is working fine in its desktop environment, and I know the flutter-pi does not use X11). |
I found a solution for the touch problem too with the help of this issue. |
Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. If you find this problem please file a new issue with the same description, what happens and logs. All system setups can be slightly different so it's always better to open new issues and reference the related ones. Thanks for your contribution. |
Hi
I'm trying to get the flutter-pi project working on a Rockchip PX30 Board. My setup consists of the Rockchip/Linaro Debian 10 rootfs and their 4.4 Kernel.
The glmark2-es2 utility is running fine on this Board. But flutter-pi isn't able to resolve the eglCreatePlatformWindowSurface. Is it possible that the Rockchip implementation doesn't implement this procedure, or is another configuration issue more likely?
The text was updated successfully, but these errors were encountered: