supertux2 is going to need some optimization of controls and some video optimizations to run well. I am getting 8-25 fps on it though, so - playable as proof of concept anyway. Before anyone goes bashing on it, Supertux2 can make my sons Sony Vaio 17" 8 core 16GB RAM with Nvidia graphics...
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.
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?
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...
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.
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...
Found it. Error exists between keyboard and screen. I had left the 3 off of DRI3.
Testing.
1597340324
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...
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.
The keyboard errors I was getting above where when booting to full-on command line with no graphics. Now that I have graphics and Mate is alive, the keyboard mapping seems to be fine and I can type | {}[] and all sorts of characters. Apparently a good chunk of the Fn layer mappings are handled...
Slide show of the opening screen closed out. Errors in command line menu.
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
Getting there - but...
From the instructions on page 7 of the thread, my next step is glxgears.
#glxgears
bash: glxgears: command not found
apt install glxgears
E: Unable to locate package glxgears
So - hmm.
Ahh - order of operations error then.
I did OS image - got keyboard error - installed Dave's boot to get past keyboard error - then no graphics - to this troubleshooting.
Daves boot file must require that to already be installed. Going to see if I can get it to now.
The point of me struggling through the process is so that the devs working 'way too high for me' can know what the rest of us will run into.
I just happen to be in a good position to show them an example of 'stumbling in the dark'.
Then wait I shall.
I suspect that a lot of the issues I'm encountering may stem from disconnects between the version of the OS available for me to download and the version(s) that the devs are currently using. I'm not sure how to, 'catch up'.
The grep of out returns nothing.
To make sure, I re-ran it then did: nano out
out has 1108 lines
I searched it with nano to see if I could find the string 'omap' in it - search wrapped, nothing.
And thank you for including the rm out to clean up. :-)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.