Igor

Fixed.

Of course.

Search Odroid forums for similar problems. Then search Raspbery Pi forums for similar problems ... then ask storage experts on some storage oriented forums if they recommend USB connected drives and why not. USB protocol / drives were not designed for 24/7 usage and Armbian can't fix what is fundamentally broken.

Disabling UASP might help.

Get another SD card - only boot loader is loaded in since it can't read from SD card it tries network boot ...

With a previous release cycle we have added support for Raspberry Pi4. Currently we are producing daily images only (rolling release):
https://www.armbian.com/rpi4b/
 
When someone steps as a maintainer, it can become officially supported:
https://docs.armbian.com/User-Guide_Board-Support-Rules/
 
We only support Ubuntu based builds for now and kernel source is attached to official RaspberryPi sources. Which is better then mainline.

https://github.com/armbian/build/commit/e868c5ddfb611cc15cfe0168db4d83666e4537d9

armbian-config -> system -> hardware and enable audio

VGA is not supported - if you manage to get it up, you are welcome to submit a working/tested patch. We haven't find time to deal with this for past half year and for another half this tasks will remain untouched.

___ _ _ _ _ _ ____ _ _ / _ \ __| |_ __ ___ (_) __| | | | | |/ ___| || | | | | |/ _` | '__/ _ \| |/ _` | | |_| | | | || |_ | |_| | (_| | | | (_) | | (_| | | _ | |___|__ _| \___/ \__,_|_| \___/|_|\__,_| |_| |_|\____| |_| Welcome to Armbian 22.02.1 Jammy with bleeding edge Linux 5.15.30-meson64 No end-user support: unsupported (jammy) userspace! System load: 102% Up time: 1:42 Memory usage: 69% of 3.70G Zram usage: 8% of 1.85G IP: 10.0.10.7 CPU temp: 66°C Usage of /: 3% of 58G ZFS pool: Online  
I am running Armbian Jammy with ZFS 2.1.2
 
 
odroidhc4:~:% zpool status pool: tank state: ONLINE config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 ata-WDC_WD80EFAX-68KNBN0_VDJKU00K ONLINE 0 0 0 cache ata-SAMSUNG_MZ7PD256HAFV-000H7_S16PNYAD800646 ONLINE 0 0 0 errors: No known data errors
Just to add that this is achieved in straightforward manner:
1. Download CLI image from download pages
2. Install headers via armbian-config
3. Installing packages: zfs-dkms zfsutils-linux
 
Done. Then dealing with ZFS.

Fixed https://armbian.atlassian.net/browse/AR-1107

dpkg -i linux-dtb-current-sunxi_22.02.0-trunk_armhf.deb dpkg -i linux-image-current-sunxi_22.02.0-trunk_armhf.deb
This is mandatory, the rest optional.

Ah. For this you need to update ca-certificates package before rolling full apt update and apt upgrade.

Why would you want to downgrade to the generic Ubuntu kernel? (where its highly possible you will not even boot)
 

Agree. You are already at best possible variant ... which could ofc be polished.
 
 
Do you know why Armbian builds kernels almost for all platforms? Because in ARM diverse world it is not possible to trust to Ubuntu, Debian, or kernel.org.
 
According to your questions I would assume you are not very familiar with the situation in ARM hardware world and it would be good to check FAQ:
https://docs.armbian.com/#what-is-armbian
"Armbian fancy some kernel development and a lot of its maintaining. Debian relies on upstream sources for ARM hardware which can be years behind and/or lack of many functions". For Ubuntu this is just a little bit better then Debian.
 
Armbian kernels are (ARM HW) HWE by default, all of them: https://github.com/armbian/build/tree/master/patch/kernel/archive
 
Armbian is hardware enabler for the device you plan to use. Not Ubuntu, which actually don't support those devices. https://docs.armbian.com/User-Guide_FAQ/
 
Also, when you will run into troubles ... We are already unable to assist Armbian (kernel) users, so other (Ubuntu kernel) users comes last. In reality - never.

Yes, better some tools then no tools, but probably we should just move to packaged version or to more recent version ...

@g00d 
 
https://github.com/armbian/build/blob/master/lib/compilation.sh#L708
If you like to help - provide merge request with TAG from git which is ok. If none, contact authors, open issue to them. We are in the process to scale the project down because we can't pay for everything users find in open source software. I used to lost up to 10 hours daily just for communicating with users request. Now I just ignore since that can only lead to insanity. To get a picture how this "armbian maintainers - do something" looks like.
 
That is the best what can be done. 
 
 
FOSS is released without any warranty because we can't pay for service users would wish to have. Fixing bugs in SW made by 10.000+ people. We can't cover even much less No interest, most users doesn't even understand the value ... fast forward. https://www.armbian.com/newsflash/armbian-needs-your-help/ There is some interest but still we are far far away, not enough to boost support on levels users would imagine to have (without paying developers for the time they will lost). Someone that will fix troubles that might be hard, not fun and by much higher pressure they are used in their well paid professional environment. In real-time and on their personal expense.

This project is backed by amateurs, by you and me and other people that like to play with those devices. There is not formal support as such (it goes under as is, best effor support) -  Armbian is not Red Hat https://en.wikipedia.org/wiki/Red_Hat with 10.000+ full time engineers looking to the code, made by them and others.
 

Yes. It is clearly written on the download pages https://www.armbian.com/rockpi-s/ (Modern kernel serial console is on UART2) I have personally lost a week trying to fix this "small" problem and I will not repeat this ever again. Armbian is dropping official support for this hardware, images and upgrade will be no more ... Not your fault - we also made mistake trusting this vendor. You (anyone) can pick up and proceed with support to keep it at least on this level as now.

Bug is actually outside Armbian domain - we are 1000 x too small to be able to fix bugs in community maintained packages -
https://www.google.com/search?q=lightdm-gtk-greeter+bug - fixed in desktop build scenario, forgotten to fix in armbian-config.
 
We have replaced buggy greeter with slick-greeter which is why desktop still works just fine.

yes.

In fact it is. Starting with v197 systemd:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-understanding_the_predictable_network_interface_device_names
 

Modern kernel luxury comes with a price:
https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one
 

If you want Armbian with the same functionality, but also no updates to the kernel, pick Armbian with a kernel 4.4.y which is still provided for this hardware.
 
Perhaps fan support works and just need enabling?

IIRC there were some issues on Debian user land and 3d acceleration and I assume they still exists (Buster is too old for fancy stuff). Its known that it works on Focal  / Hirsute. Since we just started on adding 3D support, this is certainly not present on images that are currently available. Its coming with a next release 21.08 / this month. We only have packages for Ubuntu based builds - they came from here. We have no plans to support 3d on Debian desktops since this represent extra work and maintenance burden.
 
As i notice https://github.com/armbian/build/blob/master/config/targets.conf#L522-L530 we didn't enable on 32bit probably because we need someone to test if it works. Build from sources is needed at this point. And remember to enable 3D since its not enabled by default.

This is the problem and the solution:
 
 

Our system only publish packages for supported distributions. Xenial is EOL from our maintaining perspective. We have to cut what is not important, but eats resources.

There is nothing wrong on our side - we just don't build and publish our package upgrades for Stretch repository anymore. (automatically) Only for those marked as supported: https://github.com/armbian/build/tree/master/config/distributions Support from Debian ended 01 Jan 2020 and I assume kernel upgrades, which are anyway coming from us, are at Stretch going to die June 2022 (this info is extracted from quick search on the net, so its not official)

Another option is to boot images from archive.

This problem should be resolved. CDN needs several hours ... so perhaps not right now.