Using the KDE image on eMMC storage, this is how far the boot process get. The results or from the serial port. [217]HELLO! BOOT0 is starting! [220]BOOT0 commit : 595900dccf [224]periph0 has been enabled [227]set pll end [229]PL gpio voltage : 3.3V [233][pmu]: bus read error [236]PMU: AXP2202 [241]PMU: AXP1530 [245]power mode:33, sys_vol:920 [249]vaild para:1 select dram para0 [253]dram_para[0]:0x4b0 [255]dram_para[1]:0x8 [258]dram_para[2]:0x7070707 [261]dram_para[3]:0xd0d0d0d [264]dram_para[4]:0xe0e [266]dram_para[5]:0x84848484 [269]dram_para[6]:0x310a [272]dram_para[7]:0x8000000 [275]dram_para[8]:0x0 [277]dram_para[9]:0x34 [280]dram_para[10]:0x1b [282]dram_para[11]:0x33 [285]dram_para[12]:0x3 [287]dram_para[13]:0x0 [290]dram_para[14]:0x0 [292]dram_para[15]:0x4 [295]dram_para[16]:0x72 [297]dram_para[17]:0x0 [300]dram_para[18]:0x8 [302]dram_para[19]:0x0 [305]dram_para[20]:0x0 [307]dram_para[21]:0x26 [310]dram_para[22]:0x80808080 [313]dram_para[23]:0x6060606 [316]dram_para[24]:0x0 [318]dram_para[25]:0x74000000 [322]dram_para[26]:0x38000000 [325]dram_para[27]:0x802f3333 [328]dram_para[28]:0xc7c5c4c2 [331]dram_para[29]:0x3533302f [335]dram_para[30]:0xc60 [337]dram_para[31]:0x48484848 [340]board init ok [363]enable_jtag [365]card no is 0 [367]sdcard 0 line count 4 [370][mmc]: mmc driver ver 2023-03-24 16:23 [380][mmc]: Wrong media type 0x0 [383][mmc]: ***Try SD card 0*** [405][mmc]: HSSDR52/SDR25 4 bit [408][mmc]: 50000000 Hz [411][mmc]: 30436 MB [413][mmc]: ***SD/MMC 0 init OK!!!*** [425]boot param - magic error [428]DRAM BOOT DRIVE INFO: V0.67 [432]DRAM_VCC set to 1160 mv [559]DRAM retraining ten [577][AUTO DEBUG]32bit,2 ranks training success! [606]Soft Training Version: T2.0 [7410][SOFT TRAINING] CLK=1200M Stable memtest pass [7415]DRAM CLK =1200 MHZ [7418]DRAM Type =8 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [7428]DRAM SIZE =4096 MBytes, para1 = 310a, para2 = 10001000, tpr13 = 6461 [7459]DRAM simple test OK. [7462]dram size =4096 [7469]nsi init 2023-2-23 [7605]Loading boot-pkg Succeed(index=0). [7609]Entry_name = u-boot [7619]Entry_name = monitor [7623]Entry_name = scp [7626]Entry_name = dtb [7631]mmc not para [7632]Jump to second Boot. NOTICE: BL31: v2.5(debug):20a8ac62a NOTICE: BL31: Built : 17:17:28, Jan 22 2024 NOTICE: BL31: No DTB found. nsi init ok 2022-11-08 ERROR: Error initializing runtime service opteed_fast

@AurealNixThank you, excellent work... boot from eMMC All that's missing is adding support for NVMe

@AurealNix download the KDE v0.2 again and I was able to write it to SD card . No issues. I am impressed, KDE loads just fine. Took a bit to load the first time. Wifi works just fine, loaded Chromium and launched Youtube. Playback is good, at the moment full screen drops frames. Audio through HDMI just worked, no issue. I also loaded the KDE image on eMMC, it did not boot. I will check what is going on use serial and report back if I see anything.

Of course. Kernel upgrade is handled via standard apt get update and upgrade. If you need to change to specific kernel, use https://docs.armbian.com/User-Guide_Armbian-Config/System/#alternative-kernels Make sure to update all packages before going that route, IIRC this problem is related to u-boot. Which is updated after all packages are up2date with armbian-install utility,

If you are using the friendlyelec image, can you really say "mpv is vanilla from Debian"? I am really asking, because I haven't used friendlyelec in a long time, and I don't remember if they have their own DEB repository. Can you identify the ffmpeg version and compilation options? Same with mpv. Run $ ffmpeg with no options, and it will print out the version and the libraries that were activated. $ apt list ffmpeg $ apt list mpv $ mpv --version $ cat /etc/issue $ uname -a I do remember that friendlyelec has some extra video abilities, because they maintain their own patches with bleeding edge code, while the official ffmpeg and mpv maintainers are still checking whether to accept the pull requests. Is it even possible to run "armbianmonitor -u" in friendlyelec? Do you see "v4l2-request" or "va-api" (or "vaapi") anywhere in the mpv log? is your gnome desktop running under X11 or Wayland? (last time I used friendlyelec with Kodi, the graphic server was gbm, and there was no desktop, only Kodi). If you run $ mpv --vo=gpu -v my.mp4 , mpv will print a more verbose log, with more details of how its running.