Ivan Shmakov <[email protected]> writes: >>>>>> Andreas Kloeckner writes: >>>>>> Ivan Shmakov <[email protected]> writes: > > […] > > >> The DISPLAY environment variable is unset, but there's indeed an X > >> session opened for A8-3870. (Using the ‘vesa’ driver, though, for > >> ‘radeon’ results in a SIGSEGV for some reason.) > > > For now, OpenCL on AMD GPUs only works with AMD's proprietary driver. > > I. e., a proprietary X video driver?
Yes. > I don't quite understand the relations between OpenCL, X, Mesa, > etc., but somehow, I've got an impression that an X server was > unnecessary to run OpenCL In theory, yes. This is currently true for Nvidia GPUs. > on AMD GPU's. AMD appears to be headed in that direction, but they're not quite there yet. > FWIW, my intent is to > run some OpenCL-based code on an otherwise “headless” system. > Thus, if feasible, I'd prefer not to run an X server there at > all. For now, you're stuck with an X server, at least on AMD. Call this snippet from your X login manager initialization (e.g. /etc/gdm3/Init/Default). Then run 'source /tmp/enable-amd-compute' before your headless/remotely run computation. You also need to create an 'amdgpu' group. ------------------------------------------------- #! /bin/sh xauth extract /tmp/x11-auth-file "$DISPLAY" chmod 660 /tmp/x11-auth-file chgrp amdgpu /tmp/x11-auth-file cat > /tmp/enable-amd-compute <<EOF export COMPUTE=$DISPLAY unset DISPLAY export XAUTHORITY=/tmp/x11-auth-file EOF ------------------------------------------------- > > That said, work on OpenCL in Mesa appears to be making progress... > > Is it Clover [1]? Yes. > [1] http://cgit.freedesktop.org/mesa/clover That's an ancient repository. CL support is already in Mesa proper, but not super-usable just yet. http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/state_trackers/clover Andreas _______________________________________________ PyOpenCL mailing list [email protected] http://lists.tiker.net/listinfo/pyopencl
