You mentioned once that your bluetooth did not work. See if this DKMS package does any good.
https://drive.google.com/file/d/1K4cjedlZs8A9rTnrxuQKzfIppdSvPYBU/view?usp=sharing
In the earlier linux-kernel (most likely linux-6.14) does not have Bluetooth on Opi5-Plus but later linux-kernel 6.15.4 Bluetoot is available. On linux-6.16.0-1 Bluetooth is available but most of the time it failed to pair with my very old bluetooth mouse.
Forgot to update in this forum as I seldom use Bluetooth mouse much. Have a very old bluetooth mouse and is not that responsive compare to wire mouse.
Thanks for the new bluetooth dkms.
Edit: Previously on linux-rc-6.14-rc5-1 the “rockchip_vdec2” is available
[jfl@opi5plus ~]$ lsmod | grep v4l2
v4l2_vp9 24576 1 hantro_vpu
v4l2_jpeg 16384 1 hantro_vpu
v4l2_h264 16384 2 hantro_vpu,rockchip_vdec2
v4l2_mem2mem 36864 3 hantro_vpu,rockchip_rga,rockchip_vdec2
videobuf2_v4l2 28672 4 hantro_vpu,rockchip_rga,rockchip_vdec2,v4l2_mem2mem
videodev 270336 5 videobuf2_v4l2,hantro_vpu,rockchip_rga,rockchip_vdec2,v4l2_mem2mem
videobuf2_common 65536 8 videobuf2_dma_contig,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_dma_sg,rockchip_vdec2,v4l2_mem2mem,videobuf2_memops
mc 69632 6 videodev,videobuf2_v4l2,hantro_vpu,videobuf2_common,rockchip_vdec2,v4l2_mem2mem
[jfl@opi5plus ~]$
But on linux-6.16.0-1 “rockchip_vdec” is available. Not sure whether this is the cause of chromium_v138 not having vpu hardware acceleration.
[jfl@jfl-opi5plus ~]$ lsmod | grep v4l2
v4l2_jpeg 16384 1 hantro_vpu
v4l2_vp9 20480 2 rockchip_vdec,hantro_vpu
v4l2_h264 16384 2 rockchip_vdec,hantro_vpu
v4l2_mem2mem 36864 2 rockchip_vdec,hantro_vpu
videobuf2_v4l2 28672 3 rockchip_vdec,hantro_vpu,v4l2_mem2mem
videodev 278528 4 rockchip_vdec,videobuf2_v4l2,hantro_vpu,v4l2_mem2mem
videobuf2_common 65536 6 rockchip_vdec,videobuf2_dma_contig,videobuf2_v4l2,hantro_vpu,v4l2_mem2mem,videobuf2_memops
mc 69632 6 rockchip_vdec,videodev,videobuf2_v4l2,hantro_vpu,videobuf2_common,v4l2_mem2mem
[jfl@jfl-opi5plus ~]$
That is because the module name was changed. There is no rockchip_vdec2 option anymore.
CONFIG_VIDEO_ROCKCHIP_VDEC=m
CONFIG_VIDEO_MESON_VDEC=m
https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/master/config?ref_type=heads
I thought rockchip_vdec and rockchip_vdec2 where two different drivers.
It is whatever warpme patches want it to be. More of a progression in a patch to get it like they want it.
You need to figure out what you are doing different than what @maxjrh has in his configs. You 2 are the only people here that has your device.
Basically the chromium flags settings are the same. @maxjrh has UEFI EDK2 on SPI whereas I have u-boot (joshua riek)on SPI.
MiniArch-EOS with warpme kernel-6.16.0 on my device also have the same chromium_v138 no vpu hardware acceleration.
Let see when and if @maxjrh build a new chromium_v139 have the same issue on my device.
Edit: Have set the chromium flags to same as @maxjrh chromium flags settings and chromium_v138 still no vpu hardware acceleration with linux-6.16.0-1. The known difference is SPI bootloader which in my case use “u-boot” and @maxjrh uses UEFI-EDK2. Not sure whether there are other differences.
But on linux-6.16.0-1 “rockchip_vdec” is available. Not sure whether this is the cause of chromium_v138 not having vpu hardware acceleration.
I have made a trial with rk3566 and have hardware a cceleration, e.g. clapper can play 4k h264. The problem for me is that this kernel is rather slow.
On Opi5-Plus with kernel linux-6.16.0-1, clapper and mpv-full-git (by @junari) can play local 4k/30 8 bit h264 video with vpu hw acceleration. Do not have local 4k/60 8bit video to test to see whether it works.
With linux-6.16.0-1 clapper and mpv-full-git can also play hevc videos.
Wow, h264 and hevc in 4k/30? That’s sound great!
You can find more different videos here
https://repo.jellyfin.org/test-videos/
Well, clapper and mpv-full-git able to play local 4k/60 hevc 8bit video from
mpv '/run/media/alarm/writable/home/jfl/Videos/Test Jellyfin 4K HEVC 8bit 40M.mp4'
● Video --vid=1 (hevc 3840x2160 60 fps) [default]
Using hardware decoding (v4l2request).
VO: [gpu] 3840x2160 drm_prime[nv12]
V: 00:00:29 / 00:00:29 (100%) Dropped: 5
Exiting... (End of file)
1 Like
It seems the kernel is not slow but the dtb with rkvdec for my device delivers the slowness noticed.
Hi @maxjrh,
Noticed this rockchip64-6.16: add patch to fix chromium v4l2 decoding with rkvdec
The Debian Repo Chromium - 140.0.7339.80-1 is now default to “–ozone-platform=wayland” and it seems to be stable on Orange Pi 5 Plus, so far did not encounter random crashes. vpu hardware acceleration is also available.
@Darksky @maxjrh,
2025-09-11: Transplanted Armbian-kernel-6.16.5-edge-rockchip64 which has the “rockchip64-6.16: add patch to fix chromium v4l2 decoding with rkvdec” on Manjaro-opi5plus-xfce.
Chromium_v139 (by @maxjrh) with kernel-6.16.5-edge-rockchip64 has vpu hardware acceleration on every boot up and it does not matter whether “/dev/video0: rkvdec or hantro-vpu rockchip,rk3328-vpu-dec” or “/dev/vdeio1: rkvdec or hantro-vpu rockchip,rk3328-vpu-dec” Chromium_v139 has vpu hardware acceleration.
The kernel patch “rockchip64-6.16: add patch to fix chromium v4l2 decoding with rkvdec” seems to resolve Chromium randomly not having vpu hardware acceleration issue depending what /dev/video0: vpu driver is being loaded".