Skip to content

/ arrayfire-python

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error when using af.set_backend('cuda') #202

Open
funcwj opened this issue Jan 27, 2019 · 1 comment
Open

Error when using af.set_backend('cuda') #202

funcwj opened this issue Jan 27, 2019 · 1 comment

Comments

@funcwj
Copy link

@funcwj funcwj commented Jan 27, 2019

When I try to switch backend using af.set_backend('cuda'), I got error like:

report

It seems that I do not have cuda devices as candiated backend although I have 8 gpus in fact, and the output of af.info()

In [2]: af.info()
ArrayFire v3.6.2 (CPU, 64-bit Linux, build dc38ef1)
[0] Intel: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz, 257588 MB, Max threads(44)

and af.get_backend()

In [2]: af.get_backend()
Out[2]: 'unified'

So does I missing something when installing the package?
@mark-poscablo
Copy link
Contributor

@mark-poscablo mark-poscablo commented Feb 5, 2019 •
edited

Hi @funcwj, do you have the arrayfire CUDA libraries on the directory you added to LD_LIBRARY_PATH? Also, could you check if you added the CUDA and CUDA NVVM lib directories to LD_LIBRARY_PATH? (Please see the wiki for more information about setting the environment variables)

I am running Ubuntu 18.04, and I have these in the same directory that I have the CPU, OpenCL, and Unified backend libraries. Please check if they are there for you:

libafcuda.so
libafcuda.so.3
libafcuda.so.3.7.0

(Note that it says 3.7.0 there because I've built these from source - we haven't released 3.7.0 yet)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@funcwj @mark-poscablo
You can’t perform that action at this time.