SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-19 14:41:53 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

frigate installer no longer installs open-vino stuff #61

New Issue
Closed
opened 2025-11-20 04:43:09 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 04:43:09 -05:00
Owner
Copy Link

Originally created by @anishp55 on GitHub (Nov 16, 2024).

Please verify that you have read and understood the guidelines.

yes.

A clear and concise description of the issue.

openvino assets are not installed

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 11

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

none working install
image
old working install
image

we can see the openvino-model directory

Please provide detailed steps to reproduce the issue.

install frigate with the latest install script and configure GPU detection
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/frigate.sh)"

configure the GPU detector and point it to an openvino model

detectors:
  ov:
    type: openvino
    device: GPU
    model:
      path: /openvino-model/FP16/ssdlite_mobilenet_v2.xml

restart frigate and check logs

OpenVino model file /openvino-model/FP16/ssdlite_mobilenet_v2.xml not found.

Originally created by @anishp55 on GitHub (Nov 16, 2024). ### Please verify that you have read and understood the guidelines. yes. ### A clear and concise description of the issue. openvino assets are not installed ### What settings are you currently utilizing? Default Settings ### Which Linux distribution are you employing? Debian 11 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. none working install ![image](https://github.com/user-attachments/assets/a672dc2a-89d1-46db-8c0c-0ef11ece858a) old working install ![image](https://github.com/user-attachments/assets/00dd9946-3fc4-483d-932d-6f5586eaf7df) we can see the openvino-model directory ### Please provide detailed steps to reproduce the issue. install frigate with the latest install script and configure GPU detection `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/frigate.sh)"` configure the GPU detector and point it to an openvino model ``` detectors: ov: type: openvino device: GPU model: path: /openvino-model/FP16/ssdlite_mobilenet_v2.xml ``` restart frigate and check logs > OpenVino model file /openvino-model/FP16/ssdlite_mobilenet_v2.xml not found.
saavagebueno commented 2025-11-20 04:43:10 -05:00
Author
Owner
Copy Link

@remz1337 commented on GitHub (Nov 17, 2024):

What GPU are you using? Can you share your LXC config please?

Also, did you use my fork that has Nvidia GPU support? because if yes, it's normal that open-vino models don't get built, as it uses TensorRT models

detectors:
  tensorrt:
    type: tensorrt
#    device: 0
model:
  path: /config/model_cache/tensorrt/yolov7-tiny-416.trt
  input_tensor: nchw
  input_pixel_format: rgb
  width: 416
  height: 416
@remz1337 commented on GitHub (Nov 17, 2024): What GPU are you using? Can you share your LXC config please? Also, did you use my fork that has Nvidia GPU support? because if yes, it's normal that open-vino models don't get built, as it uses TensorRT models ``` detectors: tensorrt: type: tensorrt # device: 0 model: path: /config/model_cache/tensorrt/yolov7-tiny-416.trt input_tensor: nchw input_pixel_format: rgb width: 416 height: 416 ```
saavagebueno commented 2025-11-20 04:43:10 -05:00
Author
Owner
Copy Link

@anishp55 commented on GitHub (Nov 17, 2024):

I'm not sure what fork I'm using since I just used the standard install options I did the first time I set this up. The only difference now is that I'm using a n5095 vs n100 machine. GPU is the iGPU from the Intel processor. I'll get the LXC conf for the 2 later. There will be a minor difference since I passed a coral through to the n100 instance

@anishp55 commented on GitHub (Nov 17, 2024): I'm not sure what fork I'm using since I just used the standard install options I did the first time I set this up. The only difference now is that I'm using a n5095 vs n100 machine. GPU is the iGPU from the Intel processor. I'll get the LXC conf for the 2 later. There will be a minor difference since I passed a coral through to the n100 instance
saavagebueno commented 2025-11-20 04:43:10 -05:00
Author
Owner
Copy Link

@remz1337 commented on GitHub (Nov 17, 2024):

ok, try to see if the openvino files would be somewhere else in the container. Run this command in the container:
find / -name "*ssdlite*"

Otherwise, please run the installation script again, but go in advanced settings and enable verbose logging. Then paste the entire installation log please.

@remz1337 commented on GitHub (Nov 17, 2024): ok, try to see if the openvino files would be somewhere else in the container. Run this command in the container: `find / -name "*ssdlite*"` Otherwise, please run the installation script again, but go in advanced settings and enable verbose logging. Then paste the entire installation log please.
saavagebueno commented 2025-11-20 04:43:10 -05:00
Author
Owner
Copy Link

@anishp55 commented on GitHub (Nov 18, 2024):

i figured it out, its because the script looks for AVX in /proc/cpuinfo (n5095 vs n100). while my processor doesn't have AVX support, it does seem to benefit from using openvino

relevant doc https://docs.openvino.ai/2024/about-openvino/release-notes-openvino/system-requirements.html

@anishp55 commented on GitHub (Nov 18, 2024): i figured it out, its because the script looks for AVX in /proc/cpuinfo (n5095 vs n100). while my processor doesn't have AVX support, it does seem to benefit from using openvino relevant doc https://docs.openvino.ai/2024/about-openvino/release-notes-openvino/system-requirements.html
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#61
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?