Werner

There is?

I'll try to give an example of what I have planned to change. These are the current terms of use: I thought about something like this: Notes: It does not make sense to note that violating various topics of these TOS lead into punishment since it is to be expected that any violation of those lead into punishment. Therefore these "inline notes" have been removed and summarized at the bottom. abusive behaviour has been summarized. The less text the TOS provide the higher the chance that they will be read at all. Or did anybody ever read the 100 pages of Google TOS?

I can only fix this 2019 thingy in the terms of use. If it is on the main page maybe @lanefu can fix this real quick. I already know the story between Thomas and you but I did not dig deeper and plan to keep it that way and simply stay neutral. Was way before my time anyways

Or meanwhile better 20.04 (Focal) You may run into some unsatisfying QEMU messages when building particular images with Bionic. Still supported though but might break someday. At the latest when it becomes EOL in three years

Checkout the build script at github. Since everything is compiled from source I guess it is easier to simply read that instead of trying to reverse engineer something that is open anyways

Yep, something like this. Another reason to get rid of one of those Understand. But it seems to me it is kind a mixed at the moment because there was not much such "movement".

If thinking about...why? See people that are moderating forums or will moderate in future are most likely no kids. They use common sense when doing their stuff. So it should suffice to MAYBE tell them these rules on time and it should be fine. Not sure if this is even necessary. Theoretically Armbian is based within the European Union and therefore the EU copyright laws are active which don't see the need of such a hint. There is copyright protection in general. Those hints are needed by US law AFAIK.

You could try to set a fixed mac in your /boot/armbianEnv.txt like ethaddr=02:38:a0:82:2d:c0

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.