dwarfman78

Hi everyone, I was experience some strange things with two similar devices, the first I installed in february this year, mesa v.24.x and EGL 1.4 and it was working fine The other one I installed this week and it turns out that it uses mesa v.25.x and EGL 1.5, although performance was great with most 3D apps (like glmark2) I had poor performance under sway/kitty or the retroarch menu for instance (something like 15 fps). It took me a few days to find a solution so if you have similar issues please try installing mesa with the kisak repository as it fixed my problems sudo add-apt-repository ppa:kisak/kisak-mesa -y sudo apt update sudo apt upgrade the last command should upgrade mesa to a more recent version than what's in the ubuntu ppa.

Hi, you need the radxa dedicated tool to do it : https://opensource.rock-chips.com/wiki_Rkdeveloptool Once it is compiled and installed, you need to start the device in "maskrom mode", to do that, push the maskrom button located under the board near the hdmi output then power the device while holding the button. The led should turn and stays on. To check if the device is ready, run the following command : rkdeveloptool ld it should print something like that : DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=302 Maskrom it means the device is ready to receive data then you need to upload the bootloader : sudo rkdeveloptool db rk356x_spl_loader_ddr1056_v1.12.109_no_check_todly.bin and finally you can upload the armbian img : sudo rkdeveloptool wl 0 Armbian-XXX.img make sure your device is properly cooled before doing those operations because heat can freeze the process. you can find the loader and more info here : https://docs.radxa.com/en/zero/zero3/low-level-dev/rkdeveloptool there's a windows version of rkdeveloptool too you can find on their website.

Well I was able to build by changing the docker image with this option : DOCKER_ARMBIAN_BASE_IMAGE=ubuntu:jammy The two other images (debian:bookworm and ubuntu:noble) simply do not work

Hi, I'm still having this issue after installing qemu-emulators-full and qemu-user-static on the host (arch) does anyone have any idea or workaround ?

Can you please explain what you mean by this ? Am I supposed to install it on the host ? If so, this solution is not working for me. I am trying to compile armbian with docker from arch, it worked a few months ago (commit from February 2025) but now it doesn't (commit from August) Same error as original poster.

Ok so here is the definitive solution : You need panfrost so use the correct armbian version with vendor kernel, then you are going to need to compile ffmpeg for rockchip, just follow those instructions : https://github.com/nyanmisaka/ffmpeg-rockchip/wiki/Compilation Once it is done, you might have some performance issues when capturing the screen with either x11 or Wayland, BUT ffmpeg allows you to capture directly from the device through kmsgrab sudo setcap cap_sys_admin+ep /usr/bin/ffmpeg sudo ffmpeg -device /dev/dri/card0 -f kmsgrab -i - -r 60 -vcodec h264_rkmpp -f rtp rtp://localhost:8004 There I am streaming to a rtp server but you can write into a file. Do not forget to use the -vcodec h264_rkmpp which will use hardware encoding through VPU.

Some news about this topic, I have dropped wayland and went back to X11 with Xvfb+ffmpeg with x11grab and h264_rkmpp codec into Janus WebRTC through a RTP output. Let's say it works, it is really slowing down the computer but I manage to stream at 30 fps, I continue my investigations to improve performances.

Hi again, somehow I am making progress, I was able to start a headless sway compositor then start recording the screen with wf-recorder which relies on ffmpeg, however, the video file generated has a very low framerate, something like 2 fps. Can you help me ? EDIT : I have plugged the hdmi output to a real display and the overall fps are very low when wf-recorder is running (not only in test.mp4 but also on the real screen), when not recording the framerate is at about 60 fps. here is my sway.cfg :

That's interesting, I have already successfully compiled ffmpeg with mpp support, I know I can handle inputs with swayvnc and I will look into mediamtx, however I am a bit worried about latency which is critical for my use case. I'll keep you posted. Thanks.

I am trying to stream my display with sunshine (https://app.lizardbyte.dev/Sunshine/) which supports only nvenc,amd vce or vaapi. With software encoding there's only 8 frames per second output and 50% CPU usage.

I've found this repository which provides the VAAPI driver : https://github.com/qqdasb/libva-rkmpp vainfo --display drm --device /dev/dri/renderD128 | grep -E "((VAProfileH264High|VAProfileHEVCMain|VAProfileHEVCMain10).*VAEntrypointEncSlice)|Driver version" libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib/aarch64-linux-gnu/dri/rockchip_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: Driver version: Rockchip Driver 1.0 However I have a new error : libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib/aarch64-linux-gnu/dri/rockchip_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 [2025-02-26 23:58:44.486]: Info: vaapi vendor: Rockchip Driver 1.0 [2025-02-26 23:58:44.487]: Error: [AVHWFramesContext @ 0xaaaae273d480] Failed to create surface: 10 (attribute not supported). [2025-02-26 23:58:44.487]: Error: [AVHWFramesContext @ 0xaaaae273d480] Unable to allocate a surface from internal buffer pool. [2025-02-26 23:58:44.492]: Info: Encoder [vaapi] failed

vainfo --display drm --device /dev/dri/renderD128 | grep -E "((VAProfileH264High|VAProfileHEVCMain|VAProfileHEVCMain10).*VAEntrypointEncSlice)|Driver version" libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib/aarch64-linux-gnu/dri/rockchip_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit vainfo --display drm --device /dev/dri/renderD129 | grep -E "((VAProfileH264High|VAProfileHEVCMain|VAProfileHEVCMain10).*VAEntrypointEncSlice)|Driver version" libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib/aarch64-linux-gnu/dri/panfrost_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit Those files are not found : sudo find / -name "*_drv_video.so" /usr/lib/aarch64-linux-gnu/dri/radeonsi_drv_video.so /usr/lib/aarch64-linux-gnu/dri/d3d12_drv_video.so /usr/lib/aarch64-linux-gnu/dri/nouveau_drv_video.so /usr/lib/aarch64-linux-gnu/dri/virtio_gpu_drv_video.so /usr/lib/aarch64-linux-gnu/dri/r600_drv_video.so

Thanks, I am already using the latest vendor kernel, is there a way to enable mesa-vpu extension afterward or do I have to recompile the kernel entirely ?

Hi, I'm trying to get h264 encoding working but VAINFO keeps searching for rockchip_drv_video.so which is nowhere to be found on my system. Is there a way to get h264 encoding working with armbian OR do I have to use radxa oses (or the ubuntu version provided by Joshua Riek) ? Thanks.