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

[Bug] multiple GPUs #11

Open
brianleect opened this issue Oct 15, 2022 · 6 comments
Open

[Bug] multiple GPUs #11

brianleect opened this issue Oct 15, 2022 · 6 comments

Comments

@brianleect
Copy link

image

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.

@brianleect
Copy link
Author

brianleect commented Oct 16, 2022

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.

@brianleect
Copy link
Author

Tested again with a 7x RTX 3090 and it works to generate a addresses at start. However, it later ended up resulting in a seg fault. Seems that the amount of logs printed is a lot more than the usual as well.

image

@brianleect
Copy link
Author

brianleect commented Oct 16, 2022

Might be linked to
johguse#69
johguse#45

@k06a
Copy link
Member

k06a commented Oct 16, 2022

Thanks for the issue, I will try to investigate. Could you try make your window a bit wider? This could help possibly.

@brianleect
Copy link
Author

brianleect commented Oct 16, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@k06a @brianleect and others