Official FutureBit Apollo BTC Software/Image and Support thread

[maxfunky]

Hi !

My miner is always inactive and I can't change de pool config. (I did changed it in the Pools section of the menu but the config stay the same in the Dashboard)



Can you help me please  

[Filax]

Hi

I got a problem to make it work my Apollo BTC on raspberry PI 3 (it work on my PC)

- I extracted the archive : Apollo-Miner_aarch64.tar.gz
- The device : /dev/ttyACM0 is correct into the directory
- When i try to launch the script file the console it quit directly => I tryed manually to launch the script in a
console and i get (translated from french)

"./start_apollo.sh: line 63 ./apollo-miner : impossible to launch the binary file : Format error for exec()"

Question two  : It is compatible with linux minera ?

Just me or?

[wavelengthsf]

Hi

I got a problem to make it work my Apollo BTC on raspberry PI 3 (it work on my PC)

- I extracted the archive : Apollo-Miner_aarch64.tar.gz
- The device : /dev/ttyACM0 is correct into the directory
- When i try to launch the script file the console it quit directly => I tryed manually to launch the script in a
console and i get (translated from french)

"./start_apollo.sh: line 63 ./apollo-miner : impossible to launch the binary file : Format error for exec()"

Question two  : It is compatible with linux minera ?

Just me or?

Are you running at 64 bit OS on your Pi? What does it say when you run "uname -a"? If it's not a 64 bit OS, the binaries won't work.

[Filax]

Hi thanks for the reply it say :

Linux raspberrypi 5.4.79-V7+ #1373 SMP "blablabla" armv7l GNU/LINUX

Raspberry Pi OS

I'll try to download and reflash with this OS : https://www.raspberrypi.org/forums/viewtopic.php?t=275370

Regards

[TheFlatline]

Hi !

My miner is always inactive and I can't change de pool config. (I did changed it in the Pools section of the menu but the config stay the same in the Dashboard)

https://i.postimg.cc/mrRntRdG/apollo.png

Can you help me please  

This looks like you are using the wrong worker name.  Have you set up an account on slushpool and named your worker the same?  In the image it says your worker is jstefanop, which is the creator of futurebit and is in the apollo_start.sh file by default.  Change that info to your slushpool info.

[jstefanop]

... and now for a little but of fun

I can actually answer if the apollo is coded to be able to find blocks or not now.
Someone decided to risk testing it (solo) on KanoPool and take that risk for apollo.

But since most around here seem to think I don't know what I'm talking about, and various people like making false accusations about me, I'll leave it up to the people who sold you the software to verify it, as it should have been done in the first place.

We have not released any solo mining capability, and when we do that will be obviously tested rigorously on our end via testnet and unit tests.

What you are talking about is testing YOUR pool code on whether it can successfully submit a block. You obviously already know we are submitting valid shares. Since your pool has not submitted a valid block in nearly a year maybe your code should be more in question than ours

[jstefanop]

Hello, I wonder if anyone can help get my standard unit hooked up to my Ubuntu machine working.

I keep getting a "packet ignored" message:



I tried with a different cable on Ubuntu machine, and now I can see the USB device. However, when I start the miner, I get the same symptom as the windows box:

Code:

6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00 
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00 
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00 
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00 
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00 
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00 
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00 

I also tried on Windows, where I see it show up as COM3, but just get this same warning and no hashing:

Code:

MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00
MsPacket: version mismatch: act 0xd165 != exp 0xd166
WARNING: slave[0]: packet ignored
[6144]: cd ab 65 d1 21 00 9d 00 ... 00 00 00 00 00 00 00 00

Send an email if you see above version mismatch error if your trying to run your standard unit with our pc/linux software.

This is caused by an older version of the firmware that was installed at the factory and should have been updated before shipment, but a few units slipped through with the older firmware. We have a simple one click firmware updater that will fix this.

[wavelengthsf]

Send an email if you see above version mismatch error if your trying to run your standard unit with our pc/linux software.

This is caused by an older version of the firmware that was installed at the factory and should have been updated before shipment, but a few units slipped through with the older firmware. We have a simple one click firmware updater that will fix this.

Thanks, the new firmware fixed it and i'm hashing away!

[jbrow8]

Hello, I don't mean to be pestering...but any eta on when a copy of the image will be uploaded? As of now, I can't use my device at all...until I can re-flash it. I'd appreciate any update/help.

Thanks!

+1 same situation here, without an image to reflash my unit is sat unable to do anything. Any estimate ETA at all?

I finally got into the menu system that was asking for the password, I went through 2 monitors before finally finding the TV HDMI port worked. one problem solved, more to follow

They did mention some HDMI monitors may not work due to a simple HDMI controller on the SBC. That's why I just hooked it up via ethernet and went in via the web GUI but some others have not been able to do so that way

The miner usually shut down after one hour, its been running for over four hours now, I changed from the extender to the router and now it continues to mine

[kano]

... and now for a little but of fun

I can actually answer if the apollo is coded to be able to find blocks or not now.
Someone decided to risk testing it (solo) on KanoPool and take that risk for apollo.

But since most around here seem to think I don't know what I'm talking about, and various people like making false accusations about me, I'll leave it up to the people who sold you the software to verify it, as it should have been done in the first place.

We have not released any solo mining capability, and when we do that will be obviously tested rigorously on our end via testnet and unit tests.

What you are talking about is testing YOUR pool code on whether it can successfully submit a block. You obviously already know we are submitting valid shares. Since your pool has not submitted a valid block in nearly a year maybe your code should be more in question than ours

Funny, again, showing that you actually have no idea about how to properly test a miner.
Well, you have spent your time dealing with scamcoins, now you've come to sell a miner to real miners, you need to brush up a bit on reality.

[TheFlatline]

... and now for a little but of fun

I can actually answer if the apollo is coded to be able to find blocks or not now.
Someone decided to risk testing it (solo) on KanoPool and take that risk for apollo.

But since most around here seem to think I don't know what I'm talking about, and various people like making false accusations about me, I'll leave it up to the people who sold you the software to verify it, as it should have been done in the first place.

We have not released any solo mining capability, and when we do that will be obviously tested rigorously on our end via testnet and unit tests.

What you are talking about is testing YOUR pool code on whether it can successfully submit a block. You obviously already know we are submitting valid shares. Since your pool has not submitted a valid block in nearly a year maybe your code should be more in question than ours

Funny, again, showing that you actually have no idea about how to properly test a miner.
Well, you have spent your time dealing with scamcoins, now you've come to sell a miner to real miners, you need to brush up a bit on reality.

Dude we get it and you’re awesome but can you have this discussion elsewhere?  Us suckers just want help with the miners we bought.  Thanks.

[maxfunky]

Hi !

My miner is always inactive and I can't change de pool config. (I did changed it in the Pools section of the menu but the config stay the same in the Dashboard)



Can you help me please  

This looks like you are using the wrong worker name.  Have you set up an account on slushpool and named your worker the same?  In the image it says your worker is jstefanop, which is the creator of futurebit and is in the apollo_start.sh file by default.  Change that info to your slushpool info.

I did all that and it is mining on my own account, the problem is the interface won't update. I see it is working fine when I look at slushpool but the Dashboard of my apollo is frozen with bad info!

[heslo]

Hi !

My miner is always inactive and I can't change de pool config. (I did changed it in the Pools section of the menu but the config stay the same in the Dashboard)



Can you help me please  

This looks like you are using the wrong worker name.  Have you set up an account on slushpool and named your worker the same?  In the image it says your worker is jstefanop, which is the creator of futurebit and is in the apollo_start.sh file by default.  Change that info to your slushpool info.

I did all that and it is mining on my own account, the problem is the interface won't update. I see it is working fine when I look at slushpool but the Dashboard of my apollo is frozen with bad info!

Is this through the web GUI? If so it's a known issue

[maxfunky]

Hi !
My miner is always inactive and I can't change de pool config. (I did changed it in the Pools section of the menu but the config stay the same in the Dashboard)

Can you help me please  

This looks like you are using the wrong worker name.  Have you set up an account on slushpool and named your worker the same?  In the image it says your worker is jstefanop, which is the creator of futurebit and is in the apollo_start.sh file by default.  Change that info to your slushpool info.

I did all that and it is mining on my own account, the problem is the interface won't update. I see it is working fine when I look at slushpool but the Dashboard of my apollo is frozen with bad info!

Is this through the web GUI? If so it's a known issue

The web UI and on screen! weird  

The only way I can see my real config is the "Pools" page of the menu. and I can only see that the miner is active in my Slushpool account.

[cryptonite!]

hello first thing my miner page says "There is a problem fetching system stats (Internal error)" I've got the whole blockchain sync and 31/32 connections for some reason I have no connections at my system info settings ? it did before now it shows 0 cpu and 0 memory used,also it says  please allow port 8333 how do I do that and the miners seem to be running in balanced mode even when it shows eco mode I have to keep a extra fan on them also I didnt know your supposed to leave them on eco mode when it s sync the blockchain seems to be stuck on balance mode

Chuck your IP in here https://canyouseeme.org/ and select port 8333. If it can see you, then the port is already forwarded. If not, you'll have to go into your router and forward the port yourself. Use google and search for your router and port forwarding settings to show you how if you don't know; it's very easy. But considering it's got 31/32 connections I'd say it's already forwarded.

As for the stats error, I don't get that but all my stats just say 0. It's a known issue and is being worked on

y miners are only doing about 1.4 Th/s changed settings doesnt seem to change anything also they show temp 48c , 82 w 8.0 volts thats not what the specs say I have the full pkg and nodes downloaded also cant tell if im mining into the pool (confused about worker name) on my slushpool dashboard it says o workers, on workers it says 0 out of 1 workers just not sure what to put in for worker name ?

[jstefanop]

Hi !
My miner is always inactive and I can't change de pool config. (I did changed it in the Pools section of the menu but the config stay the same in the Dashboard)

Can you help me please  

This looks like you are using the wrong worker name.  Have you set up an account on slushpool and named your worker the same?  In the image it says your worker is jstefanop, which is the creator of futurebit and is in the apollo_start.sh file by default.  Change that info to your slushpool info.

I did all that and it is mining on my own account, the problem is the interface won't update. I see it is working fine when I look at slushpool but the Dashboard of my apollo is frozen with bad info!

Is this through the web GUI? If so it's a known issue

The web UI and on screen! weird  

The only way I can see my real config is the "Pools" page of the menu. and I can only see that the miner is active in my Slushpool account.

Can you email support with this (hello at futurebit dot io). We are trying to get more logs to figure out how this bug is caused.

[Jota_US]

After running the miner for a few weeks everything is pretty stable (I also have an LTC)

The only thing that is a bit problematic is the fact that the BTC miner randomly stops mining. (solid red light)
Not sure what is causing that, and I only have to restart the miner to get it going again but it's annoying when it happens in the middle of the night or when I am away for a few days. It would be nice to have an auto-restart or something like that.
The LTC miner used to do similar stuff when I upgraded it to run a node but since I stopped the node it doesn't do it anymore so I tried to stop the node on the BTC one but the same issue persists so it's not because of the node running...

Again not sure what is causing that, it's really just random.
Both miners are next to each other so they share the same connectivity and environment.

Edit: Also, it's too bad that the activity LED is not the same as the LTC miner (flashing red/yellow light when mining). When I see flashing red only I think there is a problem

[Kindpker]

Is there Remote Access to the full Futurebit BTC package? i am seeing the same issue as everyone else. The unit goes offline randomly i have yet to get more than 2 days uptime! Also, will this only mine BTC?

[jstefanop]

Is there Remote Access to the full Futurebit BTC package? i am seeing the same issue as everyone else. The unit goes offline randomly i have yet to get more than 2 days uptime! Also, will this only mine BTC?

Will have a fix for this in the next update. This mines any SHA256 algorithm coin.


FYI posted release image for people requesting it


Apollo BTC Image Link: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_Q


Keep in mind this will wipe your SSD on first boot, so if you have synced your node, remove the SSD, boot it with the fresh image, shut it down, then re-install SSD.

[jbrow8]

Double-check your USB node drive is plugged in the USB port in the back of your Apollo, properly formatted with the folder name "Bitcoin" in the root directory, and press the Start button below.

30 minutes later, several times, nothing but the same message, but it is mining finally for extended hours.