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
incorrect balls #2355
Comments
no matter how I set it up, broken balls come:( |
Run the checker on the computer where you have my miner and post a screenshot here, also post a screenshot of your normal xmrig command line options. |
Can you scroll up in the checker? Since not everything can be seen. |
Everything looks correct and should work, are you using different worker names to see the different stats from the miners in the pool? And xmrig should use 256MB when in light mode as is said in the documentation:
|
Yes, I use different names. I tried to recreate the manner and run it on another PC, still invalid balls. and if I run xmrig, then everything is fine |
There's no worker name set in the miner (in the checker), can you try setting one to make sure it's the silent miner that causes it? I tried building a hashpool miner with light mode and it seems to work fine on my end. |
That's strange, does it happen if you don't use light mode? |
I'll check it out now |
Everything seems to be fine without light |
Hmm, so it seems like it's some xmrig light mode bug specifically on that computer/vm. What happens if you run a normal xmrig on the same virtual machine as that with the command (not JSON): |
I'll check it out now |
Everything works |
By the way, the balls go faster. |
Hmm, then there might possibly have been some undocumented fix in the latest xmrig versions for that. Though using light mode is never really recommended due to the very low hashrate. If you really need a low RAM when mining then maybe mining the GhostRider algorithm or some CryptoNight algorithm would be better. |
Which ones should I choose? |
Would depend on what you want to mine, there's many coins listed here: https://www.hashrate.no/coins. |
I want to mine XMR :) |
Then you'll have to mine RandomX, though with light mode you won't mine much. |
I understand. But, with a large consumption of RAM, computers slow down. That's why I want to use the light mode. |
Using RAM should never really slow down a computer, unless the RAM becomes full of course. But mining XMR using light mode might not be very profitable, unless you don't care about that. On my computer light mode reduces the hashrate by 90% (from 700 H/s to 70 H/s). |
I have created 2 identical systems in a virtual box.
I installed the original XMRig on 1 system.
I put your miner on the second system.
Through the original Xmrig everything is fine, but through your incorrect balls come. Why?
There is a Light mode everywhere.
And why in the original Xmir manner in Light mode consumes 10MB of Ram, and your manner consumes 256MB of Ram?
The text was updated successfully, but these errors were encountered: