Official FutureBit Apollo BTC Software/Image and Support thread

[jstefanop]

What's shipping looking like for April orders?

Currently shipping march orders, should have those done by end of the month. April orders should start going out early June.

Leadtimes will probably decrease end of the month as we catch up to demand.

[jstefanop]

Temperatures:
What are the safe temps for the miner? I was 67C for Eco mode, now I'm at 71 - 73 for Balanced mode. Before I try out turbo mode, I'd like to know at what temperature I need to throttle it back?

Anything under 80c is fine for these ASICs, the miner has mutiple levels of protection and will auto shut down power at 83+ (even if the fan or controller dies)

The fan/temps are tuned for quiet operation...if you are running these in a garage or basement you can set a manual fan profile that keeps temps even cooler for slightly better efficiencies

[jstefanop]

Support for Apollo II USB Standard units on your own linux/windows systems has been released below:

https://github.com/jstefanop/Apollo-Miner-Binaries

Release section has not been updated yet so click on "Code" then download Zip and run the appropriate binary for your system.

Will also upload updated Apollo 1/BTC binaries next week.

Sorry this took so long windows port took longer than expected...had to compile under GCC for windows (not msvc) so has only been tested under windows 10 as working. Let me know if anyone has any .dll errors.

[TIRMINE]

What's shipping looking like for April orders?

Currently shipping march orders, should have those done by end of the month. April orders should start going out early June.

Leadtimes will probably decrease end of the month as we catch up to demand.

Awesome, can't wait!

[WeAreAllSatNak]

Support for Apollo II USB Standard units on your own linux/windows systems has been released below:

https://github.com/jstefanop/Apollo-Miner-Binaries

Release section has not been updated yet so click on "Code" then download Zip and run the appropriate binary for your system.

Will also upload updated Apollo 1/BTC binaries next week.

Sorry this took so long windows port took longer than expected...had to compile under GCC for windows (not msvc) so has only been tested under windows 10 as working. Let me know if anyone has any .dll errors.

Awesome, thank you!

Regarding the updated Apollo 1/BTC binaries: is there any kind of changelog or list of changes? I am interested to know the benefits of upgrading from the existing binaries to the new ones.

Thank you again!

[RotorDriven]

Running the new binaries for my Apollo 2 Standard on a Raspberry Pi 4 after updating the start_apollo.sh script, it looks like apollo-miner-v2 is not detecting my miner.

Code:

*** MASTER STATS:
Date: 2024-05-18 18:50:55, UpTime: 241 secs, mbHwVer: 0x0, osc: 0
Smooth osc: step: 1, ignore broken pwc: 0
Found boards:   0
Broken SPI:     0

Then it scrolls off the screen repeating this:

Code:

MsPacket: version mismatch: act 0xd167 != exp 0xd166
WARNING: slave[0]: packet ignored

And the status update shows this:

Code:

*** MASTER-SLAVE SPI BUS STATS:
SLAVE                       UID  B-LEN   B-CRC-C   B-CRC-L         VER  TIME    PING    M=>S  rx   err       %    S=>M  rx  err     %  SS  SD  Rst  LastRstT  Packets  Time msec.  Speed(pack./sec)
    0  000000000000000000000000      0  00000000  00000000  0x00000000     0  666666    3121   0  3118  100.0%       0   0    0  0.0%   0   0    0         0

Any ideas?

[LowlyPleb]

Good morning.  Perhaps covered elsewhere but could not readily find a resolution.
Got my Apollo II plugged in a few days ago and sync'ed to the current block but mining function is getting error message of [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 4445094100
Any insight as to how to resolve?
Thank you.

[jstefanop]

Good morning.  Perhaps covered elsewhere but could not readily find a resolution.
Got my Apollo II plugged in a few days ago and sync'ed to the current block but mining function is getting error message of [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 4445094100
Any insight as to how to resolve?
Thank you.

Updated to 2.0.4 if you have not already done so. There is also another overflow bug that is fixed in 2.0.5 (out in the next few days) but a reboot will fix this temporarily.

FYI this is just a UI bug (everything in the backend miner/node is still working fine).

[jstefanop]

Running the new binaries for my Apollo 2 Standard on a Raspberry Pi 4 after updating the start_apollo.sh script, it looks like apollo-miner-v2 is not detecting my miner.

Code:

*** MASTER STATS:
Date: 2024-05-18 18:50:55, UpTime: 241 secs, mbHwVer: 0x0, osc: 0
Smooth osc: step: 1, ignore broken pwc: 0
Found boards:   0
Broken SPI:     0

Then it scrolls off the screen repeating this:

Code:

MsPacket: version mismatch: act 0xd167 != exp 0xd166
WARNING: slave[0]: packet ignored

And the status update shows this:

Code:

*** MASTER-SLAVE SPI BUS STATS:
SLAVE                       UID  B-LEN   B-CRC-C   B-CRC-L         VER  TIME    PING    M=>S  rx   err       %    S=>M  rx  err     %  SS  SD  Rst  LastRstT  Packets  Time msec.  Speed(pack./sec)
    0  000000000000000000000000      0  00000000  00000000  0x00000000     0  666666    3121   0  3118  100.0%       0   0    0  0.0%   0   0    0         0

Any ideas?

Can you send output of ./apollo-miner-v2 --help (top line version/build date).

[RotorDriven]

Can you send output of ./apollo-miner-v2 --help (top line version/build date).

Sure thing:

Code:

$ ./apollo-miner-v2 --help
apollo-miner 2.0.2-c 2024-03-20, msp ver 0xd166

[WeAreAllSatNak]

Thank you for releasing the Apollo 2 binaries, jstefanop! Quick question: are there plans to release a linux-aarch32 version for Apollo 2 like you have for Apollo 1? I was planning to drive it with a 32-bit architecture machine that I have accessible but can adapt if needed, but I wanted to check to see if that's coming. Thank you again!

[LowlyPleb]

Good morning.  Perhaps covered elsewhere but could not readily find a resolution.
Got my Apollo II plugged in a few days ago and sync'ed to the current block but mining function is getting error message of [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 4445094100
Any insight as to how to resolve?
Thank you.

Updated to 2.0.4 if you have not already done so. There is also another overflow bug that is fixed in 2.0.5 (out in the next few days) but a reboot will fix this temporarily.

FYI this is just a UI bug (everything in the backend miner/node is still working fine).

Thank you, updating to 2.0.5 resolved this issue.  One question, the unit seems to beep intermittently for different length of time, no real pattern to it.  Is there a way to turn that beeping off?

[jstefanop]

Good morning.  Perhaps covered elsewhere but could not readily find a resolution.
Got my Apollo II plugged in a few days ago and sync'ed to the current block but mining function is getting error message of [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 4445094100
Any insight as to how to resolve?
Thank you.

Updated to 2.0.4 if you have not already done so. There is also another overflow bug that is fixed in 2.0.5 (out in the next few days) but a reboot will fix this temporarily.

FYI this is just a UI bug (everything in the backend miner/node is still working fine).

Thank you, updating to 2.0.5 resolved this issue.  One question, the unit seems to beep intermittently for different length of time, no real pattern to it.  Is there a way to turn that beeping off?

We havent released 2.0.5 yet.

Beep? There is no speaker on the Apollo, I believe there is a beeper on the board, but this is not used.

[jstefanop]

FYI If you have been trying to solo mine with a taproot address and stuck on "Waiting for Share" the issue is the taproot address.

Only legacy or Segwit addresses are supported for Solo mining currently

EDIT: Actually its all 62 char addresses so P2WSH (pay to witness script hash) and  P2TR (pay to taproot) wont work either.

Just legacy, script, and normal SegWit (P2WPKH) are supported.

[jstefanop]

Can you send output of ./apollo-miner-v2 --help (top line version/build date).

Sure thing:

Code:

$ ./apollo-miner-v2 --help
apollo-miner 2.0.2-c 2024-03-20, msp ver 0xd166

Ahh oops uploaded the Apollo 1/BTC binary will fix shortly.

[LowlyPleb]

Good morning.  Perhaps covered elsewhere but could not readily find a resolution.
Got my Apollo II plugged in a few days ago and sync'ed to the current block but mining function is getting error message of [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 4445094100
Any insight as to how to resolve?
Thank you.

