Lost GPU support after Home assistant Operating system update v17 #21729
Replies: 3 comments 2 replies
|
The error After a Home Assistant OS update, you may need to verify your hardware acceleration configuration. For Intel-based systems, the default driver is Try switching to the i965 driver: Add the following environment variable to your Frigate configuration. For Home Assistant Add-on users, you can add this in the environment_vars:
LIBVA_DRIVER_NAME: i965Verify your hwaccel configuration: Make sure you're using the appropriate preset for Intel hardware. For VAAPI (which works with both H.264 and H.265 streams automatically), use(1): ffmpeg:
hwaccel_args: preset-vaapiCheck device access: Ensure the CPU Generation matters: According to the documentation, different Intel CPU generations work better with different drivers(1):
Check your Intel CPU generation to determine the correct driver and preset(1). If switching to 📚 Sources: Have another question? Just tag @inkeep. |
|
This is my conf using the HomeAssistant Module |
Same issue — Intel N5105 (Jasper Lake), HAOS 17.3 bare metal, Frigate Full Access 0.17.1Previously working with VAAPI hardware acceleration. After updating to HAOS 17.3, Environment
Confirmed behavior
Tried without success
All fail with the same errors: OpenVINO GPU error: Current workaround
This appears to be a regression in HAOS 17.x breaking Additional noteSwitched from standard Frigate NVR add-on to Frigate NVR Full Access specifically to enable GPU access, as the standard add-on has Protection Mode enabled by default. Even with Full Access, With the standard Frigate add-on, the Google Coral USB detector worked correctly — suggesting USB devices are properly passed through, but DRI devices are not. |

Uh oh!
There was an error while loading. Please reload this page.
Hi
I just migrate to the v17 version of HA Operating system, and I've launch the driver docker migration.
After that. I notice my Frigate module stop using my GPU !
Any idea ?
All reactions