I got emby installed and working. Made it launch with the ir remote, it was all perfect until I tried to play a video I've set it to use mpv but it seems the emby package has it's own version of mpv and ffmpeg baked in as the versions reported in the mpv.log are different and it fails to use drm, it seems the following errors are the problem. [ 0.028][v][libmpv_render/drmprime] drmprime hwdec requires at least one dmabuf interop backend. [ 0.028][v][libmpv_render] Loading failed. [ 1.422][v][ffmpeg] Unable to open any dma_heap device [ 1.422][e][ffmpeg/video] hevc: Failed to set destination format: S265 1920x1080 [ 1.422][e][ffmpeg/video] hevc: Failed setup for format drm_prime: hwaccel initialisation returned error. When I launch the same file directly in mpv, it plays fine and doesn't have the errors above. The system has mpv version 0.35.1 but emby reports using 0.38.0-dirty. Same with ffmpeg and all the associated lib files, they are all higher versions and I can't find duplicates in the system so I believe they are packaged as part of the emby app so I really doubt it's something I will be able to fix unfortunately. Tried Kodi and that's missing all the acceleration settings. Jellyfin client doesn't work with an emby server anymore. Just to attempt to keep this on topic, I don't suppose there is anything I can config with the image that might resolve the dma_heap errors?

You can't use emby and the h618 acceleration with ffmpeg-v4l2request... you need to make emby work under Debian, and tell emby to use mpv.

Hi if anyone have interested, this is dtb files and orangepienv file 🙂 allwinner.zip

I found the problem: [ 2299.766819] Out of memory: Killed process 43216 (pahole) total-vm:8235296kB, anon-rss:4667816kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:12912kB oom_score_adj:0

@maxsub: Out-of-RAM may be possible if it simply spits out "killed". My machine has 32 Gb RAM and 16 Gb swap, does not encountered the OOM-killer lately. Until now, but exhausting RAM is probably kernel-dev-hobby 😗