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

[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

[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

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

Yes. Fully synced and solo mining. Max connections set to 40, but only connected to 11.

Edit: Got this resolved. Last night when I added nodes I also changed max connections and now when I looks to bitcoin.conf in the node it didn't actually addnodes at all, even tho it was showing in the gui Ui so I have added them manually and now I have 20 connections at least.

[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

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

Yes. Fully synced and solo mining. Max connections set to 40, but only connected to 11.

Edit: Got this resolved. Last night when I added nodes I also changed max connections and now when I looks to bitcoin.conf in the node it didn't actually addnodes at all, even tho it was showing in the gui Ui so I have added them manually and now I have 20 connections at least.

Unfortunately it seems there is some kind of bug with my configuration. Every time I restart the miner it takes first addnode=x.x.x.x and populate with same ip address all other entries in my bitcoin.conf. When I manually change bitcoin.conf and only restart node it does work fine and connects to all ips, but as soon as whole miner get restarted it does again wipe all ips in .conf except the first one. Not really sure what is causing this.

[johnstewart]

Hello Everyones !

Can you please tell me exactly wich model of MCU is in the Apollo 2 ? it seems it's an orange pi 4 but i'm not shure if it's this one  ?

Thanks you !!!! 

[TIRMINE]

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

Any update on 2.0.6?  I'm now getting this error too