Werner

@tepo  The Banana PI M2 Zero is not supported by Armbian maintainers.  It is "Community Support" status, which means that it is available for the public at large to support.  There is currently no one in the community that has stepped up to say they will be a maintainer for that board.  So the board is languishing for lack of support by anyone interested enough to contribute.
Armbian is first and foremost a platform for building images for the many different Arm based boards that are out there.  But with limited resources (both people and money) only a handful of boards get officially supported by the project.  The majority end up supported (or not supported) by the community of volunteers interested in the particular boards.

@Patrick Domack can you provide uart logs if you have usb ttl converter?

Maybe if you provided more than a one sentence description on what your problem is and what you have tried, you would get a better answer.  u-boot logs are really useful in debugging booting issues for example.

There is not. Install code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } iptables or code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } nftables or a framework like code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ufw via apt that makes use of either one of those.

On your sd/eMMC/NVMe/whatever maybe but not on your ramlog device
 
As suggested long time ago check what is filling your logs and fix. 50M of compressed(!) text is a LOT.
You can increase its size but this will also reduce the overall free memory for other applications. check in /etc/default/ here.
Or disable ramlog which will write logs directly to your disk. However when using an sdcard this will significantly short its lifetime.
 
As for me I run pihole for years and never had an issue with filling up logs.

Debian does not support PPAs. Try Ubuntu variant.

Vendor making false claims/advertisements about speed, memory...

@roykWell done! I've just uploaded a new version of ffmpeg to my ppa.

Funny. Reading the datasheet of the S905L2 SoC it seem it supports only 4GB of memory. So once again a scam box.

Interview with @rpardini.
 

Tried using ppa version instead of snap?

Aside from all the unheard user wishes we decided to create a new dedicated room for specific tasks with defined clear goals.
Topic creation is limited to collaborators.

@vitor  Have you paid for support?  Armbian is composed of volunteers who donate their time.  If no volunteer desires to work on any particular board/feature/bug, no one is getting paid to be told to add such board/feature/bug.  This is open source so anyone can go in and make changes/fixes/improvements and then hopefully submit them back for others to benefit from.  First and foremost Armbian provides a place (forums, frameworks, source code) for anyone to join the volunteer community and help support the wide variety of boards that are out there.

@madade  Why do you ask for help again when you haven't provided the information that Igor asked of you.
He asked you for four things:
You only provided an answer to one request.
 
Which hardware revision (picture please)?
Where does booting end? (capture of the console output of the boot)
Try another sd card.  (Just because a card works in some circumstances, doesn't mean it will work for this purpose, sbc's are finicky when it comes to sd cards at times)

added:
console=both now I have a shell!
 
Thanks!

With working PCI
https://github.com/armbian/os/releases (look for Rock5 "midstream")
 

Take note  that there is no guarantee that community-hacked Armbian versions will work on that hardware properly. TVboxes are like cancer on the SBC market. You can read more on that here: https://docs.armbian.com/User-Guide_FAQ/#i-have-a-tv-boxtablet-from-insert-random-vendor-can-i-use-armbian-on-it
 
 

I'm pretty sure this is a bug and I have logged it as such: https://github.com/armbian/build/issues/4905

https://www.armbian.com/newsflash/armbian-23-02/
 
 
Changelog: https://docs.armbian.com/Release_Changelog/

https://www.armbian.com/newsflash/armbian-23-02/
 
 
Changelog: https://docs.armbian.com/Release_Changelog/

https://www.armbian.com/newsflash/armbian-23-02/
 
 
Changelog: https://docs.armbian.com/Release_Changelog/

@rpardini
Next/main. Creating patches.
 
When I create a patch with armbian/build master (deprecated) using  CREATE_PATCHES=yes, I get a patch in the output/patch folder in mbox format.
When I create a patch with armbian/build main using  CREATE_PATCHES=yes ARTIFACT_IGNORE_CACHE=yes, I only get a diff file in the output/patch folder.

Is this intentional, a bug, or have I perhaps not set something up?  Can I get a mbox patch?

Just a typo 😅

Thank you for the excellent tutorial!
 
Just a little simplification:  Instead of using the script in step 9.9, I put
command="/usr/bin/cryptroot-unlock"
at the start of the line in /etc/dropbear-initramfs/authorized_keys, to force that command when SSHing in using that key.