The instructions in the last post did the trick with loading the driver (omaplfb), thanks However I have no clear way of telling if hardware rendering is being used. Running glxinfo reveals SGI once again Is there an alternative CLI tool around that can provide details about the video driver that is used?
The instructions in the last post did the trick with loading the driver (omaplfb), thanks However I have no clear way of telling if hardware rendering is being used. Running glxinfo reveals SGI once again Is there an alternative CLI tool around that can provide details about the video driver that is used?
That’s as far as I got… What you have now is all that John needed to run qt 5.1 in ews? mode. I also think it’s enough for Wayland egl mode, but don’t have much to show for that yet either. So, that’s as far as we got.
Ran glxgears and the tool reported an average of 32 FPS which is average. Before loading the driver the average was 28 FPS. CPU load is still around 100%, something seems a bit off…
Strange that the sample JavaFX 8 program still doesn’t work even though it requires EGL 2.0 support from the video driver. Still getting the same errors like the following for example:
ant -f /home/a_user/NetBeans_Projects/JavaFX_Test -Dremote.platform.rp.target=linuxarmvfphflt-15 -Dremote.platform.password=***** -Dremote.platform.rp.filename=linuxarmvfphflt -Dremote.platform.java.spec.ver=18 run-remote init: Deleting: /home/a_user/NetBeans_Projects/JavaFX_Test/build/built-jar.properties deps-jar: Updating property file: /home/a_user/NetBeans_Projects/JavaFX_Test/build/built-jar.properties compile: Detected JavaFX Ant API version 1.3 jfx-deployment: jar: Connecting to xxx.xxx.xxx.xxx:22 cmd : mkdir -p '/home/ubuntu/NetBeans_Projects/JavaFX_Test/dist’ Connecting to xxx.xxx.xxx.xxx:22 done. profile-rp-calibrate-passwd: Connecting to xxx.xxx.xxx.xxx:22 cmd : cd ‘/home/ubuntu/NetBeans_Projects/JavaFX_Test’; ‘/home/ubuntu/ejre-1.8.0_fx/bin/java’ -Dfile.encoding=UTF-8 -jar /home/ubuntu/NetBeans_Projects/JavaFX_Test/dist/JavaFX_Test.jar libEGL warning: DRI2: xcb_connect failed libEGL warning: DRI2: xcb_connect failed libEGL warning: GLX: failed to load GLX eglInitialize failed! Graphics Device initialization failed for : es2 Error initializing QuantumRenderer: no suitable pipeline found
Very similar error messages when trying to run the sample JavaFX 8 program
remotely (via SSH). Robert can you please confirm if you can run one of the
SGX demos (eg Magic Lantern) successfully, and post the results from running
the fbset -i and es2_info commands (locally).
Updated the OpenGL ES libraries so that the SGX ones are used. Ran the Magic Lantern demo again locally and ended up with different error messages appearing like the following:
Restarted the rc.pvr daemon without any issues. Ran the demo (Magic Lantern) again and ended up with the following errors:
ubuntu@arm:/opt/gfxsdkdemos/ogles2$ ./OGLES2MagicLantern
Can’t open keypad input device (/dev/input/event0)
PVRShell: EGL 1.4 initialized
Exit message has been set to: "PVRShell: Unable to create surface
".
InitAPI failed!
PVRShell: Unable to create surface
Have a funny feeling that I am getting very close to remotely running the sample JavaFX 8 program without any issues. Currently the following errors occur when running the sample JavaFX 8 program remotely, provided the rc.pvr daemon on the BBB is running:
Have a funny feeling that I am getting very close to remotely running the sample JavaFX 8 program without any issues. Currently the following errors occur when running the sample JavaFX 8 program remotely, provided the rc.pvr daemon on the BBB is running: