Werner

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.

Don't drink and drive write, son.

https://docs.armbian.com/#what-is-the-difference-between-armbian-and-debianubuntu

Maybe. But I don't know how. The easiest is probably sticking with the customization script. Install the tools, build your thing, and then do some cleanup (apt purge, apt clean, apt autoremove ....).

What prevents you to use apt inside the customization script to install the necessary tools?

https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-image-customization-script

I'd try with linux-image-vendor-rk35xx and linux-dtb-vendor-rk35xx and leave cli bsp package for now as it is. That being said it would be more useful to get an idea about WHAT is actually failing an attempting to fix before messing with the kernels. Hook up a serial console and set verbosity to 7. https://debug.armbian.de

You seem to be the first person reporting such an issue and none of us has a second sight. Therefore without logs there is pretty much nothing we can do.

https://docs.armbian.com/User-Guide_FAQ/#can-i-upgrade-my-userspace-flavor-like-bullseye-to-bookworm-or-jammy-to-noble

Moved

Don't use bleeding edge if you expect stability. Use vendor until mainline is more matured.