Werner

If they have the have the exact same ratings in voltage and current I'd say (and assumed you are a bit familiar with the basics) pickup a couple fitting connectors and solder them to the wires.

Isn't U-Boot the same for dev and current at the moment? Both are 2020.04?

Basically doing the same thing as I did before when merging common issues and p2p. Merge their names too.

What I meant was merge the two seperate text blocks into one of not decided to throw the moderator part out completly. I know it is there, I got the mentioned information from right there

Marking this one as done to keep clarity and all important things has been adjusted.

There. Done

Then the best idea is to not get a tvbox but a board that is officially supported: https://www.armbian.com/download/

The registration terms containing: While the regulation as it is makes sense it does not being in the registration notes since the chance that a users registierung him-/herself just to become a moderator is decently low. These should be more kind of rules that members have to agree which are elected to become a forums moderator. Therefore I suggest to either remove those entirely or rewrite them to descripe what the rights and duties of moderators are and integrate this information into the common terms.

Another minor update. Contact information has been updated. You can access and edit these information by clicking on your avatar at the very top right corner, click on Profile and then hit the Edit Profile button.

As long as noone takes up the task and write a proper driver for it and push it to mainline: no.

Not much to say about that. Do some of these mostly proprietary IM even still exist? I suggest to replace a few of those with more adequate solutions like IRC, Matrix or Mastodon and threw out AIM, MSN, ICQ and Yahoo. Opinions?

I also noticed that the subforums SD card and PSU issues and the garbage collector Board doesn't start are kind of redundant. Should those be merged too?

Sure, have multiple OrangePi One and an OrangePi Zero here which are built around the H2+/H3 SoC and working nicely. However in your case I'd suggest start a) using the search engine and b) using the matching thread and not the one for aarch64 (H3 is 32bit and armhf).

Providing logs with armbianmonitor -u significantly raises chances that issue is getting addressed. What command do you use to copy your files?

Move to p2p support since this is not an officially supported board. You can try to isolate the issue by trying other builds like legacy (5.4), current (which is 5.8 at the moment so your current build is outdated) or even dev (5.9.0-rc2).

Patch has been upstreamed and is available in 5.8.6. No changes for us but to remove the previously added patch.

[ warn ] * applying kali-wifi-injection-1.patch [ failed ] There is more. No idea about the cause. But did not really look into. Just noticed by chance.

[ warn ] * [l][c] wifi-4003-fix-sha256_state-clashes.patch [ failed ] [ warn ] * [l][c] wifi-4004-fix-cfg80211-for-5.8.patch [ failed ] FYI

Yeah I was thinking about to add these codenames...but I think I remove it again to to confuse newbies...

Usually ntpd/chrony should take care for that. You could try to restart the equivalent daemon and check the logs if the times is correct again. No need for an open port. A working internet connection is sufficient.

Common issues and peer to peer support have been merged since they mostly cover the same Bugtracker forums for A64 & H5 has been merged with H6 since they share the same board family

done.

For headless application OrangePi boards could be good as well. You could decentralice stuff if possible and invest in a couple of OrangePi One Plus featuring Allwiner H6 Quadcore and 1GB memory. NO eMMC though. OrangePi3 is available with 2GB and eMMC, but also useless stuff like BT and WiFi. Same SoC. OrangePi4 is available with RK3399 and has 4GB if memory. But in general from what I read RK3399 is still suffering from issues across all kernels so it is kind a gamble.... take note about @balbes150 comment below What about an Odroid N2+? AFAIR most powerful supported SBC atm.

Sometimes the syntax of DTS changes (by upstream). That is why adjustments might be necessary. Next is also drivers in the kernel change and therefore adjustments to the device tree might be necessary as well to fit the intersection with the kernel.

The mentioned file is not a part of shipped Armbian images but a part of the build system and should point you in the direction how to accomplish something similar. It is not a oob solution .