Pages:
Author

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

newbie
Activity: 15
Merit: 1
Is there a way I can change the name of the Apollo BTC miner that shows in the network attached devices list? How can I do this? Thanks!
jr. member
Activity: 49
Merit: 11
You have time to make something then hamstring it then sell it? crush or burn?does crushing and fire void the warranty as i dont see the warranty of these items anywhere?
newbie
Activity: 17
Merit: 0
Just wanted to chime in here and say that since the last update, my units have been 100% stable.
I used to rarely make it over a week without a unit going offline, or having a hashboard lose power, now they have been up and running properly literally since the minute they updated.

So thanks for a good release, look forward to the additional features on the way.
legendary
Activity: 1202
Merit: 1181
Just switch the NVMe drive and let it re-sync. Nothing else needed
newbie
Activity: 4
Merit: 0
Apollo BTC SD Card Image/OS Download and Install

Folder for all Apollo BTC Image Releases: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_Q

Release 12/17/21

36d263c1328ae95fba79451730838fdf6885156213c0da7df64f416b218b0799  apollo-btc_171221.img.xz

-Updated Apollo UI to latest 0.3.2
-Added Getting Started Guide
-System level fixes/tweaks for stability

Release 7/31/21

d6f820869268383883db4741dcfcade8f57ad1a1c20c359fd7a3015c78ffe3dd  apollo-btc_310721.img.xz

-Updated Apollo UI to latest 0.3.1
-Image no longer wipes SSD if it detects it has already been formatted
-Added additional swap memory to prepare for Lightning network/block explorer apps
-System level fixes/tweaks for stability


Initial Release 5/14/21

c5dfeb7812e43df64fac2fd4dbc929ec7c78f6df513bed0d8aba81a6573bec7e  apollo-btc-14-05-21.img.xz



SD Card Flash Instructions:

  • Download image linked above, verify SHASUM is correct
  • Decompress the image (should have just a .img extension when its done full size ~7GB when decompressed)
  • Use an easy cloner tool like etcher (etcher.io) or dd etc if your know what your doing
  • Insert SD card in your computer, select the the decompressed apollo.img file, and select the SD card you inserted
  • Flash away...this will return your SD card back to stock state

Is there an update thread to upgrading the NVME and flashing the card?
newbie
Activity: 41
Merit: 0

Yes.

Try also port forwarding port 8334 to your nodes ip address in your router this will allow tor nodes to connect. mine stayed at 30 of 32 connections until i forwarded port 8334 as well as 8333 now it stays at 32/32 all the time.

Still nothing. after opening on both router and even modem, I run the scan to see if it shows 8334 open and it doesnt show it open. so weird.

so I ended up finding a great site with some helpful tips. I followed #1 http://www.pcwintech.com/common-problems-fixes-port-forwarding. So I the modem in the front house has built in wifi which I disabled so I could connect the Velop Mesh system. I had to add the actual internet Ip address from the router into the DMZ page on the modem and as soon as I did that my connections started going up. Currently at 16/32
newbie
Activity: 41
Merit: 0

Yes.

Try also port forwarding port 8334 to your nodes ip address in your router this will allow tor nodes to connect. mine stayed at 30 of 32 connections until i forwarded port 8334 as well as 8333 now it stays at 32/32 all the time.

Still nothing. after opening on both router and even modem, I run the scan to see if it shows 8334 open and it doesnt show it open. so weird.
newbie
Activity: 41
Merit: 0

Yes.

Try also port forwarding port 8334 to your nodes ip address in your router this will allow tor nodes to connect. mine stayed at 30 of 32 connections until i forwarded port 8334 as well as 8333 now it stays at 32/32 all the time.

Amazing i'll give this a shot now and report back. Thanks
newbie
Activity: 3
Merit: 0
Hi, loyal Futurebit fans...just wanted to comment on the inquiries about the error rate for the apollo miners...I have had and still continue to have this issue with one of my miners and so I contacted Futurebit Support and this is the response I received from them... mind you it is one response but I happen to agree and understand the response I was given and am at ease about the error rate on my miner...so I copy and paste part of the email response I received from them and it goes..."Yep, that unit is running perfectly! Our software can’t currently filter out bad shares that are spit out by some bad cores out of the thousands of cores that are in your machine, so it shows a higher than normal error rate. If your hash rate was 20% lower as well then you should be concerned your unit is not running well."   Now that is the response I got in my instance and as I said I am confident at ease with the response I was given...the miner does still act up at times as to the error rate but the miner in all other regards including its hash rate has been performing perfectly so my concerns are abated for now...if I were to notice a reduction in its hash rate then I would be concerned but so far so good...Dr. J my man I hope I have not spoken out of turn I just wanted to maybe put the mind at ease of some of your users as to their miners...if I have spoken out of turn please let me know and my apologies...ok that is it for me for now...Dr. J hope you are well and regards to the crew...a loyal fan...Tempestblack... Smiley Wink Cheesy Grin Cool

P.S. uuumm hope to hear back from Futurebit about those temp numbers though...would be helpful... Wink

Super helpful. Thanks! I figured it was probably fine because everything seemed to be working.
newbie
Activity: 18
Merit: 1
Hi, loyal Futurebit fans...just wanted to comment on the inquiries about the error rate for the apollo miners...I have had and still continue to have this issue with one of my miners and so I contacted Futurebit Support and this is the response I received from them... mind you it is one response but I happen to agree and understand the response I was given and am at ease about the error rate on my miner...so I copy and paste part of the email response I received from them and it goes..."Yep, that unit is running perfectly! Our software can’t currently filter out bad shares that are spit out by some bad cores out of the thousands of cores that are in your machine, so it shows a higher than normal error rate. If your hash rate was 20% lower as well then you should be concerned your unit is not running well."   Now that is the response I got in my instance and as I said I am confident at ease with the response I was given...the miner does still act up at times as to the error rate but the miner in all other regards including its hash rate has been performing perfectly so my concerns are abated for now...if I were to notice a reduction in its hash rate then I would be concerned but so far so good...Dr. J my man I hope I have not spoken out of turn I just wanted to maybe put the mind at ease of some of your users as to their miners...if I have spoken out of turn please let me know and my apologies...ok that is it for me for now...Dr. J hope you are well and regards to the crew...a loyal fan...Tempestblack... Smiley Wink Cheesy Grin Cool

P.S. uuumm hope to hear back from Futurebit about those temp numbers though...would be helpful... Wink
newbie
Activity: 3
Merit: 0
My Apollo node is displaying Hardware Errors of 50%-85%. It used to be at 0.2%. I've tried rebooting, letting it sit for half a day, boot back up, but the errors persist. Appears to be a problem for all the mining modes (Eco, Balanced, and Turbo).

Regardless, it appears to be mining properly with all 44 asics up.

Any idea what the errors are? Thanks!

what pool does it point to.

maybe pool changed its software.

Slushpool.
What exactly are these errors, anyway?
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
My Apollo node is displaying Hardware Errors of 50%-85%. It used to be at 0.2%. I've tried rebooting, letting it sit for half a day, boot back up, but the errors persist. Appears to be a problem for all the mining modes (Eco, Balanced, and Turbo).

Regardless, it appears to be mining properly with all 44 asics up.

Any idea what the errors are? Thanks!

what pool does it point to.

maybe pool changed its software.
newbie
Activity: 3
Merit: 0
My Apollo node is displaying Hardware Errors of 50%-85%. It used to be at 0.2%. I've tried rebooting, letting it sit for half a day, boot back up, but the errors persist. Appears to be a problem for all the mining modes (Eco, Balanced, and Turbo).

Regardless, it appears to be mining properly with all 44 asics up.

Any idea what the errors are? Thanks!
newbie
Activity: 41
Merit: 0
Here is what i'm noticing with node connections. I'll be at 10/32 for hours then it'll randomly go to 11/32 then back to 10/32. Does anyone have any recommendations on this or is it a patience game?




Did you port forward in your router settings to your nodes ip address port 8333?

Yes.
jr. member
Activity: 49
Merit: 11
Here is what i'm noticing with node connections. I'll be at 10/32 for hours then it'll randomly go to 11/32 then back to 10/32. Does anyone have any recommendations on this or is it a patience game?




Did you port forward in your router settings to your nodes ip address port 8333?
newbie
Activity: 41
Merit: 0
Here is what i'm noticing with node connections. I'll be at 10/32 for hours then it'll randomly go to 11/32 then back to 10/32. Does anyone have any recommendations on this or is it a patience game?


newbie
Activity: 41
Merit: 0
I'm fully synced and when I tried to turn on the miners and change the power to balanced the 2 standards are fine but the Full shows that the hashboard is inactive. Is that normal?

Seemingly have fixed mine here is what i did:

stop the node

$ cd /opt/apolloapi/backend/apollo-miner

$ ls (will show files below)
apollo-miner.27002A001850324E31323320  apollo-miner.4B001D001650324E31323320
apollo-miner.4A003C0008504E3943303320  apollo-miner.4C0042001650324E31323320

$ mkdir bckup

$ mv apollo-miner.* bckup/

Start mining and node again

now when you 'ls /opt/apolloapi/backend/apollo-miner' it only shows 3 of these files apollo-miner.4A003C0008504E3943303320 is the one that didn't reappear.






Awesome thanks so much for this!
newbie
Activity: 6
Merit: 0
couple of newbie questions
1) is there an optimum method to stacking the units?  I have 3 now and they are eating up valuable desk space in my office

2) also has anyone put a rough guide out for optimum OC settings I get about 9-9.3THs @ 616w on Turbo
newbie
Activity: 41
Merit: 0
One last thing. As I'm fully synced it's still showing 10/32 connections and saying that i have to open port 8333. It's open as I've tested it for the apollo ip "(succeeded) then I tested it for one of my computers IP's and it says it failed which is fine. I'm assuming it just takes time to connect to other nodes but I just want to make sure there is nothing else I need to do.
jr. member
Activity: 49
Merit: 11
I'm fully synced and when I tried to turn on the miners and change the power to balanced the 2 standards are fine but the Full shows that the hashboard is inactive. Is that normal?

I'm having the same problem no its not normal if you shut down your node and reboot it will fix it for awhile then fails again. see my reply
Pages:
Jump to: