[Detector Support]: OpenVINO with Intel J4105 #18125
Replies: 3 comments 5 replies
-
|
I don't believe this hardware is supported by OpenVINO |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
See this post from Intel: https://community.intel.com/t5/Intel-Distribution-of-OpenVINO/OpenVINO-with-Intel-Celeron-J4125/m-p/1309143 And see this similar issue: #13388 |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
@pietro1796 have you found a solution yet? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
I’m running Frigate inside an LXC container on Proxmox (Debian 12.7). I’m trying to use OpenVINO with the iGPU passed through to the container.
I have successfully passed the iGPU to the LXC, and it is correctly visible inside the container. I then pass the GPU to the Frigate container via Docker Compose, and it also appears to be correctly detected there.
However, when I configure OpenVINO to use the GPU as the device, the detector fails to start and crashes the system (the service does not come up). If I switch to using the CPU as the device, it works, but detection is very slow (around 120ms).
Any help getting the iGPU working properly with OpenVINO in this setup would be greatly appreciated.
Version
0.15.0-6cb5cfb
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Install method
Proxmox via Docker
Object Detector
OpenVino
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Both on the LXC container (Debian) and inside the Frigate Docker container, the vainfo command and ls /dev/dri work correctly and show the GPU. Also, intel_gpu_top shows some activity, so it looks like something is using the GPU.
Beta Was this translation helpful? Give feedback.
All reactions