Bitcoin Forum
May 14, 2024, 04:14:46 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: April 07, 2024, 06:43:06 AM

I assume that the internal flash memory is being read much too quickly, but all services have not started yet. A pause would then have to be inserted in the rc.local before mounting the SSD.

Code:
mount /dev/nvme0n1p1 /media/nvme
#mount nvme drive


Code:
#mount nvme drive
sleep 5 && mount /dev/nvme0n1p1 /media/nvme

if there is a pause of about 5 seconds before the mount command is set, the SSD will work after booting the MCU-2.

This helps with super-fast SD cards or internal flash memory of the Orange PI 4 LTS
2  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: April 05, 2024, 06:33:14 AM
...as soon as the SBC/MCU has completely booted up, I can subsequently mount the SSD using the command.

mount /dev/nvme0n1p1 /media/nvme
3  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: April 05, 2024, 05:56:33 AM
Thank you for the great new V2 SD card image. I've been following you on Github for a long time and compiling the image myself.

The installation of the V2 SD card image went smoothly. The Apollo V1 starts with the SCB/MCU 2 board with full fan performance. I don't know yet whether this is a feature or a bug. The Apollo SBC/MCU 1 didn't do that. It's very annoying...
If you shut down the board, the large black fan also runs at full power.
Shortly after switching on, the fan switches off and the volume becomes bearable again.

If you use an OrangePi 4 LTC with internal eMMC storage, the internal SSD is not mounted.

It would make sense to wait until the network has "booted up" before mounting the SSD?!?!?

I assume that the internal flash memory is being read much too quickly, but all services have not started yet. A pause would then have to be inserted in the rc.local before mounting the SSD.

Code:
mount /dev/nvme0n1p1 /media/nvme
#mount nvme drive
4  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: March 30, 2024, 05:36:10 PM
For testing I use an OrangePi 4 LTS with internal 16 GB ECC memory.
I have to mount my 1 TB SSD with fully synchronized blockchain manually. I took the start file from my old V1 Apollo because the new one unfortunately doesn't work. I connected the Apollo1 to the SBC board via USB.

miner_start.sh

chmod 755 miner_start.sh


Code:
#!/bin/bash

cd /opt/apolloapi/backend/apollo-miner
settings=$(cat miner_config)

start_hashboards()
{
    while [ $1 ];
            do
            screen -dmS miner ./futurebit-miner -comport $1 -ao_mode 1 $settings
            sleep 1
            shift
    done
}

#clear old log files
rm apollo-miner.*

#reset internal hashboard
gpio write 0 0
sleep .5
gpio write 0 1

sleep 30
#start internal hashboard

screen -dmS miner ./futurebit-miner -comport /dev/ttyS1 -ao_mode 1 $settings

#find and start external hashboards

ports=$(ls /dev/ttyACM*)
start_hashboards $ports

echo "Started"







5  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: March 28, 2024, 07:07:48 PM


This is completely normal... the first sync of my Apollo 1 took several days.
There is a trick...I sync my Apollos with an existing blockchain in my network. So I transfer the blockchain from one device to the Apollo. This only takes a few hours
6  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: March 28, 2024, 06:52:41 AM
...next step I will try Armbian with kernel 6.6...

Armbian_24.2.1_Orangepi4-lts_jammy_current_6.6.16_xfce_desktop.img

7  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: March 28, 2024, 06:39:51 AM

The miner_start.sh didn't work and I had to adjust the start file. I then connected the Apollo to the MCU 2 version of the SCB board via USB. The power consumption of "only" 80 watts doesn't seem to be correct. A fully synced SSD 1 TB from the Apollo 1 doesn't seem to work either. I'm really looking forward to the V2, which will be released tomorrow, and I'm looking forward to being able to repair more of your devices.

I made the following notes during installation.

Orangepi4-lts_3.0.6_ubuntu_jammy_desktop_xfce_linux5.18.5.img # flash SD-Card
root/orangepi # user/pass
apt-get update
apt-get upgrade
reboot

# Download and start Image-install
wget https://raw.githubusercontent.com/jstefanop/apolloapi-v2/dev/backend/image_install
chmod 755 image_install
./image_install dev

Yes, there still seem to be a lot of bugs in the code and the bash installation cannot work because the "dev" attribute is missing. You are welcome to integrate me as a beta tester, as I currently have two devices here to be repaired.

curl -o- https://raw.githubusercontent.com/jstefanop/apolloapi-v2/dev/backend/install-v2 | sudo bash   # "dev" attribute is missing

but in Code need attribute "dev"

if [ "$1" = "dev" ]; then

8  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: March 23, 2024, 08:15:28 PM
it works now - looks nice !!!

9  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: March 19, 2024, 10:45:11 AM
i change code in

/opt/apolloapi/backend/install

Line 33
git clone --single-branch --branch dev-BTC https://github.com/jstefanop/apolloapi-v2.git $APOLLO_DIR

line 35
git clone --single-branch --branch dev-BTC https://github.com/jstefanop/apolloui-v2.git $APOLLO_DIR/apolloui

and start the Install with #./install dev

Code:
root@futurebitbtc:/opt/apolloapi/backend# ./install dev
 ---> Installing required system packages
Hit:1 http://ports.ubuntu.com focal InRelease
Hit:2 http://ports.ubuntu.com focal-security InRelease                                                                             
Hit:4 http://ppa.launchpadcontent.net/saiarcot895/chromium-beta/ubuntu focal InRelease                                             
Hit:5 http://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu focal InRelease                                                       
Hit:6 http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu focal InRelease                                               
Hit:7 http://ports.ubuntu.com focal-updates InRelease                                                                             
Hit:8 http://ports.ubuntu.com focal-backports InRelease                 
Hit:3 https://box64.debian.ryanfortner.dev/debian ./ InRelease           
Ign:9 http://mirrors.xtom.de/armbian focal InRelease           
Err:10 http://fi.mirror.armbian.de/apt focal Release   
  404  Not Found [IP: 65.21.120.247 80]
Reading package lists... Done                         
E: The repository 'http://apt.armbian.com focal Release' no longer has a Release file.
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.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  chromium-browser chromium-codecs-ffmpeg-extra python3-software-properties python3-update-manager software-properties-common software-properties-gtk ubuntu-advantage-tools update-manager
  update-manager-core
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
libreadline-dev is already the newest version (8.0-4).
net-tools is already the newest version (1.60+git20180626.aebd88e-1ubuntu1).
whois is already the newest version (5.5.6).
zip is already the newest version (3.0-11build1).
python-dev-is-python2 is already the newest version (2.7.17-4).
tor is already the newest version (0.4.2.7-1).
traceroute is already the newest version (1:2.1.0-2).
curl is already the newest version (7.68.0-1ubuntu2.21).
git is already the newest version (1:2.25.1-1ubuntu3.11).
libpq-dev is already the newest version (12.18-0ubuntu0.20.04.1).
libsqlite3-dev is already the newest version (3.31.1-4ubuntu0.6).
libssl-dev is already the newest version (1.1.1f-1ubuntu2.22).
libxml2-dev is already the newest version (2.9.10+dfsg-5ubuntu0.20.04.7).
libxslt1-dev is already the newest version (1.1.34-4ubuntu0.20.04.1).
network-manager is already the newest version (1.22.10-1ubuntu2.4).
openssh-server is already the newest version (1:8.2p1-4ubuntu0.11).
sudo is already the newest version (1.8.31-1ubuntu1.5).
vim is already the newest version (2:8.1.2269-1ubuntu5.22).
zlib1g-dev is already the newest version (1:1.2.11.dfsg-2ubuntu1.5).
imagemagick is already the newest version (8:6.9.10.23+dfsg-2.1ubuntu11.9).
libmagickwand-dev is already the newest version (8:6.9.10.23+dfsg-2.1ubuntu11.9).
build-essential is already the newest version (12.8ubuntu1.1).
iptables is already the newest version (1.8.4-3ubuntu2.1).
iputils-ping is already the newest version (3:20190709-3ubuntu1).
unzip is already the newest version (6.0-25ubuntu1.2).
htop is already the newest version (3.1.0-0~armbian20.08.2+1).
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
 ---> Adding futurebit user
adduser: The user `futurebit' already exists.
 ---> Cloning Apollo app
 ---> Using DEV branch
fatal: destination path '/opt/apolloapi' already exists and is not an empty directory.
Cloning into '/opt/apolloapi/apolloui'...
warning: Could not find remote branch dev-BTC to clone.
fatal: Remote branch dev-BTC not found in upstream origin
 ---> Installing firewall
 ---> Installing NVM
Installing nvm
mkdir: cannot create directory ‘/usr/local/nvm’: File exists
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14926  100 14926    0     0  66337      0 --:--:-- --:--:-- --:--:-- 66337
=> nvm is already installed in /usr/local/nvm, trying to update using git
=> => Compressing and cleaning up git repository

=> nvm source string already in /root/.bashrc
=> bash_completion source string already in /root/.bashrc
=> Close and reopen your terminal to start using nvm or run the following to use it now:

export NVM_DIR="/usr/local/nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion
v14.16.1 is already installed.
Now using node v14.16.1 (npm v6.14.12)
default -> 14.16.1 (-> v14.16.1)
 ---> Installing API modules

> yarn@1.22.22 preinstall /usr/local/nvm/versions/node/v14.16.1/lib/node_modules/yarn
> :; (node ./preinstall.js > /dev/null 2>&1 || true)

/usr/local/nvm/versions/node/v14.16.1/bin/yarn -> /usr/local/nvm/versions/node/v14.16.1/lib/node_modules/yarn/bin/yarn.js
/usr/local/nvm/versions/node/v14.16.1/bin/yarnpkg -> /usr/local/nvm/versions/node/v14.16.1/lib/node_modules/yarn/bin/yarn.js
+ yarn@1.22.22
updated 1 package in 2.161s
yarn install v1.22.22
warning package.json: License should be a valid SPDX license expression
warning apolloapi@2.0.0: License should be a valid SPDX license expression
[1/5] Validating package.json...
warning apolloapi@2.0.0: License should be a valid SPDX license expression
[2/5] Resolving packages...
success Already up-to-date.
Done in 1.06s.
 ---> Installing UI modules
./install: line 79: cd: /opt/apolloapi/apolloui: No such file or directory
yarn install v1.22.22
warning package.json: License should be a valid SPDX license expression
warning apolloapi@2.0.0: License should be a valid SPDX license expression
[1/5] Validating package.json...
warning apolloapi@2.0.0: License should be a valid SPDX license expression
[2/5] Resolving packages...
success Already up-to-date.
Done in 1.11s.
 ---> Building UI (could take few minutes)
yarn run v1.22.22
warning package.json: License should be a valid SPDX license expression
$ pkg . --targets node8-linux-armv7 --no-bytecode
> pkg@4.5.1
> Fetching base Node.js binaries to PKG_CACHE_PATH
  fetched-v8.17.0-linux-armv7  [                    ] 0%
> Error! 404 Not Found
  https://github.com/zeit/pkg-fetch/releases/download/v2.6/uploaded-v2.6-node-v8.17.0-linux-armv7
> Asset not found by direct link:
  {"tag":"v2.6","name":"uploaded-v2.6-node-v8.17.0-linux-armv7"}
> Not found in GitHub releases:
  {"tag":"v2.6","name":"uploaded-v2.6-node-v8.17.0-linux-armv7"}
> Building base binary from source:
  built-v8.17.0-linux-armv7
> Error! Not able to build for 'armv7' here, only for 'arm64'
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
 ---> Starting firewall
 ---> Installing miner binaries
cp: cannot create regular file '/opt/apolloapi/backend/apollo-miner/futurebit-miner': Text file busy
 ---> Installing systemd files
 Installation complete
10  Bitcoin / Hardware / Re: Official FutureBit Apollo BTC Software/Image and Support thread on: March 12, 2024, 12:48:19 PM

https://github.com/jstefanop/apolloui-v2/tree/dev

Is it possible to integrate this dev branch into a current Apollo Miner?
I tried to install the new Web Ui V2 on the miner using git clone and checkout dev via npm...Unfortunately I get an error message when building
11  Bitcoin / Hardware / Re: New GekkoScience product, the Smart Hub on: January 02, 2024, 02:28:03 PM
I think the SmartHub is great!!!

Is it possible to incorporate the SSH cgminer display into the website?

0: GSF 10051826: BM1397:01+ 400.00MHz T:400 P:390 (31:16) | 92.4% WU:^62% | 206.8G / 130.3Gh/s WU: 1820.0/m


Would it also be possible to integrate the bgminer into a screen process for the Moomlander II and have it displayed on the dashboard?
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!