[Detector Support]: Doesn't work GPU with OpenVINO #9574
Comments
|
@NateMeyer have you seen this before? |
|
No, I just try to setup it. Actually no, it seems I tried a month ago to setup OpenVINO when Frigate has ver 0,12 and it was the same. |
|
This is I can see when set device=AUTO, but as I mentioned earlier, it doesn't work when detect is enabled.
|
|
to be clear I tagged someone else with that question |
|
No that is a new one to me. I'll see what I can dig up later today. |
|
It looks like the container is missing something like this one |
|
That page is outdated. Also, many users are using this in GPU mode so it will likely be something host specific |
|
Clear. Let me please know if I need to share more information about the case. |
|
I just wanted to add that I found a message in syslog when I am trying to launch a Frigate with Openvino and device GPU |
|
it seems that the error occurs that there is some OpenCL bag in kernel because of there are similar messages on the Internet related to the incorrect work of hardware acceleration for example in Plex. Hopefully, a solution to this problem will be found. |
|
I have the exact same issue, same cpu in a nuc but with proxmox. Indeed Plex struggled for a long time with some of these processors after an update but was resolved a few weeks back. As far as i know their issue was related to changes in the drivers used. |
|
Same issue on a docker nested container inside a proxmox unprivileged container using intel N3350. |
|
I seem to have the very same issue, is there any solution already? |
No, I didn't find and just bought Google Coral TPU |
|
I have intel J4105 with Proxmox 8.1 / debian 12 docker LXC running into the same "GPU Hang" syslog. Reading a similar issue #5799 that suggests some kernel issue, I eventually replace Proxmox with 7.4 and debian 11 LXC, and the issue is resolved. My kernel in LXC is |
|
Same issue here with proxmox 8.1.10 (kernel 6.5.13-5-pve) and frigate running in LXC |
I am running Proxmox as well and it was working on kernel 6.5.13-3. I just updated to Proxmox 8.2.2 today and it uses kernel 6.8.4-2 and Frigate is unable to detect my GPU: Nothing has changed in my config, and it's rather simple for detectors: detectors:
ov:
type: openvino
device: GPUI'm guessing it's something to do with how the kernel may be exposing devices, and/or with an update required to some libs in the Frigate container? FYI - if I change to |
|
@esand I think it is most likely that your issue is not related to frigate. You probably need to reconfigure the GPU passthrough to LXC/VM after Proxmox upgrade. |
The /dev/dri devices are still visible in both the linux container and the frigate container. Permissions are correct and I've still got hwaccel working just fine. As far as I'm aware, no changes in Proxmox 8.2.2 impacted hardware passthrough configurations and my LXC still boots up just fine (it would error out on a bad config). I also have other devices that I do passthrough with in other containers and those are still functioning fine. |
|
Same observation as @esand. Hwaccel working fine and other cotainers working with the gpu (e.g. plex transcoding). |
|
I just upgraded proxmox to 8.2.2 and have the same issue as described above with intel gpu passthrough
|
|
looks like this is an issue with the kernel included in the new proxmox 8.2.2 loading the previous kernel in proxmox with the following guide solved my issue until a new proxmox release comes out. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Not sure when this was fixed, but I just commented out the I'm on version 6.8.8-3-pve now. |
Just updated to 6.8.8-3-pve to test and no success. Do you have similar setup that OP? |
Yes, similar to OP. The host is Proxmox 8 with an i7-8700 CPU. I was experiencing the same exact issue, prior to updating the kernel to 6.8.8-3. I've rebooted several times, verified that the newer kernel was actually being used, and haven't experienced any issues. |
|
I recently updated to proxmox 8.2.4 with kernel 6.8.8-4 from 7.4 with 5.15.158-1-pve I'm experiencing the same issue. I tried kernel 6.8.8-3 and even 6.5 with no luck. I decided to set up a proxmox 7.4 VM just to test it and it works perfectly. I tried the what was suggested here #12266 on proxmox 8 but it didn't solve my issue. |
|
I'm pretty sure this is an upstream issue in the compatibility between intel-compute-engine and the kernel GPU hang check functionality. Here is a related discussion with the exact same CPU (J4105) As far as I'm aware of, downgrading to kernel 5.15 seems to be the only solution. |
I don't believe that intel/compute-runtime#679 is the culprit, but rather intel/compute-runtime#710. If you put some ENV variables in to override some GPU settings it works, or if you update the openvino libraries (#10785). There's supposedly a fix in the works to the kernel code to correct the issue, but until then either ENV variables or updating openvino appear to solve the problem. It might be best to close this and other related issues and point them all to #10785 which documents both potential fixes. |
None of these solutions works for me. It seems my J4125 just isn't supported. |
The issue you mentioned is about unable to detect GPU, which I think #10785 is the right thread to merge with. OP, @Fahmula and myself experienced a different one. The one is related to J4105/J4125 specifically, and relevant logs are clearly different than the one you posted in #9574 (comment). As @Fahmula mentioned, none of the solutions work. |
My apologies - it seems you are indeed correct. I think what suckered me in to posting on this thread was that my error was almost identical to OP and I thought they were the same thing initially. |
Describe the problem you are having
When I am trying to enable OpenVINO detector with device=GPU I can see the error in log and Frigate becomes inactive for a while. If I set device=AUTO it starts to work, but when detect is enabled I can see high cpu utilization and no any activity in intel_gpu_top which shows that GPU acceleration is not working. HW acceleration of camera is working good.
I set LIBVA_DRIVER_NAME=iHD because of if I choose i965 then I see how the blitter in intel_gpu_top is connected, I'm not sure, but it doesn't seem good and openvino doesn't work also.
I have Celeron J4105 and Unraid system.
Version
0.13
Frigate config file
docker-compose file or Docker CLI command
Relevant log output
Operating system
UNRAID
Install method
Docker Compose
Coral version
CPU (no coral)
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: