On Sun, Sep 11, 2011 at 2:41 AM, DRC <dcomman...@users.sourceforge.net>wrote:
> On 9/10/11 10:23 AM, Kevin Van Workum wrote:
> > In my TurboVNC display (:1) I see the when running my app (VMD):
> >
> > ERROR) The X server does not support the OpenGL GLX extension. Exiting
> ...
> > Info) Unable to create OpenGL window.
> >
> > "glxinfo -display :0" reports:
> > direct rendering: No
> <SNIP>
> > which makes sense since I don't have Pbuffer support.
> >
> > But still can't get my OpenGL to work on TurboVNC using your suggestions.
>
> I can't either. Tried on RHEL 5 (Mesa 6.5.1) and RHEL 6 (Mesa 7.10).
> Now that I think about it, how could setting LIBGL_ALWAYS_INDIRECT=1
> possibly work? That's forcing Mesa to use indirect OpenGL rendering,
> which requires that the X server have a GLX extension (which TurboVNC
> doesn't.)
>
Yes DRC that makes sense. In hindsight my setup may have always had the
software mesa driver and therefore always ignored that env variable. Maybe
thats the diff between the 2 env variables. How did you guys go with
LIBGL_ALWAYS_SOFTWARE ?
A little digging for Red Hat revealed the driver package might be called
'swrast' or 'mesa-dri-swrast-driver' which has swrast_dri.so. Centos might
be 'dri-swrast'.
hth
Shanon
------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users
