Pages:
Author

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

newbie
Activity: 6
Merit: 0
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.
legendary
Activity: 1202
Merit: 1181
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
newbie
Activity: 6
Merit: 0
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.
legendary
Activity: 1202
Merit: 1181
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
newbie
Activity: 11
Merit: 0
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,
full member
Activity: 658
Merit: 118

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?
full member
Activity: 214
Merit: 100
1KippERXwH1PdBxKNt1ksgqh89WBv6CtWQ
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
newbie
Activity: 12
Merit: 0
  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. 
legendary
Activity: 2174
Merit: 1401
  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.
newbie
Activity: 12
Merit: 0
In addition to question above, is it possible to use TLS with this miner software?
newbie
Activity: 10
Merit: 0
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... Grin
full member
Activity: 658
Merit: 118
  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.

newbie
Activity: 12
Merit: 0
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!
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Quote
Thats not a problem as long as you plug in both PCIE cables from the same PSU to the back of the Apollo, and the PSU has at least 200-300 watts headroom for the Apollo.

Issue come in when you try to plug in two separate power supplies in the back of the Apollo (ie some people think if they have 100 watt headroom in one PSU, and 200 watts in another, they'll just plug in one PCIE cable from each PSU to the back of the Apollo...THIS IS THE FIRE HAZARD. Even a small imbalance in voltage will cause major current to flow between the PSUs and melt the cables/start a fire.
Emphasis mine.
Ja. One should NEVER try to run ANY sort of PSU's in parallel. Because they are independent devices they will literally fight each other. If you want to run PSU's in parallel they MUST be designed for it (master-slave modes) and wired accordingly.
legendary
Activity: 2174
Merit: 1401
Hi everyone!
I got mine.  Yeah!#  Grin

I searched in the forum but did not get any suitable information about my question.
I have read that there can be fire Hazzard if you connect the Apollo miner incorrectly.
I got a Miner without PSU.

Can I connect the miner with a PSU that already supplies GPU-s during mining.
I have more than two x 6+2pin free and the PSU still has over 1000w power that is not needed, or is that a problem?
I'm not sure...  Huh Huh Huh

Thank you for the Support.

Gags

Thats not a problem as long as you plug in both PCIE cables from the same PSU to the back of the Apollo, and the PSU has at least 200-300 watts headroom for the Apollo.

Issue come in when you try to plug in two separate power supplies in the back of the Apollo (ie some people think if they have 100 watt headroom in one PSU, and 200 watts in another, they'll just plug in one PCIE cable from each PSU to the back of the Apollo...THIS IS THE FIRE HAZARD). Even a small imbalance in voltage will cause major current to flow between the PSUs and melt the cables/start a fire.
newbie
Activity: 10
Merit: 0
Hi everyone!
I got mine.  Yeah!#  Grin

I searched in the forum but did not get any suitable information about my question.
I have read that there can be fire Hazzard if you connect the Apollo miner incorrectly.
I got a Miner without PSU.

Can I connect the miner with a PSU that already supplies GPU-s during mining.
I have more than two x 6+2pin free and the PSU still has over 1000w power that is not needed, or is that a problem?
I'm not sure...  Huh Huh Huh

Thank you for the Support.

Gags
newbie
Activity: 12
Merit: 0
If you don't mind me asking, what pool would you mine against when you set it and forget it?


Few pools are going to give you a payout at this hashrate.  However, as suggested in the OP, on slushpool you can set it as low as 0.001 BTC for a payout which should only take a couple of months.  I'm solo mining on ckpool until they get the on device solo mining working.  You could also mine sha256 altcoins on zergpool and autoexchange into BTC and the payout is only .002 BTC.  I'm not Phil but I tested all three pools mentioned here with my Apollo.

Im trying to get zergpool setup with a standalone unit and I cant get the apollo miner software to accept zergpool pool options like -o and -a.  Anyone figure this out?

Im already frustrated the (aftermarket) psu I bought for 4 standalone units was doa, so I can only run 1 unit on leftover power from my other psu.   Angry  Irritating day.  Grin

Edit-  needed to remove stratum+tcp:// from front of url, appears to be working now with options defined in apollo mining software (-host -pswd, etc)

edit2-  Forgot to say units look sharp and well made, nice job!  Very happy with this purchase.
newbie
Activity: 14
Merit: 2
Hey everyone, support question.
Loving my miners, and they have generally been reliable, but recently had an issue.


Overnight, my miners seemingly went "offline" in that they were no longer accessible by the web-ui, and stopped sending hashes to my pool (0 reported speed).

However, the physical units themselves were still purring away, red LED and yellow LED's flashing, as well as the network port.
My router showed the device as online and identifiable as well.

I tried setting up with HDMI and keyboard but that seems to only work if they are already plugged in on boot.
So in this instance I got a black screen with no signal.


What should I do to safely shut these two units down other than pull the plug, knowing that the node seems to still be running?
Also, what in gods' name are those things 'hashing' if they are offline and sending out no data?

Thanks!

I too have had the same issue happen multiple times with the some units randomly going inactive on dashboard and monitor giving a black screen with no signal after some period of time running. Reboot fixes both when one or both happens. Have flashed SD card no change. Happens on both old and new update version.
newbie
Activity: 17
Merit: 0
Hey everyone, support question.
Loving my miners, and they have generally been reliable, but recently had an issue.


Overnight, my miners seemingly went "offline" in that they were no longer accessible by the web-ui, and stopped sending hashes to my pool (0 reported speed).

However, the physical units themselves were still purring away, red LED and yellow LED's flashing, as well as the network port.
My router showed the device as online and identifiable as well.

I tried setting up with HDMI and keyboard but that seems to only work if they are already plugged in on boot.
So in this instance I got a black screen with no signal.


What should I do to safely shut these two units down other than pull the plug, knowing that the node seems to still be running?
Also, what in gods' name are those things 'hashing' if they are offline and sending out no data?

Thanks!

[UPDATE]
With it non-responsive and just wasting energy for the last 12 hours I went ahead and turned off the power supply.
Upon booting the units back up they are functional, but no-longer get any system info?

"There is a problem fetching system stats (Internal error)"
No CPU Temp, SSD storage space, or other hardware related info shows in the dashboard now.
Have re-booted multiple times since via software and the issue persists.  :'C
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
AND A VERY good sale for the 1tb micron ssd



https://www.newegg.com/crucial-mx500-1tb/p/N82E16820156174?


$99.00 - 15 with this code. SS2AZ9A525.


84 bucks

mine does that I put in the 1 tb and no worries for years to come
Pages:
Jump to: