obiwantoby

Using the latest 6.1.75-vendor-rk35xx ls -l /dev | grep -E "mpp|rga|dri|dma_heap" drwxr-xr-x 2 root root 80 Dec 31 1969 dma_heap drwxr-xr-x 3 root root 140 Nov 7 09:38 dri crw------- 1 root root 241, 0 Nov 7 09:38 mpp_service crw------- 1 root root 10, 122 Nov 7 09:38 rga I am having some issues, very similar to https://forum.radxa.com/t/opencl-fails-with-failed-creating-base-context-during-opening-of-kernel-driver-on-reboots-for-rockchip-rk3558-orange-pi-5-plus/21558. That is when I install the OpenCL extensions, it seems to work fine, but upon reboot the system is non responsive. I am following instructions for that that libmali https://github.com/tsukumijima/libmali-rockchip/releases/download/v1.9-1-2d267b0/libmali-valhall-g610-g13p0-gbm_1.9-1_arm64.deb For the 6.1 LTS kernel on Ubuntu-Rockchip & Armbian and the legacy 5.10 LTS kernel, install v1.9-1-2d267b0. For the 6.1 LTS kernel on other SBC vendor-made distros, install v1.9-1-55611b0. ocker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v debug -init_hw_device rkmpp=rk -init_hw_device opencl=ocl@rk ffmpeg version 7.0.2-Jellyfin Copyright (c) 2000-2024 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14) configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-ptx-compression --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto=auto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libxml2 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libharfbuzz --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=arm64 --cross-prefix=/usr/bin/aarch64-linux-gnu- --toolchain=hardened --enable-cross-compile --enable-rkmpp --enable-rkrga libavutil 59. 8.100 / 59. 8.100 libavcodec 61. 3.100 / 61. 3.100 libavformat 61. 1.100 / 61. 1.100 libavdevice 61. 1.100 / 61. 1.100 libavfilter 10. 1.100 / 10. 1.100 libswscale 8. 1.100 / 8. 1.100 libswresample 5. 1.100 / 5. 1.100 libpostproc 58. 1.100 / 58. 1.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument 'debug'. Reading option '-init_hw_device' ... matched as option 'init_hw_device' (initialise hardware device) with argument 'rkmpp=rk'. Reading option '-init_hw_device' ... matched as option 'init_hw_device' (initialise hardware device) with argument 'opencl=ocl@rk'. Finished splitting the commandline. Parsing a group of options: global . Applying option v (set logging level) with argument debug. Applying option init_hw_device (initialise hardware device) with argument rkmpp=rk. Applying option init_hw_device (initialise hardware device) with argument opencl=ocl@rk. arm_release_ver: g13p0-01eac0, rk_so_ver: 10 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded [AVHWDeviceContext @ 0xaaab04dcb0d0] 1 OpenCL platforms found. [AVHWDeviceContext @ 0xaaab04dcb0d0] 1 OpenCL devices found on platform "ARM Platform". arm_release_ver: g13p0-01eac0, rk_so_ver: 10 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded [AVHWDeviceContext @ 0xaaab04dcb0d0] 0.0: ARM Platform / Unknown Device Any idea what's up?

I have to say the latest ./compile.sh with 6.8.0-rc1-edge-rockchip-rk3588 seems to be operating great. For some reason the benchmarks have increased dramatically from 5.10-legacy. Ping times are a big lower overall too on average - unsure if the big.LITTLE scheduling improvements are contributing - but in ARM those should have been fairly mature, not like the Adler Lake e core changes. Either way I am welcoming the change. https://pibenchmarks.com/benchmark/78720/ 19,000 --> 32,000 Category Test Result HDParm Disk Read 376.81 MB/sec HDParm Cached Disk Read 386.25 MB/sec DD Disk Write 270 MB/s FIO 4k random read 86050 IOPS (344201 KB/s) FIO 4k random write 46972 IOPS (187889 KB/s) IOZone 4k read 172508 KB/s IOZone 4k write 131029 KB/s IOZone 4k random read 69041 KB/s IOZone 4k random write 159514 KB/s Score: 32652

I played around with affinity, no change. It got so bad that via SSH I'd be kicked off or my commands would partially input. I did a restore from backup, and since I do use docker, back up and running perfectly again. I wish I knew what was tainting the system though. Could it be this or similar? https://community.home-assistant.io/t/home-assistant-in-docker-causes-network-packet-loss-on-host/520067 Unknown, as I am not running anything privileged. I am not sure *if* this is a hint as well. There has to be an explanation but as to what still at a loss. Especially since I can restore like I did, and everything is working perfectly. Perhaps I should just avoid apt-get upgrades

Standard install - Armbian Bookworm, full 'firmware install'. I am getting some packet loss over the LAN. A raspberry pi, Synology NAS and Deban x86 install on the same LAN do not seem to exhibit the same loss. Anyone have experience or ideas? Oddly enough this never seems to occur on fresh installs. This is a docker host for pihole and home assistance, no other packages are really installed at all. I've not really tried much, but since this is a standard install, apt-get update & upgrade are about the only modifications outside of docker install that has occurred. 1. This plugs directly in to a Ubiquiti switch 2. I have tried a few different ethernet cables. 3. dmesg does not really show disconnects on the regular

The normal apt-get update cycle this time around also caused issues. For me my networking was unstable. Remote SSH would time out and keystrokes would be 5 - 30 seconds delayed. Not sure what happened here.