Official FutureBit Apollo II/BTC Software/Image and Support thread

[kyle15]

Ok, I read though this thread again before posting this.  I was able to free up enough power on my other PSU to run two standard units.  After a few hours they stop mining, looks like a lot of people have this issue.  But I'm getting a message related to a segmentation fault in screen:  Command terminated with signal 11 (core file generated).   For the time being I wrapped my start script with crypto_curious's script from page 14, and they haven't stopped mining since.  However I dont think enough time has passed for me to consider this a good fix, we'll see.  Some people in this thread suggested the issue could be related to a bad connection to the internet, which is definitely possible in my situation.  I'll setup something to track that when I get back on site.  Im wondering if anyone else has seen the "Command terminated with signal 11 (core file generated)" message in the screen session running the miner software.  I am on Ubuntu 20.04 with an older kernel 5.4.0-58-generic (needed for issues related to GPU mining). 

My only other gripe is the miner output is extremely busy compared to other miners Im familiar with like trm and xmrig.  What stats should I keep an eye on?  Im sure I'll learn more as I get more familiar with this, but Im not really sure what is considered normal yet.  Thanks!

[wavelengthsf]

  Im wondering if anyone else has seen the "Command terminated with signal 11 (core file generated)" message in the screen session running the miner software.  I am on Ubuntu 20.04 with an older kernel 5.4.0-58-generic (needed for issues related to GPU mining). 

Yep, that's the miner binary crashing for some reason. Impossible to know though because it's not open source so we cant run a debug version. Wrapping it in the shell script will reload it when it crashes so that segmentation fault would happen, but the application would restart right away.

[Gags]

Hey...
Futurebit recommeds Slushpool.
During setup, the URL stratum+tcp://stratum.slushpool.com:3333 was recommended.
What about Stratum V2?
Is it possible to use Startum V2?
What are the advantages? If the hashrate is more stable, it is better for the miner, etc.

What do you use?
Stratum V2?
Slush pool? Different pool?

(Slush has a fee 2%.
Basically, I don't think it's a bad thing to pay if it's safe and profitable.
In your opinion, what are the good alternatives if you want to change?)

Thanks.

@jstefanop & @NotFuzzy Warm: Thanks for the quick Answer!
I got one 650w PSU for the Miner...save is save...

[kyle15]

In addition to question above, is it possible to use TLS with this miner software?

[jstefanop]

  Im wondering if anyone else has seen the "Command terminated with signal 11 (core file generated)" message in the screen session running the miner software.  I am on Ubuntu 20.04 with an older kernel 5.4.0-58-generic (needed for issues related to GPU mining). 

Yep, that's the miner binary crashing for some reason. Impossible to know though because it's not open source so we cant run a debug version. Wrapping it in the shell script will reload it when it crashes so that segmentation fault would happen, but the application would restart right away.

Yes the miner crashes when your internet connection disconnects, we have fixed the issue with a workaround in the full package version, but we have to fix the miner binary for the standard units which we should have an update for next week.

FYI if your running standard units on a linux distro you can wrap the miner binary in systemd with auto-restart flag for a temp fix.

[kyle15]

  Im wondering if anyone else has seen the "Command terminated with signal 11 (core file generated)" message in the screen session running the miner software.  I am on Ubuntu 20.04 with an older kernel 5.4.0-58-generic (needed for issues related to GPU mining). 

Yep, that's the miner binary crashing for some reason. Impossible to know though because it's not open source so we cant run a debug version. Wrapping it in the shell script will reload it when it crashes so that segmentation fault would happen, but the application would restart right away.

Yes the miner crashes when your internet connection disconnects, we have fixed the issue with a workaround in the full package version, but we have to fix the miner binary for the standard units which we should have an update for next week.

FYI if your running standard units on a linux distro you can wrap the miner binary in systemd with auto-restart flag for a temp fix.

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. 

[kipper01]

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

[wavelengthsf]

Yes the miner crashes when your internet connection disconnects, we have fixed the issue with a workaround in the full package version, but we have to fix the miner binary for the standard units which we should have an update for next week.

FYI if your running standard units on a linux distro you can wrap the miner binary in systemd with auto-restart flag for a temp fix.

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?

[merdock69]

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,

[heslo]

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,

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

[TooTall68]

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.

[heslo]

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.

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

[TooTall68]

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.

[heslo]

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.

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

[chrisism]

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!

[Muppet007]

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!

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.

[chrisism]

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!

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.

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

[chrisism]

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!

[Max1965]

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!

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.

[apex350]

Well I thought I had it but I havent. Miner restarted and now stuck at 10 connections again. I've checked the port is open with various checkers online and the IP address for the Apollo is static. Also allowed port access with my firewall (not that it should affect the router I suppose as its on my main PC). But still its stuck at 10 connections.

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.