Werner

https://www.armbian.com/orange-pi-lite/ Scroll to the bottom and grab rolling release image

moved to tvboxes

Have you tried to create a single partition on the nvme beforehand?

Yes. https://www.armbian.com/newsflash/armbian-leaflet-8/

Can you hook up a serial console to see where it fails?

https://www.armbian.com/newsflash/armbian-leaflet-8/

Known issue. Regression seem to have introduced by the kernel bump from 5.10.110 to 5.10.160. Needs research.

split

Can you adjust partition setup of your ssd so it has one partition only and retry?

Did you write boot loader to mtd?

We hope so. Allwinner32 in general had boot issues. https://armbian.atlassian.net/browse/AR-1765?focusedCommentId=11868

moved

Hm I never had to set any of that stuff, it just worked. Could you try like code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } sudo screen /dev/ttyUSB0 1500000 ? code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; }

On Windows PuTTY Or KiTTY working nicely, on Linux I simply use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } screen

Allwinner32 is known to have issue. http://armbian.hosthatch.com/archive/orangepizero/archive/

The adapter you bought supports this rather high baud rate, right? Also double-check your connection and make sure ground (GND) is connected as well.

apt repo is still behind. working on it. Might be available via nightly

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.