Bitcoin Forum
May 24, 2024, 02:48:41 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: April 17, 2024, 12:46:30 AM
Quote from: jstefanop on April 12, 2024, 03:56:28 AM
Want to get this tested here by a few of you since we dont have a lot of MCU1 devices left to test.

Below feedback would be appreciated:
OS detects internal board and starts up fine
OS detects and starts up external USB Standard units (both Apollo BTC or if any MCU1 owners have an Apollo II standard yet)
Was able to flash an Apollo BTC Full MCU1 and plug in via USB to Apollo 2 Full, it was detected and started contributing hashing.

It appears to be a little finnicky if you are manipulating the web dashboard for both units simultaneously. For example, it was initially showing both units and hashboards on the Apollo 2 miner page. After restarting the Apollo 1, it seems to be operating independently with no apparent communication with the the Apollo 2. Both are mining and contributing hashrate to the pool.

Also doesn't appear that the Apollo I node wants to start up, but this may be by design when connected via USB? I never updated the SSD on it, so ostensibly it couldn't fit the blockchain right now anyway.

Testing further, seems Apollo II device and 2.0.4 OS aren't connecting to Apollo I standard units even after several minutes, maybe just a USB issue?
2  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: April 12, 2024, 01:11:49 AM
Went back and forth a bit with jstefanop for a bit to figure out why my Apollo II could sync & solo mine, but wouldn't stay connected to a pool. Wanted to share what we found in case others encounter the same issue:

Asus routers (and presumably others) have a feature called AiProtection with a a Two Way Intrusion Protection setting that will specifically block bitcoin mining.

https://www.asus.com/support/faq/1008719/#a3

You'll have to disable this if you plan on mining behind any router with a similar protection. Worth noting that it can sometimes be automatically re-enabled during a firmware update.
3  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: January 05, 2022, 03:39:14 AM
Quote from: jstefanop on January 03, 2022, 04:35:57 PM
Quote from: amanz360 on January 03, 2022, 06:20:31 AM
Quote from: mr_eee on January 01, 2022, 10:30:14 PM
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.
I experienced the same issue, except that my standard unit doesn't go active at all anymore. Solid red light, no blinking yellow underneath, while connected via USB. Full unit will continue hashing as normal. Sent an email through the contact form on the futurebit site.
4  Alternate cryptocurrencies / Mining (Altcoins) / Re: Official FutureBit Apollo LTC Image and Support thread on: November 06, 2021, 09:51:31 PM
Has anyone tried replacing the fan on the FutureBit PSU yet? The supply that came with my Apollo LTC is no longer spinning, but the power supply itself seems to be operating just fine.
5  Alternate cryptocurrencies / Mining (Altcoins) / Re: Official FutureBit Apollo LTC Image and Support thread on: February 15, 2021, 08:41:01 PM
Quote from: VictorGT on February 15, 2021, 03:13:24 PM
You can only use two or more pools, if they are both mining the same coin. If you use multipools, use only one (no failover). This is a bfgminer known problem.
Thanks man, did not realize that the problem. Appreciate the answer!
6  Alternate cryptocurrencies / Mining (Altcoins) / Re: Official FutureBit Apollo LTC Image and Support thread on: February 14, 2021, 08:40:40 PM
@jstefanop

Hey, I don't know if this is an issue with the Apollo firmware or the way that Prohashing issues work and switches coins, but figured I'd give you a heads up in case you or anyone else had ideas on how to solve.

TL;DR: When using Prohashing and having an active and failover pool enabled in my Apollo dash, I get high error rate, reducing hashing, and hash power going to active and failover pools simultaneously.


This is what I posted on their support forums, just speculating:

Quote
I used the configurator to get the default options for my Futurebit Apollo scrypt miner and pointed it at the pool, I am noticing that it takes a long time to start up, skipping over the first coin in fact and going directly to LTC.

After a short period the hardware error rate skyrockets up to 30% and the hashrate declines dramatically. The error rate seems to slowly stabilize around 14-15%, with my hashrate ultimately being stuck around 80-90. I am using it in Eco mode, which should provide roughly at least 100 Mh/s.

Worth nothing, I don't experience this issue with others pools, such as litecoinpool. I wouldn't mind pointing my Scrypt miner at Prohashing, but this hit to hashrate is untenable and I don't want to inadvertently crash my miner, any possible solutions?

Edit: I don't know if this is the root problem or not. It looks like while having a failover pool set, perhaps because of the delay of initially getting work, the miner is considering Prohashing as simultaneously being in an active and fail state and sending some hash power to the failover pool. Perhaps this is causing a problem with the difficulty calculation from Prohashing and causing the error rate when switching between currently mined coins? Disabling the backup pool altogether, which is non-ideal, seems to resolve the HW error and reduced hashing state.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!