Raspberry Pi is good for testing the minimum resource requirements needed to run Monero. As long as Monero continues to work on ARM devices like the Raspberry Pi then scaling concerns related to hardware requirements will not be a problem for most people.
It also is extremely inexpensive in terms energy consumption, with a Raspberry Pi and other ARM systems ...
As of v0.10.0, yes the LMDB files are cross-compatible between 32 and 64bit architectures. They have always been cross-compatible between OSs. They are still byte-order dependent but almost everyone uses little-endian CPUs these days so it's not much of an issue.
For your pi 3, just grab the ARMv7 binaries. https://getmonero.org/downloads/
They'll work for pi 2 as well. If anyone is trying to run a node on pi 1 or pi zero, I can upload ARMv6 binaries but I believe the plan is to drop support for these ARMv6 devices soon.
ARMv6 binaries now available: https://www.reddit.com/r/Monero/comments/543euo/...
I think you would have to do a lot to get a miner running on a pi. The CPU doesn't have much cache, isn’t that strong, and would need the AES-NI instruction set (which not all Pi s have). And it would get a very low H/s anyway. There's a GPU on the pi but I haven't seen much info about using it for mining. However since the power is free it could be fun just ...
At the present time, nobody ships a 64bit kernel or OS for Raspberry Pi 3. That's why we only provide 32bit binaries for the Pi 3. So no, you cannot leverage the ARMv8 features of the Pi 3 yet. If you want an actual 64 bit ARM device with 64 bit software support, try the Pine A64.
Other devices with good ARM64 support - anything using Rockchip RK3368, ...
I'm working on project focused to provide best-possible RPi3 mining.
Pool used: https://supportxmr.com/
In order to exploit RPi3 hardware at maximum level I'm using Arch Linux. together with my fork of xmrig/xmrig miner - can be found on GitHub
Hashing perfromances are so far between 15-20H/s
I can confirm that @Mark is right though I get a lower hash rate(some compile tweaking maybe and overclock the board):
[2017-12-21 04:53:06] Using JSON-RPC 2.0
[2017-12-21 04:53:06] CPU Supports AES-NI: NO
[2017-12-21 04:53:06] Starting Stratum on stratum+tcp://xmr-us-east1.nanopool.org:14444
[2017-12-21 04:53:06] 4 miner threads started, using '...
Rasbian is out because its libboost-all-dev is only version 1.55 (1.58 is required to build). I don't have an rpi3 with Arch Linux on it to test on right now, but that would probably be your best bet since it is a rolling release distro.
You cannot compare hash-rates for SHA and CryptoNight as they have different characteristics. CryptoNight requires 2MB of processor cache per thread and if you don't have that, the hashing will be significantly slower than other algorithms.
Raspberry Pi 3 to my recollection only has 512KB L2 cache so it's always going to be slow hashing CryptoNight compared ...
No, definetley not worth the time required to set them up for solo mining, if that's even possible. If it is possible, you'll probably never win a block.
As for pool mining, I guess it depends on the hashrate you can get out of one board but for comparison my i7 does about 90H/s, where a single 1070 will do about 500-600H/s using less juice. If there is ...
There was a bug in the ARMv7-specific source code, which was triggered when using newer versions of GCC to compile the code.
It has recently been fixed.
Thanks to Monero Reddit people, I solved the issue. This is the link to the discussion.
The issue was related to timezones because the timezone of the system was set on wrong timezone, one hour behind the correct one. So, I changed timezone with:
sudo dpkg-reconfigure tzdata
and restarted the Pi.
After a long time, the node completed the blockchain ...
Yes, you can! It's quite fun to finally see your miner up and running.
As you smile at last at your accomplishment, you notice something.
Your smile falters.
CPU #0: 1.51 H/s
CPU #1: 1.48 H/s
CPU #2: 1.53 H/s
CPU #3: 1.52 H/s
Damn it, how are you going to pay the electricity bill this month?
Not worth the trouble. You won’t earn enough to get a payout on any pool I’m aware of. And even if you were to find a pool with basically a zero payout threshold, you’d be earning at most $2.47 a YEAR at current price and difficulty. And that’s with free power and after tweaking to get it up to 10 h/s.
Boot the Raspberry, change admin password (keep this safe!) turn off the wifi and bluetooth.
Turn wifi and bluetooth off:
sudo nano /boot/config.txt
Reboot and NEVER turn on the internet again on this Raspberry.
Note all the software you think you will need (Monero, gpg and maybe KeePassX). ...
I use a server at home and it is an old Power Edge 2950 (2 x duel quad core Xeons and 32gb RAM). I am running UBUNTU 14.04 LTS and it seems to run the daemon, wallet, and front end via Apache2 pretty well. I haven't had a bunch of traffic on it yet because it is still in the testing phase and it is like pulling teeth finding miners to connect and hash to ...
After reading some of the instructions over at http://pinode.co.uk, I think I found the culprit. Turned out Ubuntu MATE for Raspberry Pi doesn't install with swap space out-of-the-box. I wasn't aware of this.
I have now added a 1024 MB linux-swap partition on my microSD card with GParted. I won't be very fast, but at least it's there.
Therefore, I also ...
You are using a 3-4 year old miner. The mining/hashing algo was changed in April (May?) You are using the old and incorrect miner, thus bad shares.
(oh and minergate is a pool with a bad rep for scamming/stealing hashes, from what I've read.)
Quick update: I couldn't get xmr-stak to compile easy enough. but ...
Running a pool requires a pretty reliable machine. Pi's are fun, but they don't fit the bill. Spend a few bucks a month on a VPS with 2GB of RAM at least and enough disk space to house the Monero blockchain (to run the full-node daemon), and you'll reliably be able to keep a pool up. Who knows, make it public and others might use it too!
Also, wouldn't ...
Your pool uses the stratum protocol instead of the older getwork protocol that cpuminer-multi defaults to. Use -o stratum+tcp://pool.bytecoin.party:3333.
I'd also recommend switching to xmrig since cpuminer-multi has been dead for a while.