Re: [PyOpenCL] device not found, ambiguous icd file contents maybe?

2016-03-03 Thread Andreas Kloeckner
Vincent Danjean  writes:

> Le 03/03/2016 00:06, michelle a écrit :
>> I have another linux system on which pyopencl is working
>>  and detecting the nvidia card fine--but that card only supports 
>> opencl v.1 and has a measly 48 cores or something like that, 
>> which is why I'm trying to get pyopencl to work on my other 
>> machine, which has a gtx 500 series. 
>
> To my knowledge, all NVidia OpenCL drivers do not support OpenCL 1.2
> and upper.

They actually have started supporting 1.2 on some more recent devices.

===

===
EXTENSIONS: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing 
cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll 
cl_nv_copy_opts·
NAME: NVIDIA CUDA
PROFILE: FULL_PROFILE
VENDOR: NVIDIA Corporation
VERSION: OpenCL 1.2 CUDA 7.5.23
---

---
ADDRESS_BITS: 64
AVAILABLE: 1
[...]
OPENCL_C_VERSION: OpenCL C 1.2
[...]

Andreas


___
PyOpenCL mailing list
PyOpenCL@tiker.net
https://lists.tiker.net/listinfo/pyopencl


Re: [PyOpenCL] device not found, ambiguous icd file contents maybe?

2016-03-03 Thread Vincent Danjean
Le 03/03/2016 00:06, michelle a écrit :
> I have another linux system on which pyopencl is working
>  and detecting the nvidia card fine--but that card only supports 
> opencl v.1 and has a measly 48 cores or something like that, 
> which is why I'm trying to get pyopencl to work on my other 
> machine, which has a gtx 500 series. 

To my knowledge, all NVidia OpenCL drivers do not support OpenCL 1.2
and upper.

  Regards,
Vincent



___
PyOpenCL mailing list
PyOpenCL@tiker.net
https://lists.tiker.net/listinfo/pyopencl


Re: [PyOpenCL] device not found, ambiguous icd file contents maybe?

2016-03-02 Thread Michelle
I got it to work; needed to make the libnvidia-opencl.so executable.



___
PyOpenCL mailing list
PyOpenCL@tiker.net
https://lists.tiker.net/listinfo/pyopencl


Re: [PyOpenCL] device not found, ambiguous icd file contents maybe?

2016-03-02 Thread michelle
I have another linux system on which pyopencl is working
 and detecting the nvidia card fine--but that card only supports 
opencl v.1 and has a measly 48 cores or something like that, 
which is why I'm trying to get pyopencl to work on my other 
machine, which has a gtx 500 series. 





___
PyOpenCL mailing list
PyOpenCL@tiker.net
https://lists.tiker.net/listinfo/pyopencl


Re: [PyOpenCL] device not found, ambiguous icd file contents maybe?

2016-03-02 Thread michelle
Andreas Kloeckner  writes:

> /etc/vendors/nvidia.icd should *not* point at libOpenCL.so. It should
> point at the actual OpenCL implementation. On my Nv system, that's
> 
> /usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-opencl.so.1
> 
> (but that file is probably somewhere different on your machine)
> 
> Andreas

Ok, thanks! For me I think that's 
/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1
which symlinks to libnvidia-opencl.so.352.79. 

libnvidia-opencl.so.1 is in my nvidia.icd. Device not found error still 
appearing
when I run demo.py.





___
PyOpenCL mailing list
PyOpenCL@tiker.net
https://lists.tiker.net/listinfo/pyopencl


Re: [PyOpenCL] device not found, ambiguous icd file contents maybe?

2016-03-01 Thread Andreas Kloeckner
Michelle  writes:
> I have a muddy situation on my Ubuntu 14.04. 
> I have the AMDAPP sdk installed. I also have various nvidia drivers (352 is 
> in use) installed and I have cuda installed. 
>
> I'm trying to get pyopencl to use the nvidia gpu.
>
> Running example opencl files from inside cuda works--ie, it finds the nvidia 
> device and can create a context. I can't get pyopencl to find the device.
>
> My siteconf.py has the directories where the cuda includes and libOpenCL.so 
> reside. I looked at etc/vendors/nvidia.icd and it has libOpenCL.so but there 
> are at least two places where it could find libOpenCL.so, inside the AMD sdk 
> and the cuda, and I'm not sure how to tell it to go to the cuda one. Should I 
> create a symbolic link and point it to the cuda one, and put the name of the 
> symbolic link in the .icd? I also have a bunch of libOpenCL.so.1, .1.0, 
> .1.0.0 in various places, so I'd have to give it a unique name. I tried 
> putting the full path to the right .so but still get  PLATFORM_NOT_FOUND_KHR.

/etc/vendors/nvidia.icd should *not* point at libOpenCL.so. It should
point at the actual OpenCL implementation. On my Nv system, that's

/usr/lib/x86_64-linux-gnu/nvidia/current/libnvidia-opencl.so.1

(but that file is probably somewhere different on your machine)

Andreas

___
PyOpenCL mailing list
PyOpenCL@tiker.net
https://lists.tiker.net/listinfo/pyopencl