Official FutureBit Apollo BTC Software/Image and Support thread - page 134.

Jota_US

newbie

Activity: 53

Merit: 0

Quote from: philipma1957 on June 15, 2021, 06:29:10 PM

short versions of the log in chrome

note: 208 dropouts

https://i.imgur.com/b4WuGLw.png

https://i.imgur.com/w9PUfon.png

sample of the log
and I highlighted the 30 second plus one that stopped the miner

https://i.imgur.com/TjXUNOs.png

Thanks I will try that. Internet is pretty good but if there are small drop outs I may not notice. The LTC miner does not stop though and the BTC node either.

philipma1957

legendary

Activity: 4354

Merit: 9201

'The right to privacy matters'

short versions of the log in chrome

note: 208 dropouts

sample of the log
and I highlighted the 30 second plus one that stopped the miner

Philipma1957cellphone

full member

Activity: 416

Merit: 125

Quote from: Jota_US on June 15, 2021, 10:58:38 AM

After running the miner for a few weeks everything is pretty stable (I also have an LTC)

The only thing that is a bit problematic is the fact that the BTC miner randomly stops mining. (solid red light)
Not sure what is causing that, and I only have to restart the miner to get it going again but it's annoying when it happens in the middle of the night or when I am away for a few days. It would be nice to have an auto-restart or something like that.
The LTC miner used to do similar stuff when I upgraded it to run a node but since I stopped the node it doesn't do it anymore so I tried to stop the node on the BTC one but the same issue persists so it's not because of the node running...

Again not sure what is causing that, it's really just random.
Both miners are next to each other so they share the same connectivity and environment.

Edit: Also, it's too bad that the activity LED is not the same as the LTC miner (flashing red/yellow light when mining). When I see flashing red only I think there is a problem

How solid is your internet connection.

Ever since covid and lots of stay at.home workers I get many I internet dropouts

I use a chrome browser app that tracks drop outs
Sometimes I get 20 thirty second drop outs in a day.

So if the drop out is long say 1 minute the node stops and the miner stops.
Once I get off the exercise bike I will show the log.

crypto_curious

full member

Activity: 933

Merit: 175

Quote from: TheFlatline on June 14, 2021, 09:06:43 PM

Quote from: kano on June 14, 2021, 06:51:53 PM

Quote from: jstefanop on June 14, 2021, 01:41:40 PM

Quote from: kano on June 13, 2021, 10:48:16 PM

... 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 Wink

Funny, again, showing that you actually have no idea about how to properly test a miner.
Well, you have spent your time dealing with scamcoins, now you've come to sell a miner to real miners, you need to brush up a bit on reality.

Dude we get it and you’re awesome but can you have this discussion elsewhere? Us suckers just want help with the miners we bought. Thanks.

Just ignore him (in your profile settings there is an option for that), this clown is trolling in this topic since the beginning, no point discussing anything with him or reading his spewouts.

oldman123

newbie

Activity: 12

Merit: 1

Any thoughts on the high error rate on hashboard #1 vs. hashboard #0?

I am see 0.6% error on hashboard #0 and >40%% on hashboard #1. hashboard #1 error rates update from 30 to over 80%....

Status   ID   Hashrate   Temp   Fan Speed   Power   Voltage   Error   Active ASICs

Active
HASHBOARD #0
2.16 Th/s
51°c
1851 rpm
124 W
7.95 v
0.6% <-- Error Rate #0
44

Active
HASHBOARD #1
2.03 Th/s
47°c
1769 rpm
124 W
7.97 v
76.2% <--Error Rate #1
44

Update: I just went and checked out the hashboard #1 unit and there are none of the yellow lights that are normally flashing on the bottom of the hashboard. The LED is solid red and the unit is cool to the touch. I will be away for an hour or so, and I will it sit as is incase any logs need to be pulled.

jbrow8

newbie

Activity: 17

Merit: 0

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.

jstefanop

legendary

Activity: 2188

Merit: 1401

Quote from: Kindpker on June 15, 2021, 11:06:19 AM

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_Q

Keep 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.

Kindpker

newbie

Activity: 5

Merit: 0

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?

Jota_US

newbie

Activity: 53

Merit: 0

After running the miner for a few weeks everything is pretty stable (I also have an LTC)

The only thing that is a bit problematic is the fact that the BTC miner randomly stops mining. (solid red light)
Not sure what is causing that, and I only have to restart the miner to get it going again but it's annoying when it happens in the middle of the night or when I am away for a few days. It would be nice to have an auto-restart or something like that.
The LTC miner used to do similar stuff when I upgraded it to run a node but since I stopped the node it doesn't do it anymore so I tried to stop the node on the BTC one but the same issue persists so it's not because of the node running...

Again not sure what is causing that, it's really just random.
Both miners are next to each other so they share the same connectivity and environment.

Edit: Also, it's too bad that the activity LED is not the same as the LTC miner (flashing red/yellow light when mining). When I see flashing red only I think there is a problem

jstefanop

legendary

Activity: 2188

Merit: 1401

Quote from: maxfunky on June 15, 2021, 05:20:15 AM

Quote from: heslo on June 15, 2021, 01:53:26 AM

Quote from: maxfunky on June 15, 2021, 01:02:12 AM

Quote from: TheFlatline on June 14, 2021, 10:37:31 AM

Quote from: maxfunky on June 14, 2021, 03:59:03 AM

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 Huh

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 Huh

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.

cryptonite!

newbie

Activity: 7

Merit: 0

Quote from: heslo on June 13, 2021, 09:21:16 AM

Quote from: cryptonite! on June 13, 2021, 08:05:11 AM

hello first thing my miner page says "There is a problem fetching system stats (Internal error)" I've got the whole blockchain sync and 31/32 connections for some reason I have no connections at my system info settings ? it did before now it shows 0 cpu and 0 memory used,also it says please allow port 8333 how do I do that and the miners seem to be running in balanced mode even when it shows eco mode I have to keep a extra fan on them also I didnt know your supposed to leave them on eco mode when it s sync the blockchain seems to be stuck on balance mode

Chuck your IP in here https://canyouseeme.org/ and select port 8333. If it can see you, then the port is already forwarded. If not, you'll have to go into your router and forward the port yourself. Use google and search for your router and port forwarding settings to show you how if you don't know; it's very easy. But considering it's got 31/32 connections I'd say it's already forwarded.

As for the stats error, I don't get that but all my stats just say 0. It's a known issue and is being worked on

y miners are only doing about 1.4 Th/s changed settings doesnt seem to change anything also they show temp 48c , 82 w 8.0 volts thats not what the specs say I have the full pkg and nodes downloaded also cant tell if im mining into the pool (confused about worker name) on my slushpool dashboard it says o workers, on workers it says 0 out of 1 workers just not sure what to put in for worker name ?

maxfunky

full member

Activity: 194

Merit: 100

Quote from: heslo on June 15, 2021, 01:53:26 AM

Quote from: maxfunky on June 15, 2021, 01:02:12 AM

Quote from: TheFlatline on June 14, 2021, 10:37:31 AM

Quote from: maxfunky on June 14, 2021, 03:59:03 AM

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 Huh

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 Huh

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.

heslo

legendary

Activity: 1235

Merit: 1202

Quote from: maxfunky on June 15, 2021, 01:02:12 AM

Quote from: TheFlatline on June 14, 2021, 10:37:31 AM

Quote from: maxfunky on June 14, 2021, 03:59:03 AM

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 Huh

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

maxfunky

full member

Activity: 194

Merit: 100

Quote from: TheFlatline on June 14, 2021, 10:37:31 AM

Quote from: maxfunky on June 14, 2021, 03:59:03 AM

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 Huh

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!

TheFlatline

newbie

Activity: 8

Merit: 0

Quote from: kano on June 14, 2021, 06:51:53 PM

Quote from: jstefanop on June 14, 2021, 01:41:40 PM

Quote from: kano on June 13, 2021, 10:48:16 PM

... 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 Wink

Funny, again, showing that you actually have no idea about how to properly test a miner.
Well, you have spent your time dealing with scamcoins, now you've come to sell a miner to real miners, you need to brush up a bit on reality.

Dude we get it and you’re awesome but can you have this discussion elsewhere? Us suckers just want help with the miners we bought. Thanks.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: jstefanop on June 14, 2021, 01:41:40 PM

Quote from: kano on June 13, 2021, 10:48:16 PM

... 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 Wink

Funny, again, showing that you actually have no idea about how to properly test a miner.
Well, you have spent your time dealing with scamcoins, now you've come to sell a miner to real miners, you need to brush up a bit on reality.

jbrow8

newbie

Activity: 17

Merit: 0

Quote from: heslo on June 13, 2021, 05:46:46 PM

Quote from: jbrow8 on June 13, 2021, 03:43:48 PM

Quote from: orbit887 on June 13, 2021, 02:08:47 PM

Quote from: wingless on June 12, 2021, 11:34:15 AM

Hello, I don't mean to be pestering...but any eta on when a copy of the image will be uploaded? As of now, I can't use my device at all...until I can re-flash it. I'd appreciate any update/help.

Thanks!

+1 same situation here, without an image to reflash my unit is sat unable to do anything. Any estimate ETA at all?

I finally got into the menu system that was asking for the password, I went through 2 monitors before finally finding the TV HDMI port worked. one problem solved, more to follow

They did mention some HDMI monitors may not work due to a simple HDMI controller on the SBC. That's why I just hooked it up via ethernet and went in via the web GUI but some others have not been able to do so that way

The miner usually shut down after one hour, its been running for over four hours now, I changed from the extender to the router and now it continues to mine

wavelengthsf

full member

Activity: 658

Merit: 118

Quote from: jstefanop on June 14, 2021, 01:43:43 PM

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.

Thanks, the new firmware fixed it and i'm hashing away!

jstefanop

legendary

Activity: 2188

Merit: 1401

Quote from: wavelengthsf on June 13, 2021, 10:55:27 AM

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:

Code:

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:

Code:

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.

jstefanop

legendary

Activity: 2188

Merit: 1401

Quote from: kano on June 13, 2021, 10:48:16 PM

... 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 Wink

Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 134. (Read 52205 times)