Werner

Known issue. Either stick with the older release for now or go for edge based: https://github.com/armbian/community

Because generic kernels only work on boards with UEFI or any other standardized interface which most cheap SBCs don't provide. Check https://docs.armbian.com/User-Guide_FAQ/#why-i-cannot-simply-shove-a-random-image-into-my-board-to-work-like-on-my-pc Kernel packages provided by Armbian are individual for each and every board. This is why ours work and generic not. Reason stated above. armbian-config only shows kernels from us since in 99.9% of cases generic kernel won't work. Reason stated above. Get some expensive hardware with proper UEFI support and all generic stuff will work. RPi has just a few boards and thousands of developers and big companies with sponsoring behind that can make something like this possible. Armbian has hundreds of boards but only a few developers and non of that additional stuff. We simply cannot afford to provide packages for each and every corner case and have to limit ourselves to a system that works in most common cases. There are plans to implement the option to install multiple kernels and to choose which one to boot. No ETA on that though. Sure it would. But compared to x86 ARM is still behind in terms of global development power. But it is catching up

Confirmed. Got a chance to test an 23.02 image which ships 5.10.110 kernel? Grab from here: https://armbian.hosthatch.com/archive/orangepi5/archive/

Interesting. Gonna look into that. Edit: From what I can see you are allowed to like up to 10 posts per day. Edit2: Ah you were just promoted from validating to member a few minutes ago. Therefor the limit mentioned above now counts.

Making it possible even for fairly new users to build an image entirely from source sis one of the big advantages of Armbian

Building from sources is always a bit ahead of pre-compiled packages. We do not push each minor kernel version to user since it always comes with the risk that something breaks. In a nutshell what we have to do is to bring the firmware packages, which are installed on the 23.05 images, to the apt repo in a way the system detects it as new version and upgrades accordingly. Sure we did this in the past many years, but this is the first time we do it with the next generation build framework

Bullseye images have been replaced in favor of upcoming Bookworm. All links here working perfectly: https://www.armbian.com/orangepi-r1plus-lts/ You can build your own image with Bullseye userspace if you want: https://docs.armbian.com/Developer-Guide_Build-Preparation/

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Feel free to do that. Your contribution is appreciated. I suggest to start here:

Instructions are similar to this: https://www.instructables.com/Setup-Orange-Pi-Using-Serial-Port/ Use baudrate 1500000 instead of 115200.

Known issue. Allwinner 32bit seems to be in bad shape unfortunately. Research is needed

Cannot say an ETA since we face multiple issues atm. Like for example for Allwinner 32bit boards which might become unbootable on upgrade which isn't ideal.

Yes. Hook up a serial console and set verbosity to 7 in /boot/armbianEnv.txt

Fix your setup. Armbian does not write-protect this file. Anyway you can probably stop debugging on your side: https://armbian.atlassian.net/browse/AR-1764

No idea. I don't use windows for such things. Too much annoyance.

Have you tried like vhdtool? https://superuser.com/questions/452720/how-do-i-convert-an-img-file-to-vhd

Depends. If you are impatient yes, you have to download new img and use this. If you can wait a bit until our apt repositories are up to date then a common apt upgrade will do.

A backup is the correct option

Edit /boot/armbianEnv.txt and bump verbosity to 7 Also you can dig archives for older images and try those.

Topic is obsolete anyways. Closing

This is expected since apt repo is still behind. Try increasing the verbosity to 7 in /boot/armbianEnv.txt to get more output on boot. Maybe this gives some clues.

moved to userspace

apt repo is still behind. please be patient. We are working on it.

repository is still behind. please be patient. We're working on it.

split from origin topic since hw is different