Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 97. (Read 48628 times)

I’ve tried to search through the threads and did a search and really didn’t find anything but has anyone tried to add sha256 usb miners to the Apollo?

It probably isn’t worth it in terms of extra electricity usage but I have 2 Ttbit sha256 usb miners lying around and is wondering if I can hook it up to the Apollo rig.

Has anyone tried something like that?

Exactly, I Previously had 2 gpu-mining rigs, one running 12 cards the other with 5 cards. Having 2 power supplies is fine as long as you have it set up correctly. First you’ll need a piece of hardware like add2psu which connects the 2nd-slave psu to the master, you can also use a paper clip if you’re willing to take that risk. The main thing is
 to connect the peripherals to 1 psu and not both. For example for mining rigs the gpu riser and gpu will be connected to 1 psu so both pull from the same power source. You should never connect the riser to one and the gpu on it to another, that would cause problems. So I’m terms of the Apollo don’t plug 2 separate power suppliers into 1 machine..

My old rig ran 24/7 for around 3 years straight never had any serious problems or fire related incidents, you just need to know what you’re doing

Oh yes, this makes so much sense! After all, the standard unit is basically an Orange Pi and a 'Only Hashboard' in one single case. I think I would then also just omit the GPIO connector and add a small USB cable; that way I can run my own OS

@jstefanop is there any reason (except maybe the sleekness of the device) to use the GPIOs? Maybe better hashrate?
For keeping the device's sleek design, but allowing users to run own OS, it might be cool to offer the GPIO connection software as a package to install!

No, my full package Apollo came with Orange Pi 4, 6-core, 4GB RAM.

Yes, that's right, if you do Ubuntu updates, it may break mining. Jstefanop use third party software package to enable miner communication via GPIO pins on top of the Orange Pi. There is some incompatibility in this software if you update system by hand.
I worked around that by connecting miner via USB cable to itself. Every shipped miner can work either via GPIO or USB.

This is a known issue that will be fixed next update. Its caused by an unstable internet connection, so you can improve this if your on wifi, but if your ISP is causing it there is not much you can do until we issue the fix.

Hi, been mining away happily for nearly a week, now seeing : There is a problem fetching system stats (Internal error) tried restart, message still the same.

2.47 Th/s
Current hashrate
15 Min Avg: 2.47 Th/s
158 Watt
Miner power usage
Watts per TH/s: 64
0.4%
Hardware errors
Rejected: 3
2 hours
Miner uptime
Last share: a few seconds ago
Hashboards
Status   ID   Hashrate   Temp   Fan Speed   Power   Voltage   Error   Active ASICs
Active
HASHBOARD #0
 2.47 Th/s
60°c   1738 rpm   158 W   8.09 v   0.4%   44

Any clues please?

Thanks in advance :-)

Also 2.03 Th/s
0.00°C

I'm not sure if I'm the only one that is experiencing this but searching this thread is a nightmare, I'm finding that every few days my standard hashboard unit will fade off leaving only my main controller unit working. Obviously, this takes my hashrate from 4.5 to 2.0'ish but for no apparent reason.

My 2 boxes are in an air conditioned environment, I've run Bitmain ASIC's in that same room with no issue and they are on a UPS for power consistency.

The fix is simple, reboot the boxes and I'm up and running but now I'm finding that I'm having to play babysitter.

Is this something that anyone else is experiencing?

Thanks!
ML

Currently have mine on slushpool. After I have enough to receive a payout can anyone recommend a solid P2Pool with a lower hashrate that is finding blocks?

I seen a standard unit on eBay with a broken usb c port what would it take to get that repaired?

Reply to your order email with the full log, and well check whats up.

Did you replace it with the Pi 4? Because mine appears to have a Pi 3.

Hey
what can I do, when a hashboard ramps up sending shares (only ~700 Gh at ~60 Watts) and seconds later stays at 0 hashes?

With "screen -r" I can see:


Can provide full logs if you need more details.

Thank you 

Should have something by end of the week.

Thanks that means a lot! Of course I have this whole community to thank just as much, none of all this grass roots non-VC funded work would be possible without all of you. Now the next step is to get the Apollo and devices like it to millions of BTC users, we need projects like this to scale if we want to take Bitcoin back from the institutional grip thats starting to take hold.

Tweet at all the influencers, drop emails to crypto news sites etc...no one has really covered us yet and we dont have a budget to spend 10s of thousands on PR.

Any news on updated miner binary?

rebooted my two miners today and both not showing stats and says inactive in web GUI?. Strange as these have been running just fine for the last couple months. But solo.ckpool shows they are actively mining. Both on 0.3.1 firmware. The node status still shows up too

Just an FYI if John still working on a fix

EDIT, I did a miner restart in the Web GUI and stats showing again. When I first rebooted I powered off at the unit because I could not access via IP (router upgrade)

This is for @Gags... Thank you for your post it is awesome to see other members chime in and be helpful to us noobs... lol... To @philipma to you bro I dig your videos and follow your hardware reviews and recommendations and yes I agree let's all go buy I TB crucial NVME cards and replace them in these beautiful Futurebit miner/nodes cause yea I can see the current 500GB drives not sufficing...this is in no way taking away from the beautiful creation by @jstefanop and his team... ideally he will in future releases install the larger 1 TB size NVME cards for due to Bitcoin size the 500 GB will not suffice within 2 years time... by the way philipma a question I pose to you is whether to clone our node drive we have installed currently or to start a fresh node install on what would be the new 1TB drive...and finally @crypto_curious thank you as well for your post every bit of input from the membership is appreciated

To the man who is at the heart of this all...JSTEFANOP...I cannot stop praising you and your team's creation...it is just gorgeous and the Node and Miner Dashboard are just awesome to view and to take in the information displayed on them...please keep up the outstanding work...you have gained a lifelong devotee and client...I so look forward to the second miner that I just ordered and hopefully expect delivery by year's end...and of course, look forward to seeing what new and amazing devices you and your crew design in the near future...

Interesting, you're the first one I come across that reinstalled the OS from scratch on an Apollo. I'm wondering then, how you got the miner working? I understood that we're not supposed to do anything with the system, not even package upgrades, since it could break something in the driver for the hashboard or something like that.

Advertising bitcoind version (0.21.1 in your case) is harmless. Every bitcoin node out there advertises its version so it can efficiently communicate with other compatible nodes. However, when you reinstall system, "FutureBit-Apollo-Node" string will disappear and your node will become generic bitcoind. This setting is configurable somewhere in bitcoin.conf, read the docs for bitcoind if you want to change it or keep it after reinstall.

You assumed bitcoind is running in Apollo as root? I don't think that's the case. You can verify this in ssh session, just run htop.

I suggest reinstalling OS on Apollo, see below. You can run bitcoind as a separate user (to decrease escape risk) with generic version string, that's what I do.

That was my very concern when I first put my hands on this machine. I have reinstalled Armbian Ubuntu (default system in Apollo) to Armbian Debian, headless, ssh access only. See my post with details:
https://bitcointalksearch.org/topic/m.57531106

You can do something like that. For me, not applying security updates on Internet-exposed machine is a big no-no. That's why I reinstalled. Since this post, I upgraded system to latest Armbian-Debian 11, did even more Telegram stats, it's been running great. Also I moved it to another country, so I am bitcoin node operator in two countries now


If you decide to go reinstall route, you have endless possibilities. I have 1TB USB spinning HDD connected as a node drive, formatted to Btrfs, so I have checksum warnings, had this drive already so cost was free. If you need to have it nice and tidy without extra equipment next to it, as it was, just buy any 1TB SSD, if will be all right. Bitcoind is barely using SSD bandwidth and speed anyway. Have fun