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

wait until node fully sync.

Yes, only at 60%.  Was hoping to get it moving faster.  I'll check again tomorrow, should be caught up then.  Thx

Are you done synchronizing with the blockchain?  If not, that is probably why.  Let the node fully synch and see what happens.

Yeah, I was running it in turbo mode for about an hour while the last tenth of a percent of the blockchain was synchronizing.  Rookie mistake that could've cost me my hardware.  Everything is all caught-up, I have 29/32 connections with the following stats:

HASHBOARD #0
Hashrate 3.03 Th/s
Temp 66°c   
Fan Speed   2823 rpm
Power 203 W    
Voltage 8.31v   
Error   0.9%
Active ASICs 44

The temp is 60.00°c at the top left of the dashboard.

What is the difference between the two temperatures?  Different components?

Did you ever solve this?  

I just got my device, port forwarded 8333 and cannot get above 10 connections.  It's ramps right up and hit that 10 ceiling.

Are you running node? in case node sync you might see high temp SBC comp? I believe recommendation while node in sync don't run turbo.

One other question: My BTC is running on turbo.  The hashboard shows:

HASHBOARD #0
Hashrate 3.12 Th/s
Temp 68°c   
Fan Speed   2828 rpm
Power 202 W    
Voltage 8.26 v   
Error   0.9%
Active ASICs 44

However, the hashrate is 3.10 Th/s and the temp is 81.67°c at the top left of the dashboard.

While I'm inclined to believe the lower number, he top number has me worried.  Any guidance?

Thanks!

Hey, thanks so much.  I will watch for it.  :EDIT:  It worked!

Wait for the worker named '[Auto]' scoring hash rate to drop from 123.7M/hs to zero/...  then tick/click the little box next to its name, should come up with the option to edit, delete worker or cancel;
click delete and confirm.

Hi -

Just started mining to Slush Pool with my Apollo BTC.  I notice in addition to my one worker, there is another that is disabled as illustrated in the attached.  Anyway to get rid of it from my dash?

https://i.ibb.co/zsPgTYq/Greenshot-2021-09-19-13-36-21.png

Thanks!

Cheers mate, you too!

Out of curiosity, what build are you on? Still 0.3.0? If so it's worth the upgrade to 0.3.1 when you get the chance; a lot of bug fixes

Thanks - haven't had a chance to update.

Recovered the password - it was a CAPS-LOCK issue, in reverse.  Unique password that works only with CAPS-LOCK "ON".  Don't know how I messed that up when I set the system up in June.

I shut the system totally off for an hour via dashboard and restarted - all is well, now.  First time I've had any issue with my units.

In any event, I appreciate your suggestion about the power supply and will contact customer support.

Have a nice weekend - or what's left of it.

Reflash the SD card with the image given by FutureBit and that will take you back to standard and let you access the dashboard again with the standard password. You will then have to set up your pool info again but after that all will be sweet.

As for the fans, sounds like the common bearing issue, hit up support and they should be able to help you out

One of my hash boards dropped; cannot login.  Swear I did not change password.  

HOW TO FIX/RECOVER the password, keeping in mind I know absolutely NOTHING about any version of Linux?

Update:  Had to power-off everything.  Pulled standard unit and full unit.  Re-plugged in everything.  Power on standard unit - standard password - futurebit123 - works on boot up screen just peachy fine.

BUT.

Lockscreen - no joy.  If I had changed the password at some point, there are a few ones I would have used. None of them work.

Been an hour now - full unit is hashing - slush pool reporting it.  Unfortunately, the standard unit is solid red light and it's obvious because slush pool is 1/2 of what it should be.

I should point out the front light on full unit has NEVER worked, but it hashes just fine.  Light on standard unit is solid red.  Prior to 2 days ago, it blinked slowly - it was hashing.

Not being able to get to the dashboard has frustrated my ability to troubleshoot any further.

HELP.  HELP.  HELP.

Oh, BTW, I have 2 of the FutureBit supplied power supplies.  When I WAS able to see the dashboard, both units were pulling within a couple watts of each other.  Unfortunately, 1 power supply "tubo's" its fan about every 2-3 minutes.  Very noisy - stays that way 5-10 seconds - then resumes back to normal.

I've tried swapping power supplies (between standard and full unit) - regardless of what this one is powering, same EXACT thing happens.  Is there some way (an internal POT or something) that can be adjusted up 2-3 degrees to stop this?


Thank you.

FutureBit has to release a new update that will include the new Bitcoin Core software

Are there instructions for upgrading the Node to 22.0?

Also, I've sent several requests to support for an RMA# on a new unit I received that won't hash and have not received a response since providing the order#.

Thanks,

Any chance of releasing the miner source? It looks like it's based on om-miner (like the bitfury b8 boxes), but haven't found the source anywhere. Is it going to continue to be closed source?

I just received my unit a couple days ago.  I set it up temporarily and it worked fine on the ethernet. I moved it to permanent location and ethernet stopped working.  Tried different cables and verified cable worked on another PC.  Wireless works fine but signal is weak in basement.  Any thoughts?
eth0
Disconnected
Address: No address found

Hey thanks, I'll give that a try when I get some time.  For now the wrapper posted on page 14 seems to be working well.