> 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'.
swrast is definitely installed, and I tried all combinations of the two environment variables. You're sure that you're using TurboVNC? What I'm saying is that I don't understand the mechanism behind how you could use Mesa libGL to do the rendering unless Mesa is either (a) integrated into the X server's DRI interface or (b) sending the OpenGL commands indirectly through GLX. In either case, it requires a capability that the TurboVNC X server doesn't have. ------------------------------------------------------------------------------ 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
