lgranie

After a fix committed this past week, these builds now work on all the amlogic based boxes I have:
TX3mini (s905w)
X96mini (s905w)
H96MaxX2 (s905x2)
TX3 (s905x3)

Armbian now has a community supported build target for amlogic TV Boxes (aml-s9xx-box).  You can now build your own builds directly with the Armbian build system.
 
This is now an opportunity for members of the community to move the support for amlogic TV boxes forward within the Armbian framework.  If you are not familiar with the Armbian build system check out the Armbian developer documentation.  If you have idea on how you would like to see things evolve/change please use this forum to share your thoughts and ideas and submit PRs for any code changes you would like to see.
 
I am currently testing this code against the four different amlogic based boxes I own, but would appreciate others testing as well.  Once I have completed my testing, I will be updating the FAQ amlogic install instructions with this information.

The fix for this would be on the armbian side (for the linux-image-current-meson64 package).  It is a one line fix in the postinst script.  I plat to submit a PR for this fix when I get a chance.

Now you can download the latest versions of images and DEB packages from the official Armbian resource via the link. 
 
https://users.armbian.com/balbes150/

I plan to send the new version to network repositories after switching to version 20.08. Without this, the kernel package will have the same name as the existing package and the update does not work correctly.

For my NanoPC-T4, I want to be able to install multiple kernel versions at the same time and boot a specific one by default. In addition, I would like to be able to select which kernel to start if necessary:
Armbian_20.07_Arm-64_focal_dev Boot Options. 1: linux-default 2: 5.8.0-rc4-arm-64 3: 5.8.0-rc3-arm-64 4: 5.8.0-rc2-arm-64 5: 5.8.0-rc1-arm-64 6: linux-test To present my solution, I have used "Armbian_20.07_Arm-64_focal_dev_5.8.0-rc4.img.xz" and "u-boot-rk3399-nanopc-t4.img 07/10/2020 8:50am" on a microSD:
With this scheme in place I am able to pull in a new kernel without the need to port over my local image configuration to a new image. If the new kernel is not working as expected all previous available ones are just a reboot away. If the new kernel version is suitable for boot on demand just a new boot stanza in extlinux.conf is nessesary.
The mainline uboot for NanoPC-T4 has not yet enabled USB keyboard support. Therefor the on demand selection of a boot option will only work via the serial console keyboard.
The build of uboot with the same options in nanopc-t4-rk3399_defconfig as it was done for Pinebook Pro and rockpro64, should probably enable it in a similar way. This means that only HDMI display and USB keyboard are required.

The clean build of the Focal-server on NanoPC T4 with NVMe took 22 minutes.

The new version 20.05.5 (20200522).
All images are build entirely on the ARM platform (rk3399 + NVMe). After fixing bugs, the process of building the first image (including downloading sources, building all packages, building the kernel, u-boot, and so on) took less than 50 minutes. 

I've done this (upgrading just kernel) previously and you need all the other /boot files from the 'new' (5.6-rc7 ) image. I've not worked out which files are key but you need u-boot*, emmc*, *autoscript_* etc.
AFAIK, kernel and initrd should be named /boot/zImage & /boot/uInitrd still.
Best to make sure the 'new' (5.6-rc7 ) fresh image boots from a fresh sdcard first and then work from that, which you've probably done.

The version of the image 20200323.
Resolved then issue of pulseadio conflict with the G12 audio device . Now you don 't need to delete PULSEAUDIO. To enable audio on g12, you only need to run the script (g12_sound.sh) or for GX\GXM models, run the script (gx_sound.sh).

Edit /etc/systemd/journald.conf
 
I set mine to:
 
SystemMaxUse=32M
SystemKeepFree=8M
SystemMaxFileSize=2M
 
Probably not optimal values, but gives you a starting point to tweak from.