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

Looks like the armbian version is indeed CLI interface only. Oh well, finally a reason t get into this!

Maybe the Ryobi power supply is to blame, or something else, but the newly built Armbian_22.05.4_Orangepi4-lts_bullseye_current_5.15.48.img.xz does not show up on the HDMI monitor when I try to reboot it.

But, after connecting the cable between Orange Pi 4 and ASICs, it does boot up and asks for login and password.

So, here I am, the fan is howling although the miner is stone-cold and that command-prompt is blinking at me...

ROTFLMAO

I'm making progress!

Meanwhile, the Apollo ASIC board is hashing away happily.

I disconnected the Orange Pi 4 from the ASICs and powered it up using some gear I found within arm's reach.....

I knew this dumb power supply would come in handy one day:  https://www.bunnings.com.au/ryobi-one-18v-usb-power-adapter-skin-only_p6210800
It has a 2.1A and a 1A 5V USB outlet and so far, things seem to work with 2.1A.

I thought it did have a GUI, to be honest.

On https://www.armbian.com/orange-pi-4/ you find all supported versions, like 'Bullseye CLI', 'Bullseye Minimal' (minimalistic GUI without a lot of bloat), and different versions of Jammy with and without graphical desktop.

I'm not sure about your power supply situation; you probably want to have around 15W of power output so the Orange Pi runs stable; worst-case, just connect the hashboard and power it up through the Futurebit enclosure (12V power supply).

Trying to follow the instructions, I found that I have to follow them very exactly!

I'm only getting some success when using the same armbian version that n0nce used ( Armbian_22.05.4_Orangepi4-lts_bullseye_current_5.15.48.img.xz )

I tried Armbian_22.11.1_Orangepi4_jammy_current_5.15.80_xfce_desktop.img.xz and Armbian_22.08.2_Orangepi4_jammy_current_5.15.69.img.xz  , but neither of them seem to be able to use the WiFi on the Orange Pi4.

For some reason I also cannot get dd to burn a valid image to SD card, but Etcher worked for all attempted versions.

After finding that the later versions of Armbian do not find the WiFi on the Orange Pi4 , I also tried the ubuntu-22.04.1-desktop-amd64.iso , Etcher reported a successful etch onto the SD card (64GB), but no signs of life on the HDMI monitor when I try to boot it.

So I went back to n0nce's instructions and downloaded the exact armbian version that n0nce used, and it does find the WiFi spontaneously during the first boot.

Now it is downloading updates / upgrades....

And I wonder if this particular armbian OS has a GUI? 

So far it's all code gobbledigook, this might be my first foray into GUI-less computing, wish me luck!   

---

Meanwhile, the Apollo ASIC board is hashing away happily.

I disconnected the Orange Pi 4 from the ASICs and powered it up using some gear I found within arm's reach.....

I knew this dumb power supply would come in handy one day:  https://www.bunnings.com.au/ryobi-one-18v-usb-power-adapter-skin-only_p6210800
It has a 2.1A and a 1A 5V USB outlet and so far, things seem to work with 2.1A.

---

Looks like the armbian version is indeed CLI interface only. Oh well, finally a reason t get into this!

Maybe the Ryobi power supply is to blame, or something else, but the newly built Armbian_22.05.4_Orangepi4-lts_bullseye_current_5.15.48.img.xz does not show up on the HDMI monitor when I try to reboot it.

But, after connecting the cable between Orange Pi 4 and ASICs, it does boot up and asks for login and password.

So, here I am, the fan is howling although the miner is stone-cold and that command-prompt is blinking at me...

ROTFLMAO

I'm making progress!

[moderator's note: consecutive posts merged]

You're welcome; that's how I felt, after going down that rabbit hole, too.

Exactly my point.

Thank you n0nce!

I found it and did the diff, but still none the wiser.

Have to give up at this point and be happy with the fact that I learned lots while trying to do this.

It has to be safer to run armbian OS with maintenance and updates and that dtb file, than running armbian without updates and that dtb file! 

Have a look in /boot/dtb/rockchip directory.
Otherwise, you can do a full system search like this:

I was hoping to diff the files somehow, but had no idea how easy that is!


But where do I find the .dtb file? Have not seached on armbian yet, but a search on Ubuntu does not find any .dtb files except for the ones I have been playing with.

I would take the stock DTB file from your Armbian install, get the DTS from that and diff it, however if I remember correctly, I've already done that and the diff was also huge. Probably since my Armbian was different from the Armbian they used when they created Futurebit OS.

I followed instructions here https://michlstechblog.info/blog/linux-decompile-show-a-device-tree-binary-file-dtb/ and am able to read the resulting .dts file.

But, understanding it is a different matter!

Seems to me that the .dtb file only runs once at bootup, but I'm clueless.

However. in the spirit of 'Don't trust, verify' I read through the whole thing and I tried to search for something giving me a hint as to which part of the code is the part needed for the Apollo. I suppose somewhere in the long file are the instructions for how to communicate with the ASIC hashboard.

Do we know the exact ASIC chips name, or something else that could help search for the Apollo related part of the code?

No, no, power always works through GPIO; just the OS needs to learn to communicate over other GPIO pins to the board.

Exactly, that's perfectly right.

Put that way, it makes sense!

But do I not need the extra power supply to power up the Orange Pi in order to install the GPIO setup?

I can put Armbian on the SD card, but 'teaching' it to communicate through that cable to the ASIC board in the Apollo requires that the Orange Pi OS is up and running.

Or will it be powered automatically, just by by virtue of being plugged into that cable, and the GPIO setup just 'teaches' it how to communicate with the ASIC board?

Maybe he meant that 'stock Futurebit OS' has some security issues. So in 'following the instructions' the 'instructions' could be the official Futurebit instructions.
There's something to that; apt updates still seem to break the kernel modifications that they have in place to connect to the hashboard. Maybe they also just break the device tree. At least that's the only thing I needed to get the hashboard recognized in stock Armbian.

Therefore, users of Futurebit OS are advised not to update; potentially running outdated and insecure packages. This can be resolved by following my guide, which installs everything on its latest version through apt.

In short; the dashboard might not work. But it's not really required to run Bitcoin Core and mine. I didn't need it, myself at least. No security risks here, though.

No, that's correct! DTB files are just device trees, though. But I'd prefer to provide just a diff between stock Armbian and the Futurebit DTS (device tree specification), such that it can be applied to any future stock Armbian DTS.
You can decompile the DTB to DTS and read that, they're huge files though and I didn't manually check it, just extracted from Futurebit OS release. So I can't say for certain whether they can (or are) problematic. I highly doubt that, but still wanted to add this disclaimer just in case.

Sorry to cause confusion and maybe concern for some readers. My fault for not really fully understanding the instructions, no doubt.

The stuff I picked up as potentially concerning was this: https://bitcointalksearch.org/topic/m.60310493

With this one I am even more uncertain if I understand it correctly.

What I thought (while reading the instructions diagonally) this sentence means is this:

'This is a binary file' = no-one can tell what is in it, i.e. no source code provided and therefore we have to trust n0nce and/or jstefanop that the content is not malicious.
I probably misunderstood that one completely, my apologies, I'm not trying to accuse anyone of bad intentions. 

Yes; it's mostly correct.

Exactly: what differentiates my guide from just installing generic Armbian, Bitcoind and Apollo-miner binaries is that the GPIO setup lets you use the hashboard through the internal connection. Saving you an USB cable and a second power supply.

No; there are no known software vulnerabilities when following my instructions! Not sure how you came to such conclusion.

Yes; if you skip the GPIO setup, but follow all other steps, that's how you would operate the miner. Hashboard connected using a microUSB to USB-A cable, and a separate power supply for the Orange Pi 4.

This would definitely work and you don't have to worry about ground loops. It will just be a 'Standard Unit' controlled from an Orange Pi 4, that is conveniently sitting in the same enclosure. Electrically, there is no difference whether it sits inside or not.

I just don't see why you would want to do that, if using this one simple step you can save around 50 bucks in cables and power supplies.

Yes, that's exactly what I've done in my guides. I labeled each step with what software is installed and the build instructions are mainly taken from the original projects' GitHub pages & modified to run on Armbian. If you're going to do it all manually (without guide), you'll be doing basically the exact same stuff.

Yes, the miner script in my guide supports external standard units, as well. Don't need separate terminals even; the script recognizes and starts up all of them!

Thanks for writing this guide and the guides for the custom Linux miner and node install!

The miner and node install instructions are above my current skill level, although I could probably follow the instructions without understanding what I am doing.

However, I wonder if there is an alternative approach.

Do I understand this correctly when stating it as follows?

1) The miner and node install instructions are needed so that the Orange Pi can be operated while the cable between Orange Pi  and ASIC board is connected, and the Orange Pi is powered that way.

2) There are still software vulnerabilities involved when following the instructions.

3) The Orange Pi 4 could be dis-connected from the ASIC board, turning it into a Standard Apollo with a Orange Pi in the same housing. With a dumb 5V power supply to the USB-C port, the Orange Pi 4 could be powered up and run Armbian OS

4) This is where it gets tricky, potentially: Can the 'separated' Orange Pi 4 be connected via USB to USB micro cable to the ASIC board in the same housing, or does that create some ground loop that could fry things?

5) If I get a new PSU to power the 'separated' ASIC board on 12V and the 'separated' Orange Pi on 5V: Would that 5V supply be 'dumb' enough to provide sufficient power to the separated Orange Pi? And would that put the separated ASIC board and Orange Pi on the same ground connection so that a ground loop is prevented?

6) Can I then just install Bitcoin Core, Electrum, Electrs and a Lightning wallet and whatever else I want into the Armbian OS, keep it updated and secure, and run the 'separated' ASIC board by using the Apollo BTC Standard software in a terminal? https://bitcointalksearch.org/topic/m.57091051

7) And can I then also run additional Standard Apollo units (each in a separate terminal, connected to the same (new) PSU on 12V?

[/quote]

The definition of quiet or silent is very dependent on the environment and the person listening to it.

Personally I refer to quiet as being basically inaudible while standing about 1 or 2 meters from it.

At 2600 RPM the stock fan is definitely audible, but for some people that can still be quiet. It can definitely get way louder at 300W+
[/quote]

True.
I did read somewhere they had a fan supply issue for a while.
Not sure if the different fans would have different noise level at same speed.

Definitely quieter than my Antminer R4 with APW7 PSU, which were sold as quiet enough for home mining, but man those are loud 
I'm running it outdoor on the balcony it's too annoying loud.

With the Apollo I definitely hear a low fan noise at 1 or 2 meters just like a home ventilator on low.
Not annoying at all

The definition of quiet or silent is very dependent on the environment and the person listening to it.

Personally I refer to quiet as being basically inaudible while standing about 1 or 2 meters from it.

At 2600 RPM the stock fan is definitely audible, but for some people that can still be quiet. It can definitely get way louder at 300W+

I set up my Apollo on Turbo getting about 3 TH, using 200W with the fan running at 2600 RPM.
It's still really quiet.
Maybe the newer batch got a better fan?
I got mine about a month ago and just got a second one.
One full, one standard. No PSU. Prefer silent PSU.

My plan was to mine solo directly with the node but that's not possible yet.
They're working on it I read.
Only way is ckpool but for not I mine in pool get a bit of money back 

Good question; in my honest opinion, they're bloated and thus less maintainable for me. That's why I prefer to start with a fresh, lean Linux distro and install just what I need.
It's also possible that there are no Umbrel / node-in-a-box distributions for this CPU. This is not a Raspberry Pi, but an OrangePi 4 and in fact, Armbian was the only distribution for which I could find a compiled ISO to download.

I'm not 100% sure that it will install on Armbian, especially Armbian on Orange Pi. But feel free to try! Technically, it's a subset of Debian, so it should work.

Honestly just quickly try it; flash Armbian, log into it and install Umbrel - would be great if you can report back how it worked out.

I don't have access to my Apollo right now, otherwise I'd try.