So, let me break this down: We don't support RPi as a server platform for VirtualGL. You are asking for support on something that is not supported and may not even be supportable in the context of this project. You are attempting to do something that no one else has attempted, so you're pretty much on your own for troubleshooting.
I don't know for sure whether RPi even supports accelerated GLX. It may not. That question is for another forum, not this one. I am simply saying that accelerated GLX is a prerequisite for using VirtualGL, in its current form, with that platform. Using VirtualGL in its current form may or may not even be useful for what you're ultimately trying to do. You are trying to run OpenGL ES applications remotely, but most OpenGL ES applications are not X applications. VirtualGL and TurboVNC only work with X/GLX applications. VirtualGL could be extended to support X/EGL applications, thus providing OpenGL ES support for the small subclass of OpenGL ES applications that are also X applications. However, most OpenGL ES applications are not X applications, so this would be of very limited benefit. This is not going to be the appropriate forum to ask for support in bringing up accelerated drivers and accessing your GPU through the X server. You need to ask people more familiar with RPi about that. Assuming you can get the accelerated drivers up and running and access your GPU through the X server, then please post here if you are still having problems that are specific to VirtualGL. If you have any further information regarding the types of OpenGL ES applications you want to run remotely, information that might affect my assessment of the general usefulness (or lack thereof) of adding OpenGL ES support to VirtualGL, then please follow up. On 4/13/14 1:12 PM, George Profenza wrote: > Thank you ! This is starting to make sense, little by little. > > I was looking for a GLX extension through the available packages: > " > libegl1-mesa - free implementation of the EGL API -- runtime > libgl1-mesa-dev - free implementation of the OpenGL API -- GLX > development files > libgl1-mesa-dri - free implementation of the OpenGL API -- DRI modules > libgl1-mesa-dri-dbg - Debugging symbols for the Mesa DRI modules > libgl1-mesa-dri-experimental - free implementation of the OpenGL API -- > Extra DRI modules > libgl1-mesa-dri-experimental-dbg - Debugging symbols for the > experimental Mesa DRI modules > libgl1-mesa-glx - free implementation of the OpenGL API -- GLX runtime > libgl1-mesa-glx-dbg - Debugging symbols for the Mesa GLX runtime > libgl1-mesa-swx11 - free implementation of the OpenGL API -- runtime > libgl1-mesa-swx11-dbg - free implementation of the OpenGL API -- > debugging symbols > libgl1-mesa-swx11-dev - free implementation of the OpenGL API -- > development files > libopengl-perl - Perl interface providing graphics display using OpenGL > libswt-glx-gtk-3-jni - Standard Widget Toolkit for GTK+ GLX JNI library > libva-glx1 - Video Acceleration (VA) API for Linux -- GLX runtime > libxcb-glx0 - X C Binding, glx extension > libxcb-glx0-dbg - X C Binding, glx extension, debugging symbols > libxcb-glx0-dev - X C Binding, glx extension, development files > mesa-utils - Miscellaneous Mesa GL utilities > rss-glx - Really Slick Screensavers GLX Port > " > I went ahead and installed libegl1-mesa-dev libgl1-mesa-glx > libswt-glx-gtk-3-jni libva-glx1 libxcb-glx0 mesa-utils > but xdpyinfo still doesn't list a GLX extension. I'm currently looking > at mesa (http://www.mesa3d.org/egl.html) > and thinking about compiling from source with "egl_glx". Will that > enable the GLX extension I need or allow me to > view gl content through vnc (even if not hardware accelerated) ? > > I had a quick look at the Raspberry Pi specs again: > The GPU is Broadcom's VideoCore > IV(http://www.broadcom.com/products/BCM2835), > currently sharing 128MB from the 512MB available on the system. > > From what I understand from "the presence of accelerated 3D drivers > (i.e. the GLX vendor > strings and the OpenGL renderer string should not have the word > "software" or "Mesa" in them.)" the above will not completely resolve > the problem and I won't be able to use VirtualGL, correct ? > > Will I be able to see a EGL content through a vnc connection even if not > hardware accelerated ? > > All my best, > George ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
