Werner

https://fi.mirror.armbian.de/apt/pool/main/

You can always try to fetch the armbian/build repository selecting an older tag but chances are high that compiling will not work since those tags obviously cannot revert changes from upstream or other dependencies Armbian relies on. Fixing if necessary is up to you. I think 5.10 is legacy at the moment for sunxi. Older kernels are no longer available in master branch. I don't know about sunxi_usb_udc. Is that one of those vendor developed and never maintained or even upstreamed hardware-specific drivers?

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

https://github.com/armbian/community Support status is unknown. May work, may not.

Balbes maintains his own fork of the Armbian Build Framework but pushes his changes frequently into Armbian. So for now only his pre-built images are available until next push.

Nobody prevents you from using any available kernel in any available userspace by simply building the combination of your choice via our build framework. However there is no guarantee that this will work/boot or even compile properly. https://docs.armbian.com/User-Guide_FAQ/ And it is our choice which prebuilt images we provide for convenience since building and providing those takes lots of computing and storage ressources

So you download the wrong image and wonder why it does not work? M4 (non V2 does not have a maintainer attached (feel free to volunteer) and therefore no images are directly provided for download. You can try those from archive: https://fi.mirror.armbian.de/archive/nanopim4/archive/

Yes but no idea how well they work https://www.armbian.com/orangepi3-lts/

We do not provide support for 3rd party images.

Increase verbosity to 7 in your /boot/armbianEnv.txt. Otherwise nobody knows what's going on inside.

moving to unsupported

Maybe @NicoD or @seclorumgets a chance to both confirm the issue and check if the commit fixes it.

https://github.com/armbian/build/pull/4296

Apologies for the short downtime about an hour ago. Both forums and main website have been relocated to new hardware. You may notice a significant performance improvement, especially in forums. Enjoy

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

Tried stable userspace like Bullseye or Jammy? I would not rely on any errors from an experimental/unstable userspace.

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

Might (Shot in the dark since nobody of you provided any debug logs) have been fixed: https://github.com/armbian/build/pull/4376 Try building/running an image with this fix.

Thanks for reporting

moved

For reference: https://github.com/armbian/build/pull/4369#event-7698677956

If you mean by installation moving the OS to onboard memory (eMMC) then first write image to and SD card (check docs if necessary) and then use armbian-install (or nand-sata-install on older images) to move OS to eMMC.

You are using VERY old firmware. Try using armbian-config to switch to a newer kernel and then retry upgrading the firmware package.

Might be an undocumented switch then. However its usage is not recommended since the kernel patchset follows upstream so sooner or later applying the patchset will fail on older branches.

There is no such switch. https://docs.armbian.com/Developer-Guide_Build-Options/