It's true. A glxinfo first, is enough to get things working, so that's a workaround. Not ideal, but something.
As far as dmesg, the only new output after a slow-instance of glxgears, is a line like this: > vgaarb: this pci device is not a vga device But since the tesla is not a VGA device, that seems reasonable. Also, a new one shows up when the fast-instance glxgears is killed, as well. So it doesn't seem like it's related. The only instance of "NVRM" in the output of dmesg, is this: > NVRM: loading NVIDIA UNIX x86_64 Kernel Module 352.55 Thu Oct 8 > 15:18:00 PDT 2015 Lloyd On 01/20/2016 12:14 PM, Thomas Lübking wrote: > Check dmesg, notably for NVRM, right after the failed gl call. > I assume any initial gl call will do, ie. running glxinfo will lead to > a first instance glxgears on the GPU? > > Cheers, > Thomas > _______________________________________________ > xorg@lists.x.org: X.Org support > Archives: http://lists.freedesktop.org/archives/xorg > Info: http://lists.x.org/mailman/listinfo/xorg > Your subscription address: %(user_address)s -- Lloyd Brown Systems Administrator Fulton Supercomputing Lab Brigham Young University http://marylou.byu.edu _______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
