-
Notifications
You must be signed in to change notification settings - Fork 44
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
Hardware: Have a single board computer spare? Will it run PiNode-XMR? #3
Comments
Parent post edited. Added Rock64 to confirmed. | Rock 64 | buster_current | ✅| ✅|Approx 4 hrs | Requires 4GB RAM (can be supplemented by swap-file)| Built on 2GB model and required an additional 2GB swapfile. It seems the 64-bit builds are more RAM heavy at Monero build level than a 32-bit build. |
Hello! I just setup PiNode-XMR on a RockPi 4B. I'm planning on writing up a detailed description soon but for now the main points are: My setup is a RockPi 4B with OS (Armbian Buster current) on an eMMC and WD Black 500Gb PCIe NVMe for blockchain storage. Here are some setup notes:
I was thinking of forking a RockPi specific branch to address some of the setup bumps I ran into. Would this be useful? Thanks again for all your hard work! (edit: I had incorrectly stated that rc-local service was disabled. It was enabled but wasn't running because rc.local needed its execution bit set) |
@lobster-kerouac Sorry I didn't see your post sooner. I don't know why it didn't notify me. So yeah that rc.local execution was 644 not 755 so that's been updated a1fae6b The UDF filesystem is a decision that keeps coming back to me and I wonder if it was the right thing. The idea was to allow someone to take the USB drive from PiNodeXMR onto any system (Mac, Linux or Windows) and copy a trusted blockchain. I now wonder if a standard filesystem such as ext4 would be better and then advise on a LAN FTP transfer of the blockchain. I'd go with whichever is easiest for a beginner. A intermediate user could format the drive to whatever they want and mount it, PiNodeXMR wouldn't know/notice. |
Odroid C4? These are 64-bit. HC4 is similar to C4 but has 2 SATA ports, M1 has M.2 slot and SATA port, I cannot see them in the table but I assume these could be good nodes. |
Yes, they can make good nodes as the base images supported by our installer scripts can be found easily... https://www.armbian.com/download/?tx_maker=hardkernel https://www.armbian.com/odroid-hc4/ What makes my hardware decisions these days is usually cost efficiency. The latest model (I think) HC4 was released late 2020, so for the unit price in relation to its age should be considered but also the additional cost for accessories. For that reason I prefer the Rock Pi 4 for cheap accessories ( case, emmc module - faster than microSD and longer life , heatsink, power supply etc). Of course if you already own one then PiNodeXMR would be a great use for it. |
Hi @shermand100 I tested PiNodeXMR on Raspberry Pi 5 (8 GB RAM model). |
Thanks for the update @yijiechoo16163 I've added the Pi5 to the table above and also the hardware wiki page. Thanks for testing that. It's a surprisingly fast build time! |
Hi , I have installed pinodexmr on ubuntu 22.04 on a atomicpi and runs well |
I'd like some assistance from the community!
With the self installer scripts releasing us from the constraints of the Raspberry Pi platform I require testers with access to single board computers (SBC). It would be rather wasteful (and expensive) for me to buy one of every SBC out there so I'm asking you to dig though your spare project box's to see what you can put to use.
The list below is not exhaustive. If you own something else that's not on the list, that's fine, give it a go, it can be added. Use the list as a guide for the info we need. If you use a non-standard disk image can you link where others can find it, however standard images should be used where possible as the point of this open source installer is that it can be trusted.
Leave your findings as a comment at the bottom.
My Expectations: The purpose of this is to see what variations (if any) affect the PiNode-XMR installer or how it functions once complete. I believe that on each device the node will install and be functional if using Debian Buster, but variations in hardware such as CPU temperature sensors may become inaccurate. Details like this will be logged in the notes column, or a link to their own issue as they arise.
Confirmed
The text was updated successfully, but these errors were encountered: