-
-
Notifications
You must be signed in to change notification settings - Fork 2k
VAAPI on N100 Stops Working After 2 Hours, Requires Reboot #16438
Replies: 2 comments · 2 replies
-
This is likely a bug in the intel_gpu_top tool, I don't think there is any issue with the GPU itself, qsv should be used on this hardware |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thanks. now happens something very strange, when i use VAAPI both camera works fine. when i use qsv, only one camera working. my back camera works good. my front camera doesn't work at all. i added the logs when i try to use only the front camera. 2025-02-14 09:56:59.502341557 [2025-02-14 11:56:59] ffmpeg.entrancezoom.detect ERROR : [vist#0:0/h264 @ 0x564f90aff8c0] [dec:h264_qsv @ 0x564f90ab3e80] Decoding error: Invalid argument |
Beta Was this translation helpful? Give feedback.
All reactions
-
Something has changed Now the VAAPI works with 0.4%. This is a small change but it's still something. Just for the demonstration I did another reboot To see how it's should be. I was thinking about running Frigate directly through Ubuntu in this case i need a new pc for that use case. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I'm having issues with VAAPI on N100 aswell (see: #16609). Mine is totally not working (0% GPU), just wondering how you got yours to work. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
I am using Frigate as an add-on in Home Assistant. Additionally, I have integrated Double Take, Deepstack, CompreFace, and Plate Recognizer. The system is set up to detect humans as well as vehicles and license plates. Currently, I have only two Reolink cameras connected.
I have been trying for a while to get the GPU to work. I have also tried VAAPI and QSV, but neither worked. It constantly shows 0% usage. The only way I can get it to work is by performing a full reboot of the computer, after which it functions for about two hours only.
I have repeated this reboot process three times, and each time the behavior is the same—it works for about two to three hours and then stays at 0% usage without recovering.
I saw that I can try using the i965 environment variable, but I got an error stating that i965 couldn't initialize. When I disable it, the system works for the two hours I mentioned earlier.
Version
0.15.0-cea210d
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Install method
HassOS Addon
Object Detector
Coral
Network connection
Wired
Camera make and model
Reolink Tracemix wifi
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
{"return_code":0,"stderr":"","stdout":"vainfo: VA-API version: 1.22 (libva 2.10.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.3.3 ()
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointFEI
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointFEI
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointFEI
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointFEI
VAProfileHEVCMain : VAEntrypointEncSliceLP
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointEncSliceLP
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointEncSliceLP
VAProfileVP9Profile1 : VAEntrypointVLD
VAProfileVP9Profile1 : VAEntrypointEncSliceLP
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointEncSliceLP
VAProfileVP9Profile3 : VAEntrypointVLD
VAProfileVP9Profile3 : VAEntrypointEncSliceLP
VAProfileHEVCMain12 : VAEntrypointVLD
VAProfileHEVCMain12 : VAEntrypointEncSlice
VAProfileHEVCMain422_10 : VAEntrypointVLD
VAProfileHEVCMain422_10 : VAEntrypointEncSlice
VAProfileHEVCMain422_12 : VAEntrypointVLD
VAProfileHEVCMain422_12 : VAEntrypointEncSlice
VAProfileHEVCMain444 : VAEntrypointVLD
VAProfileHEVCMain444 : VAEntrypointEncSliceLP
VAProfileHEVCMain444_10 : VAEntrypointVLD
VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP
VAProfileHEVCMain444_12 : VAEntrypointVLD
VAProfileHEVCSccMain : VAEntrypointVLD
VAProfileHEVCSccMain : VAEntrypointEncSliceLP
VAProfileHEVCSccMain10 : VAEntrypointVLD
VAProfileHEVCSccMain10 : VAEntrypointEncSliceLP
VAProfileHEVCSccMain444 : VAEntrypointVLD
VAProfileHEVCSccMain444 : VAEntrypointEncSliceLP
VAProfileAV1Profile0 : VAEntrypointVLD
VAProfileHEVCSccMain444_10 : VAEntrypointVLD
VAProfileHEVCSccMain444_10 : VAEntrypointEncSliceLP"}
No response
Beta Was this translation helpful? Give feedback.
All reactions