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

[kimjpeck]

Hi Apollo Support,

I received a new Apollo 2 (Full Node) on Wednesday and it has finally finished syncing (Hash Rate 0 during sync).

No matter what I do (start, stop, reboot, pool, solo, eco, balanced) the miner sits at 0 h/s

I have checked ckpool and there is no hash rate being displayed.

I have download a fresh image (MC2) and setup with a new SDCard and still the same issue.

Front Status Light is flashing white.

regards

Kim

0.00 H/s

0.00 H/s - 1 hour average

0°C - Miner temperature
42°C - System temperature
0% - Hardware errors

0 watts - Power Usage

5% - CPU usage
31.38% - Memory usage
47.76% - System disk usage


Current block - 852,150

Details

04:22 - Minutes since last block
619.52 GB - Blockchain size
617.15 EH/s - Network hashrate
About 79 trillion Difficulty
31/32 - Connections
30.73% - Remaining space



futurebit@futurebit-apollo-2:/dev$ sudo screen -dr miner

*** BOARDS STAT DELTA (10 secs, 1 boards, 44 chips):
BRD  SOL  ERR   bySol  E/S  byJobs  CR  mW/GHs  EPWC
  0    0    0  0 GH/s   0%  0 GH/s   0    0.00     4

*** BOARDS STAT TOTAL (878 secs, 1 boards, 44 chips):
BRD  SOL  ERR   bySol  E/S  byJobs  CR  mW/GHs  EPWC
  0    0    0  0 GH/s   0%  0 GH/s   0    0.00     4

*** MASTER STATS PER INTERVAL:
INTERVAL   sec  bySol  byDiff  byPool  byJobs  CHIP GHs  mW/GHs  SOL  ERR  ERR(%)  CR
  30 sec   10s    0.0     0.0     0.0     0.0      0.00    0.00    0    0    0.0%   0
   5 min  100s    0.0     0.0     0.0     0.0      0.00    0.00    0    0    0.0%   0
  15 min  302s    0.0     0.0     0.0     0.0      0.00    0.00    0    0    0.0%   0
  1 hour  878s    0.0     0.0     0.0     0.0      0.00    0.00    0    0    0.0%   0
   total  878s    0.0     0.0     0.0     0.0      0.00    0.00    0    0    0.0%   0

*** MASTER STATS:
Date: 2024-07-14 12:47:56, UpTime: 878 secs, mbHwVer: 0x0, osc: 0
Smooth osc: step: 1, ignore broken pwc: 0
Found boards:   1
Broken SPI:     1

*** POOL STATS:
Pool: host:port: solo.ckpool.org:3333, user: *******************.Apollo2, diff: 10000, reconnects: 1
extraNonce1: 942d6d72, extraNonce2Size: 8, jobs: 9, rollingEnabled: 1, rollingMask: 1fffe000
INTERVAL   sec  JOBS  clean  SHARES  ok  err  POOL sol  minRespT  avgRespT  maxRespT  loss  INSERVICE       %
  30 sec   10s     1      0       0   0    0         0         0         0         0  0.0%        10s  100.0%
   5 min  100s     4      0       0   0    0         0         0         0         0  0.0%       101s  100.0%
  15 min  302s    11      1       0   0    0         0         0         0         0  0.0%       302s  100.0%
  1 hour  878s    32      3       0   0    0         0         0         0         0  0.0%       878s   99.9%
   total  878s    32      3       0   0    0         0         0         0         0  0.0%       878s   99.9%

*** EVENT STATS:
Legend: SE - subbsribe error (initialising issue)
        DIFF - diff changes, REC - reconnects, RECE - reconnects on error
        SHARES - sent to pool, PSS - pwc shares sent, PSD - pwc shares dropped
        MRS - master received shares, DJS - default job shares
        SJS - stale job shares, DUP - duplicates, LDS - low diff shares
        BDS - big diff shares, BTS - below target shares
        PR - pwc restart, SO - stat overflow
INTERVAL   sec  SE  DIFF  REC  RECE  SHARES  PSS  PSD  MRS  DJS  SJS  DUP  LDS  BDS  BTS  PR  SO
  30 sec   10s   0     0    0     0       0    0    0    0    0    0    0    0    0    0   0   0
   5 min  100s   0     0    0     0       0    0    0    0    0    0    0    0    0    0   0   0
  15 min  302s   0     0    0     0       0    0    0    0    0    0    0    0    0    0   0   0
  1 hour  878s   0     1    0     0       0    0    0    0    0    0    0    0    0    0   0   0
   total  878s   0     1    0     0       0    0    0    0    0    0    0    0    0    0   0   0

FAN INFO:
Slave   RPM
    0  1480

Temp(C) (min/avr/max): 0 / 0 / 0

*** 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  SR  Rst  LastRstT  Packets  Time msec.  Speed(pack./sec)
    0  3D0063001251323532343337      0  00000000  00000000  0x13160100   886   343    4660  4639   20  0.4%    6114  5979  135  2.2%   0   0   0    0         0

Total packets: 4660 in 864882 ms, speed: 5.39 packets/sec
Exporting stat... [done]

[boonleng]

I'm attempting to make the unit even quieter, I don't really mind lowering my hash rate. I found the system service `futurebit-miner-v2`, what are the actual limits of these parameters? The UI configuration only allows up to -brd_ocp 30 -osc 25 -fan_temp_low 69 -fan_temp_hi 89.

[tarator40]

FYI - It would appear the "[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: ..." problem is still alive and well in v2.0.5. I've had my Apollo 2 for a couple of days now and it has v2.0.5 installed. I'm not sure if the "other overflow bug" you mentioned is the same issue, related, or different - but it would seem to have the same error message? In any case, I can only say that I'm using HTTP / web browser on the network and not a dedicated monitor & keyboard to the unit (if that makes a difference I don't know). I've tried both Windows 11 and Linux Mint with Firefox and Brave browsers on both machines and have the same issue after about 4-5 minutes. I've tried the reboot suggestion and again after 4-5 minutes the same error. This is just an FYI as it doesn't seem to actually be disconnecting the miner as you already clarified, although it is annoying, especially when it pops up back-to-back for 1-2 minutes and then goes away for a few minutes and then comes back to taunt me some more - lol.

I am experiencing the same issue. Also using the unit in headless mode (no monitor/kbd - web only). Workaround is to restart the miner process. However you cannot do it via the web UI. Login via ssh and then:

Code:

sudo /opt/apolloapi/backend/apollo-miner/miner_stop.sh
sudo /opt/apolloapi/backend/apollo-miner/miner_start.sh

ignore the errors

[PennyBit]

FYI - It would appear the "[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: ..." problem is still alive and well in v2.0.5. I've had my Apollo 2 for a couple of days now and it has v2.0.5 installed. I'm not sure if the "other overflow bug" you mentioned is the same issue, related, or different - but it would seem to have the same error message? In any case, I can only say that I'm using HTTP / web browser on the network and not a dedicated monitor & keyboard to the unit (if that makes a difference I don't know). I've tried both Windows 11 and Linux Mint with Firefox and Brave browsers on both machines and have the same issue after about 4-5 minutes. I've tried the reboot suggestion and again after 4-5 minutes the same error. This is just an FYI as it doesn't seem to actually be disconnecting the miner as you already clarified, although it is annoying, especially when it pops up back-to-back for 1-2 minutes and then goes away for a few minutes and then comes back to taunt me some more - lol.

I am experiencing the same issue. Also using the unit in headless mode (no monitor/kbd - web only). Workaround is to restart the miner process. However you cannot do it via the web UI. Login via ssh and then:

Code:

sudo /opt/apolloapi/backend/apollo-miner/miner_stop.sh
sudo /opt/apolloapi/backend/apollo-miner/miner_start.sh

ignore the errors

Thanks for the suggestion. I'm assuming you are on v2.0.5 as well which would indicate that the bug did not get fixed from v2.0.4.

[tarator40]

