-
Notifications
You must be signed in to change notification settings - Fork 160
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
Unabled cuda with unminable in config.json and screen not responding. #131
Comments
I would expect problems using less than toolkit 10.2 for anything newer than Pascal If windows get the 11_4 dll If Linux get the newest CUDA toolkit and rebuild against that instead of 10.0 |
I encountered a similar issue even after compiling xmrig-cuda with CUDA 11.4 in Ubuntu 20.04. How do I overcome this issue?
Following instructions in https://xmrig.com/docs/miner/build/ubuntu, I had run the Basic Build commands for
and for
In the
In directory /home/user/test/xmrig/build/, I ran this cmd |
It compiled with some issues... Are they the cause for the nothing happens issue that I previously mentioned?
|
No, those are normal. I think I submitted patches for some of the warnings but merges haven't happened here in a long time. |
@Spudz76 In this case, can you explain why XMRIG hangs upon using GPU? I am quite certain the GPU is not fired up. Mining via CPU works. How do I troubleshoot this issue? |
Thanks. For now, it seems xmrig is stable for mining with CPU but not with GPU. Hope things get resolved here. Meanwhile, I have managed to use Pheonix miner in place of xmrig miner when GPU is involved. |
I have found T-Rex to be superior (in stability at least) plus it only supports CUDA so they aren't wasting focus on OpenCL. |
I am using xmrig-6.15.2 for mining with nvidia-gpu. Installed cude and all dependencies and enabled cude in config.json. but screen just not responding. when I mine on cpu, it works fine. below i have attached screenshot.
system: Ubuntu 18
after this line, screen not responding and gpu load is also almost 0%.
The text was updated successfully, but these errors were encountered: