Werner

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.

Existing installations can simply be apt update/upgraded since both Ubuntu and Debian released fixed versions for their supported userspaces. Armbians rootfs packages, which are used for building new images, have been recreated and pre-built images available for download are being rebuilt/replaced as well. tl;dr: mitigation is in the works/already done

Not possible without tinkering since at least the boot loader must be present either via sd or on board SPI flash. However no idea how to access this onboard 2M storage w/o the option to boot the board via sd beforehand. Not sure if it is worth exploring in this direct. Faster and probably cheaper too is to buy a new board.

Sometimes newer kernel packages are not pushed automatically via apt for various reason. This usually isn't an issue. Having .36 instead of .32 most likely does not give you significant advantages. There is however always the option to build a kernel package by yourself and then install via dpkg. https://github.com/armbian/build

There is no UEFI or Secureboot available on this board. However you may want to try this: https://github.com/edk2-porting/edk2-rk3588 and then https://github.com/tianocore/tianocore.github.io/wiki/How-to-Enable-Security

@NicoD do you still have your m4v2 and may verify uart connection and working debug console? thx in advance

Hm as for me I only have standard jumper wires for debugging my stuff. last but not least because it does not connect 5 volts which isn't necessary anyways for serial interaction and reduces the risk of frying a board by connecting this wrongly.

Well the other variant of course is that it might be connected wrongly . Tried to flip RX and TX lines? common mistake having these mixed up. If it boots from sdcard there MUST be ouput to the debug serial.

This output isn't related to uboot. So I assume you don't get any output whatsoever which means broken/missing boot loader. I'd try to boot from fresh sdcard and then start investigating.

Have you simply tried either + or +2E images if they work?