FYI - It would appear the "[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: ..." problem is still alive and well in v2.0.5. I've had my Apollo 2 for a couple of days now and it has v2.0.5 installed. I'm not sure if the "other overflow bug" you mentioned is the same issue, related, or different - but it would seem to have the same error message? In any case, I can only say that I'm using HTTP / web browser on the network and not a dedicated monitor & keyboard to the unit (if that makes a difference I don't know). I've tried both Windows 11 and Linux Mint with Firefox and Brave browsers on both machines and have the same issue after about 4-5 minutes. I've tried the reboot suggestion and again after 4-5 minutes the same error. This is just an FYI as it doesn't seem to actually be disconnecting the miner as you already clarified, although it is annoying, especially when it pops up back-to-back for 1-2 minutes and then goes away for a few minutes and then comes back to taunt me some more - lol.

I am experiencing the same issue. Also using the unit in headless mode (no monitor/kbd - web only). Workaround is to restart the miner process. However you cannot do it via the web UI. Login via ssh and then:

Code:

sudo /opt/apolloapi/backend/apollo-miner/miner_stop.sh
sudo /opt/apolloapi/backend/apollo-miner/miner_start.sh

ignore the errors

Thanks for the suggestion. I'm assuming you are on v2.0.5 as well which would indicate that the bug did not get fixed from v2.0.4.

Yes - using 2.0.5. I assume it's a counter variable bug in the UI code. When some miner stat grows above a certain value - the UI gets broken and cannot properly handle it.
However, I am not sure whether we get any mining penalty by restarting the miner every couple of days...

[PennyBit]

FYI - It would appear the "[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: ..." problem is still alive and well in v2.0.5. I've had my Apollo 2 for a couple of days now and it has v2.0.5 installed. I'm not sure if the "other overflow bug" you mentioned is the same issue, related, or different - but it would seem to have the same error message? In any case, I can only say that I'm using HTTP / web browser on the network and not a dedicated monitor & keyboard to the unit (if that makes a difference I don't know). I've tried both Windows 11 and Linux Mint with Firefox and Brave browsers on both machines and have the same issue after about 4-5 minutes. I've tried the reboot suggestion and again after 4-5 minutes the same error. This is just an FYI as it doesn't seem to actually be disconnecting the miner as you already clarified, although it is annoying, especially when it pops up back-to-back for 1-2 minutes and then goes away for a few minutes and then comes back to taunt me some more - lol.

I am experiencing the same issue. Also using the unit in headless mode (no monitor/kbd - web only). Workaround is to restart the miner process. However you cannot do it via the web UI. Login via ssh and then:

Code:

sudo /opt/apolloapi/backend/apollo-miner/miner_stop.sh
sudo /opt/apolloapi/backend/apollo-miner/miner_start.sh

ignore the errors

Thanks for the suggestion. I'm assuming you are on v2.0.5 as well which would indicate that the bug did not get fixed from v2.0.4.

Yes - using 2.0.5. I assume it's a counter variable bug in the UI code. When some miner stat grows above a certain value - the UI gets broken and cannot properly handle it.
However, I am not sure whether we get any mining penalty by restarting the miner every couple of days...

Sir, I believe you are correct. Also, I found another much longer ["GraphQL" error with more textual information] which happens when I just have the node running (or once when I started the node with the miner already running) but it is very scarce and random, although from what I have been able to read before it disappears it has similar text throughout the error. I will start trying to capture it in the future - but it is random as heck - lol. Just a note for readers - this is all a headless operation on v2.0.5 and may not affect direct connections with monitors/keyboards. I don't know for sure - but feedback would be welcome.

[jstefanop]

FYI - It would appear the "[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: ..." problem is still alive and well in v2.0.5. I've had my Apollo 2 for a couple of days now and it has v2.0.5 installed. I'm not sure if the "other overflow bug" you mentioned is the same issue, related, or different - but it would seem to have the same error message? In any case, I can only say that I'm using HTTP / web browser on the network and not a dedicated monitor & keyboard to the unit (if that makes a difference I don't know). I've tried both Windows 11 and Linux Mint with Firefox and Brave browsers on both machines and have the same issue after about 4-5 minutes. I've tried the reboot suggestion and again after 4-5 minutes the same error. This is just an FYI as it doesn't seem to actually be disconnecting the miner as you already clarified, although it is annoying, especially when it pops up back-to-back for 1-2 minutes and then goes away for a few minutes and then comes back to taunt me some more - lol.

I am experiencing the same issue. Also using the unit in headless mode (no monitor/kbd - web only). Workaround is to restart the miner process. However you cannot do it via the web UI. Login via ssh and then:

Code:

sudo /opt/apolloapi/backend/apollo-miner/miner_stop.sh
sudo /opt/apolloapi/backend/apollo-miner/miner_start.sh

ignore the errors

Thanks for the suggestion. I'm assuming you are on v2.0.5 as well which would indicate that the bug did not get fixed from v2.0.4.

Yes - using 2.0.5. I assume it's a counter variable bug in the UI code. When some miner stat grows above a certain value - the UI gets broken and cannot properly handle it.
However, I am not sure whether we get any mining penalty by restarting the miner every couple of days...

Sir, I believe you are correct. Also, I found another much longer ["GraphQL" error with more textual information] which happens when I just have the node running (or once when I started the node with the miner already running) but it is very scarce and random, although from what I have been able to read before it disappears it has similar text throughout the error. I will start trying to capture it in the future - but it is random as heck - lol. Just a note for readers - this is all a headless operation on v2.0.5 and may not affect direct connections with monitors/keyboards. I don't know for sure - but feedback would be welcome.

This has been fixed on dev, finally got to the source of all the 32bit errors. Should push 2.0.6 soon.

[jstefanop]

Hi Apollo Support,

I received a new Apollo 2 (Full Node) on Wednesday and it has finally finished syncing (Hash Rate 0 during sync).

No matter what I do (start, stop, reboot, pool, solo, eco, balanced) the miner sits at 0 h/s

I have checked ckpool and there is no hash rate being displayed.

I have download a fresh image (MC2) and setup with a new SDCard and still the same issue.

Front Status Light is flashing white.


*** 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  SR  Rst  LastRstT  Packets  Time msec.  Speed(pack./sec)
    0  3D0063001251323532343337      0  00000000  00000000  0x13160100   886   343    4660  4639   20  0.4%    6114  5979  135  2.2%   0   0   0    0         0

Total packets: 4660 in 864882 ms, speed: 5.39 packets/sec
Exporting stat... [done]

This looks like a bad board...reply to your order email and they'll open and rma and take care of this.

[POD5]

Good morning,

Are futurebit btc node queries allowed? How?  

My next question:

When using SOLO MINING are the rewards paid to the address that was entered in my settings? Also the "accepted shares"?

Thanks in advance!

[MakerAZ]

Hello!

I've recently got my Futurebit Apollo II Full Node BTC Miner.
I have some questions:

1) What type of BTC wallet address does Apollo II Solo Miner support? Does it support bc1 address?
2) What software Apollo II does use for BTC Mining? Is it CGMiner?
3) Is it possible to install custom built CGMiner onto Apollo II BTC Miner? if yes, what are the steps?

Thank you!

[PennyBit]

Hello!

I've recently got my Futurebit Apollo II Full Node BTC Miner.
I have some questions:

1) What type of BTC wallet address does Apollo II Solo Miner support? Does it support bc1 address?
2) What software Apollo II does use for BTC Mining? Is it CGMiner?
3) Is it possible to install custom built CGMiner onto Apollo II BTC Miner? if yes, what are the steps?

Thank you!

1) I've used several bc1 addresses and they've all worked fine. You shouldn't have a problem.
2) Interesting question that I really can't answer with much knowledge. Although, it would be interesting to know if you could take, for instance, an R909 pod miner and connect it to the USB port on the Apollo 2 full node and run it. But I'm just thinking out loud. Anyway, I do know that CGMiner will allow a command-line interface so as to configure various mining configurations but I haven't found much yet in the way of that sort of access on AP2. It seems to be all accessed via the interface. Now, I should state that I haven't nosed around much inside the Linux-side files at this point and would say that if you decide to do that, beware.
3) See above.

[jstefanop]

Hello!

I've recently got my Futurebit Apollo II Full Node BTC Miner.
I have some questions:

1) What type of BTC wallet address does Apollo II Solo Miner support? Does it support bc1 address?
2) What software Apollo II does use for BTC Mining? Is it CGMiner?
3) Is it possible to install custom built CGMiner onto Apollo II BTC Miner? if yes, what are the steps?

