-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
starfive visionfive2 support? #420
Comments
I just built with default option, in |
@ptitSeb - thanks a lot for the quick response - will give it a try this way soon |
As a followup: https://www.reddit.com/r/RISCV/comments/11vtqkf/video_of_superhexagon_running_on_visonfive2_riscv/ here is gl4es in action on the Vision Five 2 :) Also note that the SDL2 version built on the default Debian image is build only with GLES2 support, so if you need to use OpenGL, you need to build a custom SDL2 and not use the system one (still using |
i just gave it a try again and i got a bit further ... i think that i have manually setup the gpu stuff properly on my own image (https://github.com/hexdump0815/imagebuilder/releases/tag/230321-02) as the included egl tests seem to work ... glxgears are working as well with gl4es but glmark2 crashes (debug trace below) but it works if i set LIBGL_FB=3 although very slow. do you have any idea what might be wrong? is glmark2 working for you with gl4es? ps: maybe my setup is still not fully ok and the tests just run against get mesa sw renderer? glmark2 debug trace with gl4es, but without LIBGL_FB=3:
|
I don't understand. I have a Vision Five 2, and gles4 is working fine on the default debian image. Not parameter tinkering needed. |
it looks the problem is in the pvr gpu setup in my own image - will have to recheck that ... i guess as soon as i have sorted that out it should work if it works for you on the starfive image |
i just confirmed that it is working fine on the original starfive debian image, so it is really a problem of my setup - sorry for the confusion |
just as a little update: i have it somehow working now on my debian image using the starfive pvr, mesa and xorg binaries ... i was struggling quite a bit why glxgears were working, but glmark2 always failed on my image with "Failed to find suitable GLX FB config" but it worked on the starfive image ... after a lot of debugging i realized that the reson are the different glmark2 versions: 2021.12 in the starfive image and 2023.01 in my debian sid image were the problem - it looks like the newer glmark2 has problems with getting the best fb config ... the 2023.01 version actually works if i explicitely provide the visual config on the cmdline via: "glmark2 --visual-config buf=16:r=8:g=8:b=8:a=8:depth=24:stencil=8" ... glmark2-es2 has the same problem, so i think it is not related to gl4es, which is working quite well so far ... |
i just came across https://www.reddit.com/r/RISCV/comments/11u0a6y/using_box64_gl4es_i_launched_a_pc_game_on_my/ ... do you have written down the steps to make gl4es to work on the vf2 somewhere? i gave it a try a few weeks ago in LIBGL_FB=3 mode trying to get opengl working this way but failed (i think early on with dri auth errors or something similar) also i'm not 100% sure if my gpu setup is working properly. some notes about how you got it working (vf2 gpu side and gl4es side) would be very welcome.
a lot of thanks in advance and best wishes - hexdump
The text was updated successfully, but these errors were encountered: