I'm only running as root for testing purposes instead of manually entering information for the xauth allow list. I've been doing it for quite some time, and it's always worked fine with native OpenCL/OpenGL interop as well as with pycuda's interop so I don't think it's the issue.
Just to confirm though, I went ahead and tested with non-root and the only difference is that it indicates that a segmentation fault occurs during the cl calls: > DISPLAY=:0 python gl_particle_animation.py <pyopencl.Platform 'NVIDIA CUDA' at 0x2aadbe0> Xlib: extension "NV-GLX" missing on display "P". zsh: segmentation fault (core dumped) DISPLAY=:0 python gl_particle_animation.py -- Aaron On Wed, Apr 12, 2017 at 5:17 PM, Andreas Kloeckner <li...@informa.tiker.net> wrote: > Aaron Myles Landwehr <a...@udel.edu> writes: > > > Hi Andreas, > > > > Here is the pyopencl platform information: > > > >> sudo DISPLAY=:0 python opencl-print-info.py > > PyOpenCL version: 2016.2.1 > > OpenCL header version: 1.2 > > 'sudo' may interfere with the Nv driver's ability to connect with other > (e.g. kernel) parts of the driver? Why are you using that? > > Andreas >
_______________________________________________ PyOpenCL mailing list PyOpenCL@tiker.net https://lists.tiker.net/listinfo/pyopencl
