-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Support]: 0.13.0 beta 4 no Intel GPU stats #8494
Comments
This is most likely related to blakeblackshear/frigate-hass-addons#122 Other users saw that it was still working as expected. Which addon variant are you running? |
CC @felipecrs |
@wimb0 what is your HAOS and Supervisor version? |
Ops, got it. You are using Debian with Supervised. I am not very sure how supervised installations work: is it possible to upgrade docker? |
I believe you need Docker v23 at least. Please confirm the docker version you have as well. |
Docker is already at the latest version:
|
That's weird. Docker's
|
I don't mind reverting the PR above, but if I were you I would probably dig a little deeper to find out why it doesn't work. Maybe there is a minimum systemd version required for this to work. |
What is your Linux kernel version? Can you also check the systemd version? |
Some more information is provided in https://github.com/intel/media-delivery/blob/3cef91ef32a5dcebb570ae5a3a4f82d339c6b105/doc/howto.rst#id2. There, docs still does not account to the fact that CAP_PERFMON is now supported. |
|
FWIW, I dont run HAOS or the addon but I was unable to get CAP_PERFMON working with the intel gpu stats/docker and reverted back to running my container in privileged mode Debian 12 Snippet from my docker compose file, the cap_add is "valid" but I still don't get stats, I had to add privileged to get them working
Also if I do this it also works (without the privileged flag):
|
@xconverge can you confirm the name of the capability with docker inspect? This is how it looks for me (HAOS), which is working: |
First (with the snippet I sent unchanged) I saw
so then I took the hint and changed my docker compose to "PERFMON" and now I get:
and it still doesn't work I also checked this
|
uname -a: systemd --version:
I did inspect as well:
|
HAOS is also systemd 252, so that must not be the problem. |
@NickM-27 I am out of ideas. Here are the options, I believe:
Let me know if you'd like any action on my side. |
let's revert for now |
This reverts commit 3323e7b, which does not seem to be supported across all systems. Closes blakeblackshear/frigate#8494
home-assistant/operating-system#2319 (comment) This might explain it for me
Changing it to 2 did indeed work for me. I suspect this is what caught up @wimb0 system too! |
Indeed, that works for me too. What I did: |
@NickM-27 how about I add a note to the docs for this case (when running supervised but not HAOS), rather than reverting the PR? |
I think that's fine, I'd suggest adding it to the hwaccel docs that already covers intel GPU stats |
Maybe, if it is a default setting in HAOS, it should be added to the HA Supervised Install docs. |
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. |
Describe the problem you are having
Since updating from beta 3 to beta 4, the Intel GPU stats do not work anymore:
ERROR : Unable to poll intel GPU stats: Failed to initialize PMU! (Permission denied)
I am using the Frigate Beta (0.13.0) Addon on Home Assistant supervised on Debian.
Version
0.13.0-65E3E67
Frigate config file
not relevant for this issue
Relevant log output
VAINFO for GPU
Frigate stats
No response
Operating system
Debian
Install method
HassOS Addon
Coral version
USB
Network connection
Wired
Camera make and model
Annke C500 and Reolink Doorbell
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: