[Guide] Futurebit Apollo BTC Custom Linux Install - Miner

MrMik

member

Activity: 203

Merit: 37

Quote from: n0nce on December 18, 2022, 09:18:05 AM

No worries; sorry for the inconveniences - it was meant to be easy to follow, just step-by-step guide. I will have to get my hands on an Apollo again and update it properly, I guess. Undecided

No inconveniences, I learned so much, thank you for helping me learn! It would have taken so much longer (years!) if I had tried to start with the 'Linux for dummies' book again!

So now I am creating a 500GB Veracrypt container to keep dd-created images in. But the armbian-SD cards themselves are a big security risk, if physically stolen. I will have to work on that for a bit. Shame armbian does not offer encryption options during installation.
Eventually I'll have an SD card image that does not need to be encrypted because the OS (that was used to make it) is sort of secure.

I'll keep following your guide to install the full node etc once I have an SD card that has been restored from an image of my working armbian Bitcoin miner! Grin

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: MrMik on December 17, 2022, 07:36:07 PM

There are three similar files on the Futurebit Apollo SD card in that /rockchip/ directory:

Code:

rk3399-orangepi.dtb
rk3399-orangepi-4.dtb
rk3399-orangepi-4-lts.dtb

This time around, I did this:

Code:

cd /home/p/rk3399-orangepi_dtbs_from_Apollo_SD-card
sudo mv rk3399-orangepi-4.dtb /boot/dtb/rockchip/rk3399-orangepi-4.dtb

After this, the WiFi is still working.

Awesome, that's good to know! I'll make sure to adapt my guide such that people can pull the latest dtb from Futurebit OS and replace the correct dtb in their stock OS.

Quote from: MrMik on December 18, 2022, 12:45:44 AM

Quote from: n0nce on June 07, 2022, 04:00:56 PM

[2] Edit the start_apollo.sh file.

Code:

cd linux-aarch64/
sudo vim miner_start.sh

I think you must mean the start_apollo.sh file, I guess it has been renamed since you wrote this guide?

No, it was meant to be like this (opening a new file with that name in a text editor).

Quote from: MrMik on December 18, 2022, 12:57:29 AM

Now 2 of them purring quietly on a properly maintained OS! It can be done, thank you n0nce!

No worries; sorry for the inconveniences - it was meant to be easy to follow, just step-by-step guide. I will have to get my hands on an Apollo again and update it properly, I guess. Undecided

MrMik

member

Activity: 203

Merit: 37

Quote from: n0nce on June 07, 2022, 04:00:56 PM

[6] To test everything's working, execute it and give it some time to start up the hashboard and perform some hashes.

Code:

sudo ./miner_start.sh

I'm stuck at this point.

I am using

Code:

sudo ./start_apollo.sh

on the freshly edited file, and it sounds sooo promising (but then fails):

The moment I hit Enter, the fan gives a short burst of full speed (maybe 300ms) and the red light starts blinking fast.

But after about 30s the red light stops blinking and goes solid on, and the console prints "Started" but no mining is actually happening.

EDIT: I got un-stuck by using a previously edited start_apollo.sh-variant file. I pasted my settings line from a start_apollo.sh file that came from the Apollo-Miner_linux-x86_64.tar.xz download.

This file does not have n0nce's additional code (ending in 'echo Started') in it, but only that one line of settings that will allow my Ubuntu laptop to mine using the ASIC board connected via USB cable without the Orange Pi 4. Transplanted from x86_64 to aarch64 file.

The missing part that stops n0nce's code from running the miner (with the USBA to USB-micro cable in the miner) is this:

Code:

/dev/ttyACM0

Code:

start_Poll-i-i_Turbo_60-80C-Fan_20221217_aarch64.sh

gets Polli purring inside of a freshly updated armbian OS.

Yippieeee!

EDIT: It is a lot easier to have the files in the home folder, so you can copy and paste at will when making new flavours of start_apollo.sh files.

I got a self-starting VPN going on this armbian OS and adding more miners works as well:

Code:

cd linux-aarch64
sudo ./start_Poll-i-i_Turbo_60-80C-Fan_20221217_aarch64.sh

Open new console window, then:

cd linux-aarch64
sudo ./start_Poll-i-i-i_Turbo_60-80C-Fan_20221218_aarch64_acm1.sh

Now 2 of them purring quietly on a properly maintained OS! It can be done, thank you n0nce!

MrMik

member

Activity: 203

Merit: 37

Quote from: n0nce on June 07, 2022, 04:00:56 PM

[2] Edit the start_apollo.sh file.

Code:

cd linux-aarch64/
sudo vim miner_start.sh

I think you must mean the start_apollo.sh file, I guess it has been renamed since you wrote this guide?

MrMik

member

Activity: 203

Merit: 37

Quote from: n0nce on June 07, 2022, 04:00:34 PM

snip
snip
snip
[7] Edit the /etc/rc.local file.

Code:

sudo vim /etc/rc.local

[8] Replace 'exit 0' line with the following.

Code:

#configure gpios
gpio mode 1 out
gpio write 1 0
gpio mode 0 out
gpio write 0 1

[9] Reboot the unit.

Code:

sudo reboot

Somehow the WiFi gets broken by following these steps. EDIT: I did not actually follow the steps! Thought I'd be extra clever and stuffed it up, see below.
It still works before the reboot at the end, but after the reboot it malfunctions:
It tries to connect to the previously set WiFi network and it shows the name of the available networks for a minute or two, but then it loses the ability to detect any WiFi network.

I tested it with a fresh SD card etch of Armbian_22.11.1_Orangepi4-lts_jammy_current_5.15.80_gnome_desktop.img.xz but unfortunately I did not reboot multiple times after each step. Will etch a new SD card and reboot frequently to figure out which step breaks the WiFi.

Progress: sudo apt update && sudo apt upgrade does not break the WiFi.

Code:

git clone https://github.com/orangepi-xunlong/wiringOP
   cd wiringOP
./build clean
./build
cd && gpio -v && gpio readall
    output similar to n0nces guide

does not break the WiFi

I found the culprit:

Code:

sudo mv rk3399-orangepi-4-lts.dtb /boot/dtb/rockchip/rk3399-orangepi-4-lts.dtb

makes the WiFi unusable.

Now what?

Next time: Rename the original

Code:

rk3399-orangepi-4-lts.dtb

file so that it does not get over-written by the file from the Apollo SD card. The I can at least get WiFi working again without rebuilding from the SD card etching step.

EDIT: I think I found the solution:

I was uncertain which file to use to replace the file in the /boot/dtb/rockchip/ directory.
Most likely my assumption that I have to use the one with -lts in it's name is to blame for the WiFi malfunction!

Stupid me thought "It's the armbian LTS version, so I use the .dtb file named rk3399-orangepi-4-lts.dtb " Embarrassed

There are three similar files on the Futurebit Apollo SD card in that /rockchip/ directory:

Code:

rk3399-orangepi.dtb
rk3399-orangepi-4.dtb
rk3399-orangepi-4-lts.dtb

This time around, I did this:

Code:

cd /home/p/rk3399-orangepi_dtbs_from_Apollo_SD-card
sudo mv rk3399-orangepi-4.dtb /boot/dtb/rockchip/rk3399-orangepi-4.dtb

After this, the WiFi is still working.

MrMik

member

Activity: 203

Merit: 37

Quote from: n0nce on June 07, 2022, 04:00:34 PM

GPIO Setup
[1] Download WiringOP to get access to GPIO of the Orange Pi 4.

Code:

cd /home/admin
git clone https://github.com/orangepi-xunlong/WiringOP
cd WiringOP

[2] Build the software

Code:

./build clean
./build

[3] Verify you have GPIO access.

Code:

cd && gpio -v && gpio readall

[4] The above command should output something like this.

Code:

gpio version: 2.46
Copyright (c) 2012-2018 Gordon Henderson
This is free software with ABSOLUTELY NO WARRANTY.
For details type: gpio -warranty

   * Device tree is enabled.
   *--> OrangePi 4

 +------+-----+----------+------+---+OrangePi 4+---+---+--+----------+-----+------+
 | GPIO | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | GPIO |
 +------+-----+----------+------+---+----++----+---+------+----------+-----+------+
 |      |     |     3.3V |      |   |  1 || 2  |   |      | 5V       |     |      |
 |   64 |   0 | I2C2_SDA |   IN | 1 |  3 || 4  |   |      | 5V       |     |      |
 |   65 |   1 | I2C2_SCL |   IN | 1 |  5 || 6  |   |      | GND      |     |      |
 |  150 |   2 |     PWM1 | ALT2 | 1 |  7 || 8  | 1 | ALT2 | I2C3_SCL | 3   | 145  |
 |      |     |      GND |      |   |  9 || 10 | 1 | ALT2 | I2C3_SDA | 4   | 144  |
 |   33 |   5 | GPIO1_A1 |   IN | 0 | 11 || 12 | 1 | IN   | GPIO1_C2 | 6   | 50   |
 |   35 |   7 | GPIO1_A3 |  OUT | 1 | 13 || 14 |   |      | GND      |     |      |
 |   92 |   8 | GPIO2_D4 |   IN | 0 | 15 || 16 | 0 | IN   | GPIO1_C6 | 9   | 54   |
 |      |     |     3.3V |      |   | 17 || 18 | 0 | IN   | GPIO1_C7 | 10  | 55   |
 |   40 |  11 | SPI1_TXD | ALT3 | 0 | 19 || 20 |   |      | GND      |     |      |
 |   39 |  12 | SPI1_RXD | ALT3 | 1 | 21 || 22 | 0 | IN   | GPIO1_D0 | 13  | 56   |
 |   41 |  14 | SPI1_CLK | ALT3 | 1 | 23 || 24 | 1 | ALT3 | SPI1_CS  | 15  | 42   |
 |      |     |      GND |      |   | 25 || 26 | 0 | IN   | GPIO4_C5 | 16  | 149  |
 |   64 |  17 | I2C2_SDA |   IN | 1 | 27 || 28 | 1 | IN   | I2C2_SCL | 18  | 65   |
 |      |     |  I2S0_RX |      |   | 29 || 30 |   |      | GND      |     |      |
 |      |     |  I2S0_TX |      |   | 31 || 32 |   |      | I2S_CLK  |     |      |
 |      |     | I2S0_SCK |      |   | 33 || 34 |   |      | GND      |     |      |
 |      |     | I2S0_SI0 |      |   | 35 || 36 |   |      | I2S0_SO0 |     |      |
 |      |     | I2S0_SI1 |      |   | 37 || 38 |   |      | I2S0_SI2 |     |      |
 |      |     |      GND |      |   | 39 || 40 |   |      | I2S0_SI3 |     |      |
 +------+-----+----------+------+---+----++----+---+------+----------+-----+------+
 | GPIO | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | GPIO |
 +------+-----+----------+------+---+OrangePi 4+---+---+--+----------+-----+------+

[5] Download the DTS file that comes with the 'Apollo OS'. Yes, this is a binary file I'm providing, but the apollo miner binary is, too, and I'm trying to figure out a better way for this as we speak.

Code:

wget https://github.com/iamthen0nce/apollo-dtb/raw/main/rk3399-orangepi-4.dtb

[6] Move it into the right directory.

Code:

sudo mv rk3399-orangepi-4.dtb /boot/dtb/rockchip/rk3399-orangepi-4.dtb

[7] Edit the /etc/rc.local file.

Code:

sudo vim /etc/rc.local

[8] Replace 'exit 0' line with the following.

Code:

#configure gpios
gpio mode 1 out
gpio write 1 0
gpio mode 0 out
gpio write 0 1

[9] Reboot the unit.

Code:

sudo reboot

I got through this part and the fan is finally running at 1800rpm, looks like it worked! Now I can continue to tackle the rest without that noisy terror distracting me! Grin

That was not easy.....

Lessons learned:

- the OS might take much longer to load than expected. I etched Armbian_22.11.1_Orangepi4-lts_jammy_current_5.15.80_gnome_desktop.img.xz
to an SD card and it took over 3 minutes before any signs of life showed up on the HDMI-connected monitor. On second reboot, it too about 4 minutes before showing it is running. I assume that maybe my failed attempts to use an Ubuntu version were due to my impatience, I never waited that long to see if it would boot.

- for some reason, the Armbian_22.11.1_Orangepi4-lts_jammy_current_5.15.80_gnome_desktop.img.xz OS has no issues when connecting to GitHub to download the wiringOP thingamajigg (just like my Ubuntu laptop OS). Not asking for a password, just doing it like n0nce's instructions suggest. So for some reason, that previously tried bullseye-minimal armbian has some issue that will not be easy to solve for a noob when following n0nce's instructions.

EDIT: This is nonsense: See next post (it breaks the WiFi) - cannot use the binary file that n0nce has linked to, because I'm using a different OS than n0nce used. At least, I assume that is the case. I got around that issue by accessing the Apollo SD card with the FutureBit OS on it (in a card reader on my laptop). Find the appropriate file for the specific OS flavour, copy it to a USB memory stick, stick it into the Apollo and copy it into the /home folder. Then (for this specific case only):

Code:

sudo mv rk3399-orangepi-4-lts.dtb /boot/dtb/rockchip/rk3399-orangepi-4-lts.dtb

Such fun typing this stuff without any typo's! [/font][/color]

- that vim text editor will drive you nuts, unless you just use the few commands needed for the task: type 'i' to get it into insert mode, then edit the file as instructed by n0nce, then Esc button to end the insert mode, then :x! to save and exit. I got that tidbit of geek-speak from here: https://www.geeksforgeeks.org/getting-started-with-vim-editor-in-linux/

- whatever you do, do not try to use the built-in help of that vim editor unless you want to spend a lot of time getting nowhere while then fan is still howling! Grin

The creator of vim must be some evil genius type of person.....

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: MrMik on December 13, 2022, 06:13:43 PM

ADDITION: I just noticed that

Code:

git clone https://github.com/orangepi-xunlong/WiringOP

- when used on my Ubuntu laptop - does NOT ask for a password and it does create the wiringOP directory as it should.
Any idea why armbian does not want to cooperate on this?

Probably your Ubuntu has GitHub credentials set up.

You can try to clone the repo like this instead:

Code:

git clone git://github.com/orangepi-xunlong/wiringOP.git

Or otherwise download it as zip, unpack and rename it.

Code:

wget https://github.com/orangepi-xunlong/wiringOP/archive/refs/heads/master.zip
unzip wiringOP-master.zip
mv wiringOP-master wiringOP

MrMik

member

Activity: 203

Merit: 37

Quote from: n0nce on June 07, 2022, 04:00:34 PM

GPIO Setup
[1] Download WiringOP to get access to GPIO of the Orange Pi 4.

Code:

cd /home/admin
git clone https://github.com/orangepi-xunlong/WiringOP
cd WiringOP

I installed Armbian_22.11.1_Orangepi4-lts_bullseye_current_5.15.80_minimal.img.xz onto an SD card and managed to boot it up and connect to WiFi.
Looks like no GUI available.

So I tried to follow the instructions but I'm running into some issues.

I managed to figure out

Code:

sudo apt update && sudo apt install armbian-config

and

Code:

sudo apt install git

but now I'm stuck at

Code:

git clone https://github.com/orangepi-xunlong/WiringOP

It asks for a user name and password for https://github.com. I dug one up from my password manager and tried various combinations of user name and email address, but always get an error message :

Quote

Support for password authenticatiion was removed on August 13, 2021.

It directs me to https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls which sends me to https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token and https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop .

And I cannot make any sense of it.

So

Code:

cd wiringOP

still returns: No such file or directory

Meanwhile, Polli is not mining but the fan is howling at full speed, not a pleasant way to try to figure this out.

Need to get a suitable 5V power supply to separate OrangePi4 and ASIC board, I think.

ADDITION: I just noticed that

Code:

git clone https://github.com/orangepi-xunlong/WiringOP

- when used on my Ubuntu laptop - does NOT ask for a password and it does create the wiringOP directory as it should.

Any idea why armbian does not want to cooperate on this?

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: itshig on November 25, 2022, 08:11:57 PM

Getting closer I think? Can I just pay you to hop on ssh and figure this out? Grin

I really hope that your SSH interface is not accessible from the internet (closed port in local and / or router firewall)!

Quote from: itshig on November 25, 2022, 08:11:57 PM

Code:

~snip~
Nov 25 19:00:46 orangepi4 miner_start.sh[1608]: sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
Nov 25 19:00:46 orangepi4 miner_start.sh[1608]: sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
Nov 25 19:00:47 orangepi4 miner_start.sh[1632]: sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
Nov 25 19:00:47 orangepi4 miner_start.sh[1632]: sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.

As far as I know, this error relates to sandboxing; now it dawns on me: Umbrel heavily relies on Docker containers. Virtualization and sandboxing like this is great for security, but it clashes heavily with my bare-metal approaches and guides. Undecided

I'm very sorry; should have catched that earlier. I have to get into Umbrel myself and make a dedicated guide for setting the Apollo miner up in Docker to run on Umbrel. That will definitely take some time, I'm afraid.

Umbrel requires installing everything through Docker, as explained here:
https://github.com/getumbrel/umbrel-apps/blob/master/README.md

itshig

newbie

Activity: 10

Merit: 1

Meh, miner shut down on its own and won't start back up. I have to keep rebooting in order to get it to load.

itshig

newbie

Activity: 10

Merit: 1

Quote from: n0nce on November 24, 2022, 04:26:42 PM

Ok, this is very helpful! Indeed, the miner needs to be executed as root to get GPIO access.
If you're working with the systemd service, make sure to uncomment these lines, as I explained before.

Code:

#User=admin
#Group=sudo

I.e., you want to remove the '#' signs in the front so it reads:

Code:

User=admin
Group=sudo

The default root user may be called 'umbrel' actually. Maybe try that, instead.
If you're logged in as 'umbrel' (check with command: whoami), try the groups command to see whether you're in sudo group. If so, use User=umbrel and Group=sudo.
Whole file then at follows:

Getting closer I think? Can I just pay you to hop on ssh and figure this out? Grin

It looks like it's running according to sudo service miner status as seen below. However, it's displaying those other errors with regard to sudo. Further, my fan is still loud af (no change from not mining to mining). And it's not registering on my pool as being an active miner; about 10 min in according to active (running) results on the latest miner status report.

^{all private info changed (ie user/password, etc)}

Code:

● miner.service - Apollo Miner
Loaded: loaded (/lib/systemd/system/miner.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2022-11-25 19:01:17 EST; 2min 23s ago
Process: 1567 ExecStart=/opt/miner/linux-aarch64/miner_start.sh (code=exited, status=0/SUCCESS)
Main PID: 3938 (screen)
Tasks: 3 (limit: 4451)
Memory: 2.7M
CPU: 4.950s
CGroup: /system.slice/miner.service
├─3938 SCREEN -dmS miner ./apollo-miner -comport /dev/ttyS1 -ao_mode 1 -host stratum+tcp://us-east.stratum.braiins.com -port 3333 -user my.worker -pswd password123 -brd>
└─3952 ./apollo-miner -comport /dev/ttyS1 -ao_mode 1 -host stratum+tcp://us-east.stratum.braiins.com -port 3333 -user my.worker -pswd password123 -brd_ocp 48 -osc 30 -f>

Nov 25 19:00:45 orangepi4 systemd[1]: Starting Apollo Miner...
Nov 25 19:00:46 orangepi4 miner_start.sh[1608]: sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
Nov 25 19:00:46 orangepi4 miner_start.sh[1608]: sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
Nov 25 19:00:47 orangepi4 miner_start.sh[1632]: sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
Nov 25 19:00:47 orangepi4 miner_start.sh[1632]: sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
Nov 25 19:01:17 orangepi4 miner_start.sh[1567]: Apollo Miner Started
Nov 25 19:01:17 orangepi4 systemd[1]: Started Apollo Miner.

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: itshig on November 24, 2022, 12:07:06 PM

I've gone back through the instructions and now I'm getting:

Code:

miner_start.sh[1599]: gpio: Must be root to run. Program should be suid root. This is an error.
miner_start.sh[1630]: gpio: Must be root to run. Program should be suid root. This is an error.

Ok, this is very helpful! Indeed, the miner needs to be executed as root to get GPIO access.
If you're working with the systemd service, make sure to uncomment these lines, as I explained before.

Code:

#User=admin
#Group=sudo

I.e., you want to remove the '#' signs in the front so it reads:

Code:

User=admin
Group=sudo

The default root user may be called 'umbrel' actually. Maybe try that, instead.
If you're logged in as 'umbrel' (check with command: whoami), try the groups command to see whether you're in sudo group. If so, use User=umbrel and Group=sudo.
Whole file then at follows:

Code:

[Unit]
Description=Apollo Miner
After=network.target

[Service]
WorkingDirectory=/opt/miner/linux-aarch64
ExecStart=/opt/miner/linux-aarch64/miner_start.sh
ExecStop=/opt/miner/linux-aarch64/miner_stop.sh

# Make sure the config directory is readable by the service user
PermissionsStartOnly=true

# Process management
####################

Type=forking
Restart=on-failure

# Directory creation and permissions
####################################

# Run as root:root
User=umbrel
Group=sudo

# Hardening measures
####################

# Provide a private /tmp and /var/tmp.
PrivateTmp=true

# Mount /usr, /boot/ and /etc read-only for the process.
# Mounts everything read-only with the exception of /dev, /proc and /sys.
ProtectSystem=full

# Disallow the process and all of its children to gain
# new privileges through execve().
NoNewPrivileges=true

# Deny the creation of writable and executable memory mappings.
MemoryDenyWriteExecute=true

## More hardening
ProtectControlGroups=yes
ProtectHostname=yes
ProtectKernelLogs=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
ProtectProc=yes

RestrictNamespaces=yes
RestrictRealtime=yes

LockPersonality=yes

SystemCallArchitectures=native
SystemCallFilter=~@privileged @resources
SystemCallFilter=@system-service

CapabilityBoundingSet=CAP_SYS_ADMIN
CapabilityBoundingSet=CAP_SYS_RAWIO
CapabilityBoundingSet=CAP_MKNOD

[Install]
WantedBy=multi-user.target

If you're running from command line, execute: sudo ./miner_start.sh .

Quote from: itshig on November 24, 2022, 12:07:06 PM

I appreciate all of your help, to me and the community as a whole!

Very welcome.

itshig

newbie

Activity: 10

Merit: 1

Quote from: n0nce on November 22, 2022, 12:02:13 PM

Quote from: itshig on November 19, 2022, 06:03:29 PM

It seems like it's still not running even though it appears to start. My fan is still racing (as if the miner was off) and the lights on the front aren't doing anything (though that may be normal given the custom route). Also, my pool still isn't picking up my miner as being active.

Is your config fine? Maybe try rebooting? The fan should not race when the miner is off; instead it should do that when mining.

I've rebooted a bunch. I took a few days off from this though and back at it. Fan has always raced when not mining (on the factor sd/nvme) until I power it down. As soon as it starts mining, the fan slows down.

I've gone back through the instructions and now I'm getting:

Code:

miner_start.sh[1599]: gpio: Must be root to run. Program should be suid root. This is an error.
miner_start.sh[1630]: gpio: Must be root to run. Program should be suid root. This is an error.

I've gone through the config file a few times and everything looks ok. This is frustrating! Lol

I appreciate all of your help, to me and the community as a whole!

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: itshig on November 19, 2022, 06:03:29 PM

It seems like it's still not running even though it appears to start. My fan is still racing (as if the miner was off) and the lights on the front aren't doing anything (though that may be normal given the custom route). Also, my pool still isn't picking up my miner as being active.

Is your config fine? Maybe try rebooting? The fan should not race when the miner is off; instead it should do that when mining.

itshig

newbie

Activity: 10

Merit: 1

It seems like it's still not running even though it appears to start. My fan is still racing (as if the miner was off) and the lights on the front aren't doing anything (though that may be normal given the custom route). Also, my pool still isn't picking up my miner as being active.

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: itshig on November 19, 2022, 04:28:33 PM

~

Seems to start fine as sudo. Try uncommenting those lines and reload the service.

Code:

sudo systemctl daemon-reload
sudo service miner restart

itshig

newbie

Activity: 10

Merit: 1

Quote from: n0nce on November 19, 2022, 03:17:48 PM

Quote from: itshig on November 19, 2022, 03:08:35 PM

It stays apollo miner was stopped (I added "apollo miner" to start and finish for my own clarity lol) and my pool isn't picking up a mining status.

Can you try manually starting /opt/miner/linux-aarch64/miner_start.sh and checking what errors it throws?

It's possible that it needs sudo privileges and the following lines need to be uncommented. I'm not 100% sure right now, why I had them commented out.

Code:

#User=admin
#Group=sudo

Code:

user@machine: /opt/miner/linux-aarch64$ sudo ./miner_start.sh
ls: cannot access '/dev/ttyACM*': No such file or directory
Apollo Miner Started
user@machine: /opt/miner/linux-aarch64$ sudo service miner status
○ miner.service - Apollo Miner
   Loaded: loaded (/lib/systemd/system/miner.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Sat 2022-11-19 14:12:38 EST; 1h 13min ago
   Process: 51417 ExecStart=/opt/miner/linux-aarch64/miner_start.sh (code=exited, status=0/SUCCESS)
   Process: 52588 ExecStop=/opt/miner/linux-aarch64/miner_stop.sh (code=exited, status=0/SUCCESS)
   Main PID: 52586 (code=exited, status=0/SUCCESS)
   CPU: 658ms

Nov 19 14:12:06 orangepi4 systemd[1]: Starting Apollo Miner...
Nov 19 14:12:37 orangepi4 miner_start.sh[51417]: Apollo Miner Started
Nov 19 14:12:37 orangepi4 systemd[1]: Started Apollo Miner.
Nov 19 14:12:37 orangepi4 miner_stop.sh[52593]: No screen session found.
Nov 19 14:12:37 orangepi4 miner_stop.sh[52594]: No screen session found.
Nov 19 14:12:38 orangepi4 miner_stop.sh[52599]: ls: cannot access '/dev/ttyACM*': No such file or directory
Nov 19 14:12:38 orangepi4 miner_stop.sh[52588]: Apollo Miner Stopped
Nov 19 14:12:38 orangepi4 systemd[1]: miner.service: Deactivated successfully.

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: itshig on November 19, 2022, 03:08:35 PM

It stays apollo miner was stopped (I added "apollo miner" to start and finish for my own clarity lol) and my pool isn't picking up a mining status.

Can you try manually starting /opt/miner/linux-aarch64/miner_start.sh and checking what errors it throws?

It's possible that it needs sudo privileges and the following lines need to be uncommented. I'm not 100% sure right now, why I had them commented out.

Code:

#User=admin
#Group=sudo

itshig

newbie

Activity: 10

Merit: 1

Quote from: n0nce on November 19, 2022, 07:51:57 AM

Quote from: itshig on November 19, 2022, 01:02:33 AM

I'm getting the error that the system can't access /dev/ttyACM. When or where was this created? I don't see it in the instructions and I don't have this file structure.

That's not a problem; this code is just in case you have standard units connected through USB. It should still pick up and start mining on your full unit's integrated hash board.

This is what it's returning:

Code:

$ sudo service miner start
$ sudo service miner status
○ miner.service - Apollo Miner
Loaded: loaded (/lib/systemd/system/miner.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sat 2022-11-19 14:04:25 EST; 5s ago
Process: 43175 ExecStart=/opt/miner/linux-aarch64/miner_start.sh (code=exited, status=0/SUCCESS)
Process: 44155 ExecStop=/opt/miner/linux-aarch64/miner_stop.sh (code=exited, status=0/SUCCESS)
Main PID: 44152 (code=exited, status=0/SUCCESS)
CPU: 736ms

Nov 19 14:03:53 orangepi4 systemd[1]: Starting Apollo Miner...
Nov 19 14:04:24 orangepi4 miner_start.sh[44153]: ls: cannot access '/dev/ttyACM*': No such file or directory
Nov 19 14:04:24 orangepi4 miner_start.sh[43175]: Apollo Miner Started
Nov 19 14:04:24 orangepi4 systemd[1]: Started Apollo Miner.
Nov 19 14:04:24 orangepi4 miner_stop.sh[44160]: No screen session found.
Nov 19 14:04:24 orangepi4 miner_stop.sh[44161]: No screen session found.
Nov 19 14:04:25 orangepi4 miner_stop.sh[44166]: ls: cannot access '/dev/ttyACM*': No such file or directory
Nov 19 14:04:25 orangepi4 miner_stop.sh[44155]: Apollo Miner Stopped
Nov 19 14:04:25 orangepi4 systemd[1]: miner.service: Deactivated successfully.

It stays apollo miner was stopped (I added "apollo miner" to start and finish for my own clarity lol) and my pool isn't picking up a mining status.

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: itshig on November 19, 2022, 01:02:33 AM

I'm getting the error that the system can't access /dev/ttyACM. When or where was this created? I don't see it in the instructions and I don't have this file structure.

That's not a problem; this code is just in case you have standard units connected through USB. It should still pick up and start mining on your full unit's integrated hash board.

Topic: [Guide] Futurebit Apollo BTC Custom Linux Install - Miner (Read 496 times)