Oh, interesting! The SSD was upgraded to 1TB. From which batch on will that be? Batch 3? Batch 4? I remember FutureBit guys still saying 500 was easily enough a few months back. Cool to see they changed their mind; just wondering when to expect the 'cutoff' between 500GB full packages and 1TB ones. From what I read, all of the Batch 3 units were upgraded. Yes we upgraded all Batch 3 orders to the 1TB drive! |
|
|
|
I’ve had a full unit since august and it’s worked great without any issues. Recently I got a standard unit (batch 3) to connect to my full unit. I can get the standard unit mining for about 10 minutes and then it goes to inactive status. Then I have to power it off and on then restart mining to get it to start again. But it only will mine for a few minutes again before going inactive. The full unit continues mining without any issues. The red light on the standard unit has the slow red blinking light like it’s mining but it’s showing inactive in the dashboard. I’m running apollo web v0.3.2
Any ideas what the problem could be?
Hmm, yeah I've been having the same exact problem for a while. I was hoping this most recent update would fix it, but looks like I'm still having the same issue. I have 1 full unit and 2 standard units, for some reason all 3 of them wont stay hashing at the same time and one of them will drop off after a while. It's always just one that drops off and they all keep blinking the slow pattern. Do the yellow lights on the bottom continue to flash? The mean the board is still hashing but something is up with the USB connection. You can also try connecting the standard units to a USB hub and trying different USB ports. If a power reset/SD card re-flash does not solve it with latest firmware you can alway contact support and well take care of you. |
|
|
|
my apollo btc units were working fine on my preferred pool until today when suddenly it is rejecting most of the shares for 'low difficulty'.
spoke with several friends on the same mining pool with same units and they all have the same problem... scratching our heads why suddenly today this is a problem
Is this gorilla pool? Admin is in contact with us about it. Issue seems to be isolated with just their pool so could be some weird config issue on their end. |
|
|
|
My BTC NODE : hard drive at 433 GB only 9.65% left ... I am assuming the 500 SSD will run out of space in a year. Did Futurebit get their calculations wrong? I see newer machines are shipping with 1TB SSD. What are we supposed to do?
No purchasing 1TB drives for the first two pre-orders would have cost an extra ~100 at the time, which we couldn't justify passing to users. Once the 500GB drives run out of space in a year or so you'll probably be able to pick up a 1TB drive for 50 bucks
Are we giving up 1% of our hash as donation to Futurebit? Someone has said this is the case. I usually donate 0.25% (1% is a bit high).
Is this confirmed? I know in the LTC version you can make a voluntary donation. With the BTC unit this option is hidden. Views please.
No, and you don't have to believe me sniff your Apollo packets
In the UK the BTC unit is NOT profitable. Rather loss making. Electricity costs are too high: the units are not efficient enough to run at profit.
Has anyone found something that these units can mine profitably? The LTC units are still profitable (thanks mainly to DOGE).
Stop mining fiat. Your mining BTC and 1 BTC=1BTC. Sure you might be DCAing at 10% higher vs exchange temporarily, but your heating your house, securing the network, and who cares when your 2,000 sats a day will be worth 1 cent per sat in the future?
The computer's OS Linux prompts me to update. Should I update or not?
I don't want it to interfere with the FuturebitWebOs (recently updated).
Only update through the web UI, updating through the system will brick it
[Mod note: merged multiple posts]
|
|
|
|
@jstefanop: This can't be correct: Yea internal error usually has to do with no network connection, so your wifi is probably not connecting. Make sure you connecting to 2.4GHz network instead of 5 for better range Because one of the Miner ist always on LAN, an when i connect to LAN or Wifi IP Adress, there is always this "internal message error" Gr€€tz Biosman This is because both interfaces are left "on" by the linux system when you use both LAN and wifi... the Web UI does not know how to deal with that currently. You need to log into the system via a monitor, and turn off the interface you are not using (drop down on the upper right corner of the desktop). |
|
|
|
I seen a standard unit on eBay with a broken usb c port what would it take to get that repaired?
any answer to this? i have one with the same issue. emailed futurebit about it but haven't heard anything yet. i know they are busy getting batch 3 orders out. You can email and well set up a RMA repair for it, but it will probably be cheaper and faster turnaround to go to a local computer repair shop that can just solder it back on in 5 minutes...(pretty easy to do it yourself as well if you know how to solder). |
|
|
|
Thanks, J! Very cool.
I admire the mission of reaching the masses and maximizing decentralization.
I purchased my first four units from you last round and am planning to purchase 4 more next pre-order. For those of us who are a little more hash hungry, does FutureBit have any future plans to offer a more premium model that would retain its quiet operation and power via normal household outlets? Perhaps a 2 or 3-in-one deluxe unit or would that be pushing the boundaries of the last two benefits I mentioned? I was just thinking it could save on other material costs if more boards were combined or what have you.
Thanks in advance! Love your work!
Thanks! We are always pushing boundaries on what can be done in a home setting, and while we probably will never make a 1kw+ machines, it does not take too much of a wild stretch of the imagination to be seeing 300w 10TH units being a possibility. Our goal is to be on par with what the big farms are getting to even out the playing field of home miners in terms of w/TH and $/TH. To get there though we need to significantly ramp up production which is what our goal will be for next year. |
|
|
|
After Update to v3.2 (all via LAN-cable) there is on every Full-Node Machine, following message: There is a problem fetching system stats (Internal error) I own: - One single Full-Node - Two Full-Node with 2 USB-Devices What does it mean? The single Full-Node is connected via LAN, everyhing is fine The other two are connected via Wifi, its seems to work, but i can't reach Miner via Wifi anymore, but Wifi is good. Via LAN no problem. In System Info it shoes me: Active wifi: No active wifi But the Front lights of machine show me blinking: work is fine Where is the problem? I can connect to my Wifi, but after using the "Wifi-IP", nothing works. After reboot in System-Info is always: No active Wifi Greetz Biosman PS: Maybe the wifi-antenna is to weak, i put it a little bit out of machine, is there a possibility to make it longer or to change it? The single Fullnode-Miner with LAN is directly to the router, i can connect dashboard with Wifi no problem. The other machines are not fare away. Amazon_Fire_Stick for TV, MobilePhone etc. all works fine, but not Dashboard via Wifi  Yea internal error usually has to do with no network connection, so your wifi is probably not connecting. Make sure you connecting to 2.4GHz network instead of 5 for better range. |
|
|
|
Same. I refuse to use my house’s heater and my GPUs alone aren’t doing the job of keeping me nice and toasty. Could use a little more hashing so I can get back to basketball shorts and a class-a instead of a hood tuxedo.  Don’t be prudish with those assembly/shipping pics. We need some miner pr0n. Check out my twitter for some cool SMT vids...got a longer treat coming for all pre-order customers so check your email soon! https://twitter.com/JStefanop1/status/1471548325128253450?s=20 |
|
|
|
I left mine updating last night, but it wasn't mining this morning, restarted the miner to no avail, in the end it needed a system restart to sort itself out.
I needed to do this as well but was fine after the reset Yea if you're having any issues after the update, a reboot will fix it. Some system services that run the miner won't restart properly depending on where you initiated the update from. |
|
|
|
Hi Jstefanop, thanks for this new release.
When do you plan to release the solo mining feature on the Apollo? Are you able to give us a forecast?
Thank you.
D.
Priority in the coming months will be getting the App ecosystem up an running (block explorers, lightning, etc). There are already good solo pools you can direct your miner too for solo mining, but will continue work on it next year. |
|
|
|
...
FYI we have full access to the source code and are pretty involved in ASIC development in all the products we build.
...
Yet just making that tiny software change to fix a code bug seems impossible ... FYI you have no involvement in the ASIC development of this miner. I speak from experience having paid bitfury over $100k for bitfury bitcoin asic chips ... You get a dev pack and the chips, they don't care what you think they should do with their ASIC development. Yes you have made it quite clear in this thread your experience is the only one that matters or exists 😂 |
|
|
|
v0.3.2 ReleaseNext version of the Apollo Web UI has been pushed to all Apollo users (you should see a yellow update button on the upper right screen, or refresh the page if you don't). This is a significant stability and bug fix update and also includes the latest miner binaries with many fixes, and latest Bitcoin Core v22 release for your node. Its recommend that every Apollo user upgrade to this version, we have resolved most remaining issues and has been rock stable in our tests (check out our 19 day uptime below!). Release Notes:- Updated Miner Software to latest
- Updated Bitcoin Core to latest
- Added NVME SSD format option in settings (only use if your formatting a newly installed SSD, or if your Node will not start up/drive is corrupted)
- Added Bitcoin Core version number in Node section
- Added swap service directly to API for dynamic ram requirements for upcoming native BTC apps
- Fixed issue that would cause connected standard units to not restart mining after internet outage
- Fixed issue that would cause dashboard to not display stats if system timezone is changed
- Many other stability and big fixes
The update will take 5-15 minutes so please do not refresh your web UI or restart/shutdown the Apollo until the web dashboard has refreshed. The miner should automatically start and dashboard refresh to latest version after update is complete. If you are having issues with the update or not seeing changes, rebooting your Apollo and closing your Web UI window and starting a new one (if you are accessing remotely) should resolve most issues.
|
|
|
|
~
I think people would feel comfortable trying it out and it could only be a good thing for customers which is a good thing for FutureBit right?
I had a random theory the other day; we shall remember that they don't use their own chips and it's not an open source project either, unlike most projects we're used to around here. We're used to getting concise clear answers on all of our questions, but when you're working with big companies and NDAs, stuff gets tricky. It's possible that e.g. they have a license for the chip, but not for 'the asicboost', or something like that. Or maybe they got a spec of the chip (under NDA) that doesn't include everything (like asicboost information / how to use or activate it). Just a theory But it seems to me that we don't achieve anything by pressing further on this. Who knows; maybe the community will release a patch that adds the two bytes which change the string output format..  We shall see  Lol nice theory, unfortunately its not true. If these chips had asicboost capable cores I would have enabled that myself even if we didn't have a "license" for it. For those that have followed me since the early days you know I started futurebit because I was able to substantially increase the hashrate and efficiency of old scrypt chips since the manufacturers themselves had no idea on how to properly implement what the ASIC was capable of. Im definitely not one to leave any extra performance on the table for you guys. FYI we have full access to the source code and are pretty involved in ASIC development in all the products we build. Hi everyone. On October 5th I sent an email to Futurebit support asking when new Apollo BTC firmware releases would be released, including being able to insert more than one pool and have the ability to solo mininig on the Apollo node. I was told that new features would come out but since then I have seen everything stopped. I sent another email on December 1st but they didn't answer me. I see everything very still, do any of you know something? Thank you
Updated miners for the basic units has already been released, we are in final testing for the update to the Full Package system...check your dashboards in the coming days for that yellow update button. Hi. I had been connected by ethernet. I went to connect to wifi. The wifi password kept coming back as invalid (although I know 100# it was entered correctly). Now I am unable to connect to the dashboard any more. I al also no longer connected to the pool. When I try to connect to the IP address of the miner, I receive a message that I am unable to connect. I powered the miner down, the ethernet cable is still connected, but no luck logging back on. Any suggestions?
Could be that the wifi actually connected, try removing the ethernet cable and see if you see a new IP address (after reboot). You can also connect to it via a monitor and keyboard/mouse so you can easily see what's going on with its network connection. |
|
|
|
Should still have the majority of orders placed on the Aug 31st out by end of the year, and the rest the first few weeks of January.
Keeping my fingers crossed for a Christmas surprise in my mailbox. The weather is finally cooling down even in the desert so I could use some heat. Would love to hear that the first ones have gotten out the door or any updates you may have. Some pictures or the assembly or shipping activity would be great to help ease the anxiety as we await out hashing beauties. Good luck with what is probably the most hectic part of the process. I don't envy someone trying to do a lot of shipping this time of year, but I do appreciate it. First PCBs should be off the line next week, and first orders should start shipping shortly after. Yea things are a mess right now, Batch 3 is over 3x the size of the previous batches and we had to split shipments of materials just to be able to get our stuff on flights here. Also had a covid outbreak at the factory which is not helping. With holidays coming up things are going to be slow the next few weeks so realistic probably will have a third of the batch out before New Years, and the rest in January. Sucks I really wanted to have everything to you guys before Christmas for my sanity and yours, but life happens. hi, when we can order new batch? any estimate?
We will be opening more orders in January. |
|
|
|
...
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. |
|
|
|
|
We are finishing PCB production this week, and will hopefully start shipping next. Really wanted to get these out in November but supply chain issues once again put a damper on that (PCBs we’re stuck for weeks trying to get a flight).
Should still have the majority of orders placed on the Aug 31st out by end of the year, and the rest the first few weeks of January.
|
|
|
|
... and still the bug is there: 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: 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.... |
|
|
|
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.1This 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. |
|
|
|
|
Show Posts
