Igor

Event -> Video (with transcripts and comments)
 
1. Merging NEXT (updated slides)

We discussed progress made in past week (Jira Epic) and set limited expectations for following week due to holidays season. We will try to enable rootfs caching CI at first (which has to be compatible with master) and Docker image creation next (which probably isn't?) 

2. Unifying boot process
 
Most single board computers needs good overlay handling so moving them to complete generic image is likely / in short term not possible. We still can not count on DTBless or DT from u-boot only, well support from vendor SPI. If we want to move like everything to UEFI and keep things operation / loose no feature, its a lot of work. Sorting out u-boots and going extlinux way with support for multiple kernels (NEXT/CURRENT) might be the best mid-way. 

3. When 6.2 and 6.1, current / edge

Keeping and stabilising 6.1 at EDGE for few months, waiting that it will be tagged as LTS for sure. Keeping new things like 3588 / 3568 at their own kernel branches, CURRENT = 6.1, EDGE = 6.2 (at once)
 
@rpardini @JetHomeDid I forget to mention something important?

Event -> Video (with transcripts and comments)
 
1. Merging NEXT (updated slides)

We discussed progress made in past week (Jira Epic) and set limited expectations for following week due to holidays season. We will try to enable rootfs caching CI at first (which has to be compatible with master) and Docker image creation next (which probably isn't?) 

2. Unifying boot process
 
Most single board computers needs good overlay handling so moving them to complete generic image is likely / in short term not possible. We still can not count on DTBless or DT from u-boot only, well support from vendor SPI. If we want to move like everything to UEFI and keep things operation / loose no feature, its a lot of work. Sorting out u-boots and going extlinux way with support for multiple kernels (NEXT/CURRENT) might be the best mid-way. 

3. When 6.2 and 6.1, current / edge

Keeping and stabilising 6.1 at EDGE for few months, waiting that it will be tagged as LTS for sure. Keeping new things like 3588 / 3568 at their own kernel branches, CURRENT = 6.1, EDGE = 6.2 (at once)
 
@rpardini @JetHomeDid I forget to mention something important?

I have runned armbian-config utility, removed headers, installed header kernel, and then runned "sudo apt -t bullseye-backports install zfs-dkms zfsutils-linux". All has worked fine, so I have tried to install plugin "openmediavault-zfs 6.0.12" and finally have installed it.

Add this
extraargs=net.ifnames=0 to /boot/armbianEnv.txt

https://www.armbian.com/rock-5b/

Hi,
 
This is my first try to add a board to armbian build system.
I got a BPI M2S since several months, but only had time recently to investigate on this promising SBC.
I made a PR here, if somebody wants to try it: https://github.com/armbian/build/pull/4597
The main improvements are to be done for the dts file, since I'm not an expert about such file definition. Only 1 ethernet of the Gbit ports is working, since I copy the config from vim3 that share the same hardware for it.
I didn't try to customize u-boot and I use the one for radxa zero2 that works to launch armbian on the board.
armbianmonitor -u is here: https://paste.armbian.com/piyuqajeye
 

Current only working software for this HW is very old stuff anyway 
 
 
Vendors objectives are different than ours. They want to sell hardware and they want to have control over software. By doing on their own, they control it and they don't help their competitors. It this aspect it makes sense. 

But yes, I totally agree. 
 
 
Research has been done on the topic, we know many pros and cons and I think we do agree to some point.
https://forum.armbian.com/topic/20847-the-boot-process-and-various-devices/
A good topic to discuss it next week - how to proceed from current stage? @ManoftheSea Too early?
 
 
If preparation and transition is not done well, we also have a lottery. It is nice that you experiment with all this, I know others also did some. We found some issues and we need to make some decisions ... 

Got an answer from SinoVoip - "Our DC port size is 4.0X1.7".
Will leave it here - just in case, if someone is looking for BPI-M2 Pro power plug specs.

This should do:
https://armbian.atlassian.net/browse/AR-1412

thanks, the answer was adding the armbianEnv.txt
extraargs=apparmor=0

Thank you. I have sent you email.

Made a release build & images are uploading and syncing. This will take at least a day ... we continue to test. Repository update can wait a bit. 

This seems to fix it.

PR https://github.com/armbian/build/pull/4480

Those are developers preview builds, where you can check what works and at some point it will be good enough for some uses cases. In a couple of years, it will be functional on the level of kernel 5.10.y. 
 
Download is possible from CI pipeline: https://github.com/armbian/build/releases
 

 
Boot log:
 
This board is looking for maintainer(s) and (this) forum moderator (contact @Werner).

Providing the serial console logs of the boot process helps with error analysis and greatly increases the likelihood that the issue can be fixed.

I spent a day on this. Made some progress and some regression  I had a working nand-sata-install, could transfer to internal eMMC and boot from it but with latest images its not working anymore ... after going closer to @Cornelius patch.
 
u-boot button detection to switch booting from SD card is very unstable. It often hangs, so its some work to be done here ... Test image and a build PR: https://github.com/armbian/build/pull/4247 

This is our test device:
 

Full logs: https://paste.armbian.com/qeqisakege (sudo armbianmonitor -u)
 
How do you power this board?

Thank you! Many people here are speaking this 1,2,3,4,5 language  Most helpful to Armbian is help on maintaining our core build system and second hardware that we are stuffed with ... I have sent you an welcome to the email associated with this account.
 
 

Checked in the last few days, with both USB2 ports and a PS/2 -> USB adapter. The board did boot fine with the thing attached with kernels 5.15, 5.19 and 6.0

Does fresh image from download section works for you?

For anyone looking to have the official cooler+fan autostart at boot, place the following rule in /etc/udev/rules.d/99-pwm-fan.rules:
ACTION=="add", SUBSYSTEM=="pwm", ATTR{npwm}=="1", ATTR{export}="0", ATTR{pwm0/duty_cycle}="6000", ATTR{pwm0/period}="12000", ATTR{pwm0/polarity}="normal", ATTR{pwm0/enable}="1"  

This is the real solution. Annoying passwords are only enforced at installation. Change it straight afterwards and forget the annoying one.

Have a read of https://docs.armbian.com/User-Guide_Basic-Troubleshooting/
Basic issues why a board will not start is a PSU that does not supply enough voltage and current to the board and also a SD card that's not suitable for use with such a SOC board.

What's the maximum rated current and voltage that the PSU can supply to the Rock 3A?
What make/manufacturer and speed class is the SD card?  Is it a standard SD card or an A1 rated card?
 

Link fixed. We only have images here https://github.com/armbian/build/releases for now. When we get more feedback, we'll placed them to expected location and CDN.