Bitcoin Forum
July 30, 2025, 10:37:29 PM *
News: Latest Bitcoin Core release: 29.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 [137] 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 »
  Print  
Author Topic: Official FutureBit Apollo II/BTC Software/Image and Support thread  (Read 58286 times)
eagleye
Jr. Member
*
Offline Offline

Activity: 114
Merit: 1


View Profile
November 30, 2024, 10:54:48 AM
 #2721

Hi
So unfortunately due to my internet provider and 4g/5g wireless restrictions in the UK I cannot open ports on my Wireless router  Angry
I was wondering what opening the port actually does ??
also would it work if I got a copy of the connections from a miner that had 64 connections and copy/paste them into my miner manually, would that work?

otherwise super impressed with this unit and I am more than happy to let it run with the restrictions that I have at the moment  Smiley

Thanks in advance people

SD
the ports allow incoming connections from other nodes.  the bitcoind attempts to open those ports.  It pushes out to other nodes to connect using a master list in a node database.  Once established the bitcoind creates P2P node connections. At this time it opens the incoming ports.  If successful you will see your node count increase.  If your providers is blocking incoming connections it may be futile and at the mercy of your provider.  Some routers close the ports for firewall purposes which is why you log into the router to open the ports.

The most important thing for all apollo users to do is look at their log.  media/nvme/Bitcoin/debug.log.   It gives loads of information on the performance of your node and status.  You can see the connections made to other full nodes or block only relays.  You can see startup and shutdown sequences.  When the bitcoind node program starts up you will see the sequence of events including the attempt to connect to the outside world.  If it fails you should see the errors there.  Your node is constantly connecting to new nodes around the world on the P2P network(decentralized).  Adding and dropping connections.  In the node tab in the GUI you can see the different nodes and addresses your apollo is connecting to and these change over time.  What is fun is to see when you connect to another apollo node.

This log also addresses the question in a previous post about the node software using the system drive for bitcoin data storage instead of the nvme drive.  during startup it defaults to the system drive for bitcoin data storage files and then reverts to the nvme drive for bitcoin data when it is found.  Described in the logs.
BrokenTractor
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
November 30, 2024, 06:11:07 PM
 #2722

I just rebooted the node and everything is up and running on v2.0.5.  I'll stay here since my node has been running well and I don't want to fix whats not yet broken on the node until these update bugs are fixed.  I don't want to have to go through reflashing a good memory card.


That is my thoughts as well. I am mining with 2 other miners using the node as well, all 3 using diff wallets and no problems. So no reason to chance updating it.

My choice was to download the update directly at https://github.com/jstefanop/apolloapi-v2/releases and then simply re-flash my 3 node machines back-to-back on new MicroSD's. It's pretty much risk free and it only took about 45 seconds on each machine to reconfigure with the minimal settings. The upside to this is that I can also keep the large update file on-hand for any future needs if necessary. If this version doesn't work out I still have the old v2.0.5 MicroSD's as well as the backups for each machine. So far so good on v2.0.6.

Cheers!

Hey PennyBit,     
I had made an old note that loading a newly flashed micro SD card would format the SSD card when it loaded for the first time. Has this behavior changed with v2.0.6? Does it now check first if you already have data on the SSD before trying to format it?
When you started v2.0.6 with the newly flashed micro SD card did it format your SSD card as well or do you still have all your Bitcoin Data intact?
I want to do it the way you did, since I have a new Micro SD card I want to use, as long as it doesn’t wipe all my node data. And if I take out the nvme SSD card before first startup will it try to create a data directory on the system disk instead?
PennyBit
Jr. Member
*
Offline Offline

Activity: 104
Merit: 8


View Profile
December 01, 2024, 12:03:58 AM
 #2723

I just rebooted the node and everything is up and running on v2.0.5.  I'll stay here since my node has been running well and I don't want to fix whats not yet broken on the node until these update bugs are fixed.  I don't want to have to go through reflashing a good memory card.


That is my thoughts as well. I am mining with 2 other miners using the node as well, all 3 using diff wallets and no problems. So no reason to chance updating it.

My choice was to download the update directly at https://github.com/jstefanop/apolloapi-v2/releases and then simply re-flash my 3 node machines back-to-back on new MicroSD's. It's pretty much risk free and it only took about 45 seconds on each machine to reconfigure with the minimal settings. The upside to this is that I can also keep the large update file on-hand for any future needs if necessary. If this version doesn't work out I still have the old v2.0.5 MicroSD's as well as the backups for each machine. So far so good on v2.0.6.

Cheers!

Hey PennyBit,    
I had made an old note that loading a newly flashed micro SD card would format the SSD card when it loaded for the first time. Has this behavior changed with v2.0.6? Does it now check first if you already have data on the SSD before trying to format it?
When you started v2.0.6 with the newly flashed micro SD card did it format your SSD card as well or do you still have all your Bitcoin Data intact?
I want to do it the way you did, since I have a new Micro SD card I want to use, as long as it doesn’t wipe all my node data. And if I take out the nvme SSD card before first startup will it try to create a data directory on the system disk instead?


Hi BrokenTractor,

