[HW Accel Support]: Nuc 12th gen i5 #4138
Comments
|
Bump. :( |
|
Please run |
|
Sorry, have been away. I couldn't get the command to work, as I said I'm not very good on linux. Running vainfo by itself gave the following. Which seems to be related to some headless installs (I don't think I had a headless install, just use ssh and no longer have the GUI load or monitor connected. |
|
If your host can't find anything with vainfo then you don't have your iGPU setup correctly. Might need to download drivers on the host |
|
I get the exact same results when I run the commands on my 8th gen nuc which I'm upgrading from... and the HW accel worked fine with that. But I'll do some googling and see if I can get a result from vainfo |
|
Are you sure the hwaccel worked fine? In previous frigate versions if hwaccel failed it would be ignored and not used. In frigate 0.11 ffmpeg will fail immediately if hwaccel is requested and not able to be used. |
|
Pretty sure hwaccel was working. Just a quick initial test bring up this from the 8th gen via intel_gpu_top And when I removed the hwacell stuff from the config, it show 0% on everything I connected a monitor and keyboard directly to the 12th gen... and vainfo returned this, so it doesn't show up when I ssh in to run that command. However running from the docker had the same error. |
|
You can install vainfo inside the docker container by running apt install vainfo Also struggling with Alder Lake GPU acceleration. i3 CPU with Ubuntu 22. Works on host, doesn't work in Frigate container. Had to install libmfx-gen1.2 on host; but I am not able to do it in the container. Maybe thats why it fails with [h264_qsv @ 0x55977adf0a00] Error during set display handle vainfo from host: vainfo in container has the same profiles; but different version: (Setting xdg runtime dir makes no difference) |
|
i have the same problem with nuc12 i7 vainfo on docker lxc |
|
Found a soltion look at this: |
|
Thanks Gomble. That worked. I have another issue now, but I'll try work it and open a new thread if I can't resolve. |
|
Maybe @blakeblackshear you can update the intel-media-va-driver-non-free in the frigate container to version 22. Than it will work out of the box ? See #4263 |
We're aware of the issue and have been looking into trying a newer driver. There's a large discussion about it at #3941 |
Describe the problem you are having
I can't get HW Accel working at all on my new nuc. I was using an 8th gen i5 nuc and had frigate working well with hwaccel using these settings. Using ubuntu and I'm not very experianced with docker or linux, I just bumble my way through most of the time... but this has me stumped.
Without any hwaccel, frigate works fine... but I have 10 cameras, and would much rather hwaccel work reducing CPU usage.
I'll post all my attempted hwaccel arguments here with errors... I have 4k h265 stream for record stream and a sub stream for detect h264... not sure if it makes a difference, but when I tried using tyhe h264 for recording and detecting, I did get slightly different errors one time.
#1
Note: This was working on my 8th gen, but not 12th.
#2
hwaccel_args: -c:v h264_qsvErrors with h265 record + h264 detect streams
Errors with both record + detect h264 streams
#3
Similar errors when I tried both of these
hwaccel_args: -hwaccel qsv -qsv_device - /dev/dri/renderD128Errors with both record + detect h264 streams, and the h265 record + h264 detect
Version
0.11.1-2EADA21
Frigate config file
docker-compose file or Docker CLI command
Relevant log output
FFprobe output from your camera
Operating system
Debian
Install method
Docker Compose
Network connection
Wired
Camera make and model
reolink 822a + 820a
Any other information that may be helpful
Sorry, I know there are a lot of threads about hwaccel, and I think I've gone through them all to try and work it out, but I'm not making any progress after hours of tinkering.
The text was updated successfully, but these errors were encountered: