Forgot to mention, it will boot the SD card image from a USB adapter.

I recently bought a used OrangePi 5, when it arrived it had a working Ubuntu image on an SD card. I decided to format the card and put my own image of Armbian on the card using the Armbian imager. when installed the card would no longer boot. lights on board but black screen no HDMI output. I tried several different SD cards and different images all with the same result (A1 Sandisk cards) Eventually I tried a hail mary and put an Armbian image on a really old USB thumb stick and it immediately booted and worked just fine. I tried putting the OrangePi os on one of my SD cards for kicks and it gets HDMI output but is just stuck on the OrangePi splash screen When I insert the SD card while running on the USB thumb drive image I can view the partitions and see that the OS image is correctly installed on the SD. I can't figure out where I'm going wrong, am I having a bootloader compatability issue with armbian?

aliexpress.com/item/1005011593571835.html Teclast P50Ai which should be almost identical T60 AI now lurks at a price of 68 euro shipped in EU for some time. aliexpress.com/item/1005011827691576.html Telcast T60Ai comes at around 120 euro shipped in EU. I note that these may be last units of a production batch. As far as I can see, https://github.com/jonas5/orangepi-4pro-armbian may be the hope for newer kernel with GPU acceleration.

Hi @sven-ola thank you so much for the detailed and thoughtful response — and for taking the time to actually try it yourself! The DKMS approach makes perfect sense; it's clean, survives kernel updates automatically, and fits right in with what's already working on the board for bcmdhd. I'll follow your instructions for b2c2-flexcop-usb. Really appreciate the effort you put into this! 🙏

While I am here: I have a Mediatek Tri-Band Wifi card installed in my RV2 (label reads MT7922A22M). There's a matching driver in OpenWrt created by Felix and friends. This will take some time until pushed upstream. So, why not make it a DKMS module? That's how things started 🤪 # Grab bleeding edge Wifi from OpenWrt cd /usr/src git clone https://github.com/openwrt/mt76.git mt76-6.18 cd mt76-6.18 # Source code massage (needs OpenWrt kernel patch, missing include) git revert 9a46d8d2 sed '/^#include <linux\/kernel.h>/i#include <linux/version.h>' mt76.h # New DKMS config (with more than one module) cat > dkms.conf << "EOF" PACKAGE_NAME="mt76" PACKAGE_VERSION="6.18" BUILT_MODULE_NAME[0]="mt76" DEST_MODULE_LOCATION[0]="/updates/dkms" BUILT_MODULE_NAME[1]="mt76-connac-lib" DEST_MODULE_LOCATION[1]="/updates/dkms" BUILT_MODULE_NAME[2]="mt792x-lib" DEST_MODULE_LOCATION[2]="/updates/dkms" BUILT_MODULE_NAME[3]="mt7921e" BUILT_MODULE_LOCATION[3]="mt7921" DEST_MODULE_LOCATION[3]="/updates/dkms" BUILT_MODULE_NAME[4]="mt7921-common" BUILT_MODULE_LOCATION[4]="mt7921" DEST_MODULE_LOCATION[4]="/updates/dkms" AUTOINSTALL="yes" MAKE="make -C ${kernel_source_dir} M=${dkms_tree}/${PACKAGE_NAME}/${PACKAGE_VERSION}/build CONFIG_WLAN_VENDOR_MEDIATEK=y CONFIG_MT76_CORE=m CONFIG_MT76_LEDS=y CONFIG_MT76_CONNAC_LIB=m CONFIG_MT792x_LIB=m CONFIG_MT7921_COMMON=m CONFIG_MT7921E=m " EOF # Add, build, install, and add matching firmware dkms add -m mt76 -v 6.18 dkms build -m mt76 -v 6.18 dkms install -m mt76 -v 6.18 cp -av firmware/ /lib/firmware/updates/mediatek # Give it a try reboot