rvalle

1. Script build all changed packages every 4 hours or manually in-between:
https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-all.yml
2. If this is successful repository rebuild follows (rolling and stable)
https://github.com/armbian/os/actions/workflows/repository-update.yml
3. Once finished, packages are pushed to rolling release repository http://beta.armbian.com (which is stable enough for this hardware and most of end users). As kernel covers many devices, pushing to default stable repo https://apt.armbian.com happens manually after observing this https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results
 
None of other distributions or distributions provided by vendors have this kind of quality control. Sadly, not even this is enough, but better we can't afford.

@Igor this recent fix seems like it: https://lore.kernel.org/all/E1sbJvd-001rGD-E3@rmk-PC.armlinux.org.uk/#r
 
apparently the driver was decoding the duplex mode incorrectly.

Traditionally I use LVM in our Storage in our servers, and we started doing it on the ARM64 servers too.
 
I am using this with Raspberry PIs and now with Armbian too.
 
I also use cloud-init for server customization, just like ubuntu does with the RPI image now. This is very good, as you can create users, add keys, install packages, set networking... extend partitions, all in an standard way.
 
So, the requirements for my Armbian image are, an extra vfat partition for cloud-init metadata, and the ROOT to be created with LVM instead of just ext4.
 
I managed to implement most with user extensions, except the Dockerfile that required extra packages and configurations, and also I had to patch the partitioning part of the script, in a similar way the CRYPT extension does, as the root filesystem will come from mapper and not from the root device, this is not possible to do from an extension.
 
I have it working for the HC4 in the master branch. I want to port it to the M1 and possibly XU4.
 

Ok some images are up for testing.
Both HKs' 4.19 and tobetter's 5.18-rcX were updated. Maybe something is fixed. Tobetter commits signal support for PCIe.
For those who are brave:
 
https://github.com/rpardini/armbian-release/releases/download/20220508d/Armbian_20220508d-rpardini_Odroidm1_jammy_legacy_4.19.219.img.zst (probably no HDMI)
https://github.com/rpardini/armbian-release/releases/download/20220508d/Armbian_20220508d-rpardini_Odroidm1_jammy_edge_5.18.0.img.zst (probably no PCIe/SATA/USB3)
EDIT: old images removed. Look for later posts for newer ones
 
unzstd them, burn to SD, insert SD, power on. 
recommend to use UART
 
Have fun @Neo2SHYAlien @Stan Pak @N4IRS @Slartibartfast9536 @Igor