-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openvino with UHD Graphics 600 error "GPU program build failed!" #245597
Comments
Works with the discrete Intel GPU I have access to:
|
I have J4125 too with the same problem
|
I wouldn't be surprised if this was a limitation on GPU inference on that model. Even though Intel claims to support basically everying from a 6th gen CPU. https://www.intel.com/content/www/us/en/developer/tools/openvino-toolkit/system-requirements.html#tab-blade-1-1 |
I'm having the same "[GPU] clWaitForEvents, error code: -14" issue using the GPU on an N4020 with UHD graphics running openvino 2024.2 on Ubuntu 22.04. Funny thing is, this system was running Ubuntu 20.04 and openvino 2021.3 and the GPU worked fine. |
That sounds like Intel dropped support in a newer release. Nothing I can for you I'm afraid. That being said, I am now running Frigate on a relatively cheap N100 platform and I would recommend upgrading to that. It also comes with AVX2 support, which is required since we switched to the binary tensorflow distribution. |
Describe the bug
Using a Celeron J4125 I am trying to run OpenVINO, but get
Steps To Reproduce
Steps to reproduce the behavior:
(It also fails using ssdlite_mobilenet_v2.xml from the frigate NVR package which is the one I really want to use, so I don't think this is a model-specific problem. I'm no expert though)
Expected behavior
Good question. I expected it not to fail with an error message, but I don't know what correct behaviour looks like. I'd like frigate to work, but it fails with the same error messages, so I hope that this is a smaller test case
Additional context
configuration.nix has
clinfo works:
If I set
LD_DEBUG=libs
I can see quite voluminous output which includes severalfatal
lines. I don't know if these are relevant ...Notify maintainers
@tfmoraes
From git history: @mweinelt @superherointj
Metadata
The text was updated successfully, but these errors were encountered: