Werner

does your monitor have an 'auto adjust' ?I had a similar issue where the monitor was underscanning or overscanning or something and 'auto adjust' (from the monitors menu) brought the whole screen into the viewport of the monitor.

Yes I should have thought of that ... but you'd be surprised at what comes in to my student labs!!
 
 

Try to blacklist panfrost module.

I thought I had edited that out ... total 'oops' moment ...

Have you tried to use xrandr for the purpose?

2h00 PM GMT make it 10h00AM EDT for me, will be drinking my second coffee cup ...

May have been removed while merging upstream config. I'll take a look.
 
Aight there are two options for you:
- Replace the legacy with the current kernel which contains this module or
- Use the build script to create your own legacy kernel package which then will be up-to-date as well

Major Updates
 
1. The install.sh script now installs the debian backports version of smartmontools which doesn't depend on Python 2 and is a much newer version. This also sped up the install process a bit.
2. Added single disk support OS/Data
3. Updated the update system, dashboard now shows the latest version, when you choose updates it ill now show the changes between the installed version and the current.
4. We added Rescan disks button to add volume in setup as well as add volume in the main web ui app.
5. The system no longer reboots after setup it now directs you directly to the login screen.
 

I advise sticking with the legacy kernel until the stability issues with the current kernels (specific to the NanoPi M4 V2) have been resolved.

Because it is not permanent.
You could use rc.local for example to turn off the leds once the boot has been finished.

Newest video.
Gaming on Armbian Focal on the RK3399 with Panfrost.
How to set it up
Thanks to all.

When you are editing, you will see below the editor window a section with a paper-clip icon and the text "Drag files here to attach, or choose files..."

Nice job!

Nice job!

Both kernels builds without overlay support. Remaining problems:
https://github.com/armbian/build/tree/AR-329/patch/kernel/sunxi-dev/check

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