[Support]: detections all suddenly broken on rknn #20946
Replies: 2 comments 2 replies
-
|
I see several issues with your setup that are likely causing the RGA errors and detection failures. Device Mapping IssueThe RKNN runtime is looking for According to the Rockchip installation documentation, you should be mapping the devices correctly. Remove the line: - /dev/dri/renderD128:/dev/dri/renderD129And ensure you have the proper device mappings as documented(1): devices:
- /dev/dri
- /dev/dma_heap
- /dev/rga
- /dev/mpp_serviceYou already have these in your compose file, which is correct. Privileged ModeYour container is running in privileged mode ( security_opt:
- apparmor=unconfined
- systempaths=unconfinedRGA Filter ErrorsThe RGA blit errors ( Recommended Steps
ls /dev/driYou should see
sudo cat /sys/kernel/debug/rknpu/versionIf the kernel upgrade broke the RKNPU drivers, you may need to reinstall them following the Rockchip installation prerequisites(1). 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
The issue you're experiencing is related to kernel-level driver support for the Rockchip NPU, not specifically a Frigate configuration problem. What's HappeningThe Why the Armbian Vendor Kernel Lost renderD129Based on the Rockchip installation prerequisites, Frigate requires "a linux distribution that comes with the rockchip BSP kernel 5.10 or 6.1 and necessary drivers (especially rkvdec2 and rknpu)"(1). The documentation specifically recommends checking: $ ls /dev/dri
by-path card0 card1 renderD128 renderD129 # should list renderD128 (VPU) and renderD129 (NPU)The fact that Joshua Riek's
Why It Worked BeforeYou mentioned it worked for 2 weeks on the Armbian vendor kernel. This suggests either:
RecommendationSince Joshua Riek's kernel works reliably, stick with it for now. The Armbian vendor kernel appears to have incomplete or misconfigured RKNPU support. You could:
The good news is that with the working kernel, your Frigate setup should function properly with the correct device mappings as documented(1). 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
After running an 'apt upgrade' on my OPI5+ running Armbian nobel (including a kernel upgrade) and updating Frigate to the latest dev build(from a slightly older dev build, frigate:a623150-rk) all detections are boned and I'm getting a bunch of RGA related errors.
The first thing I noticed was that the rknn runtime fails to initialize because for some reason it is trying to use /dev/dri/renderD129, which doesnt exist. I only have /dev/dri/renderD128!
So I tried adding the mapping "/dev/dri/renderD128:/dev/dri/renderD129" to my docker-compose.yml. Now the rknn runtime starts but all detections are failing with strange errors related to RGA:
So I immediately downgraded the kernel packages that we upgraded and went back to the 'known good' frigate build that I was previously using (a623150-rk) and oddly enough the problem is still present! I have no idea what could have possibly happened. please haalp!
Version
a623150-rk
What browser(s) are you using?
firefox
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
No response
Install method
Docker Compose
docker-compose file or Docker CLI command
Object Detector
RKNN
Network connection
Wired
Camera make and model
various
Screenshots of the Frigate UI's System metrics pages
No response
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions