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

Wolf_schiesst

newbie

Activity: 8

Merit: 0

Quote from: TIRMINE on August 13, 2024, 09:59:47 AM

Quote from: Wolf_schiesst on August 13, 2024, 03:51:28 AM

I have configured my Apollo BTC miner (firmware v2.0.5) for solo mining with the new easy GUI function. So I just had to enter my personal BTC wallet address and nothing more. My intention was to have my miner running directly attached on my local node.

Configuration: SOLO settings > Mine directly to your Bitcoin node > activated "SOLO Mining mode" and added my "Wallet address".

However, when I click in the GUI on "Solo mining", I get this message: "CK Pool Disconnected! Please check your node connection and the CK Pool status."

Is this message normal and can be ignored? Or do I still have to connect to ck pool?

PS: Can anyone please provide a reply on my question above regarding the update of the pending Ubuntu packages? I would highly appreciate any help, too

Are you fully synced? You need to fully sync the node before you can solo mine on the apollo

Funny, but after a system reboot, It works now as intended and shows the miner working on my local node.

in2tactics

hero member

Activity: 578

Merit: 501

What is the max safe miner temp for the Apollo II?

kawshon

newbie

Activity: 1

Merit: 0

Quote from: Ultra5240 on April 29, 2024, 11:33:16 AM

Quote from: sorensenes on April 26, 2024, 08:33:45 PM

I just got an Apollo II and it will connect over ethernet, but when I try to connect to my wifi it keeps giving me the same error - 'secrets were required but not provided'. I have never seen an error like that before and am not sure what to do. I know I've put in the right password for the wifi. Any insight from anyone on how to navigate this error?

I am having this same issue. I am guessing that there may be a glitch in the OS that needs to be resolved. Until then, I will stay connected via Ethernet.

Sounds like the same issue/symptoms I'm having; I just received my Appollo II yesterday and somehow I was able to connect via WiFi with mixed 2.4/5GHz and staid connected for ~12 hrs. When I woke up today still connected and decided to change another setting requiring restart and was not able to connect to WiFi. I worked with my ISP to troubleshoot to no avail and when reaching out to FutureBit received the following clarification: "...the wifi controller on the Apollo can only handle separate 2.4GHZ networks with WPA2 only encryption. If it’s a mix mode SSID or WPA3 encryption it probably wont work and will need a seperate network to connect too."

kimjpeck

newbie

Activity: 9

Merit: 0

Hi,

I have just received a Apollo 2 BTC and have a quick question regarding solo mining.

When setting up Solo mining ... can you mine directly to a Hardware wallet receive address i.e. Tangem?

Thank you in advance.

johnstewart

jr. member

Activity: 31

Merit: 4

So my apollo 2 with the first MCU doesn’t work properly anymore. It was working like a charm until now.
Tried multiple reflash ( beta version , current ect ) … : it starts show up in the network access to the dashboard and start mining properly, node is synchronizing and then few minutes later disappear from the network seems to mine but in nowhere ??
It seems there is some network issues or something like that ? Like a firewall on the Apollo os ?

Wolf_schiesst

newbie

Activity: 8

Merit: 0

Quote from: TIRMINE on August 13, 2024, 09:59:47 AM

Quote from: Wolf_schiesst on August 13, 2024, 03:51:28 AM

I have configured my Apollo BTC miner (firmware v2.0.5) for solo mining with the new easy GUI function. So I just had to enter my personal BTC wallet address and nothing more. My intention was to have my miner running directly attached on my local node.

Configuration: SOLO settings > Mine directly to your Bitcoin node > activated "SOLO Mining mode" and added my "Wallet address".

However, when I click in the GUI on "Solo mining", I get this message: "CK Pool Disconnected! Please check your node connection and the CK Pool status."

Is this message normal and can be ignored? Or do I still have to connect to ck pool?

PS: Can anyone please provide a reply on my question above regarding the update of the pending Ubuntu packages? I would highly appreciate any help, too

Are you fully synced? You need to fully sync the node before you can solo mine on the apollo

Yes, I am.

TIRMINE

jr. member

Activity: 123

Merit: 4

Quote from: Wolf_schiesst on August 13, 2024, 03:51:28 AM

I have configured my Apollo BTC miner (firmware v2.0.5) for solo mining with the new easy GUI function. So I just had to enter my personal BTC wallet address and nothing more. My intention was to have my miner running directly attached on my local node.

Configuration: SOLO settings > Mine directly to your Bitcoin node > activated "SOLO Mining mode" and added my "Wallet address".

However, when I click in the GUI on "Solo mining", I get this message: "CK Pool Disconnected! Please check your node connection and the CK Pool status."

Is this message normal and can be ignored? Or do I still have to connect to ck pool?

PS: Can anyone please provide a reply on my question above regarding the update of the pending Ubuntu packages? I would highly appreciate any help, too

Are you fully synced? You need to fully sync the node before you can solo mine on the apollo

Wolf_schiesst

newbie

Activity: 8

Merit: 0

I have configured my Apollo BTC miner (firmware v2.0.5) for solo mining with the new easy GUI function. So I just had to enter my personal BTC wallet address and nothing more. My intention was to have my miner running directly attached on my local node.

Configuration: SOLO settings > Mine directly to your Bitcoin node > activated "SOLO Mining mode" and added my "Wallet address".

However, when I click in the GUI on "Solo mining", I get this message: "CK Pool Disconnected! Please check your node connection and the CK Pool status."

Is this message normal and can be ignored? Or do I still have to connect to ck pool?

PS: Can anyone please provide a reply on my question above regarding the update of the pending Ubuntu packages? I would highly appreciate any help, too

crypto_curious

full member

Activity: 933

Merit: 175

Quote from: jstefanop on August 08, 2024, 05:01:27 PM

Quote from: crypto_curious on August 07, 2024, 08:24:08 AM

Futurebit team has confirmed on e-mail:

Quote

Hi the USB version is designed to be shutdown via the power switch. If you are using another computer and not an apollo there is no way to shut it down via USB as this functionality is only possible with the full node unit.

Quote

Hi standard units controlled with a third part pc can only be shutdown with the power switch in the back.

FutureBit Team
[email protected]

Had I known this, I would never buy this device. Now, I have to use 24/7 or not at all. Cannot temperature or time control it. Once internet goes down or want it to idle, it just continues to burn full power forever.

It's an issue with USB reset on windows devices for the new Apollo. Have not been able to do much testing on windows but if there are apps or a "reset" command you can send over the COM port it should turn it off.

Other option is to use a smart plug and shut it on/off that way if you cant physically access it.

Thanks for your reply!
I don't use Windows at all. I obtained Linux binaries from your unreleased github tree. I am still waiting for support on e-mail to come back to me, it's been very slow. They confirmed that, quote:

Quote

Hi this functionality is only available on linux systems due to a driver change windows made for USB devices.

You can try powering it down by making a seperate power off bat file and only have this flag after the binary executable: -comport COM4 -brd_pwr_off_all

FutureBit Team
[email protected]

However, binary I have here on Linux from your github doesn't recognize this -brd_pwr_off_all. Can you tell me if I am ok on Linux, and eventually you will be able to give me proper binary with this functionality, or all hope is lost?

azereki

newbie

Activity: 7

Merit: 0

Does anyone know the steps for generating a Bolt12 offer on the Apollo II full node, is it possible to do so?

MrMik

member

Activity: 203

Merit: 37

Quote from: jstefanop on August 09, 2024, 04:16:56 PM

Hmm looks like current control and/or one of the voltage controllers has gone bad on the main board. Unfortunately stuff like that is hard to fix without a full hashboard replacement. What mode were you running it on?

Not sure exactly what it was set to. It stopped working some time about a year ago, I did not have time to muck around with it at the time. I think it might be the OrangePi that stopped working, because it just did not boot any longer. It was running the FutureBit OS from SD card, with a second Apollo connected to it by USB cable, both with 200mm fans on top and stock fans replaced with something that spins down to 1500rpm when not hot. Set to minimum noise to heat the bedroom at night and to start mining by flicking the power switch on (no monitor attached).

I had tried all sorts of settings before using it as the bedroom heater and it was running quietly for several months before it stopped booting up.

jstefanop

legendary

Activity: 2174

Merit: 1401

Quote from: MrMik on August 09, 2024, 03:34:42 AM

One of my Apollo BTC's is misbehaving in a strange way.

It's few years old, Model # : FBA2001 is written on the cover. Powered by an after-market PSU, which is good, 'cause the stock PSU would have issues with what it's doing....

No matter what command I use to start it (in a terminal on a Linux SBC and also on a Linux laptop), it will always run at full bore.

That means sucks 350W (measured at the wall) and produces around 3.5 TH/s, while the terminal claims this:

BOARDS SYS INFO (1 boards, 44 chips):
BRD FOUND REV SPI PWR CHIPS ON ON_T inOhOsc OhOscN OhOscT OhN OhT loI Tc Th T, C TA RevADC OCP HE osc OSChip U, mV I, mA P, Wt
0 1 BREV:20 1x 4 2x2x11 44 1 1 0 0 0 0 0 33 0 0 67 0 0( 0) 0( 0) 4007 0x00 0 (0) 50 N/A U0: 9999 U1: 7662 I0: 8 I1: 8106 62

The command to start it was something like this: sudo ./start_etc..etc..etc.sh

And the text in the .sh file is this (but with proper pool and user info):
./apollo-miner -host Xxxx -port xxxx -user Xxxxxx -pswd x -comport /dev/ttyACM0 -brd_ocp 50 -osc 50 -ao_mode 1 -fan_temp_low 65 -fan_temp_hi 70 -fan_pwm_low 1 -fan_pwm_hi 100

Any idea what has gotten into it and how to exorcise whatever is bedevilling it?

Hmm looks like current control and/or one of the voltage controllers has gone bad on the main board. Unfortunately stuff like that is hard to fix without a full hashboard replacement. What mode were you running it on?

jstefanop

legendary

Activity: 2174

Merit: 1401

Quote from: MakerAZ on August 08, 2024, 11:38:09 PM

I wish my Apollo II UI could show me time-based statistical graphs like those all other pools have.

Already in the works for 2.1!

MrMik

member

Activity: 203

Merit: 37

One of my Apollo BTC's is misbehaving in a strange way.

It's few years old, Model # : FBA2001 is written on the cover. Powered by an after-market PSU, which is good, 'cause the stock PSU would have issues with what it's doing....

No matter what command I use to start it (in a terminal on a Linux SBC and also on a Linux laptop), it will always run at full bore.

That means sucks 350W (measured at the wall) and produces around 3.5 TH/s, while the terminal claims this:

BOARDS SYS INFO (1 boards, 44 chips):
BRD FOUND REV SPI PWR CHIPS ON ON_T inOhOsc OhOscN OhOscT OhN OhT loI Tc Th T, C TA RevADC OCP HE osc OSChip U, mV I, mA P, Wt
0 1 BREV:20 1x 4 2x2x11 44 1 1 0 0 0 0 0 33 0 0 67 0 0( 0) 0( 0) 4007 0x00 0 (0) 50 N/A U0: 9999 U1: 7662 I0: 8 I1: 8106 62

The command to start it was something like this: sudo ./start_etc..etc..etc.sh

And the text in the .sh file is this (but with proper pool and user info):
./apollo-miner -host Xxxx -port xxxx -user Xxxxxx -pswd x -comport /dev/ttyACM0 -brd_ocp 50 -osc 50 -ao_mode 1 -fan_temp_low 65 -fan_temp_hi 70 -fan_pwm_low 1 -fan_pwm_hi 100

Any idea what has gotten into it and how to exorcise whatever is bedevilling it?

Wolf_schiesst

newbie

Activity: 8

Merit: 0

Quote from: Wolf_schiesst on August 08, 2024, 07:49:02 PM

I tried a "sudo apt update" after I had sucessfully completed a "sudo apt upgrade" via SSH using Putty.
Unfortunetlay, with the latest firmware version v2.0.5 (MCU2) I am getting the following error message:

Code:

Err:10 http://deb.volian.org/volian scar InRelease
  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
Hit:9 http://netcup.armbian.com/apt jammy InRelease
Hit:8 https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease
Reading package lists... Done
E: Failed to fetch http://deb.volian.org/volian/dists/scar/InRelease  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: The repository 'http://deb.volian.org/volian scar InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Can you maybe explain to me, how I can solve this issue? Thanks for your support!

got it fixed with changing "/etc/apt/sources.list.d/nala.list" from

Code:

deb [signed-by=/usr/share/keyrings/nala.gpg] http://deb.volian.org/volian/ scar main

to

Code:

deb [signed-by=/usr/share/keyrings/nala.gpg] http://deb.volian.org/volian/ nala main

Result (i am not sure, whether I should update the kept back ones with "sudo apt-get --with-new-pkgs upgrade" or not):
Note: The Ubuntu Pro ESM Apps nag message can be ignored IMHO or removed (see https://askubuntu.com/questions/1452519/what-are-the-services-apt-news-and-esm-cache-and-how-do-i-disable-them/)

Code:

Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
  libmagickcore-6.q16-dev python2.7-minimal libde265-dev libmatio11
  libmagickwand-dev libheif1 libvips-dev imagemagick libiperf0 libpathplan4
  libopenexr-dev graphviz libavdevice58 libgvpr2 libgvc6 libopenexr25
  libpostproc55 libcgraph6 libmagickcore-6.q16-6-extra libcdt5 libavcodec58
  traceroute iperf3 libmagickwand-6.q16-6 libpython2.7 libavutil56
  imagemagick-6.q16 libswscale5 libvips42 libheif-dev libmagickcore-6.q16-6
  gir1.2-vips-8.0 liblab-gamut1 libswresample3 imagemagick-6-common
  libmagickcore-6-arch-config libavformat58 python2.7-dev libpython2.7-dev
  libmagickwand-6-headers libmatio-dev python2.7 libde265-0
  libpython2.7-minimal libmagickwand-6.q16-dev libmagickcore-6-headers
  libpython2.7-stdlib libavfilter7
Learn more about Ubuntu Pro at https://ubuntu.com/pro
The following packages have been kept back:
  armbian-bsp-cli-orangepi4-lts armbian-bsp-cli-orangepi4-lts-current armbian-config armbian-firmware armbian-jammy-desktop-gnome armbian-plymouth-theme armbian-zsh libharfbuzz0b linux-dtb-current-rockchip64 linux-image-current-rockchip64 linux-u-boot-orangepi4-lts-current python3-apport python3-problem-report
  python3-update-manager update-manager update-manager-core
0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.

MakerAZ

newbie

Activity: 27

Merit: 5

I wish my Apollo II UI could show me time-based statistical graphs like those all other pools have.

Wolf_schiesst

newbie

Activity: 8

Merit: 0

I tried a "sudo apt update" after I had sucessfully completed a "sudo apt upgrade" via SSH using Putty.
Unfortunetlay, with the latest firmware version v2.0.5 (MCU2) I am getting the following error message:

Code:

Err:10 http://deb.volian.org/volian scar InRelease
  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
Hit:9 http://netcup.armbian.com/apt jammy InRelease
Hit:8 https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease
Reading package lists... Done
E: Failed to fetch http://deb.volian.org/volian/dists/scar/InRelease  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: The repository 'http://deb.volian.org/volian scar InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Can you maybe explain to me, how I can solve this issue? Thanks for your support!

jstefanop

legendary

Activity: 2174

Merit: 1401

Quote from: crypto_curious on August 07, 2024, 08:24:08 AM

Futurebit team has confirmed on e-mail:

Quote

Hi the USB version is designed to be shutdown via the power switch. If you are using another computer and not an apollo there is no way to shut it down via USB as this functionality is only possible with the full node unit.

Quote

Hi standard units controlled with a third part pc can only be shutdown with the power switch in the back.

FutureBit Team
[email protected]

Had I known this, I would never buy this device. Now, I have to use 24/7 or not at all. Cannot temperature or time control it. Once internet goes down or want it to idle, it just continues to burn full power forever.

It's an issue with USB reset on windows devices for the new Apollo. Have not been able to do much testing on windows but if there are apps or a "reset" command you can send over the COM port it should turn it off.

Other option is to use a smart plug and shut it on/off that way if you cant physically access it.

heslo

legendary

Activity: 1235

Merit: 1202

Quote from: MrMik on August 07, 2024, 11:33:51 PM

Looks like I fried my Apollo, I'm after advice on how to diagnose if it's worth trying to repair it.

This is what happened before I let the magic smoke out:

I dug out the unused Apollo to use it for a bit of heating. Powered it up with a monitor, running Armbian on the OrangePi and starting the miner via the sudo ./start etc etc command prompt in a terminal, all worked well.

Then I plugged it into a 2kW PSU but I used cables that came from a different (650W) PSU. Nothing seemed to happen except it smelled a bit funny....

The I used the cables that are the correct ones for the 2kW PSU, and now the Apollos fan turns on, the all lights are out and it's dead as a door-nail.

I already disconnected the OrangePi and tried to power the miner via laptop and USB, but same result, fan spins, nothing else happens.

I find it hard to believe that they make cables labelled PCIe on one end, with an 8 pin connector at the other end that will it into different PSUs that use different pin layouts at the PSU end, but that seems to be what happened. Bastards!

Any idea what part of the Apollo would have fried due to this and if it can be repaired?

And is it possible that the OrangePi may have survived the 12V getting connected to the wrong pins?

Not all PSU's are pinned out the same (stupid I know) Sounds like you've shoved 12v into somewhere you shouldn't have

MrMik

member

Activity: 203

Merit: 37

Looks like I fried my Apollo, I'm after advice on how to diagnose if it's worth trying to repair it.

This is what happened before I let the magic smoke out:

I dug out the unused Apollo to use it for a bit of heating. Powered it up with a monitor, running Armbian on the OrangePi and starting the miner via the sudo ./start etc etc command prompt in a terminal, all worked well.

Then I plugged it into a 2kW PSU but I used cables that came from a different (650W) PSU. Nothing seemed to happen except it smelled a bit funny....

The I used the cables that are the correct ones for the 2kW PSU, and now the Apollos fan turns on, the all lights are out and it's dead as a door-nail.

I already disconnected the OrangePi and tried to power the miner via laptop and USB, but same result, fan spins, nothing else happens.

I find it hard to believe that they make cables labelled PCIe on one end, with an 8 pin connector at the other end that will it into different PSUs that use different pin layouts at the PSU end, but that seems to be what happened. Bastards!

Any idea what part of the Apollo would have fried due to this and if it can be repaired?

And is it possible that the OrangePi may have survived the 12V getting connected to the wrong pins?

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