Re: [VirtualGL-Users] Error: Xlib: extension "GLX" missing ondisplay":1.0".

[DRC <dco...@us...>]

The documentation explains how to open up permissions on display :0 (using
xauth) so that VGL can access it.  VirtualGL has to be able to access
display :0 because that's the display that is connected to the 3D hardware.
It doesn't actually display anything on display :0, but it has to go through
that X server so it can create OpenGL Pbuffers in which to do the 3D
rendering.
 
VirtualGL's approach is called "split rendering", since the GLX rendering
occurs on a different X display from the rest of the X11 rendering.  The
non-3D X11 rendering is performed by VNC (display :1, in your case.)

[-=DRC=-]


 


  _____  

From: vir...@li...
[mailto:vir...@li...] On Behalf Of Adam
Thomas
Sent: Monday, April 30, 2007 10:08 AM
To: VirtualGL Users
Subject: Re: [VirtualGL-Users] Error: Xlib: extension "GLX" missing
ondisplay":1.0".



Thanks, I had missed that in the docs. I tried it with vglrun, but I'm now
getting a permissions error:

[vnc@xenon vnc]$ vglrun suma

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified 

[VGL] Could not open display :0.
[vnc@xenon vnc]$ echo $DISPLAY
:1.0
[vnc@xenon vnc]$ vglrun -d $DISPLAY suma

Xlib:  extension "GLX" missing on display ":1.0".
trying lame single buffer visual 
Warning: trying lame single buffer visual
Xlib:  extension "GLX" missing on display ":1.0".
Error: no good visual


Can you advise?

Thanks,
-Adam



On 4/30/07, DRC <dco...@us...> wrote: 

Are you invoking the OpenGL application with
 
vglrun {application}
 
??
 
TurboVNC (or any VNC, for that matter) does not support GLX, thus you have
to use VirtualGL to redirect the GLX commands from the application to the
"real" X server, which is attached to the 3D hardware.  VirtualGL then reads
back the rendered 3D frames from the 3D hardware and draws the frames as 2D
X Images in TurboVNC.
 
NoMachine NX does support the GLX extension, which is why your application
works in that environment without invoking vglrun.  However, NX's
implementation of GLX is not hardware-accelerated, so you would still need
to use VirtualGL and invoke the application with vglrun in order to get 3D
hardware acceleration in NX.
 
The upcoming VirtualGL 2.0.1 release has more clear documentation on how to
use TurboVNC with VirtualGL.  You can get a sneak preview of this here:
http://www.virtualgl.org/vgldoc/2_0/#hd0010
<http://www.virtualgl.org/vgldoc/2_0/#hd0010> 
 
The instructions in this new documentation should be applicable to VGL 2.0
as well.

[-=DRC=-]


 


  _____  

From: vir...@li...
[mailto:vir...@li...] On Behalf Of Adam
Thomas
Sent: Monday, April 30, 2007 8:01 AM
To: vir...@li...
Subject: [VirtualGL-Users] Error: Xlib: extension "GLX" missing on
display":1.0".



Hello,

I'm trying to install TurboVNC on a Redhat 9 box with an  NVIDIA GPU Quadro4
750 XG card and NVIDIA driver version 1.0.9631. I'm working with the 2.0-el3
rpm of VirtualGL, 1.10.2 for turbojpeg, and 0.3.2 for turbovnc. The TurboVNC
client (also 0.3.2) is running on Windows XP.

OpenGL application work fine on the console and through NX
(http://www.nomachine.com/). However when I try to launch an OpenGL
application inside a turboVNC window, I get the following error: 

Xlib:  extension "GLX" missing on display ":1.0".
trying lame single buffer visual
Warning: trying lame single buffer visual
Xlib:  extension "GLX" missing on display ": 1.0".
Error: no good visual

Can anyone advise me on what's going wrong?

Thanks,
-Adam Thomas




-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now. 
http://sourceforge.net/powerbar/db2/
_______________________________________________
VirtualGL-Users mailing list 
Vir...@li...
https://lists.sourceforge.net/lists/listinfo/virtualgl-users