Werner

v25.11.2 for Orange Pi 5 Plus running Armbian Linux 6.1.115-vendor-rk35xx on mine. Just saying. You should use a spoiler for the slop. tl;dr: vendor kernel has exactly nothing in common with mainline besides the fact that it is supposed to run in the same hw.

Actually no. While 6.12.y may be an LTS kernel, support for rk3588 was barely there so very few boards actually work with this. I suggest to download/build an image with either "vendor" kernel 6.1.115 or "edge" with >=6.18.y. This should work better.

According to the datasheet (https://de.scribd.com/document/948890791/MT7988A-Datasheet) the supported baudrate seems to be between 300baud and 3Mbaud. However cannot tell anything about support status. Neither do I have this hw, nor did I ever dig into this soc. Starting with device tree overlays might be a good start or check the whole device tree in general for the uart nodes if present.

There is no such board. There is either Orangepi5 plus or Orangepi5b. Check your hw what you actually have. If there is indeed a "Orangepi5b plus" then it must be fairly new and is totally unsupported.

logs? versions??

ha extension is not a part of the framework. Copy from here https://github.com/armbian/os/tree/main/userpatches/extensions

I suggest to get a better heatsink and/or thermal paste/glue. Next I would at the device tree if there are thermal points defined. Perhaps they are missing. You can use the dtc tool to decompile the device tree from /boot. Output values might be in hex instead of decimal, so just in case you wonder.

Applying kernel provided DT overlay rockchip-rk3588-orangepi-5-pro-disable-leds.dtbo Meaning the overlay was applied successful. If it does not work, perhaps this means some pin definitions or whatever differ from opi sources vs ours.

Related to Again, you are using the wrong image. You cannot assume an image for the opi5+ works for the opi5b. Those are different boards.

wrong image. you cannot simply use an image for board X and assume it works on board Y

moved to staging

Attach debug serial console so you can follow u-boot logs and get an idea what the overlay is not applied.

None of these images will most likely work. https://docs.armbian.com/User-Guide_FAQ/#why-no-universal-image

This is quite old. Isn't there anything more recent? Perhaps this was fixed at some point already.

booting from sd should work even with proper mtd in place. Get usb uart adapter and provide boot logs.

Feel free to reach out and become a partner: https://www.armbian.com/partners/ @Bruno Santos

Armbian default login and password is always root and 1234. If this does not work, the image is not genuine.

I don't know, perhaps the author knows. Try. If it doesn't work, then fe's wiki is misleading.

You can try the following: After writing to nvme and spi do NOT reboot but mount the nvme drive to a random directory and check in /boot/armbianEnv.txt if the UUID matches the one from the nvme. If not, correct it (check blkid).

Neither of these is good advice. dd does not verify written data and balena etcher has known issues, hence it is not recommended either. Either use Armbian Imager (https://docs.armbian.com/User-Guide_Getting-Started/) or USBimager (https://gitlab.com/bztsrc/usbimager). Both are known to work.

moved

Hi, welcome. Syncing forums and tags with supported boards is (still) a manual job and from time to time I either cannot keep up or miss things. Like in this case. I'll fix this later and then move appropriately. Until then feel free to state your question in "Beginners" using the "other" tag. Cheers

moved to tvboxes

BalenaEtcher has known issues and therefore not recommended. Use Armbian Imager or USBimager. Also verify that the downloaded image is good by utilizing the checksum. https://docs.armbian.com/User-Guide_Getting-Started/#download-and-verification https://github.com/armbian/imager https://bztsrc.gitlab.io/usbimager/

Which device? which armbian version? nobody here has a second sight. from the screenshot you aren't even using armbian or at least nothing official.