Skip to content
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

ccminer tpruvot/ Cryptonight latest version supports more than 10 GPUs, not the Nicehash version #639

Closed
propergol opened this issue Nov 20, 2017 · 6 comments

Comments

@propergol
Copy link

Version v2.2.2 : https://github.com/tpruvot/ccminer/releases/tag/2.2.2-tpruvot
supports more than 9 or 10 GPUs

The actual version in Nicehash (v2.2) does not.

@DillonN
Copy link
Contributor

DillonN commented Nov 21, 2017

The release notes specify this feature is for Linux, can you verify it works on Windows? Also the syntax is unclear. If it is just -d 10,11 e.g. then it should work in NHML already. You can manually update any ccminer by just copying over the exe, provided that the syntax doesn't change, I'll look into updating on next release

@propergol
Copy link
Author

I have just tryed to manualy launch mining using Nicehash provided algo and it works.

When I try inside Nicehash directly the ccminer console repeat open/close and fail at GPU 11.

I tryed to redo the benchmark and the first 10 cards a benched correctly but the last 3 seems to bench very quicly without error, but then when trying to mine, the same issue with GPU 11 appear.

@propergol
Copy link
Author

I have in fact just discovered that when doing a bench on this particular algo and just select GPU11,12,13, then in reality GPU1,2 and 3 are used.

Trying the same on all Dagger algo works perfectly.

@propergol
Copy link
Author

ok, I did finaly replaced the .exe with 2.2.2 version and problem solved! 👍

For some reasons I had already tried that but Nicehash was then redownloading all miners, maybe because I was also overwritting the .dll. Not sure. Only replacing the .exe did the job and everything works now.

@DillonN
Copy link
Contributor

DillonN commented Dec 1, 2017

Good you got it working, I'll mark this as enhancement for updating to 2.2.2

@DillonN
Copy link
Contributor

DillonN commented Feb 19, 2018

Updated

@DillonN DillonN closed this as completed Feb 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants