The second may provide an explanation for why your client program insists on using features of its local X server (the NV GLX driver) - perhaps it thinks that localhost:10.0 is the same computer, and so attempted a direction connection. I believe the fist point answers your question about whether this is possible or not: it should certainly be possible. In this case, the client application is then allowed to directly access the video hardware through several API layers. If client and server are running on the same computer and an accelerated 3D graphics card using a suitable driver is available, the former two components can be bypassed by DRI. The client and server software may run on different computers. GLX An extension of the X protocol, which allows the client (the OpenGL application) to send 3D rendering commands to the X server (the software responsible for the display). To close your remote RPi desktop over X11+SSH, you can either close a small terminal seen in your active virtual terminal 8 (see picture above), or kill su session running in your virtual terminal 7. The solution (if it exists) would also preferably work for other OS's including Windows over WinSCP.Ī few notes from the GLX Wikipedia article: You can move between first and second virtual terminals by pressing CTRL + ALT + F7 or CTRL + ALT + F8. The remote machine is running Ubuntu and my local machine is a Mac running 10.8.2 I already know that I have x11 forwarding set up properly for normal use as I can get things like xclock to open up in XQuartz just fine. Gazebo doesn't build in an agnostic manner with branching codepaths for different hardware whatever your system looks like when it builds is what you get.It works just fine.Īs near as I can tell, it seems that one of three things are happening: I've tested X11 forwarding of gazebo between two machines with NVIDIA cards. The remote machine is running with an NVIDIA card, and my local machine is using an AMD card. Minor opcode of failed request: 16 (X_GLXVendorPrivate)Ĭurrent serial number in output stream: 25 Major opcode of failed request: 149 (GLX) X Error of failed request: GLXUnsupportedPrivateRequest Xlib: extension "NV-GLX" missing on display "localhost:10.0". The exact error output: Xlib: extension "NV-GLX" missing on display "localhost:10.0". The problem that I seem to be running into is that gazebo crashes due to a mismatch in the graphics cards it can't find "NV-GLX" extensions. I'm interested in forwarding an X11 session over SSH, in order to launch a remote process that utilizes OpenGL (specifically, gazebo for anyone familiar.)
0 Comments
Leave a Reply. |