i recently purchased an orange pi 5 plus 16gb with the wifi / bt card, the aluminum wifi case, fan and 1tb ssd. when i go to the official website i see different images there none of which seem to work 100%. i mean i was able to get each up and running but what i noticed is that the graphical drivers would not load. i saw a youtube video claiming armbian has the right driver support for the mali 610 gpu. can someone assist me getting this to work? im big into emulation gaming and right now it doesnt even have Vulkan support i crave. someone help thanks

@Nick A You previously taught how to build an image for Transpeed 8k618-t. If I want to replace the default version kernel with a newer kernel. Could I tell you if there's a way to create one?

Boot with serial attached and see if the DRAM is being properly detected. If not this patch would appear to solve the issue. https://lore.kernel.org/linux-sunxi/2813637.mvXUDI8C0e@jernej-laptop/T/#t

You should pipe the output from a serial console cable to another computer where you store it. Make sure kernel cmdline loglevel=7 AFAIR the OPI5+ can only use 5V as input supply power. Your 100W PSU might be a standard spec one so it does only deliver 3A at 5V. This might be a perfect 5.000V, but an extra cable in between will drop that a bit and the risk is then that short higher power drap will either make the 5V goo too low and/or the PSU will cut the power because more than 3A drawn during a short peak. You will need to look at powering first. Usually 5V only SBC's can be powered via other input then the USB-C input. You need to read the instruction for your OPI5+, and also OPi5, those might be different. OPI5+ and also OPi5 should transcode at more or less the same speed, large amount of memory does not really matter as it is just HW processing blocks doing the work in a rather limited memory space. You should do a manual CLI jellyfin-ffmpeg based transcode, see /var/log/jellyfin how commandline arguments for that specific video look like (and simplify it, output to 1 file instead of chunks m3u8). And or search this forum, I at least have posted examples for check/test earlier. You might also try to reproduce it with a publiclicy know video, look for big buck bunny test vids or so.

Nanopi neo air stucks on "Starting kernel..." after some random power losses (2-50) during loading I think it's because of corruption of armbianEnv.txt. Normal UART logs: UART Logs with stucking on "Starting kernel" U-Boot SPL 2024.01_armbian-202ns16550_serial serial@1c28000: p024.01-S866c-P7738-Hadc5-Vefe9-B2eb2-R448a (Feb 06 2026 - 03:49:45 +0000) Allwinner Technology 0) Model: FriendlyARM NanoPi NEent from FAT... Unable to use mmc 1:1... ial Err: serial Net: No ethernet found. starting USB... No working controllers found 1(part 0) is current device Scacr 5475 bytes read in 2 ms (2.6 MiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD MMC: no card present * ** Failed to load '/boot/armbianEnv.txt' Load fdt: /boot/dtb/sun8i-h3-nan13293004 bytes read in 419 ms (30.3 MiB/s) 10014752 bytes read in 317 ms (30.1 MiB/s) ion 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 13292940 Bytes = 12.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree bloing Ramdisk to 49352000, end 49fOK Loading Device Tree to 49 Starting kernel ... U-Boot SPL 2024.01_armbian-2024.01-S866c-P7738-Hadc5-Vefe9-B2eDRAM: 512 MiB Trying to boot frns16550_serial serial@1c28000: p CPU: Allwinner H3 (SUN8I 168Core: 64 devices, 16 uclasses, mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... In: serial,usbkbd Out: serial Err: serial Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Sca/s) ## Executing script at 4310dary SD MMC: no card present ** Bad device specification mmc 0Failed to load '/boot/armbianEnv.txt' Load fdt: /boot/dtb/sun8i-h3-nanopi-neo-air.dtb 13293004 bytes read in 433 ms (29.3 MiB/s) it Ramdisk from Legacy Image at 43400000 ... Image Name: uux RAMDisk Image (gzip compressed) Data Size: 13292940 Bytes = 12.7 MiB Load Address: 00000000 Entry Point: 0000b at 43000000 Booting using the fdt blob at 0x43000000 Working Ramdisk to 49352000, end 49fff58c ... 2e0000, end 49351fff ... OK Worns16550_serial serial@1c28000: p19 U-Boot 2024.01_armbian-22eb2-R448a (Feb 06 2026 - 03:49:45 +0000) Allwinner Technology O Air DRAM: 512 MiB ent from FAT... switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr /s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD MMC: no card present ** Bad device specification mmc 0 ** Failed to load '/boot/armbianEnv.txt' 13293004 bytes read in 447 ms (2ing Ramdisk to 49352000, end 49f ing USB... No working controlleAutoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Sca0000 * Bad device specification mmc 0 ** Failed to load '/boot/armbianEnv.txt' Load fdt: /boot/dtb/sun8i-h3-nanopi-neo-air.dtb 13293004 bytes read in 433 ms (29.3 MiB/s) OK ## Flattened Device Tree blob at 43000000 Booting using ing FDT set to 43000000 Loading Ramdisk to 49352000, end 49fff58c ... OK Loading Device Tree to 492e0000, end 49351fff ... OK Working FDT set to 492e0000 Starting kernel ... I builded armbian image with compile.sh BOARD=nanopiair BRANCH=legacy RELEASE=bookworm BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no CLEAN_LEVEL="make,debs,cache" OVERLAYS="analog-codec i2c0 i2c1 i2c2 usbhost2 usbhost3" COMPRESS_OUTPUTIMAGE=sha,gz WIREGUARD=yes NAMESERVER=8.8.8.8 DOCKER_ARMBIAN_BASE_IMAGE="ubuntu:jammy" for Nanopi Neo Air. Image is flashed to eMMC. Is any way to solve it?