-
Notifications
You must be signed in to change notification settings - Fork 100
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
[Bug] multiple GPUs #11
Comments
Just tested again with 2x RTX 3090 & seems to work fine. Weird. Will try with a 10x RTX 3090 and see if I can replicate the error seen with 10x GTX 1080 Ti. |
Might be linked to |
Thanks for the issue, I will try to investigate. Could you try make your window a bit wider? This could help possibly. |
Np, thanks for the response. Hope the issue regarding seg fault can be identified. The window was already maximized sadly so I don't think that's the issue. If it helps I was attempting to use vast.ai cloud gpu with nvidia/opencl image to run profanity2. |
ran it with an instance w 10x GTX 1080 Ti.
Was profanity made with running on instances with multiple gpus in mind?
Gave it a simple command to match for 'dead' but seems that I just get flooded with a stream of total Ghz on terminal without any private key info printed.
The text was updated successfully, but these errors were encountered: