Igor

You already have the answer to this question
This is open source, you can report the problem and hope someone volunteers their time to research and fix (which is realistically unlikely to happen any time soon), you can dig in and fix it yourself and become part of the solution by contributing back to the open source communities, or you can pay for/hire someone to fix it for you.  Those are realistically the only way things get fixed in open source.
 
Complaining about something and calling into question the volunteer work others do to provide you something for free, isn't going to motivate anyone to help you.

FYI. Bullseye does not add or remove anything related to hardware on Armbian Linux. If you build Bullseye / Jammy / Focal / whatever image today with our build tools https://github.com/armbian/build your WiFi will also work. 

@Contributor/Maintainer 

- added missing Rockpi 4C plus
- enabled Mekotronic boards https://www.armbian.com/download/?device_support=Supported&tx_maker=mekotronics
- added Orangepi 5 Plus
 
In case there is another missing or broken images, please report, here or to Jira directly https://armbian.atlassian.net/browse/AR-1765 

@Contributor/Maintainer 

- added missing Rockpi 4C plus
- enabled Mekotronic boards https://www.armbian.com/download/?device_support=Supported&tx_maker=mekotronics
- added Orangepi 5 Plus
 
In case there is another missing or broken images, please report, here or to Jira directly https://armbian.atlassian.net/browse/AR-1765 

We support VIM3L, just download page was disabled by mistake. Enabled now https://www.armbian.com/khadas-vim3l/

Duo2 was tested with 23.5.2 image that was uploaded yesterday.

./compile.sh kernel SHARE_LOG=yes  ARTIFACT_IGNORE_CACHE='yes' BOARD=odroidxu4 BRANCH=current  
 
This   https://www.google.com/search?q=one+bite+at+the+time

Having used YOCTO for a couple of years at work I assumed that creating my own Armbian image was going to be difficult. However to my suprise I was able to create a Bullseye image for the Orange Pi R1+ LTS in less than 1 hour. And, .... it actually runs correctly on the target board. That is pretty good.

If you didn't download image from www.debian.org or www.ubuntu.com, then there those OSes does not support this HW. RebornOS is a desktop tweaking on top of one of those "Debian" / "Ubuntu" stock images. Just to straighten things ... and yes, this is common, nothing extraordinary.
 

Armbian maintainers are already totally overloaded, your support is almost not existing, vendor does not support us ... there is little we can do. We don't have endless time or equipment to support random purchases people made. But as our build framework is well maintained, making an image is pretty straightforward. Anyone can do it https://docs.armbian.com/Developer-Guide_Adding-Board-Family/ but maintaining and dealing with problems, that lies in this cheap products, is another story.

Yes but you are smart Igor.   I'm actually writing a book on building a home media server. Not for smart people. i wrote one of the first website automation books for Wiley back in 1996, and gave away on the CD what was probably the first remote authoring software for the masses, long before wordpress.  When I figure out a repeatable path to do cool stuff easy I like to share it, and I think the pis are an absolute revolution.  Figured I'd keep the instructions on an os as easy as possible and consistent. I'll try this again in a month or so and see if it's fixed. No biggie. Linux Mint is pretty light and you set up a user and pw so you don't have to go searching for the login.
 
Thanks for answering Igor. 

Try with:
 
sudo touch /root/.not_logged_in_yet  
+ reboot.

https://forum.armbian.com/topic/27323-http-error-404-for-sha-hashes-banana-pi-m1/#comment-165132
 
 

SSH & serial login is enabled by default. I don't think allowing blank password would be a good idea under such circumstance. Yes, its users call, but we have to prevent at least most stupid actions. One can always override this later in case he knows what he is doing. We even used to have password complexity check error, which was perhaps too hard and a while back was downgraded to a warning.

IMO there are enough of safety compromises. 
 
 
Making it work on Ubuntu packages base represented months of work in exchange for virtually nothing. Rare people is able to understand that and most people are just used to consume without compensation, complaining and asking for more. If you / people would understand what they are asking for ...  it would already be a great step forward. No, this is not easy to make. Especially because everyone expects from developers to pay for everything. Join, do your part. But not with requests and demands. Project would hire several developers to make it better for you ...
 

As it is impossible to satisfy everyone in this aspect, we don't even try. Armbian provides clean base images with minimum set of applications. Additional applications can be installed classical APT way, via armbian-config or you start making your own images - build framework https://github.com/armbian/build is a masterpiece. You can do your own Armbian based image and adding your own applications in no time.

Rock Pi-4B - Armbian_23.05.1_Rockpi-4b_jammy_current_6.1.30_gnome_desktop.img
installed to emmc: logs 
wlan, hdmi, nvme working
 
Rock-5B - Armbian_23.05.1_Rock-5b_jammy_legacy_5.10.160_gnome_desktop.img
Took me a while to boot from SD, was using an older 23.05-trunk version.
Even 'sudo dd if=zero.img of=/dev/mtdblock0' with radxa zero.img would continue to boot happily from nvme instead of sd, changed armbianEnv.txt to sd root, updated bootloaderon mtd -> worked.
besides mtd being a mystical thing for me, almost anything worked:
installed to mtd+nvme: logs
using btrfs on nvme + mtd did not work (don't know if supported, but installer lets you pick it).
performance with panfrost ppa's enabled is absolutely stunning. 

Btw, this time for testing I used my 45W PD PSU (+ PD C<->C Cable 60W) instead of fixed 5V@4A w/o errors and activated the max 12V PD option in armbian-config just for fun.
Sensors report ed
in0: 12.00 V (min = +12.00 V, max = +12.00 V) curr1: 1.50 A (max = +1.50 A) and had no reboots or whatsoever.

Rock Pi 4A and 4C boot to working gigabit ethernet with bookworm-current minimal image, USB ports all work. HDMI output not tested yet.
 
Rock 3A also boots to working gigabit ethernet with jammy-edge minimal image. USB ports all work. HDMI output not tested yet here either.
 
Rock64 also boots to working gigabit ethernet with bookworm-current minimal image. USB ports all work. HDMI output not tested.

Nanopi Neo Plus 2 (H5)
linux-u-boot-nanopineoplus2-current_23.05.0-trunk--2022.07-Se092-P6b27-Ha9af-Vaada-B4b55_arm64.deb
linux-image-current-sunxi64_23.05.0-trunk--6.1.26-Sca1c-D4008-P8596-C1438Hfe66-HK01ba-Vc222-Ba98e_arm64.deb
OK, but distorted audio output over USB, I believe this came up since kernel 5.16+ and is still present in 6.x
 
Banana Pi Pro (A20)
linux-u-boot-bananapipro-current_23.05.0-trunk--2022.07-Se092-P6b27-H0429-Vaada-B4b55_armhf.deb
linux-image-current-sunxi_23.05.0-trunk--6.1.26-Sca1c-D4008-P8596-C596bHfe66-HK01ba-V014b-Ba98e_armhf.deb
OK
 
Odroid C2
linux-u-boot-odroidc2-current_23.05.0-trunk--2022.01-Sd637-P6c67-H7ff5-V603e-B4b55_arm64.deb
linux-image-current-meson64_23.05.0-trunk--6.1.27-Sca48-D4008-Pc5ba-C072bHfe66-HK01ba-Ve377-Ba98e_arm64.deb
OK
 
Armbian_23.05.0-trunk_Odroidc2_bullseye_current_6.1.29_minimal.img
full image test: OK
 
new build system is a very good improvement 👍
 

Le Potato
   -boot, hdmi audio, USB, NIC
Tritium H2/3 and H5
    - Boot, NIC, USB
 

- Orange Pi PC
- Pine64
Images boot (xfce_desktop), network connection functions (iperf3). USB ports function, HDMI video and audio work.

Just to let you know I am the author of the reddit thread. And yes noticing the superior WiFi support did not take long, I have collected approximately 20 different WiFi chipsets/adapters trying to find adapters supported on later images of Pwnagotchi. Resulting in nothing but total failure. Around half of those adapters work in Armbian (with monitor mode) without any interaction from myself.
 
I do indeed have a working image that a few people are testing and reporting good results with. It's taken a long time to get it to this state, so a couple more weeks of testing shouldn't be too much hold up.
 
I am also in contact with DrSchottky who is one of the maintainers of Nexmon. Who is of the opinion that Nexmon should and will work as well as it does on the Raspberry Pi (in fact better as we have an external antenna). Once I get around to spending some more time on the project. He has had it installed and working on the M2 Zero.
 
The last piece of the puzzle will be getting the screens working over the GPIO, but that will likely require someone with better knowledge of such things than myself, as the drop in replacement RPi.GPIO library didn't seem to work.

With a lot of help from going I finally could fix the problem.
The problem is that the GPIO-lines needed for spi are not defined neither in the basic device.tree nor in the spidev-overlay.
to get spidev0 working download  the device-tree source below and compile it with dtc.
Copy the resulting file "sun8i-r40-spi-spidev0.dtb" to "/boot/dtb/overlay/sun8i-r40-spi-spidev0.dtbo"
Ensure that in /boot/armbianEnv.txt "overlay_prefix=sun8i-r40" is set and the line overlay=.... contains spi-spidev0
reboot
 
sun8i-r40-spi-spidev0.dts

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

BTW. I have NanoPi M4V2 which by default comes with the fan. It works with Armbian out of the box, low rpm on idle, full on full load, when temp go up. So the problem is configuration.

In case anyone has a similar problem, the plugin depends on the wireguard meta package and on a 6.x kernel and headers (at least the >5.5 kernels I tried were unstable except the 6.1.11).
 
So unfreeze in armbian-config and select the 6.1.11 kernel, apt install linux-headers-edge-rockchip64 to install the headers then manually install the wireguard meta package then OMV from there.
 
Thanks for your time Igor.

Unknown. Plus I managed to fry the board. It was sent to repair, got repaired, it is coming back ... but sadly anyway don't have time to do anything. 
 

When they boots, images would be at the download pages with at least WIP / community support status.
 

This might be helpful.
https://github.com/Kwiboo/arm-trusted-firmware

Download:

https://www.armbian.com/nanopi-r6s/
(unofficial WIP support)

Thanks to @Efe Çetin
 
 
Lets keep it in WIP section for awhile until we don't do more testings. I found out armbian-install doesn't work well so this needs to be fixes, perhaps something else ...

Download:

https://www.armbian.com/nanopi-r6s/
(unofficial WIP support)