Updated to 2.6.2 for Aeon, XMR, TRTL and Sumo PoW changes - cryptonight-heavy support
This miner is a compilation of https://github.com/xmrig/xmrig version 2.6.2, compiled with gcc/g++ 7.3.0 specifically for Armbian on Orange Pi Zero (H2/256mb untested on other Orange Pi models - but please feel free to try and post your findings). As noted in the Ubuntu build instructions on the official xmrig repo: "Optionally you can use gcc 7 to small performance increase" (https://github.com/xmrig/xmrig/wiki/Ubuntu-Build). Additionally, a recent change might take further advantage of 7.3.0 over 7.1.0, seen discussed here: xmrig/xmrig#385. TL;DR - use this binary for a 10%-15% performance boost on Armbian.
The latest version of gcc/g++ available from Armbian repositories is 6.1.0, and you will be hard-pressed to find a third party binary for 7+ at the moment. To solve this, I compiled 7.3.0 from source, directly on an Orange Pi Zero (long process- saving you time here!). Then, after making a slight tweak to the flags.cmake file from the original xmrig repo, I was able to successfully compile xmrig 2.6.2 with gcc-7.3.0:
I now see an approximate 14% hashrate increase with my new xmrig binary! I am using a heatsink with no overclock. Mining TRTL (cryptonight-lite) with the gcc 6.1.0 xmrig binary, I average ~12 H/s. With the new 7.3.0 xmrig binary, I'm averaging ~13.7 H/s! Not bad for an $8 SBC!
Usage is the same as xmrig-v2.6.2: https://github.com/xmrig/xmrig/tree/v2.6.0-beta1#usage
Please install the XMRig dependencies before running:
sudo apt-get install git build-essential cmake libuv1-dev libmicrohttpd-dev
I DO NOT RECOMMEND that anyone ever download binaries/executables from third party sources or unofficial Github repos. You can review my credits section to see my sources, and really just take me at my word from there. Hopefully some brave users will try it out and report back here to vouch for me :)
I have not altered, or reduced the default xmrig donations in my compilations, as I respect the work that the developers have put in, I'm merely standing (crouching?) on their shoulders. However, if you feel like giving me a small donation for my time spent and sharing this binary and my findings, please feel free to donate to one of my wallets:
- xmr: 4BrL51JCc9NGQ71kWhnYoDRffsDZy7m1HUU7MRU4nUMXAHNFBEJhkTZV9HdaL4gfuNBxLPc3BeMkLGaPbF5vWtANQuJBHa28DsCLY6LkxP
- aeon: WmsqiMAQtMHCLs1XzCm7bL6aAALG7GBaGW2CfPF6X9L7hoNZQK3dMsvTMFooCncshGCG2JC6nhFeAcmR1197MKGU2Dojden7k
- sumo: Sumoo3Puf8bAUMqCtmhfeVD48rypZDPCsCVgEe3mGp5FXQC8vcV3n2wV53hKNYbknHSfCeEC82K2JBFQkPCo3qEMMHpB17MeRux
- trtl: TRTLv3STqeVN3WGh6Je1ikLTsUxejmvqiKo3FaigDQSkSMeGfnY2U8SX92eH7KixU3Mdss59wS2NXXwV7TLstURPWPi6C99aWfT
- Official xmrig repo: https://github.com/xmrig/xmrig
- Guide that helped me in compiling gcc on Raspberry Pi: https://solarianprogrammer.com/2017/12/07/raspberry-pi-raspbian-compiling-gcc/
- Max hashrate stat seems to get stuck shortly after starting - no actual impact
- I find --av=3 gives best results
- Running on 3/4 cores seems to be the sweetspot for hashrate/thermal throttling of CPU (11.9 h/s)
- Monitor temperature & frequency with
armbianmonitor -m - I suggest using a proxy like xmrig-proxy if you plan to cluster some pi's or other small devices for mining: https://github.com/xmrig/xmrig-proxy