Search content
Sort by

Showing 10 of 10 results by Poker8
Post
Topic
Board Hardware
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
by
Poker8
on 25/05/2025, 22:52:43 UTC
My Apollo II has stopped working. It seems to light up when you power it on. But it does not hash any longer. It does not heat up. I have been using it with a Apollo II Full Node. I purchased it last November. I had it connected via the USB to my Apolo II full node, which still works perfectly. I changed out the USB cable hoping that was the issue. I received this on 12/11/2024 and it has quit properly working within six months. Any suggestions would be appreciated.
Post
Topic
Board Hardware
Re: unoffical futurebit best share compare
by
Poker8
on 17/03/2025, 17:54:52 UTC
Apollo2 Full Node (ECO), Apollo 2 Standard, + Bitaxe Supra
One Hour Average Hash Rate: 11.40 TH/s
Accepted Shares: 22,895,874,661
Best Share: 275,810,715,670 (Apollo 2)
Latest Uptime: 1 month
Post
Topic
Board Hardware
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
by
Poker8
on 27/11/2024, 04:32:57 UTC
New release is finally out...apologize once again for this being over a month late but this should have squashed a large number of bugs and should be super stable before we start working on a big 2.1 feature release.

As always if you do an OTA update please wait at least half an hour or simply close the tab out and start a new one and wait for the UI to come up (if UI shows 0% update has finishes and you can refresh)

2.1 will also include a new update mechanism that will eliminate update failure and make process way smoother

Apollo OS v2.0.6 - 11/26/24

https://github.com/jstefanop/apolloapi-v2/releases/tag/v2.0.6

New Changes in v2.0.6:

- Redesigned Solo Miner Page making it easy to keep track of multiple miners/wallets mining on the solo pool! Stats are organized by individual wallet addresses, and each wallet address can have multiple workers  (ie address.worker1 address.worker2 etc).
- Node connection count has been upped to 64 connections by default for more robust peering especially during solo mining
- Pesky 32bit and graphQL errors have finally been squashed...small number of users that were affected by this should not see this again
- UI improvements, especially for small format screens and mobile UI
- Improved reliability of node startup during boot, which should reduce "Connection Refused" Node errors for some users
- Multiple UI bug fixes, and backend improvements


Up and running v2.0.6!! Flawless and quick update. Running great. Thank you so much for the update.
Post
Topic
Board Hardware
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
by
Poker8
on 23/11/2024, 19:52:46 UTC
Two questions: Any eta on this error being fixed?

Logo Overview Miner SOLO Mining Node System Settings [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 4193135690

Any good instructions on pointing my bitaxe to my Apollo2 solo node?


Please see the ssh instructions on how to update below:

2.0.6 is finally merged on production and doing a public test before pushing to everyone next week

If anyone wants to test ssh into your device (futurebit/password you set for your dashboard) and

Code:
cd /opt/apolloapi/backend/

sudo ./update

to manually force an update

reminder can take up to 20 min to rebuild the system and it will auto reboot when finished. Close your UI tab and clear cache so your browser does not load the old version.

Please shoot any build issue or bugs...this will definitely fix all the graphql errors small number of users have seen

Sorry this took way longer than planned!

Then all you need to do is point your bitaxe to the IP address listed at the top of your solomining page on your apollo...

"SOLO LAN Mining
Point any Bitcoin Miner on your local network to your Solo Pool with the following URL: x.x.x.x:3333 Username: <bitcoin address>"

So your stratum URL in the BitAxe will be the IP address of your Apollo. 
Port will be 3333
stratum user will be your bitcoinaddress.workername

Save the settings on your bitaxe and restart.

And that should do it!



Thank you so very much!!
Post
Topic
Board Hardware
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
by
Poker8
on 23/11/2024, 16:41:41 UTC
Two questions: Any eta on this error being fixed?

Logo Overview Miner SOLO Mining Node System Settings [GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 4193135690

Any good instructions on pointing my bitaxe to my Apollo2 solo node?
Post
Topic
Board Hardware
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
by
Poker8
on 16/11/2024, 18:34:27 UTC
samsung pro plus sdxc 128gb was on sale at the local BB store.
180 mb/sec read 130 mb/sec write
I was looking for any new memory card with video grade speed microsdxc.

I picked up the same micro card mentioned. Thursday. I have a PC with two SD card slots. What program did you use to clone the old card to the new please?

follow the futurebit instructions online.
https://www.futurebit.io/flashing-sd-card


It went smooth sailing!! I made sure to back up the sittings first. After flashing the new microSD card to the firmware and botting it. I just restored the settings and a few minutes later was back up to 32/32 connections. Smiley
Post
Topic
Board Hardware
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
by
Poker8
on 15/11/2024, 11:19:00 UTC
samsung pro plus sdxc 128gb was on sale at the local BB store.
180 mb/sec read 130 mb/sec write
I was looking for any new memory card with video grade speed microsdxc.

I picked up the same micro card mentioned. Thursday. I have a PC with two SD card slots. What program did you use to clone the old card to the new please?
Post
Topic
Board Hardware
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
by
Poker8
on 11/11/2024, 02:37:09 UTC
samsung pro plus sdxc 128gb was on sale at the local BB store.
180 mb/sec read 130 mb/sec write
I was looking for any new memory card with video grade speed microsdxc.

Thank you for the help and guidance!!
Post
Topic
Board Hardware
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
by
Poker8
on 10/11/2024, 21:52:12 UTC
Is there any advantage to upgrading the MicroSD card from 16 GB to 32 GB?
Can this additional space be utilized to prevent any system issues?
I plan on upgrading to an “Industrial” grade card since it has a wider functioning temperature range than the consumer grades, and just need to decide if 32 GB will make a difference or not.


Reliability.  The new card is more reliable than the factory supplied card.  Memory wise I haven't found a use other than lots of free space.  Maybe a slight bit faster on boot.  I picked a microsd with the fastest memory access speed I could find and I could only find a card with 128GB on sale.  It's rated industrial or gaming speeds and temps.  Works fine.  I believe my system is more stable.  I seemed to have more crashes with the factory 16GB. Now, almost none.  

That's my experience.

With more memory you could download more programs for your LINUX os running on the raspberry PI Or use the space for downloaded research online.  but then This machine really only has one purpose. Cache memory belongs in ram and on the NVME drive.  They are fast.  The system memory on the microsd is dedicated to OS programs.  That's proper delegation and design.

What brand of microsd card did you purchase? I have been running my new Apollo2 for six days and it is 94.35% synced. It has crashed a few times during this process. It has shown usually 16/32 connections. My factory 1tb nvme card has 37% remaining space left. So, I will probably go to a larger nvme also.
Post
Topic
Board Hardware
Re: Official FutureBit Apollo II/BTC Software/Image and Support thread
by
Poker8
on 08/11/2024, 17:34:42 UTC
2.0.6 is finally merged on production and doing a public test before pushing to everyone next week

If anyone wants to test ssh into your device (futurebit/password you set for your dashboard) and

Code:
cd /opt/apolloapi/backend/

sudo ./update

to manually force an update

reminder can take up to 20 min to rebuild the system and it will auto reboot when finished. Close your UI tab and clear cache so your browser does not load the old version.

Please shoot any build issue or bugs...this will definitely fix all the graphql errors small number of users have seen

Sorry this took way longer than planned!

Is this ready for public release yet?