When the MicroSD is flashed it is flashed in the correct OS language (Linux) along with the new default Apollo v2.0.6 OS and will overwrite anything currently on the MicroSD your aiming at (so make sure the target MicroSD has nothing on it you want to keep). The process doesn't format the NVME node drive or do anything else except you will lose any "special" data you might have added in the "Bitcoin node configuration" under the "Settings" menu - things such as "listenonion=0" or "addnode=xxx.xx.xxx.xx", etc. At least that was my experience.

After you flash the new card just replace the old card with the newly flashed card and insert it into the appropriate slot and boot up. At this point you will need to re-enter your information such as wallet address, user info, etc. - the same info you were previously using is what I would suggest unless you want to change it now. After that, everything will start up and your node will pick up where it left off (or catch up first). That's it!

Cheers!
bubbAJoe
Newbie
*
Offline Offline

Activity: 105
Merit: 0


View Profile
December 01, 2024, 09:29:27 PM
 #2724

I just rebooted the node and everything is up and running on v2.0.5.  I'll stay here since my node has been running well and I don't want to fix whats not yet broken on the node until these update bugs are fixed.  I don't want to have to go through reflashing a good memory card.


That is my thoughts as well. I am mining with 2 other miners using the node as well, all 3 using diff wallets and no problems. So no reason to chance updating it.

My choice was to download the update directly at https://github.com/jstefanop/apolloapi-v2/releases and then simply re-flash my 3 node machines back-to-back on new MicroSD's. It's pretty much risk free and it only took about 45 seconds on each machine to reconfigure with the minimal settings. The upside to this is that I can also keep the large update file on-hand for any future needs if necessary. If this version doesn't work out I still have the old v2.0.5 MicroSD's as well as the backups for each machine. So far so good on v2.0.6.

Cheers!

Hey PennyBit,     
I had made an old note that loading a newly flashed micro SD card would format the SSD card when it loaded for the first time. Has this behavior changed with v2.0.6? Does it now check first if you already have data on the SSD before trying to format it?
When you started v2.0.6 with the newly flashed micro SD card did it format your SSD card as well or do you still have all your Bitcoin Data intact?
I want to do it the way you did, since I have a new Micro SD card I want to use, as long as it doesn’t wipe all my node data. And if I take out the nvme SSD card before first startup will it try to create a data directory on the system disk instead?


https://www.youtube.com/watch?v=uoDD1LEI4DY
PennyBit
Jr. Member
*
Offline Offline

Activity: 104
Merit: 8


View Profile
December 01, 2024, 10:22:55 PM
 #2725

I just rebooted the node and everything is up and running on v2.0.5.  I'll stay here since my node has been running well and I don't want to fix whats not yet broken on the node until these update bugs are fixed.  I don't want to have to go through reflashing a good memory card.


That is my thoughts as well. I am mining with 2 other miners using the node as well, all 3 using diff wallets and no problems. So no reason to chance updating it.

My choice was to download the update directly at https://github.com/jstefanop/apolloapi-v2/releases and then simply re-flash my 3 node machines back-to-back on new MicroSD's. It's pretty much risk free and it only took about 45 seconds on each machine to reconfigure with the minimal settings. The upside to this is that I can also keep the large update file on-hand for any future needs if necessary. If this version doesn't work out I still have the old v2.0.5 MicroSD's as well as the backups for each machine. So far so good on v2.0.6.

Cheers!

Hey PennyBit,     
I had made an old note that loading a newly flashed micro SD card would format the SSD card when it loaded for the first time. Has this behavior changed with v2.0.6? Does it now check first if you already have data on the SSD before trying to format it?
When you started v2.0.6 with the newly flashed micro SD card did it format your SSD card as well or do you still have all your Bitcoin Data intact?
I want to do it the way you did, since I have a new Micro SD card I want to use, as long as it doesn’t wipe all my node data. And if I take out the nvme SSD card before first startup will it try to create a data directory on the system disk instead?


https://www.youtube.com/watch?v=uoDD1LEI4DY

Nice to see a more recent video from someone using the Apollo node.

Cheers!
BrokenTractor
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
December 01, 2024, 11:54:22 PM
 #2726

I just rebooted the node and everything is up and running on v2.0.5.  I'll stay here since my node has been running well and I don't want to fix whats not yet broken on the node until these update bugs are fixed.  I don't want to have to go through reflashing a good memory card.


That is my thoughts as well. I am mining with 2 other miners using the node as well, all 3 using diff wallets and no problems. So no reason to chance updating it.

My choice was to download the update directly at https://github.com/jstefanop/apolloapi-v2/releases and then simply re-flash my 3 node machines back-to-back on new MicroSD's. It's pretty much risk free and it only took about 45 seconds on each machine to reconfigure with the minimal settings. The upside to this is that I can also keep the large update file on-hand for any future needs if necessary. If this version doesn't work out I still have the old v2.0.5 MicroSD's as well as the backups for each machine. So far so good on v2.0.6.

Cheers!

Hey PennyBit,     
I had made an old note that loading a newly flashed micro SD card would format the SSD card when it loaded for the first time. Has this behavior changed with v2.0.6? Does it now check first if you already have data on the SSD before trying to format it?
When you started v2.0.6 with the newly flashed micro SD card did it format your SSD card as well or do you still have all your Bitcoin Data intact?
I want to do it the way you did, since I have a new Micro SD card I want to use, as long as it doesn’t wipe all my node data. And if I take out the nvme SSD card before first startup will it try to create a data directory on the system disk instead?


https://www.youtube.com/watch?v=uoDD1LEI4DY

Thanks for your input guys. It looks like I was worried about nothing. I searched why I had made that note and found it was a very old issue with a much earlier version but was fixed in 2021. I found the below note in updated post #3 on page one of this thread.

Release 7/31/21
-Updated Apollo UI to latest 0.3.1
-Image no longer wipes SSD if it detects it has already been formatted
-Added additional swap memory to prepare for Lightning network/block explorer apps
-System level fixes/tweaks for stability
PennyBit
Jr. Member
*
Offline Offline

Activity: 104
Merit: 8


View Profile
December 02, 2024, 02:00:32 AM
 #2727

I just rebooted the node and everything is up and running on v2.0.5.  I'll stay here since my node has been running well and I don't want to fix whats not yet broken on the node until these update bugs are fixed.  I don't want to have to go through reflashing a good memory card.


That is my thoughts as well. I am mining with 2 other miners using the node as well, all 3 using diff wallets and no problems. So no reason to chance updating it.

My choice was to download the update directly at https://github.com/jstefanop/apolloapi-v2/releases and then simply re-flash my 3 node machines back-to-back on new MicroSD's. It's pretty much risk free and it only took about 45 seconds on each machine to reconfigure with the minimal settings. The upside to this is that I can also keep the large update file on-hand for any future needs if necessary. If this version doesn't work out I still have the old v2.0.5 MicroSD's as well as the backups for each machine. So far so good on v2.0.6.

Cheers!

Hey PennyBit,     
I had made an old note that loading a newly flashed micro SD card would format the SSD card when it loaded for the first time. Has this behavior changed with v2.0.6? Does it now check first if you already have data on the SSD before trying to format it?
When you started v2.0.6 with the newly flashed micro SD card did it format your SSD card as well or do you still have all your Bitcoin Data intact?
I want to do it the way you did, since I have a new Micro SD card I want to use, as long as it doesn’t wipe all my node data. And if I take out the nvme SSD card before first startup will it try to create a data directory on the system disk instead?


https://www.youtube.com/watch?v=uoDD1LEI4DY

Thanks for your input guys. It looks like I was worried about nothing. I searched why I had made that note and found it was a very old issue with a much earlier version but was fixed in 2021. I found the below note in updated post #3 on page one of this thread.

Release 7/31/21
-Updated Apollo UI to latest 0.3.1
-Image no longer wipes SSD if it detects it has already been formatted
-Added additional swap memory to prepare for Lightning network/block explorer apps
-System level fixes/tweaks for stability


That's a hoot. Reminds me of when I was clearing out some of my old stuff from the house I grew up in after my dad passed. I found a box of old things that contained an old notebook I had once used as a sudo diary of sorts. Inside I found a page that stated, "Beware, don't date that crazy Sharon again!!!" The funny thing is, I can't even remember who she was - lol.

Cheers!
eekbert
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
December 02, 2024, 04:26:03 AM
 #2728

Hi, I upgraded my Apollo II full node to V2.0.6 and it worked solo for a few days. Now, the web gui reports 0 degrees and 0.0 Th/s . However, it is mining to the pool. What is going on? Any help would be appreciated! Regards, Eino
terra.tec
Jr. Member
*
Offline Offline

Activity: 37
Merit: 7


View Profile
December 02, 2024, 10:38:13 AM
 #2729

Hi, what is your hashrate in eco mode with an Apollo II?

My device delivers 5.4 Th/s with 96.4% error rate (console output).
The GUI always shows 0%.

@jstefanop: is this a bug in the GUI? Because the Apollo-BTC 1 shows 1-3% (as expected).
floridaman86
Jr. Member
*
Offline Offline

Activity: 49
Merit: 4


View Profile
December 02, 2024, 08:21:34 PM
 #2730

THIS IS THE SUPPORT THREAD: Keep this thread on topic!
All other comments/general questions go to the anouncment thread: https://bitcointalk.org/index.php?topic=5314398.0
__________________________________________________

We are depreciating Bitcointalk forum support for FutureBit devices and latest support and download links etc is at our dedicated support page here:

https://www.futurebit.io/apollo-btc-support

Bitcointalk has been home for us for almost 10 years now but with our increased customer base we are moving to more dedicated support through our website/email!


Getting Started

This post is for the Full Package/Node version, while it is geared for new users its still recommended you read the whole post as there is important information that pertains to how our system works.

If you are looking for software for your USB Standard Version to run on your own system see post below:

https://bitcointalk.org/index.php?topic=5340015.msg57091051#msg57091051

If you are looking for the Apollo BTC Image for your SD card (to re-flash to stock state etc) you can find that below:

https://bitcointalk.org/index.php?topic=5340015.msg57091052#msg57091052

Below are the quick getting started instructions that you should have also received inside your Apollo, with more details and an FAQ section at the end. This thread is a great resource for additional questions, and is always monitored so if you have additional questions that are not covered below please feel free to post.

  • Carefully remove the Apollo BTC, Power Supply, and AC Power Cable from the box. Be sure not to touch any PCB components on the exposed bottom of the unit
  • Turn the ASIC miner over so the blue micro-controller is exposed. Make sure the white Micro SD card, as well as the M.2 SSD are both firmly in their sockets and did not become loose during shipment
  • Plug in your HDMI Monitor cable to the side HDMI port on your Apollo, and a USB Keyboard/Mouse to the USB ports in the back of the Apollo. If you are not using wifi, plug in your network ethernet cable to the ethernet port on the back of the unit (note you can setup your Apollo over ethernet without a monitor/keyboard/mouse if you wish, see instructions below).
  • Plug the supplied AC power cable into the APU-200W Power supply, and the other end into your AC socket (please note the power cable is for NA markets, the power supply works in all markets (120 and 240v), but you will need an adapter or your own AC cable). Plug in the two 6 Pin PCIE output cables into both power ports of the Apollo. Make sure the 6 Pin connectors are firmly plugged into the Apollo, the cable will overheat if it does not have good contact.
    WARNING: Always make sure both PCIE plugs are plugged into the Apollo, even if you are using your own PSU
    NEVER Plug in two separate power supplies into the same Apollo THIS IS A FIRE HAZARD
  • If you ordered Standard Units, repeat the steps above, and plug in the supplied Micro USB cable to the back Micro USB Port of the Standard Apollo and the other end into the USB port of the Full Package Apollo (you can use any standard USB hub if you run out of USB ports).
  • Switch on your power supply on all the Apollo units, and wait for the Full Package Apollo to boot. Please be patient on first Boot, the Apollo BTC will automatically set up your SSD, configure the Bitcoin Node, and a bunch more system level setup that can take several minutes to complete. Once it reaches the login screen, type in "futurebit123" as the password.
  • Once logged in, you will automatically be directed to the web dashboard. First connect your Apollo to your wifi network if you are not using an ethernet cable (internet/wifi icon on upper right corner of screen), then follow the setup instructions on the dashboard to setup your pool and dashboard password
  • Thats it! You should be presented with your Apollo’s dashboard and any connected standard Apollos should be automatically mining on your pool. You can also check out your node on the node dashboard on the right side panel. It should have already started syncing!


If you want to interact with your Apollo directly through its web dashboard without a monitor/keyboard/mouse setup you can do so, and it works similar to most web based miners

  • Follow the steps above and make sure your Apollo BTC is connected to ethernet before powering it on
  • Wait several minutes until the Apollo has fulled booted and started mining (slow front Red LED flashing)
  • Connect your PC, tablet, or mobile phone to the same local network your Apollo is plugged into
  • If your are on a Mac or iOS/Andriod device navigating to futurebit-btc.local might work
  • If this does not work you need to locate the Apollo BTC's local IP address. Easiest way is to either log into your router app/settings and find it in the device list, or download an ip scanner tool that lists all the device IPs connected to your network/
  • Once you find your Apollos IP address, copy and paste it into your web browser, and you will be directed to the Apollo's webdashboard/setup page




Choosing/Configuring a Pool

Picking a Bitcoin pool to mine on with your Apollo BTC is a more important process today than it has been in the past (or if you have mined on other lower difficulty coins). This is because of two main reasons:

1) Due to the low relative hash-rate of the Apollo, and the high difficulty of Bitcoin it can take a very long time to receive a minimum payout on some pools, especially if you want to avoid paying a "payout fee." Do your research on each pool and what their minimum payout is and their fees. Once you commit to a pool you will be tied there for up to several months until you get your payout, its its extremely important your committed to that pool before you start mining. While some pools can pay out smaller amounts to their own side chains/internal wallets you have to DYOR on whether this is right for you

2) Bitcoin Pools are very centralized and a lot of hash power directed at these pools are from large mines/cooperations with a large portion in China. While the individual hash-rate of your Apollo might not seem like much, the collective hash power of all FutureBit Apollos could have a significant impact....you are voting on what kind of network you want Bitcoin to turn into when you point your hash power somewhere, and that usually boils down to what the particular pool supports. While we dont want to play sides on where our users choose to point their hash power, we think slush pool is a good first choice. They have a great user interface, relatively low hash-rate, are based in Europe (and outside of China which is important), and are developing Startum V2 protocol which we intend to support and further help decentralizing pooled mining.

Once you have chosen a pool, go to its help section (for example on slush pool its at https://help.slushpool.com/). You need to figure out the mining URL and port for your region, your username if its an account based pool or a wallet address your mined bitcoin will be deposited to if its wallet based, and password (usually can be anything, but some pools use this for options).

You can enter this information the first time you visit the Apollo dashboard, or by selecting the pool settings on the left navigation menu.

  • In the URL field you have to enter both the pool URL as well as the port (ie stratum.slushpool.com:3333). If you do not enter the port the dashboard will not let you save the pool information. You do not need to enter stratum+tcp:// before the pool URL.
  • In the username field follow the instructions your pool gave you for your username (its usually the account or worker name you setup with the pool, or a BTC address). These are sometimes case sensitive, and the Apollo will not connect to the pool if it is not correct
  • In the password field just enter any value if the pool does not require it, or whatever password you setup with the pool/worker (sometimes this is NOT the same as your account pool password). This field is also sometimes used for more advanced pool settings


3) For users wanting to play the lottery with their Apollo (ie solo mine), we are working on direct solo-mining support to your full node on the device itself. For the time being you can use a good solo pool like https://solo.ckpool.org



Mining Settings/Tuning

The Apollo BTC comes pre-tuned with three main modes, and these modes should be more than enough for most users. The Apollo-Miner firmware already has built in per chip tuning so unless you are an expert user that really wants to push the hardware on the extreme efficiency or performance side you probably dont need to touch the custom settings.

Under the Settings side panel you will find the three different modes you can toggle. Your Apollo is shipped and starts mining in ECO mode

ECO: This is the most efficient, quiet, and low power mode. Your Apollo will mine at about 2TH/s in this mode and consume about 120 Watts. The fan should be barely audible in this mode.
BALANCED: This mode provides a good balance between power, efficiency and noise. Your Apollo will mine at about 2.5TH/s in this mode and consume about 160 Watts. The fan will be slightly louder in this mode, but should still be quiet in a normal setting.
TURBO: This mode provides the highest hash rate capable with the FutureBit APU-200 PSU. Your Apollo will mine at about 3TH/s in this mode and consume about 200 Watts. The fan will be loud in this mode.

Custom Settings




Full Node Info

The Apollo Full Node runs the latest release binaries from bitcoincore.org, and is automatically configured and setup at the system level. It will start syncing a clean chain state from block 0 on your nvme SSD on first boot, and is capable of downloading a full unpruned node on its 500 GB drive with a 1-2 year buffer. This is the core that will enable us to release additional apps and services in the coming months and years (solo mining, block explorer, Lightning network all planned in the short term), and allow you the user to verify your own transactions and chain state without needing to trust anyone else.

These updates will be issues directly through the dashboard, and you will see a yellow "Update" button once we start releasing additional functionality.

Few things to keep in mind:

  • While our SBC is extremely powerful for its size, the initial chain state download will stress all 6 of its cores to the max for several days while your node syncs. Its not recommend to run your hashboard past the ECO setting while the node syncs, as this can overheat the CPU and cause it to shutdown. If your in a warmer environment its recommend to stop the miner until the node fully syncs (24-48 hours).
  • Do NOT hard shutdown your system while the node is running (ie press the off button on your power supply). You should always shutdown your system via the shutdown menu in the Apollo Dashboard, or via the Desktop. This will ensure your node saves the chain state properly and does not corrupt the node, or your SD card
  • The node should automatically configure your router to open port 8333 via UPnP, and you should see more than 8 connections in your dashboard. If it stays on 8, this means you need to manually open the port to your Apollos IP address in your router port forwarding rules. This will help count your node as a public node, help other nodes sync, and further decentralize the Bitcoin network.
  • All blockchain data is stored on the NVME drive which is located at /media/nvme on the linux system. It is also accessible on the desktop via the file browser.
  • If you want to download the Bitcoin Core wallet (which is not installed by default for obvious reasons) you need to first shutdown the node via the dashboard menu FIRST, then startup Bitcoin Core UI. The Bitcoin core wallet can not run/share the blockchain data at the same time as the node is running. If you are setting up the wallet for the first time, make sure you select /media/nvme/Bitcoin as the default folder otherwise it will start to download the blockchain on your SD card which will cause you lots of headaches (will fix this with symlinks in an update)
    FUTUREBIT IS NOT RESPONSIBLE FOR LOST WALLETS OR DATA/BITCOIN ON YOUR APOLLO
  • As always, its recommended to store your Bitcoin on a hardware wallet/seed capable wallet where you have your seed backed up. Since the Apollo is a essentially a full desktop computer you can download any third party wallet software you wish, and use almost all USB/Bluetooth hardware wallets
  • Never store wallet data/sensitive information on the SD card your system resides on. Treat the NVME drive as your permanent storage solution (ie third party wallets/apps make sure your wallet info is store in the /media/nvme directory and NOT a default location in the system. If your SD card becomes corrupted/unsusable (which is very common with SD cards), you will need to reflash your SD card which means any information stored on it will be lost. The NVME drive on the other hand is a much more robust storage solution, and any information you have saved on it will be accessible even if you have to wipe your SD card
  • Tell all your Bitcoin friends your miner runs a full node, and you now have a device that embodies one of the purest versions of satoshi's original vision.  Cool  (ie something that has not occurred since the original bitcoin core release when EVERYONE mined, ran a full node, and wallet on the same CPU!)




FutureBit OS/System

DO NOT perform a distribution update to 22.04, only regular and security update are supported. You will need to reflash your SD card if you perform this update as its not supported.

The FutureBit Apollo BTC with its modern 6 core ARM processor and 4 GB of RAM allows it to run a full desktop environment. It runs a flavor of the latest Ubuntu 20.04 operating system with 5.10 linux kernel. You can run almost any Linux based application and use it as a full desktop/web browser system.

  • Most Monitors, Keyboards/Mouse, and bluetooth accessories will work with the system, but support is limited beyond the basics. Dont expect high resolution / odd sized monitors to work, or drivers for all USB devices to be available.
  • We chose the Ubuntu Desktop environment since it is a familiar and easy to use desktop even if you have never used linux. All your wifi/settings/login/shutdown items are on the upper right hand corner, and all internal apps are available on the dock at the right (OS comes pre-installed with several useful applications
  • It is beyond the scope of FutureBit to provide support for desktop/ OS level questions. The linux/ubunutu community is huge, so please direct questions to places dedicated for such support and keep this thread on topic for things to do with Bitcoin Apps, Mining support, and Full Node support
  • Just like we outlined for Bitcoin wallets above, if you do install third party apps that store information or work on the system make sure you use the NVME SSD drive to do so. Anything you store on the SD card (which is where the OS, your Desktop, and Home folders reside) will be lost in the event the SD card becomes corrupted or you need to reflash it




LED Status Lights

Front Red LED:

-Fast Blinking LED: System Boot/Hardware initialization
-Solid LED: Hardware passed all checks/inits, ready to start mining
-Slow Blinking LED: Miner successfully connected to hashboard/started mining

Hashboard Yellow LEDs

-On the bottom of the hashboard there are four status LEDs that are not directly visible due to the controller blocking them, but once they activate they are obvious and easy to see (lots of flashing). These indicate normal mining/share activity, and will only power on if you are successfully connected to your pool, and there are no issues with your hashboard (this is akin to the "red flashes" if you have an Apollo LTC)

If these LEDs dont come on it means

1) Your not properly connected to the internet
2) Your pool information is input incorrectly
3) There is a hardware fault on the hashboard (unlikely)

Green SBC LED:

-If you turn your Apollo over there is a green status LED that turns on when your board has successfully booted, and turns off when it has fully shutdown
-Do not unplug your Apollo's power cable, or shutoff the power supply until this LED has turned off after you have shutdown your system



If these posts do not cover your question, or you have additional questions that has not already been answered feel free to post and someone from the community for FutureBit will respond. You can also reach support directly at www.futurebit.io.




I can't get etcher to work on the miner, anyone know how to make it work? I'm trying to flash the drive
PennyBit
Jr. Member
*
Offline Offline

Activity: 104
Merit: 8


View Profile
December 02, 2024, 09:55:14 PM
 #2731

THIS IS THE SUPPORT THREAD: Keep this thread on topic!
All other comments/general questions go to the anouncment thread: https://bitcointalk.org/index.php?topic=5314398.0
__________________________________________________


I can't get etcher to work on the miner, anyone know how to make it work? I'm trying to flash the drive


Don't run Etcher on the miner. Here are the full instructions from the Futurebit website: https://www.futurebit.io/flashing-sd-card

Cheers!
gatorandy
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
December 03, 2024, 03:24:01 PM
 #2732

My Apollo II stops hashing after about 5 minutes from a reboot. I did notice that even when it hashes the fans show “n.a. rpm” despite the board being in the 80s on eco mode. I reflashed the device but still experiencing the same issue. My initial guess is it’s overheating since I’ve never heard the fans. When I used the device last winter the fans would spin up briefly on boot but that has not been happening.
PennyBit
Jr. Member
*
Offline Offline

Activity: 104
Merit: 8


View Profile
December 03, 2024, 04:34:07 PM
 #2733

My Apollo II stops hashing after about 5 minutes from a reboot. I did notice that even when it hashes the fans show “n.a. rpm” despite the board being in the 80s on eco mode. I reflashed the device but still experiencing the same issue. My initial guess is it’s overheating since I’ve never heard the fans. When I used the device last winter the fans would spin up briefly on boot but that has not been happening.

Whoa . . . when you say "board being in the 80s on eco mode" I assume you're referring to the temp being in the 80's as in Celsius (not Fahrenheit). If so, that's too high and you are probably over-heating. And that's why it's stopping. Sounds to me like it's repair time if it's not already cooked. You might want to reach out to Futurebit for a fan replacement.

Cheers!
LeoFist
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
December 05, 2024, 03:55:08 PM
 #2734

Hello, is there a recommended max Temperature for the Apollo 2 full node and miners that is a healthy steady temp for long-term use? Asking because I'd like to try to maintain BALANCED mode as much as possible, but if the indoor temp increases, I would just reduce it to ECO until indoor temp drops again.
PennyBit
Jr. Member
*
Offline Offline

Activity: 104
Merit: 8


View Profile
December 05, 2024, 10:10:34 PM
 #2735

Hello, is there a recommended max Temperature for the Apollo 2 full node and miners that is a healthy steady temp for long-term use? Asking because I'd like to try to maintain BALANCED mode as much as possible, but if the indoor temp increases, I would just reduce it to ECO until indoor temp drops again.

Check out the post from jstefanop on August 16, 2024-  #2397 https://bitcointalk.org/index.php?topic=5340015.msg64433384#msg64433384
He addresses some heat limits there.

Cheers!
LeoFist
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
December 05, 2024, 11:01:46 PM
 #2736

Hello, is there a recommended max Temperature for the Apollo 2 full node and miners that is a healthy steady temp for long-term use? Asking because I'd like to try to maintain BALANCED mode as much as possible, but if the indoor temp increases, I would just reduce it to ECO until indoor temp drops again.

Check out the post from jstefanop on August 16, 2024-  #2397 https://bitcointalk.org/index.php?topic=5340015.msg64433384#msg64433384
He addresses some heat limits there.

Cheers!

Thanks, I did see this, I'm also wondering if there is a recommended temp range per mode (ECO, BALANCED, etc.), not just a max of 80c. I'm trying to maximize the lifespan and not just try to stay under the max.
jstefanop, any thoughts?
eagleye
Jr. Member
*
Offline Offline

Activity: 114
Merit: 1


View Profile
December 06, 2024, 02:55:13 AM
Last edit: December 06, 2024, 06:50:03 AM by eagleye
 #2737

Hello, is there a recommended max Temperature for the Apollo 2 full node and miners that is a healthy steady temp for long-term use? Asking because I'd like to try to maintain BALANCED mode as much as possible, but if the indoor temp increases, I would just reduce it to ECO until indoor temp drops again.

Check out the post from jstefanop on August 16, 2024-  #2397 https://bitcointalk.org/index.php?topic=5340015.msg64433384#msg64433384
He addresses some heat limits there.

Cheers!

Thanks, I did see this, I'm also wondering if there is a recommended temp range per mode (ECO, BALANCED, etc.), not just a max of 80c. I'm trying to maximize the lifespan and not just try to stay under the max.
jstefanop, any thoughts?
Fan speed and air flow and temp.  My unit runs balanced at 69-71 deg. C. 3600RPM optimal.  When it gets hotter RPM jumps to 3800 rpm.  That is optimal to me.  Also I have my unit turned sideways to get maximum airflow through the bottom(now the side)vents.  These bottom vents give maximum cooling flow.  Top vents are too restrictive.  In ECO mode they are ok.  Fan runs too hard when all the vents are faced down.  Room temp 74-78 deg F.   1" stilts or a open frame stand to lay flat

Turbo mode works, but then it sounds like an antminer with turbo fan.  
3600RPM is ok.  3800RPM is  a little loud and happens when ambient temp increases above 78F.  Check and blow dust out every 2 / 3 months.  The fan speed would also indicate this when it increases unexpectedly at lower temps. Listen to your fan as a heartbeat telling you how your miner is doing.

I haven't been able to leave my apollo II alone for extended periods.  My unit is still not stable enough.  I've had occasional power brownout surge knock my apollo offline and shut down running high speed fan.  No remote reset or monitoring beyond the firewall for me.  It can run 7 days non-stop with no issues then the node crashes after only 1 or 2 days of a reboot.
v2.0.6 didn't work for me.  Apollo would freeze.  Crashed more often than v2.0.5.  Still running v2.0.5 stable.
aurel57
Legendary
*
Offline Offline

Activity: 1344
Merit: 1001



View Profile
December 06, 2024, 11:46:50 AM
 #2738

Hello, is there a recommended max Temperature for the Apollo 2 full node and miners that is a healthy steady temp for long-term use? Asking because I'd like to try to maintain BALANCED mode as much as possible, but if the indoor temp increases, I would just reduce it to ECO until indoor temp drops again.

Check out the post from jstefanop on August 16, 2024-  #2397 https://bitcointalk.org/index.php?topic=5340015.msg64433384#msg64433384
He addresses some heat limits there.

Cheers!

Thanks, I did see this, I'm also wondering if there is a recommended temp range per mode (ECO, BALANCED, etc.), not just a max of 80c. I'm trying to maximize the lifespan and not just try to stay under the max.
jstefanop, any thoughts?
Fan speed and air flow and temp.  My unit runs balanced at 69-71 deg. C. 3600RPM optimal.  When it gets hotter RPM jumps to 3800 rpm.  That is optimal to me.  Also I have my unit turned sideways to get maximum airflow through the bottom(now the side)vents.  These bottom vents give maximum cooling flow.  Top vents are too restrictive.  In ECO mode they are ok.  Fan runs too hard when all the vents are faced down.  Room temp 74-78 deg F.   1" stilts or a open frame stand to lay flat

Turbo mode works, but then it sounds like an antminer with turbo fan.  
3600RPM is ok.  3800RPM is  a little loud and happens when ambient temp increases above 78F.  Check and blow dust out every 2 / 3 months.  The fan speed would also indicate this when it increases unexpectedly at lower temps. Listen to your fan as a heartbeat telling you how your miner is doing.

I haven't been able to leave my apollo II alone for extended periods.  My unit is still not stable enough.  I've had occasional power brownout surge knock my apollo offline and shut down running high speed fan.  No remote reset or monitoring beyond the firewall for me.  It can run 7 days non-stop with no issues then the node crashes after only 1 or 2 days of a reboot.
v2.0.6 didn't work for me.  Apollo would freeze.  Crashed more often than v2.0.5.  Still running v2.0.5 stable.


eagleye did you get the email from FutureBit telling us not to run them on their side? My temps are defiantly lower on its side but they say it could not properly cool the psu.
MakerAZ
Jr. Member
*
Offline Offline

Activity: 46
Merit: 5


View Profile
December 06, 2024, 01:12:14 PM
 #2739

I want to run my miner in Turbo mode most of the time. Apart from it is beeing noisy at that mode, my appartment is quite warm during winter season. Is it OK if I operate the miner outdoors? Outside temperature during winter can range from 15 Degrees C to close to 0. We may have a few days below 0 in February. Humidity is below 80%.
I will locate the miner in my balcony and will fully protect it from any dust and rain.
eagleye
Jr. Member
*
Offline Offline

Activity: 114
Merit: 1


View Profile
December 06, 2024, 02:48:51 PM
 #2740

Hello, is there a recommended max Temperature for the Apollo 2 full node and miners that is a healthy steady temp for long-term use? Asking because I'd like to try to maintain BALANCED mode as much as possible, but if the indoor temp increases, I would just reduce it to ECO until indoor temp drops again.

Check out the post from jstefanop on August 16, 2024-  #2397 https://bitcointalk.org/index.php?topic=5340015.msg64433384#msg64433384
He addresses some heat limits there.

Cheers!

Thanks, I did see this, I'm also wondering if there is a recommended temp range per mode (ECO, BALANCED, etc.), not just a max of 80c. I'm trying to maximize the lifespan and not just try to stay under the max.
jstefanop, any thoughts?
Fan speed and air flow and temp.  My unit runs balanced at 69-71 deg. C. 3600RPM optimal.  When it gets hotter RPM jumps to 3800 rpm.  That is optimal to me.  Also I have my unit turned sideways to get maximum airflow through the bottom(now the side)vents.  These bottom vents give maximum cooling flow.  Top vents are too restrictive.  In ECO mode they are ok.  Fan runs too hard when all the vents are faced down.  Room temp 74-78 deg F.   1" stilts or a open frame stand to lay flat

Turbo mode works, but then it sounds like an antminer with turbo fan.  
3600RPM is ok.  3800RPM is  a little loud and happens when ambient temp increases above 78F.  Check and blow dust out every 2 / 3 months.  The fan speed would also indicate this when it increases unexpectedly at lower temps. Listen to your fan as a heartbeat telling you how your miner is doing.

I haven't been able to leave my apollo II alone for extended periods.  My unit is still not stable enough.  I've had occasional power brownout surge knock my apollo offline and shut down running high speed fan.  No remote reset or monitoring beyond the firewall for me.  It can run 7 days non-stop with no issues then the node crashes after only 1 or 2 days of a reboot.
v2.0.6 didn't work for me.  Apollo would freeze.  Crashed more often than v2.0.5.  Still running v2.0.5 stable.


eagleye did you get the email from FutureBit telling us not to run them on their side? My temps are defiantly lower on its side but they say it could not properly cool the psu.

I never saw that e-mail.  my experience is the CPU/system temp is fine.  System temp doesn't go above 70.  Fan does increase on its own. without the miner running.  Airflow is the key to cooling and those bottom vents and spacing in original design don't give enough airflow trapping heat causing fan to run faster.   All dust falling to the tabletop get sucked into those vents.   To lay flat there needs to be at least 1" of space below apollo to allow for proper airflow volume as fan speed increases.  The top vents would have to be double the width.  Fan speed and sound is always my key indicator to how efficient a system is running.  Faster fans means higher temps needing more airflow.  In this case constricted airflow needs higher fan speeds.

When my miner is running system temp is 43C with cpu idle and miner at 68-70C.  3600RPM.  This higher fan speed seems to cool the cpu fine.  Laying the apollo flat in eco mode works fine and the fan speed is quiet enough.

RE running miner outside.  Other than ambient humidity and environment.  I think the Miner should run fine in turbo mode and keep the miners cool. Fan speed is key.  You need faster fan speeds to move the air to cool the miners.  For longevity of the miner processor i think those temps should stay below 75C.  With antminers those fans would keep the miner temp between 60 and 70C.   I ran antminers outside in the garage and they ran great with temps below 60F.  Lower fan speeds keeping system cool.  Running these fans at full speed helps move maximum airflow but does put stress on those fans causing higher risk of failure.  Running at 3600RPM/half speed and the fans can last a long time with very low risk of failure.   Always listen to the sounds your fans are making.

Case Study:  I just turned my apollo down, lay flat running in balanced mode.  Temp increase to 72-74C on the miner.  Fan increase 4000 to 4500RPM.  No change in system temp 43C. So that email suggestion is a big fail on my apollo II.  Dust is building up on top slots after 2 months of running so will need to be blown clean soon. Bottom slots on the side operation seem to be clean and cool.  Isn't the bottom where the raspberry pi CPU is located?
Pages: « 1 ... 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 [137] 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!