On 13/03/15 11:25 AM, Alex Xu wrote: > I get the aforementioned error when running almost anything through > VirtualGL through various methods (SSH X11 forwarding and local VNC). > > Specifically, running "vglconnect -s <host> <<< 'vglrun glxinfo'" > results in this error. > > However, running "ssh <host> <<< 'DISPLAY=:0 glxinfo'" shows that > GLX_ARB_create_context is in fact provided by the graphics driver and > should be available. > > Furthermore, running "vglconnect -s <host> <<< 'vglrun glxgears'" does > work (i.e. output to the connecting machine) and is much faster than > indirect rendering. > > I tried Googling for it, but all I found was "update your graphics > drivers" and "use the proprietary drivers". I am using the latest > drivers, xf86-video-intel-2.99.217, and there are no proprietary drivers. > > What troubleshooting steps could I take to narrow down the problem?
Funny timing: I just posted a patch for that the other day. The VGL nightly page that my search engine pulls up doesn't have that change, so you'll either have to wait for a build with that patch included or if that's something you can do, build the latest trunk yourself. I haven't personally tested VirtualGL with Intel drivers, so I don't know if you'll hit any other issue after solving that one. I have used Mesa + nouveau. -Nathan ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
