-
Notifications
You must be signed in to change notification settings - Fork 312
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
Non-existant CUDA device '12(Or 11)' specified in -d option #90
Comments
ok, I think I have found the bug |
Hello, thanks for looking into it. It does seem to apply to every ccminer out there that ive tested. Any ways to spread this to the other developers without individually telling them in their github? |
The closest thing would be be the bitcointalk forum. |
Could you give me a quick description of what the error was? Probably
helpful when I make the post.
2017-12-17 5:45 GMT+01:00 KlausT <notifications@github.com>:
… The closest thing would be be the bitcointalk forum.
Here for example:
https://bitcointalk.org/index.php?topic=770064.0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#90 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AhAc1-g8FwVLnFHUGQi5rXo5HimUnUL8ks5tBJx7gaJpZM4REeN2>
.
|
The old code was checking the length of the numbers. |
I have an issue controlling what cards CCminer will use above number 9. Im able to use -d 1,2,3,,,9.
But when I get to 10, it just runs GPU 0.
When I try -d 11 or 12 I get this error:
Non-existant CUDA device '12' specified in -d option
If I just run it without -d at all, it detect all 13 nvidia GPU's and run fine. (Problem with 8+ of the same brand GPU is fixed in windows 10).
To me it seems like CCminer can use all my GPU's fine, but the -d command does not support numbers above 9.
Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
CUDA support by Christian Buchner, Christian H. and DJM34
Includes optimizations implemented by sp-hash, klaust, tpruvot and tsiv.
[2017-12-16 22:57:29] NVML GPU monitoring enabled.
[2017-12-16 22:57:29] Non-existant CUDA device '12' specified in -d option
[2017-12-16 22:57:29] stopping 0 threads
[2017-12-16 22:57:29] resetting GPUs
The text was updated successfully, but these errors were encountered: