Official FutureBit Apollo BTC Software/Image and Support thread

[kano]

...
There is no bug, the miner supports version rolling for new ASICs but its not implemented in the current ASIC hardware. This is why you are seeing incorrect version data.

Incorrect.

The bug in the code is that you use %x instead of %08x for writing out the version.
That is all it is.
Try reading the code.

Just like if you sent out a block without the leading zeros, no one on the network would accept it.

[n0nce]

...
There is no bug, the miner supports version rolling for new ASICs but its not implemented in the current ASIC hardware. This is why you are seeing incorrect version data.

Incorrect.

The bug in the code is that you use %x instead of %08x for writing out the version.
That is all it is.
Try reading the code.

Just like if you sent out a block without the leading zeros, no one on the network would accept it.

Now I'm intrigued: do you have Apollo ASIC firmware code available or are you reading the disassembly?

[dannysonfire]

I’m sorry if this has been asked as I tried searching for it but I can’t get my Apollo btc to mine. The dashboard is indicating no hash rate or anything. I’ve tried restarting, checking WiFi, and numerous different settings and pools. It was working fine for months now all of a sudden nothing.

[jstefanop]

...
There is no bug, the miner supports version rolling for new ASICs but its not implemented in the current ASIC hardware. This is why you are seeing incorrect version data.

Incorrect.

The bug in the code is that you use %x instead of %08x for writing out the version.
That is all it is.
Try reading the code.

Just like if you sent out a block without the leading zeros, no one on the network would accept it.

Lol ok buddy...want to take over writing the driver code for me will save me lots of time since you know what's on our ASICs die better than me

[crypto_curious]

Any news on updated miner binary?

Should have something by end of the week.

Hello jstefanop, how is that update going? That was 28th September when you said "next week", and then again 12th November "next week", but it's December now and we have nothing. Binary was never updated since release.  We still have to use bugged binary from 26th May 2021, that's 189 days ago. It's not like this is donation-only project, we are on what, 3rd batch of pre-orders now? We all, Apollo users, would appreciate if you can dedicate few hours to update and compile bugged software please.
Thank you.

[carrawayjb]

Hello jstefanop, how is that update going? That was 28th September when you said "next week", and then again 12th November "next week", but it's December now and we have nothing. Binary was never updated since release.  We still have to use bugged binary from 26th May 2021, that's 189 days ago. It's not like this is donation-only project, we are on what, 3rd batch of pre-orders now? We all, Apollo users, would appreciate if you can dedicate few hours to update and compile bugged software please.
Thank you.

Next week...

[jstefanop]

You guys should know about software releases that are due next week by now  

Updated Binaries for Standard Unit users are below:

https://github.com/jstefanop/Apollo-Miner-Binaries/releases/tag/1.1

This release has a lot of bug fixes and resolves the issue people with unstable internet connections were having. These should now be super stable and run for weeks/months.

32 Bit Arm support was also added, if you want to run these on your raspberry pi make sure you updated to the latest Rasbian system release (otherwise you'll need to update libstdc++6 to latest version if your running an older version and don't want to upgrade).


Same updated binaries will be pushed to Apollo Full Node users with the next software update due "next week"...seriously though we are wrapping up some UI testing for the next release and should have it out soon.

[crypto_curious]

Fantastic, thank you!!! 

[kano]

...
Updated Binaries for Standard Unit users are below:

https://github.com/jstefanop/Apollo-Miner-Binaries/releases/tag/1.1

... and still the bug is there:

Code:

strings apollo-miner  | grep '%x'

{"id":%d,"method":"mining.submit","params":["%s","%s","%s","%s","%s","%x"]}

As I already explained, it's supposed to be %08x
Though I guess without showing you the exact line, it was too difficult to understand ...

I really wonder about this software, that also isn't properly tested either according to your own statement.

Sigh.

You guys should know about software releases that are due next week by now 

You said it was due back in May ...

Excellent, thanks! Downloading and running binary was very easy on normal Linux system.

That being said however, I have quite good Raspberry Pi 2, quad core ARM, which is still running strong, and that's where I want to run Apollo. I don't have Raspberry Pi 4. I could not find source code for your apollo-miner binary. Will there be code released for apollo-miner binary, so I can compile it myself and run on Raspberry Pi 2?
Hardware says:

Code:

OS: Raspbian GNU/Linux 10 (buster) armv7l
Host: Raspberry Pi 2 Model B Rev 1.1

But I also have plenty of Pi zeros, would love to run miner on that too.

Yea thats on the list, should have binaries for 32bit arm next week.

[heslo]

You guys should know about software releases that are due next week by now  

Updated Binaries for Standard Unit users are below:

https://github.com/jstefanop/Apollo-Miner-Binaries/releases/tag/1.1

This release has a lot of bug fixes and resolves the issue people with unstable internet connections were having. These should now be super stable and run for weeks/months.

32 Bit Arm support was also added, if you want to run these on your raspberry pi make sure you updated to the latest Rasbian system release (otherwise you'll need to update libstdc++6 to latest version if your running an older version and don't want to upgrade).


Same updated binaries will be pushed to Apollo Full Node users with the next software update due "next week"...seriously though we are wrapping up some UI testing for the next release and should have it out soon.

If you need testers I'd gladly step forward again; I helped with the 0.3.1 release

[jstefanop]

...
Updated Binaries for Standard Unit users are below:

https://github.com/jstefanop/Apollo-Miner-Binaries/releases/tag/1.1

... and still the bug is there:

Code:

strings apollo-miner  | grep '%x'

{"id":%d,"method":"mining.submit","params":["%s","%s","%s","%s","%s","%x"]}

As I already explained, it's supposed to be %08x
Though I guess without showing you the exact line, it was too difficult to understand ...

I really wonder about this software, that also isn't properly tested either according to your own statement.

Sigh.

You guys should know about software releases that are due next week by now 

You said it was due back in May ...

Excellent, thanks! Downloading and running binary was very easy on normal Linux system.

That being said however, I have quite good Raspberry Pi 2, quad core ARM, which is still running strong, and that's where I want to run Apollo. I don't have Raspberry Pi 4. I could not find source code for your apollo-miner binary. Will there be code released for apollo-miner binary, so I can compile it myself and run on Raspberry Pi 2?
Hardware says:

Code:

OS: Raspbian GNU/Linux 10 (buster) armv7l
Host: Raspberry Pi 2 Model B Rev 1.1

But I also have plenty of Pi zeros, would love to run miner on that too.

Yea thats on the list, should have binaries for 32bit arm next week.

Not sure how else to explain it to you, rolling version ASICBOOST is not supported on the hardware so there is no reason to work on this codebase until it is supported by the ASICs themselves....

[SpeedForceGN]

Obviously you'll mine BTC if you have a winning strategy.

Other sha-256 coins like BCH are rubbish IMO.

How much is your daily return on bitcoin? Hash rate and post pic please

[NotFuzzyWarm]

Best answer is to just Google it...
The White paper is here

[kano]

...
Not sure how else to explain it to you, rolling version ASICBOOST is not supported on the hardware so there is no reason to work on this codebase until it is supported by the ASICs themselves....

The code's ability to handle asicboost is what matters.
Versions sent and received work, but alas with a bug.
Getting any performance gain using asicboost is not relevant.

I've already given you the bug fix to your code so I've no idea why you wont implement it.

There are cases where the miner needs to be able to handle asicboost because not every mining target on the planet supports both: on and off.
With the VERY simple fix added, that issue disappears, the person running an apollo can have it turned on or off as required.

Though I will quote you that probably explains you have no idea what you are talking about:

...
There is no bug, the miner supports version rolling for new ASICs but its not implemented in the current ASIC hardware. This is why you are seeing incorrect version data.

No, it's using the wrong display of the version data - %x - instead it should be the equivalent of %08x

[n0nce]

Best answer is to just Google it...
The White paper is here

Interesting, one of the first sentences:

​AsicBoost is an ​algorithmic​ optimization and therefore applicable to all types of mining hardware.

Seems like kano is right here

On the other hand:

It involves a new design of the SHA 256 hash­engines (inside the ASIC)

Unfortunately, as with all closed-source stuff, we end up in the situation where the community likes to help but missing sources make it hard for everyone involved :/

[jstefanop]

...
Not sure how else to explain it to you, rolling version ASICBOOST is not supported on the hardware so there is no reason to work on this codebase until it is supported by the ASICs themselves....

The code's ability to handle asicboost is what matters.
Versions sent and received work, but alas with a bug.
Getting any performance gain using asicboost is not relevant.

I've already given you the bug fix to your code so I've no idea why you wont implement it.

There are cases where the miner needs to be able to handle asicboost because not every mining target on the planet supports both: on and off.
With the VERY simple fix added, that issue disappears, the person running an apollo can have it turned on or off as required.

Though I will quote you that probably explains you have no idea what you are talking about:

...
There is no bug, the miner supports version rolling for new ASICs but its not implemented in the current ASIC hardware. This is why you are seeing incorrect version data.

No, it's using the wrong display of the version data - %x - instead it should be the equivalent of %08x

Not sure why im bothering replying to you when you keep insulting me, but since you keep spouting false accusations ill further explain what's going on in the interest of being as open as possible, and correcting you since you are the one that has no idea what your talking about.

 That version rolling flag should not even be enabled on the public builds, its used only for internal testing. We have a proprietary implementation internally, which that code is designed to work for our internal servers and testing. You have no idea what we do internally, nor do you even have the faintest clue why that string you pulled from our code is coded that way. If we had that flag hidden you would be none the wiser.

Stop spreading miss-information and confusing our customers. These miners do not support asicboost period, and every major pool supports non-asicboost miners.

[amanz360]

You guys should know about software releases that are due next week by now  

Updated Binaries for Standard Unit users are below:

https://github.com/jstefanop/Apollo-Miner-Binaries/releases/tag/1.1

This release has a lot of bug fixes and resolves the issue people with unstable internet connections were having. These should now be super stable and run for weeks/months.

32 Bit Arm support was also added, if you want to run these on your raspberry pi make sure you updated to the latest Rasbian system release (otherwise you'll need to update libstdc++6 to latest version if your running an older version and don't want to upgrade).


Same updated binaries will be pushed to Apollo Full Node users with the next software update due "next week"...seriously though we are wrapping up some UI testing for the next release and should have it out soon.

Not sure why things are getting heated, all I know is I'm excited for this update to roll out to my full node! It'll be a great boon to have increased stability!

[kano]

...
Stop spreading miss-information and confusing our customers. These miners do not support asicboost period, and every major pool supports non-asicboost miners.

The code supports asicboost, but puts out the wrong format for the last parameter.
However, they work on my pool since I add in the missing zeros.

They are returning valid shares with block versions that hash correctly when the zeros are added.
Works fine on my pool.
The chips may or may not make any difference in their hashing performance - no idea - not a problem.

They wont work on any other pool that expects you to put out the correct format %08x.
Without the zeros added, the shares are rejected since they don't hash to the correct diff.

[Bosiman]

Problems with 2 Full Node Miners: The only way reflash SD-Card?

Hello Dudes,
i have problems with 2 Apolloe Futurebit Full Node miner, but i think the solution is only to reflash the sd-card.

- Miner01: I bought it used in eBay, the seller can't tell me the LogIn-PW for Dashboard configuration. Is it possible to recover the PW or do i have to reflash it?

- Miner02: Everything worked fine. After a router configuration, but this could be a conicidene, Wifi Connection through Dahsboard was no more possible.
Then i turn off the miner directly with power supply, not how is recommended over Dashboard "Shut Down".
After this it was no more connection with eth0 possible, with a portscanner also no possibility to get the correct IP.
Sometimes wifi works after reboot, but no direct connection via eth0 possible anymore.
This i bad, because i have to reach Dashboard with eth0 normally.
I think i have damaged the sd-card, correct? I changed sd-card with Miner01, there i can see hardware is not damaged (connection with wifi sometimes possible with eth0 not)
But eth0 hardware works for sure on Miner01 (where i have no possibility to LogIn, but i can connect via eth0).
Another question: By Miner02 i can't see via LogIn HDMI-TV screen the 500GB SSD, but hardware is in Miner. Defect or also a problem with configuration sd-card?
The RAW-Status always writes new things when i check it.

- Generall question: Are only this SanDisk Industrial cards 16GB recommended or can use for example a SanDisk Ultra MicroSD Class 10?

Are this problems, i describe, known?
Solutions?

Thx for reading and your help
Gr€€tz Bosiman

PS: Short question, if  i really have to reflash:

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

Under Windows_10:
- Which programm do i need to verify SHASUM? With WinRar 5.x possible?
- Easyer way to flash .img on a sd-card is "etcher" or "dd" the easiest possibility, Which one is easier?

[HagssFIN]

Just reflash and do things easy way.

Etcher will do.