Werner

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

https://docs.armbian.com/User-Guide_Networking/#minimal-images-networkd So any instructions you can find here should work:https://www.google.com/search?q=systemd-networkd

is debug uart console an option?

Just FYI if that has an impact for you: MINIMAL images only differ in the amount of pre-installed userspace packages. Kernel/firmware-wise all images, regardless if CLI, desktop or minimal share the very same kernel package. No minimalism there.

https://docs.armbian.com/User-Guide_FAQ/#why-is-there-no-image-for-board-with-bookwormjammynobletrixie-and-minimalclignomekdexfce-with-vendorlegacycurrentedge-kernel Build your own if you need it: https://docs.armbian.com/Developer-Guide_Build-Preparation/

legacy is considered deprecated. Try vendor (6.1.y) kernel.

That would be impossible to create since all boards have different demands to make them work. Here are a few examples on how to add a new board or whole family: https://docs.armbian.com/Developer-Guide_Adding-Board-Family/

Me neither

omv extension isn't automatically shipped with the build framework. You can grab it here: https://github.com/armbian/os/blob/main/userpatches/extensions/omv.sh

This board is community maintained, not by the Armbian team. Therefore only untested automated builds are provided. https://docs.armbian.com/Board_Maintainers_Procedures_and_Guidelines/ This is intended for a minimal image. https://docs.armbian.com/User-Guide_FAQ/#i-cannot-find-armbian-config-on-my-device armbian-config did not receive much attention since it is undergoing a major rewrite. However at the bottom line it doesn't do much more than calling an official way of installing. https://forum.armbian.com/topic/40598-status-of-armbian-configng/ Most they can do if you ignore this advice is to refuse support if something goes wrong. topic moved

Hm. I'd retry with 6.1.y vendor kernel since 5.10.y is to be considered deprecated.

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

Why? Both USBimager and BalenaEtcher handle compressed images on their own. Tried booting from sdcard? Not sure if USB boot is supported.

What about writing it to an USB stick and then use armbian-install to copy to nvme?

moved

I'd start at ethernet@fe010000

Home Using Armbian Advanced users - Development

Not sure if I understand correctly. The images available for download are made with the very same build framework you find on Github: https://github.com/armbian/build

moved

Most likely same answer as the other thread since in terms what emby needs both the rk3588s and rk3588 SoC are identical.

If you need them to build like dkms kernel modules then yes, the headers MUST match the installed kernel version. armbian-config should be able to do that for you as well. Ah yes. Newer ones are in beta/nightly repository only. You may get 6.10 or 6.11-rc edge images and packages from repo after Armbian August release.

Probably. https://www.google.com/search?q=emby+orange+pi+5

Use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-config to freeze firmware. This will set the packages in question to hold. You can. But if you should is up to you. Mainline support is maturing pretty nicely and I expect to have a decent set of working features in 6.11 which may (or may not) become next LTS kernel. 6.10 is a pretty good preview. If you are fine with having something older but most hw features working use rockchip bsp, 6.1.43 to say. This should work with armbian-config as well. Go to Hardware and then Other.

https://docs.armbian.com/User-Guide_Networking/

edit /boot/armbianEnv.txt and set verbosity to 7 to get more info after Starting kernel.