Help with GPU

Hi,

Usually when I get a new SBC one of the things I like to try out is to test the GPU. Usually I start with running glxinfo, but I’m get the error:

$ glxinfo
name of display: :0.0
Error: couldn't find RGB GLX visual or fbconfig

Is there anything that I can use to test the GPU? I can see the driver option when I reconfigured the kernel, but somehow after reconfiguring I can’t seem to find anything that suggests the GPU exists.

3 Likes

Maybe this will help:

not sure was a random google search from the error

The GPU in the VF2 doesn’t support OpenGL, it does support EGL and GLES2 though. You can use the es2gears_x11 (or es2gears_wayland) demos to test the GPU.

You can also prepend the commandline with vblank_mode=0 to run unconstrained by vsync, eg vblank_mode=0 es2gears_x11 within an X session

2 Likes

for some scenarios maybe gl4es: GitHub - ptitSeb/gl4es: GL4ES is a OpenGL 2.1/1.5 to GL ES 2.0/1.1 translation library, with support for Pandora, ODroid, OrangePI, CHIP, Raspberry PI, Android, Emscripten and AmigaOS4. works - it wrapps opengl around gles in the form of a shared library which you simply ld-preload via LD_LIBRARY_PATH … it worked for me quite well for several arm systems with mali gles blobs … this is how i built it for those arm systems, so similar options might maybe work on the vf2 (not yet tested it myself yet): mesa-etc-build/gl4es-build.txt at master · hexdump0815/mesa-etc-build · GitHub

good luck and best wishes - hexdump

2 Likes

it looks like gl4es seems to work to make opengl somehow work - i did not successfully try it myself, but the gl4es author has it working, so i guess it should just work - see starfive visionfive2 support? · Issue #420 · ptitSeb/gl4es · GitHub

Imaginationtech sad IMG BXE-4-32 MC1 is supported vulkan.
This means zink is a batter choice for opengl.

1 Like
2 Likes