I havent received my Apollo yet (should arrive tomorrow) I've got a 1tb drive to swap in straight away too.
The link above, the Satoshi 0.21.1, are they all Apollos??
That's the entire bitcoin network. To verify what bitcoin version yours is running, login to it and type. bitcoin-cli getnetworkinfo | head
It should say near the top "subversion": "/Satoshi:0.21.1/",
P.S. would be of interest to post what it replies. Its running the latest 21.1 core binaries. The public apollo nodes will have a user agent string "FutureBit-Apollo-Node" you can see them if you scroll down in that list. |
|
|
|
Just want to take a moment here to thank you guys taking part in this movement, because FutureBit is not just some consumer hardware company making toy miners but it truly is a movement enabled by all you guys. https://bitnodes.io/nodes/?q=Satoshi:0.21.1So cool to see those Apollo user agents dominating that list Hundreds of nodes have come online, and thousands more will once they are done syncing (and make sure you are all forwarding those 8333 ports!) I am beyond humbled in seeing this play out in real time, and I take my hat off to everyone sitting there running these on their desks, not because its profitable, not because its cool, but because you truly believe in what Bitcoin is and should be and we are all taking the first step in reclaiming some balance back from these power hungry, greed seeking, centralized entities/individuals that have entrenched themselves in and are trying to soil the true vision of what Bitcoin is We have a ways to go but the Future of Bitcoin is looking bright  |
|
|
|
I have the same problem with miner dropouts and can pretty much confirm it is an internet issue, I live in a rural area with very poor and unreliable broadband, and the miner dropouts coincide with internet dropouts.
It is annoying and a hassle to restart the miner every time that happens, especially since I obviously can't do it when I am not at home. An auto-restart feature when the hash rate drops would be incredibly helpful. I also mine Ethereum with HiveOS, and they have such a feature implemented. For people like me with poor internet it is a real helpful feature.
Will have the system auto-restart in the first update hopefully next week. |
|
|
|
Hello anybody, is it possible that these miners can get stuck in some sort of "safe mode" mine only do average 1.35 Th/s and average 82 watts I keep trying different modes and settings say its in different mode but no change the "eco" mode green light is not quite luminated and the temp seems high 48c with extra fan , maybe this has something to do with why I don't see any active workers in slushpool ?
If you dont see active workers it means your pool settings are incorrect. Make sure your not including the stratum+tcp bit in front in your pool section(whole url for slush should be stratum.slushpool.com:3333), and double check your username is correct. |
|
|
|
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.
Shoot us an email (reply to your order email). Well trouble shoot node drive...most likely a ssd connection issue. |
|
|
|
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_QKeep 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. |
|
|
|
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. |
|
|
|
Is there a reason why these miners don't have asicboost enabled?
That's pretty much the same as throwing away 10% of your hash rate you'd get for the same power.
Because its not implemented in the ASIC obviously. |
|
|
|
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: 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: 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. |
|
|
|
... 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  |
|
|
|
Hello! How are we now for batch 1. Still need another week to send out?
Thank you
We got most remaining orders out this week. About the tail 10% or so is left to ship next week. |
|
|
|
Received today all setup but the dashboard shows the miner is inactive with no stats/ power info etc but it is mining successfully as it shows on my pool with hashrate any ideas please?
I've got I think the same issue - with the unit connected directly to a monitor I can see the stats fully on the screen. However if I use another PC and connect over the network, then the dashboard loads and sends commands fine, but displays no metrics and looks as if it is inactive. This is a known issue, trying to pinpoint what’s causing it since I can’t reproduce on my end. Shoot us an email if your having this issue so you can send us some logs. Could be pool specific that’s returning some weird data and breaking out json parser for front end. |
|
|
|
Where can I get an image to re-flash my sd card? I already forgot the password I set-up for my miner  I clicked on the link on the first page of this thread but it just took me to a post that mentioned an updated image will be posted soon, but there was no download link to the current image file. Can someone please point me in the right direction? Thanks! Will have this posted today. |
|
|
|
One question ...my node is synched. Now, if I download Bitcoin Core Wallet from the official repo and install it (of course point it to the correct directory), will it just read the status of the blockchain from there, or will it try to sync again...what I definitely don't want to happen ?!
You need to point the core wallet to /media/nvme/Bitcoin and shutdown the node before you start the wallet. The core wallet launches its own bitcoind and two cant be running at the same time. |
|
|
|
Hey guys sorry to everyone that got shipment notifications last week and has had no movement. We had scheduled a pickup last week and another yesterday which Fedex refused to pickup since it would have taken too much space on the truck (even though we made the volume clear both times).
Just rented a truck and dropped off all the backlog of packages this morning, and everyones shipment has been upgraded to 2 day. If your near CA you should get it tomorrow, and everyone else by thurs.
Assembly is going well for rest of orders, we project 75% will be ready to ship by end of the week, and the whole Batch 1 Pre-order will be shipped out by end of next week.
I take it your projection for "the whole batch 1 will be shipped out eonw" was off. The end of next week from your message was June 5. I'm 38xx but I see 36xx and 37xx still waiting. Now John ... I support your work, dedication and finished products. Your expectation management sure could use some work though. I can only go off what my operations team tell me. We were on track before memorial day, but then the holiday hit, and we had to stop the line to correct some issues from the first deliveries so lost about a week there. Either way the original expectations were 4 weeks to complete full Batch 1 shipment, we are only one week behind schedule on that (not counting the 2-3 weeks production start delay). I know everyone is eager to get their product, but you guys have to appreciate the fact that we paid about 20% extra in whole product costs (which is a large chunk of our margins), to procure overpriced parts, to ship everything air from suppliers, and ship everything 2 day to you guys. We could have kept everything as is, with another month delay, but things like that matter to me regardless of whether we are sold out with a long wait list. What we do almost no one does for a reason, its hard as shit and almost no one can do it profitably. Companies funded with 10's of millions have failed where we have succeeded, but we are still just a small company pushing boundaries and we have a lot more delays, growing pains, and learning until we get to where we want to go. Either way I appreciate everyones patience and for coming along for this crazy ride! |
|
|
|
How to connect 2 Apollo to one computer (hashboard mode only, no controller)? Using -comport /dev/ttyACM0 and -comport /dev/ttyACM1 in one apollo-miner command line doesn't work, also running 2x apollo-miner instances with two separate ACM defined doesn't seem to work, both miner pick up orders from one apollo-miner instance.
You need to run a separate instance for each. Just edit the comport to the correct one of each board, you should only have one -comport in your line otherwise it will just pick up the first. |
|
|
|
I fired up my Apollo-BTC the other day and noticed that it's sending out a DNS query every five seconds for raw.githubusercontent.com.
Any insight into what it's after up there?
This is our rushed update mechanism for initial release. Well update this to something else down the line (hopefully git won't ban us in the meantime  |
|
|
|
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: 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. Any updates on this? Would like to run on Raspberry Pi 2 and Raspberry Zero W, any updates would be much appreciated. Will try and get this compiled by end of the week, trying to push out the critical bug updates for the main unit first. |
|
|
|
Well it worked for about 15 minutes, got a pool started and soon the red light went solid and I could no longer access the device, the IP address no longer shows up.
Found the IP address after rebooting and now refuses to connect
- after hooking up a monitor and keyboard, nothing to see here, but the miner suddenly starts mining again and I can access it again. Its still in eco mode, Node syncing is about half way finished now, Did something overheat or is the dynamic IP address a problem?
Locked up again after maybe one hour, cannot access with a monitor or through the IP address, no mining is happening on the website and the the blinking redlight and heat from the unit means its doing something, (using electricity).
They system might lock up a few times while its syncing, it should resolve by itself. Node uses up 100% of system resources, mining has priority though and should not stop. If you want to avoid these issues I would recommend you stop mining for ~24 hours while the node completes most of the syncing. If your in a hot environment it could be that the CPU is overheating and shutting down. While we did extensive tests during syncing and running in ECO mode, it would overheat in certain situations while in Balanced/Turbo. |
|
|
|
For standard hashing unit:
What is the -ao_mode 1 in the last command line parameter?
How to disable Exporting stat ... ERROR: cannot create file descriptor
Otherwise booted and started thrashing immediately on slushpool.
Showing 3.1 TH/s poolside
The -ao_mode is the auto ASIC tuning mode, you should not touch this. You can ignore the error message...did not have time to fix this for the standard unit software and it does not affect anything. |
|
|
|
|
Show Posts
