Production Pyra photos/videos/thoughts thread

[daveshah]

export LD_LIBRARY_PATH=/opt/omap5-sgx-ddk-um-linux/lib/:/home/david/gl4es DRI3_VSYNC=1

 

[Grench]

I reran the export string and glxgears again - and noticed that there is the same collection of four errors that I noted above from attempting Supertux2.

 

[Grench]

Found it. Error exists between keyboard and screen. I had left the 3 off of DRI3.
Testing.

Post automatically merged: Aug 13, 2020

Supertux2 still in slideshow mode and generating the errors:
LibGL error: MESA-LOADER: failed to retrieve device information
LibGL error: unable to load driver: omapdrm_dri.so
LibGL error: driver pointer missing
LibGL error: failed to load driver: omapdrm

Post automatically merged: Aug 13, 2020

I'm on Central time. Time for the midday cessation of activities for the consumption of mass quantities. I'll be back on after a bit.

 

[daveshah]

Is libGL.so.1 in the `/home/.../gl4es` folder and did you change `david` to your own username?

Post automatically merged: Aug 13, 2020

If everything is working correctly and gl4es used rather than soft OpenGL you should see as output:

LIBGL: Initialising gl4es
LIBGL: v1.1.3 built on Jun  7 2020 21:34:13
LIBGL: Using GLES 2.0 backend
LIBGL: loaded: libGLESv2.so
LIBGL: loaded: libEGL.so
LIBGL: Using GLES 2.0 backend
LIBGL: Hardware Full NPOT detected and used
LIBGL: Extension GL_EXT_blend_minmax  detected and used
LIBGL: Extension GL_EXT_draw_buffers  detected and used
LIBGL: FBO are in core, and so used

 

[TrashyMG]

apt-cache search name-of-whatever

or just "apt search name-of-whatever" the apt command has improved a bit over the years. can install and search from the single command.

 

[Grench]

Is libGL.so.1 in the `/home/.../gl4es` folder and did you change `david` to your own username?

Post automatically merged: Aug 13, 2020

If everything is working correctly and gl4es used rather than soft OpenGL you should see as output:

LIBGL: Initialising gl4es
LIBGL: v1.1.3 built on Jun  7 2020 21:34:13
LIBGL: Using GLES 2.0 backend
LIBGL: loaded: libGLESv2.so
LIBGL: loaded: libEGL.so
LIBGL: Using GLES 2.0 backend
LIBGL: Hardware Full NPOT detected and used
LIBGL: Extension GL_EXT_blend_minmax  detected and used
LIBGL: Extension GL_EXT_draw_buffers  detected and used
LIBGL: FBO are in core, and so used

I included 'david' - I figured this was your own version of code to later be pulled into the main Pyra kernel. Doh!

Fixing and testing...

 

[Grench]

I ran:
# export LD_LIBRARY_PATH=/opt/omap5-sgx-ddk-um-linux/lib/:/home/grench/gl4es DRI3_VSYNC=1

And still get:
$ Supertux2
Slide show with errors:
LibGL error: MESA-LOADER: failed to retrieve device information
LibGL error: unable to load driver: omapdrm_dri.so
LibGL error: driver pointer missing
LibGL error: failed to load driver: omapdrm

So close, but seems to be missing something.

 

[Blue Shadow]

does /home/grench/gl4es exist?

 

[daveshah]

Can you run 'ldd /usr/games/supertux2' (after running the export command) and make sure in the output that libGL.so.1 is pointing to the copy you put in that folder?

 

[Grench]

does /home/grench/gl4es exist?

No

 

[daveshah]

The instructions have a download link to libGL.so.1 to put in that folder.

 

[Grench]

The instructions have a download link to libGL.so.1 to put in that folder.

Ahh - I see it now. I had thought all of the commands were in the code boxes.

So - installing Chromium on my Pyra (no web browser by default) so I can download the file directly to it.

 

[Grench]

Chromium installed, zip file downloaded, extracted, folder created, file copied.
home/grench/gl4es/libGL.so.1 now exists.
Ran the export command as:
# export LD_LIBRARY_PATH=/opt/omap5-sgx-ddk-um-linux/lib/:/home/grench/gl4es DRI3_VSYNC=1
Should that have or not have created a file in the folder? I see no signs or feedback from running the export command. How do I know it was successful or not?

 

[daveshah]

The ldd command I mentioned a few posts up is a good way to check that LD_LIBRARY_PATH is set up correctly.

 

[Grench]

The ldd command I mentioned a few posts up is a good way to check that LD_LIBRARY_PATH is set up correctly.

# ldd /usr/games/supertux2

Took me a bit to find the right line in the output.
libGL.so.1 => /home/grench/gl4es/libGL.so.1 (0xb664d000)

 

[daveshah]

That looks good, I would now expect supertux2 to work properly.

 

[Grench]

That looks good, I would now expect supertux2 to work properly.

grench@Marble:/usr/games$ supertux2

Slide show with errors:
LibGL error: MESA-LOADER: failed to retrieve device information
LibGL error: unable to load driver: omapdrm_dri.so
LibGL error: driver pointer missing
LibGL error: failed to load driver: omapdrm

Hmm. Where should omapdrm_dri.so be?

 

[daveshah]

I see a change between # and $, export and running supertux2 should all be in the same terminal.

omapdrm_dri.so does not exist and is a sign that the wrong libGL is still being used.

 

[Grench]

I see a change between # and $, export and running supertux2 should all be in the same terminal.

omapdrm_dri.so does not exist and is a sign that the wrong libGL is still being used.

Success. Thank you!

Still a bit slow at 1280x720 full screen, but then I have 8 other things running at the same time. I'm going to reboot and try it again. But - you found the key. I was doing all of what I saw as 'system stuff' from the root prompt and trying to launch from the user prompt.

 

[daveshah]

I am not sure if gl4es will actually be setup as the default system wide as I've seen some desktop stuff behave a bit strangely with it in LD_LIBRARY_PATH.

It is more likely that things will follow the Pandora, and stuff that needs OpenGL rather than GLES will add gl4es to LD_LIBRARY_PATH inside their dbp launch script.