Updated to 2.0.4 if you have not already done so. There is also another overflow bug that is fixed in 2.0.5 (out in the next few days) but a reboot will fix this temporarily.

FYI this is just a UI bug (everything in the backend miner/node is still working fine).

Thank you, updating to 2.0.5 resolved this issue.  One question, the unit seems to beep intermittently for different length of time, no real pattern to it.  Is there a way to turn that beeping off?

We havent released 2.0.5 yet.

Beep? There is no speaker on the Apollo, I believe there is a beeper on the board, but this is not used.

Sorry, updated to 2.0.4 that addressed the GraphQL error message.  I had the Apollo II plugged into a battery back up / surge protector ... thats where the beeping came from.  Plugging it into the wall socket handled that issue as well.

[RotorDriven]

Ahh oops uploaded the Apollo 1/BTC binary will fix shortly.

It's working now, thanks!

[TheHoliestRoger]

FYI If you have been trying to solo mine with a taproot address and stuck on "Waiting for Share" the issue is the taproot address.

Only legacy or Segwit addresses are supported for Solo mining currently

EDIT: Actually its all 62 char addresses so P2WSH (pay to witness script hash) and  P2TR (pay to taproot) wont work either.

Just legacy, script, and normal SegWit (P2WPKH) are supported.

Should we immediately see accepted shares if it's working correctly? Still waiting for first share no matter what kind of wallet address is used

[bowstring]

Hello FutureBit!
I received my apollo-2 full node systems about a month ago,
and it's been quite an educational journey!  I joined the
ocean pool and received my first payout with lightning.

However a few days ago the bitcoin nodes on both my apollo-2
systems (configured as TOR mode) lost connection to other nodes,
so they're stuck syncing blocks (~644000/844366).

Tor logs in /var/log/syslog are filled with messages like this :

May 22 04:49:35 futurebit-apollo-2 Tor[202872]: No circuits are opened. Relaxed timeout for circuit 123467 (a Hidden service client: Fetching HS descriptor 4-hop circuit in state waiting to see how other guards perform with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1348 similar message(s) suppressed in last 3900 seconds]
May 22 09:42:24 futurebit-apollo-2 Tor[202872]: We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. [4454 similar message(s) suppressed in last 600 seconds]
May 22 09:47:18 futurebit-apollo-2 Tor[202872]: Failed to find node for hop #1 of our path. Discarding this circuit.

The internet connection is fine, and the miner continues to contribute
to the ocean pool.

I am able to use tor from other computers on my LAN.
Rebooting the apollo-2 does not help.

Tor version 0.4.6.10 is a couple years old.
How are updates managed?

Do you have any hints about this?
Thanks!

[jstefanop]

Hello FutureBit!
I received my apollo-2 full node systems about a month ago,
and it's been quite an educational journey!  I joined the
ocean pool and received my first payout with lightning.

However a few days ago the bitcoin nodes on both my apollo-2
systems (configured as TOR mode) lost connection to other nodes,
so they're stuck syncing blocks (~644000/844366).

Tor logs in /var/log/syslog are filled with messages like this :

May 22 04:49:35 futurebit-apollo-2 Tor[202872]: No circuits are opened. Relaxed timeout for circuit 123467 (a Hidden service client: Fetching HS descriptor 4-hop circuit in state waiting to see how other guards perform with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1348 similar message(s) suppressed in last 3900 seconds]
May 22 09:42:24 futurebit-apollo-2 Tor[202872]: We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. [4454 similar message(s) suppressed in last 600 seconds]
May 22 09:47:18 futurebit-apollo-2 Tor[202872]: Failed to find node for hop #1 of our path. Discarding this circuit.

The internet connection is fine, and the miner continues to contribute
to the ocean pool.

I am able to use tor from other computers on my LAN.
Rebooting the apollo-2 does not help.

Tor version 0.4.6.10 is a couple years old.
How are updates managed?

Do you have any hints about this?
Thanks!

Tor is notorious for sync issues. I would temporarily turn tor off and let the node sync then turn it back on.

Update issues have been resolved, so as long as you dont do a dist upgrade you should be fine with apt update/upgrade going forward (kernel is now frozen).