-
Notifications
You must be signed in to change notification settings - Fork 88
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
Never proceeds past benchmarks on Raspberry ARM64 #128
Comments
do you have hwloc installed? seems some kind of memory issue. Undoubtedly due to arm incompatibility |
I know someone who is good with arm, will try to ask them to take a look later |
This info should help: I copied a xmrig.json from another PC to skip the benchmarks, then tested one algorithm at a time. |
do u have hwloc installed, ext? |
|
please do |
OK, I have it installed now. Should I try recompiling xmrig now, or is there something from the output of |
It's worth noting that |
Hello 👋 |
I had never updated this issue with my full findings. With the very helpful tip from @mickbot-92, it's worth sharing them now.
|
I have made a change to the Pi-Apps install script for XMRig which should solve the issue. Botspot/pi-apps@d6c9402 |
I'm having the same issue with a Pi 3 failing during cn/r benchmarking. I tried the suggestions in this thread and the pi-apps build script. The non Monero Ocean XMRig works fine with XMR mining on Monero Ocean. I know the Pi 3 is old and not worth I but I was just messing around with it on Monero Ocean. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Compile xmrig as shown in this script: https://github.com/Botspot/pi-apps/blob/master/apps/XMRig/install
Expected behavior
Running xmrig for the first time completes all benchmarks and then mining begins.
I think this is the same problem as what was encountered in issue #125.
Please respond. Let me know if you need additional context or information. I can provide you with remote access to my Raspberry Pi 5 for testing and debugging.
The text was updated successfully, but these errors were encountered: