Werner

how about to "not touch" the network configuration?
Some dont like to have the system changed by an "additional" app like SimpNAS.
 
Pihole also doesnt change the network configuration.
 
armbian is normally using networkmanager and Iam personally like the old fashioned way of the /etc/network/interfaces because I dont like to run a service for every little OS puzzle part. Inlikeca short process-list in htop/top
 
some of my non-armbian ARM systems use pnly under 32MB for bootup.
 
So maybe add a option "let network as it is" and DONT TOUCH the ssh access, because thats for the most the way to access their device (no TTL-RS232)
 
Why ist SSH disabled? Doesnt systemd networkd work together with OpenSSH-server?

There is a little more to adjust, but I ran out of time ... until later. In case someone finds it amusing to proceed https://github.com/armbian/build/pull/2056/files

That cannot be answered by a simple yes or no. It depends.
Let's take the 5.4 example.
If you follow the current branch it leads us to megi's orangepi-5.4 branch. If you check the Makefile (https://github.com/megous/linux/blob/orange-pi-5.4/Makefile)
you will notice that the actual version of this branch is 5.4.18. But when you compile the kernel it is actually 5.4.47 or something like that.
This means these patches come from Armbian. If you check the patch directory for your board family (https://github.com/armbian/build/tree/master/patch/kernel/sunxi-current)
you can see that the upstream patches are added here. If you need a very specific kernel version remove or rename the patches you do not need.
 
That was a quite easy example to get what you want.
On other sources, vanilla for example, it is a bit tougher. You would need to specify a commit at which point you want to use the sources.
Sometimes a board is fixed to a specific commit or kernel version because it is known that newer version of the same kernel branch are known to be broken and (as most of the times) nobody has time or resources to deal with it.

In personal experience - it's generally doable... and it's really the makefiles for externals like device drivers that are the devils to be solved.
 
In any event - cross-builds produce the same performance as native - ARM on X86, MIPS on ARM, ARM on ARM...
 
For most folks - LEDE/OpenWRT has solved that particular problem...

Please contact the administration to move this topic to the TV box section. I would like to (as far as possible) continue this direction (native Armbian build directly on ARM devices). For skeptics. Recently, I completely moved the LivreELEC build to the ARM platform (i.e. the entire process of creating LE images and Addons now takes place on ARM rk3399\s922x devices). My dream is (perhaps) to try to transfer the ArmbianTV build completely to the ARM platform and get rid of the x86 dependency.

** Network Manager CLI **
 
use NMCLI
$ nmcli device status DEVICE  TYPE      STATE         CONNECTION          enp1s0  ethernet  connected     Wired connection 1  wlp2s0  wifi      disconnected  --                  lo      loopback  unmanaged     --    
to check radio
$ nmcli radio WIFI-HW  WIFI     WWAN-HW  WWAN     enabled  enabled  enabled  enabled 
Let's see what's out there... scan for AP's
$ nmcli dev wifi list SSID                  MODE   CHAN  RATE       SIGNAL  BARS  SECURITY  MYSSID         Infra  11    54 Mbit/s  100     ▂▄▆█  WPA2      MYSSID         Infra  132   54 Mbit/s  100     ▂▄▆█  WPA2      SOMEOTHERSSID  Infra  52    54 Mbit/s  49      ▂▄__  WPA2      MYSSID         Infra  149   54 Mbit/s  45      ▂▄__  WPA2      MYSSID         Infra  11    54 Mbit/s  42      ▂▄__  WPA2      SOMEOTHERSSID  Infra  1     54 Mbit/s  27      ▂___  WPA2  
Now, let's connect to WiFi (note, one must be root or sudo access)

Connecting to an open AP
$ nmcli device wifi connect <SSID|BSSID> For a password protected AP, see below
$ nmcli device wifi connect <SSID|BSSID> password <password>  
Cool, eh?
 
To set up a device as an AP - this assumes that WLAN0 is the wireless interface...
$ nmcli dev wifi hotspot ifname wlan0 <SSID> password "<password>"  
Cool, eh?

To bring this thread up to date - somewhere along the line the DTs dropped the correct trip list and cooling maps...I checked in fixes for this for the H3, H5, and H6 about a month ago (see https://armbian.atlassian.net/browse/AR-244 and https://armbian.atlassian.net/browse/AR-285).  All seems to work well now 

The sources need some adjustments to compile with 5.7.x most likely. Just be patient and hope that the creator makes these changes since  he knows his work the best.

https://armbian.atlassian.net/projects/AR/issues/AR-314?filter=allissues
 

Confirmed working on Orange Pi 3 based on Allwinner H6, kernel 5.4.7 with pcie-wrapped. No particular changes needed apart from new dts.
Link here: https://github.com/ingamedeo/orangepi3-h6-mainline

Thought you might want to know :-)
 

I think I've found the problem :
 
Those "of_chosen" symbol dependencies came in the @megi commit https://github.com/megous/linux/commit/4ea85aef763727ab40791ae3c0c8dd1bb87ef577
But the "of_chosen" symbol export is not provided in driver/of/base.c like suggested by a guy 4 years ago :
https://lore.kernel.org/patchwork/patch/710174/
 
I'm now compiling new 5.7.y build and will let you know if it is succeeded ...

Suppose we need to dig in to kernel config , thus " KERNEL_CONFIGURE=YES "
and see what is going on there ... maybe later when I had some sleep ...

If you could provide this as patches for Armbian to include into the building process it would be appreciated

Hi,
 
shame on me!
 
Your'e completly right, this image works with another SDCARD.
The broken one was out of the box and looked good, nothing seemed to be wrong.
 
I apologize very much for any inconvenience and would like to thank you for the quick help.
 
Best wishes
Paul
 
 

How?

We now do have a documentation about all the IRC related stuff and its features. Check it out: https://docs.armbian.com/Community_IRC/

Images has been fixed (v20.05.4 ->). Try now.

Not sure which country you are but on amazon you can find the following good replacement : https://www.amazon.com/dp/B07NCG1P8X
You might have to look for the same product ref. on the correct market place according to your country.
 
 
While for sure our bandwidth is more focus on Helios64, we are still supporting Helios4, and no plan to change that ;-)
For instance latest Armbian 20.05 Kagu still actively includes Helios4. Ok we will still need to put a post on our blog about that and link the image in our wiki :/
 
 
 

1. I don't owe anything.
2. if you Want to get detailed documentation and dedicated resources for posting materials for download, pay 5000 to donate Armbian.
3. I have a very negative attitude to those who use someone else's development for free (in which a lot of work\money\time of different people is invested), absolutely do not help this project in any way and at the same time make claims.

Mainline kernel is of fairly decent quality in regard to most popular RK3399 boards. All critical components work fine and have really good support. But something, which makes such boards outstanding, still doesn't work in 5.*  It is normal for the situation when vendor's developers are locked inside of their private sandboxes (they call it SDK, LTS branch whatever, we call it simpler - "legacy") and do not really see the world is bigger outside  . However, I have good news for those who own RK3399 based SBCs with Fairchild FUSB302 controller responsible for type-c handling and power delivery protocol. This chip is widely popular, so there are some other users of its driver in the kernel and driver itself is very well elaborated (IMHO again). But it still misses many things that we, Rockchip+FUSB302 owners, really need. There is absolutely no need to write new drivers or wait when developers from Rockchip will do it (they won't). The driver deserves some extension and we will get both DisplayPort and properly working Type-C port (not statically fixed to USB3 host in the dtb, as many present maintainers do for their boards, but real DRD with role switching based on cable detection). I was working on this subject for two (or even three of last weeks, don't remember exactly anymore  ) and managed to fill this gap and get working DP on this "silently abandoned" port. Dual Role support for Type-C was in progress, but it can be solved too indeed. Right now, I have neither technical possibility nor motivation nor even time to continue anymore. The best what I can do is to recover what I've lost and handover my patches to some other volunteers who can/want to continue development (but even this needs a lot of time). My plan A was to deliver those features to my lovely Armbian community, and then try pushing it upstream.

A RaspberryPi and any board that is supported by Armbian cannot be compared really.
At RaspberryPi a lot of people working with just a few boards while at Armbian just a few people working literally on hundreds of boards which not even share the same sources. You see while at their place they have plenty of time to tweak every aspect Armbian simply cannot do that due to lack of ressources.

You dont have a Raspberry Pi 4 with armbian These are Rockchip64 SBCs  
because there is no armbian for the Raspberry Pi