-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
How do I fix this error? '_cuda_setDevice' #360
Comments
The current code only supports PyTorch 0.4+. See Q & A for more details. |
yup I tried the latest versions (0.4+) first. Same error. |
Hmm, do you have an NVIDIA GPU on your Mac? If not, you can set |
add |
okay thanks! I will try the examples and come back :) |
The PyTorch binary for osx does not support CUDA. So if you run with gpu_ids not -1, you will see such error. You can build from pytorch github source to support CUDA. |
Oh I see! Thank you for the feedback. |
Both linux and windows binaries work with CUDA. Have fun! |
Thank you ! :) |
where should I type this command? |
You add it when you call |
i'm having the same issue as @ArchitectTaeyoon with python3.8. |
An example will be like (suppose I want to apply a pre-trained model): |
That worked for me as well. Thank you. |
Hello,
I have been following the instruction up to the training stage, where I got stuck.
And I get the following error;
Seems like this is a popular question, and after looking at the previous answers, I have been trying to install different versions of Pytorch, but didn't succeed. I couldn't figure out how to run it on the CPU like the other answer suggests. (
--gpu_ids 0
)Running on Mac OS High Sierra 10.13.3
Python 2.7 version.
Installed : pip, anaconda2, pytorch (python2.7, CUDA 9.2), visdom, dominate, brew, bash, wget, CUDA developer toolkit, cuDNN
I also installed python3 using brew, but switching the path became problematic, so I stuck to 2.7 versions. I have tried installing pytorch 0.4.0, although the terminal seems to be using 0.4.1
I tried downgrading to pytorch 0.3.1 and the same error appears. (#267)
The text was updated successfully, but these errors were encountered: