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

Sledge0001

full member

Activity: 633

Merit: 159

Quote from: Bamieater on April 19, 2024, 06:01:54 AM

Quote from: jstefanop on April 12, 2024, 01:16:21 PM

Quote from: Bamieater on April 12, 2024, 11:55:28 AM

Quote from: jstefanop on April 11, 2024, 10:56:28 PM

Link to download MCU1 Apollo OS 2 below.

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)

https://www.dropbox.com/scl/fi/j4o3rcwe88emzsuwe4wm7/apollo-2-mcu1_110424.img.xz?rlkey=cu3i66xtl5n4ln8ji7mct3zth&dl=0

This includes latest v2.0.4-beta release

Reminder MCU1 controllers are Batch 1/2 Apollos with the longer GPIO pins on the board (check link below if you are not sure which you have).

https://mega.nz/file/dghWnKJC#J2kkpfH5RVKynf0OvuE5mKojXdUqAFCczHMyv6mDrM4

My miner is crashing, and restarting every 10-20 minutes. To my feeling it's happening the moment new blocks are mined.

The node falls back a couple of hundred blocks after the restart, i.e. the current block was 838879 and the node would start syncing at 838663 again.

MCU1 board. This behaviour was also happening before, and I was hoping the upgrade would fix this.

This sounds like a corrupted SSD drive. You might need to reformat the drive and start syncing again. Can also try a re-indexing the node before you reformat the drive.

I've reformatted the SSD drive, and started syncing again. Once the node was synced, I enabled mining again on ECO mode. I could observe on the miner uptime that restarts were still happening. After a bit more than a day of mining, the whole web interface became unreachable.

Anything else I can troubleshoot?

Check to make sure the CPU fan is still working on the MCU unit. It may be gunked up or dead. That would cause the MCU to overheat and crap out on you.

Bamieater

newbie

Activity: 2

Merit: 0

Quote from: jstefanop on April 12, 2024, 01:16:21 PM

Quote from: Bamieater on April 12, 2024, 11:55:28 AM

Quote from: jstefanop on April 11, 2024, 10:56:28 PM

Link to download MCU1 Apollo OS 2 below.

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)

https://www.dropbox.com/scl/fi/j4o3rcwe88emzsuwe4wm7/apollo-2-mcu1_110424.img.xz?rlkey=cu3i66xtl5n4ln8ji7mct3zth&dl=0

This includes latest v2.0.4-beta release

Reminder MCU1 controllers are Batch 1/2 Apollos with the longer GPIO pins on the board (check link below if you are not sure which you have).

https://mega.nz/file/dghWnKJC#J2kkpfH5RVKynf0OvuE5mKojXdUqAFCczHMyv6mDrM4

My miner is crashing, and restarting every 10-20 minutes. To my feeling it's happening the moment new blocks are mined.

The node falls back a couple of hundred blocks after the restart, i.e. the current block was 838879 and the node would start syncing at 838663 again.

MCU1 board. This behaviour was also happening before, and I was hoping the upgrade would fix this.

This sounds like a corrupted SSD drive. You might need to reformat the drive and start syncing again. Can also try a re-indexing the node before you reformat the drive.

I've reformatted the SSD drive, and started syncing again. Once the node was synced, I enabled mining again on ECO mode. I could observe on the miner uptime that restarts were still happening. After a bit more than a day of mining, the whole web interface became unreachable.

Anything else I can troubleshoot?

jstefanop

legendary

Activity: 2188

Merit: 1401

Quote from: azereki on April 16, 2024, 07:46:30 PM

Quote from: jstefanop on April 11, 2024, 10:56:28 PM

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?

Yea UI is only designed to register the internal SSD drive node.

When you restart the miner you should see the USB standard units start flashing their front LEDs, if they dont then that means the system is not seeing them. Try a different USB port/USB hub. USB hubs seem to fix most USB issues on this controller.

azereki

newbie

Activity: 7

Merit: 0

Quote from: jstefanop on April 11, 2024, 10:56:28 PM

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?

potentabit

newbie

Activity: 14

Merit: 0

Quote from: Jota_US on April 15, 2024, 10:46:37 PM

EDIT: No luck with asicboost..

Make sure you have the latest update installed.

Jota_US

newbie

Activity: 53

Merit: 0

Quote from: potentabit on April 15, 2024, 08:31:37 PM

Quote from: potentabit on April 13, 2024, 07:35:06 PM

Quote from: Jota_US on April 13, 2024, 07:04:43 PM

Quote from: potentabit on April 13, 2024, 10:01:51 AM

Quote from: jstefanop on April 12, 2024, 01:17:27 PM

Quote from: potentabit on April 12, 2024, 12:56:09 PM

MCU1 full node with Apollo 2 Standard attached to USB.
Using v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.

Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?

I believe what you are seeing is the Apollo BTC is hashing and the Apollo 2 is not.
That's why you see "reduced' hashrate but actually it's the Apollo BTC's hashrate that you are seeing. They are mislabeled in the software.

I have the same problem with miningrigrentals, I can only get the Apollo BTC to hash there, the Apollo 2 doesn't send data. It works fine on Braiins though, but I would like to have it work on MRR.
I believe you would need separate id's for each unit but it doesn't look like you can do that right now.

OK, I see and agree, they must be cross labeled or not reading assigned values. Also agree that some pools need separate Id's depending on how data is sent/received. I have a few GPU rigs on NiceHash and all cards on each rig have their own ID's

Hopefully Monday's update will address some of these issues as we are still in a Beta version.

I got both (MCU1 and Apollo II S) sending data at the same time to NiceHash by using "stratum+tcp://sha256asicboost.auto.nicehash.com:9200" instead of stratum+tcp://sha256.auto.nicehash.com:9200. However they do appear to be inversely labeled as displayed on the "Hashboards and Pools" page.

Ok thanks I'll try with asicboost and see if there is a difference on MMR.

By the way, anybody able to connect Sparrow to the node? Not sure why it's not connecting now (it was before the new OS). Do I have to put something in particular in bitcoin.conf?

EDIT: No luck with asicboost..

potentabit

newbie

Activity: 14

Merit: 0

Quote from: potentabit on April 13, 2024, 07:35:06 PM

Quote from: Jota_US on April 13, 2024, 07:04:43 PM

Quote from: potentabit on April 13, 2024, 10:01:51 AM

Quote from: jstefanop on April 12, 2024, 01:17:27 PM

Quote from: potentabit on April 12, 2024, 12:56:09 PM

MCU1 full node with Apollo 2 Standard attached to USB.
Using v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.

Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?

I believe what you are seeing is the Apollo BTC is hashing and the Apollo 2 is not.
That's why you see "reduced' hashrate but actually it's the Apollo BTC's hashrate that you are seeing. They are mislabeled in the software.

I have the same problem with miningrigrentals, I can only get the Apollo BTC to hash there, the Apollo 2 doesn't send data. It works fine on Braiins though, but I would like to have it work on MRR.
I believe you would need separate id's for each unit but it doesn't look like you can do that right now.

OK, I see and agree, they must be cross labeled or not reading assigned values. Also agree that some pools need separate Id's depending on how data is sent/received. I have a few GPU rigs on NiceHash and all cards on each rig have their own ID's

Hopefully Monday's update will address some of these issues as we are still in a Beta version.

I got both (MCU1 and Apollo II S) sending data at the same time to NiceHash by using "stratum+tcp://sha256asicboost.auto.nicehash.com:9200" instead of stratum+tcp://sha256.auto.nicehash.com:9200. However they do appear to be inversely labeled as displayed on the "Hashboards and Pools" page.

jstefanop

legendary

Activity: 2188

Merit: 1401

Quote from: Jota_US on April 15, 2024, 01:58:13 PM

Quote from: jstefanop on April 14, 2024, 07:17:05 PM

Quote from: jb1972 on April 14, 2024, 02:44:13 PM

anyone know what to do with the satscards? I'm in UK and haven't come across these before.

Use it as a hardware wallet for your mining or solo mining address.

We included it for new users that dont have wallets so they can get started in one step by just importing the wallet address for either solo mining or mining straight to wallet address using ocean pool.

I didn't get a satscard...

Only Full Node units get one

potentabit

newbie

Activity: 14

Merit: 0

Quote from: Guill57 on April 15, 2024, 01:38:47 PM

Hi, it looks like the Unit opened up port 8333 via UPnP, but I still see only 10 connections...Is it because it is still syncing with the Blockchain?
Any thoughts? Thanks.

It takes a while!

Jota_US

newbie

Activity: 53

Merit: 0

Quote from: jstefanop on April 14, 2024, 07:17:05 PM

Quote from: jb1972 on April 14, 2024, 02:44:13 PM

anyone know what to do with the satscards? I'm in UK and haven't come across these before.

Use it as a hardware wallet for your mining or solo mining address.

We included it for new users that dont have wallets so they can get started in one step by just importing the wallet address for either solo mining or mining straight to wallet address using ocean pool.

I didn't get a satscard...

Guill57

newbie

Activity: 2

Merit: 0

Hi, it looks like the Unit opened up port 8333 via UPnP, but I still see only 10 connections...Is it because it is still syncing with the Blockchain?
Any thoughts? Thanks.

DarthLego

newbie

Activity: 2

Merit: 0

Quote from: jb1972 on April 14, 2024, 02:44:13 PM

anyone know what to do with the satscards? I'm in UK and haven't come across these before.

The Satscard is basically an NFC card version of an Opendime. You can use the Nunchuk wallet app to access it.

potentabit

newbie

Activity: 14

Merit: 0

Quote from: jstefanop on April 14, 2024, 01:28:06 PM

Quote from: potentabit on April 13, 2024, 07:35:06 PM

Quote from: Jota_US on April 13, 2024, 07:04:43 PM

Quote from: potentabit on April 13, 2024, 10:01:51 AM

Quote from: jstefanop on April 12, 2024, 01:17:27 PM

Quote from: potentabit on April 12, 2024, 12:56:09 PM

MCU1 full node with Apollo 2 Standard attached to USB.
Using v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.

Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?

I believe what you are seeing is the Apollo BTC is hashing and the Apollo 2 is not.
That's why you see "reduced' hashrate but actually it's the Apollo BTC's hashrate that you are seeing. They are mislabeled in the software.

I have the same problem with miningrigrentals, I can only get the Apollo BTC to hash there, the Apollo 2 doesn't send data. It works fine on Braiins though, but I would like to have it work on MRR.
I believe you would need separate id's for each unit but it doesn't look like you can do that right now.

OK, I see and agree, they must be cross labeled or not reading assigned values. Also agree that some pools need separate Id's depending on how data is sent/received. I have a few GPU rigs on NiceHash and all cards on each rig have their own ID's

Hopefully Monday's update will address some of these issues as we are still in a Beta version.

Currently when more Standard units are connected it looks like a single miner as far as the pool is concerned. We only test on standard pools, but will check nice hash and mining rentals to see what the issue is, but these are notoriously buggy pools since they just send the connection to a downstream pool anyway.

Meanwhile it would be good if we can have an option to control (on-off) each miner attached to main Apollo BTC, including the built in unit. I'd rather send the higher hash rate from the external Apollo then the lower on MCU1 controller. As this is what is actually happening even if both miners are running.

jstefanop

legendary

Activity: 2188

Merit: 1401

FYI official images for all Apollo units are out.

This release is pretty stable and will probably knock of the beta tag on the next release after we fix a few last mostly visual bugs.

https://github.com/jstefanop/apolloapi-v2/releases/tag/v2.0.4-beta

Will release the windows/linux Apollo 2 mining binaries tomorrow.

jstefanop

legendary

Activity: 2188

Merit: 1401

Quote from: jb1972 on April 14, 2024, 02:44:13 PM

anyone know what to do with the satscards? I'm in UK and haven't come across these before.

Use it as a hardware wallet for your mining or solo mining address.

We included it for new users that dont have wallets so they can get started in one step by just importing the wallet address for either solo mining or mining straight to wallet address using ocean pool.

jb1972

newbie

Activity: 6

Merit: 0

anyone know what to do with the satscards? I'm in UK and haven't come across these before.

jstefanop

legendary

Activity: 2188

Merit: 1401

Quote from: potentabit on April 13, 2024, 07:35:06 PM

Quote from: Jota_US on April 13, 2024, 07:04:43 PM

Quote from: potentabit on April 13, 2024, 10:01:51 AM

Quote from: jstefanop on April 12, 2024, 01:17:27 PM

Quote from: potentabit on April 12, 2024, 12:56:09 PM

MCU1 full node with Apollo 2 Standard attached to USB.
Using v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.

Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?

I believe what you are seeing is the Apollo BTC is hashing and the Apollo 2 is not.
That's why you see "reduced' hashrate but actually it's the Apollo BTC's hashrate that you are seeing. They are mislabeled in the software.

I have the same problem with miningrigrentals, I can only get the Apollo BTC to hash there, the Apollo 2 doesn't send data. It works fine on Braiins though, but I would like to have it work on MRR.
I believe you would need separate id's for each unit but it doesn't look like you can do that right now.

OK, I see and agree, they must be cross labeled or not reading assigned values. Also agree that some pools need separate Id's depending on how data is sent/received. I have a few GPU rigs on NiceHash and all cards on each rig have their own ID's

Hopefully Monday's update will address some of these issues as we are still in a Beta version.

Currently when more Standard units are connected it looks like a single miner as far as the pool is concerned. We only test on standard pools, but will check nice hash and mining rentals to see what the issue is, but these are notoriously buggy pools since they just send the connection to a downstream pool anyway.

potentabit

newbie

Activity: 14

Merit: 0

Quote from: Jota_US on April 13, 2024, 07:04:43 PM

Quote from: potentabit on April 13, 2024, 10:01:51 AM

Quote from: jstefanop on April 12, 2024, 01:17:27 PM

Quote from: potentabit on April 12, 2024, 12:56:09 PM

MCU1 full node with Apollo 2 Standard attached to USB.
Using v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.

Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?

I believe what you are seeing is the Apollo BTC is hashing and the Apollo 2 is not.
That's why you see "reduced' hashrate but actually it's the Apollo BTC's hashrate that you are seeing. They are mislabeled in the software.

I have the same problem with miningrigrentals, I can only get the Apollo BTC to hash there, the Apollo 2 doesn't send data. It works fine on Braiins though, but I would like to have it work on MRR.
I believe you would need separate id's for each unit but it doesn't look like you can do that right now.

OK, I see and agree, they must be cross labeled or not reading assigned values. Also agree that some pools need separate Id's depending on how data is sent/received. I have a few GPU rigs on NiceHash and all cards on each rig have their own ID's

Hopefully Monday's update will address some of these issues as we are still in a Beta version.

Jota_US

newbie

Activity: 53

Merit: 0

Quote from: potentabit on April 13, 2024, 10:01:51 AM

Quote from: jstefanop on April 12, 2024, 01:17:27 PM

Quote from: potentabit on April 12, 2024, 12:56:09 PM

MCU1 full node with Apollo 2 Standard attached to USB.
Using v2.0.4-beta

Noticed that hash rate to NiceHash is only a fraction of actual mining.
When looking at the stats only shows one of the 2 miners (Apollo2) reporting data at no more than fraction (1.2 TH) of actual rate (5.8TH).
Apollo BTC is showing 1.9 TH and 0TH on NiceHash account.

Is this on nice hash only? Would wait at least an hour for hashrate to settle.

Might be NiceHash only. One of the 2 (Apollo 2 S) is sending data at severely reduced rate even after a few hours. MCU1 unit does not send data at all as shown in the "Hashboards and Pools" page.
NiceHash may require separate Id's for each mining unit?

I believe what you are seeing is the Apollo BTC is hashing and the Apollo 2 is not.
That's why you see "reduced' hashrate but actually it's the Apollo BTC's hashrate that you are seeing. They are mislabeled in the software.

I have the same problem with miningrigrentals, I can only get the Apollo BTC to hash there, the Apollo 2 doesn't send data. It works fine on Braiins though, but I would like to have it work on MRR.
I believe you would need separate id's for each unit but it doesn't look like you can do that right now.

jstefanop

legendary

Activity: 2188

Merit: 1401

Quote from: Guill57 on April 13, 2024, 02:28:26 PM

Hello all, any suggestions as to what the best way is to connect Gen I full Node with the New Apollo II?
Thanks for your help!

Hi we are about to release updated images for Gen 1 units with Apollo II support officially on our support and GitHub pages on monday so look for an announcement/email. You can find the links for beta images if you go back a few pages.

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