Thank you!

1) I've used several bc1 addresses and they've all worked fine. You shouldn't have a problem.
2) Interesting question that I really can't answer with much knowledge. Although, it would be interesting to know if you could take, for instance, an R909 pod miner and connect it to the USB port on the Apollo 2 full node and run it. But I'm just thinking out loud. Anyway, I do know that CGMiner will allow a command-line interface so as to configure various mining configurations but I haven't found much yet in the way of that sort of access on AP2. It seems to be all accessed via the interface. Now, I should state that I haven't nosed around much inside the Linux-side files at this point and would say that if you decide to do that, beware.
3) See above.

All addresses are supported except the longer segwit and taproot addresses (forgot the script address names of the top of my head but all legacy, and segwit addresses that are 42 char I believe are currently supported for solo mining).

Apollo uses a custom firmware that is not cgminer based. Yes you could connect any other USB based miner to the apollo to run in the backend (obviously would not show up in the GUI).

Most miner options are exposed in the GUI, but if you want to see all of them and tinker just go to binary directory (/opt/apolloapi/backend/miner) and ./futurebit-miner --help

[PennyBit]

Hello!

I've recently got my Futurebit Apollo II Full Node BTC Miner.
I have some questions:

1) What type of BTC wallet address does Apollo II Solo Miner support? Does it support bc1 address?
2) What software Apollo II does use for BTC Mining? Is it CGMiner?
3) Is it possible to install custom built CGMiner onto Apollo II BTC Miner? if yes, what are the steps?

Thank you!

1) I've used several bc1 addresses and they've all worked fine. You shouldn't have a problem.
2) Interesting question that I really can't answer with much knowledge. Although, it would be interesting to know if you could take, for instance, an R909 pod miner and connect it to the USB port on the Apollo 2 full node and run it. But I'm just thinking out loud. Anyway, I do know that CGMiner will allow a command-line interface so as to configure various mining configurations but I haven't found much yet in the way of that sort of access on AP2. It seems to be all accessed via the interface. Now, I should state that I haven't nosed around much inside the Linux-side files at this point and would say that if you decide to do that, beware.
3) See above.

All addresses are supported except the longer segwit and taproot addresses (forgot the script address names of the top of my head but all legacy, and segwit addresses that are 42 char I believe are currently supported for solo mining).

Apollo uses a custom firmware that is not cgminer based. Yes you could connect any other USB based miner to the apollo to run in the backend (obviously would not show up in the GUI).

Most miner options are exposed in the GUI, but if you want to see all of them and tinker just go to binary directory (/opt/apolloapi/backend/miner) and ./futurebit-miner --help

Thanks jstefanop. Good info to know.

[zeekmine]

Anyone having problems with the solo miner stopping. I have to reboot. It happens every 1 to 3 days. Anyway to debug aside from manually logging into Linux and checking? ? I have the 2.0.5 Apollo II running low speed on the miner and a HTTP connection to a S19. I am testing an a little worried about hooking up more to it. Thanks.

[TIRMINE]

Anyone know if there is a way to adjust the difficulty settings when renting hash and pointing to the Apollo?

[bluudz]

Hey everyone.
Very happy with my Apollo 2 so far. Only thing I'm a bit struggling with is to get node to connect to more peers. Any workaround? I did add quite a few through addnode=x.x.x.x:8333 but still it doesn't seem to connect easily to more than 10 peers.

Any ideas how to get more peers to connect to the node?

Also I was wondering whether there shouldn't be field or some way to show when one finds block! Otherwise it could take long time before you realize you actually found one.

Thanks

[TIRMINE]

Hey everyone.
Very happy with my Apollo 2 so far. Only thing I'm a bit struggling with is to get node to connect to more peers. Any workaround? I did add quite a few through addnode=x.x.x.x:8333 but still it doesn't seem to connect easily to more than 10 peers.

Any ideas how to get more peers to connect to the node?

Also I was wondering whether there shouldn't be field or some way to show when one finds block! Otherwise it could take long time before you realize you actually found one.

Thanks

Are you fully synced?  When I was syncing it would max at 10 for me but once fully synced I'm getting the 32