Closed kcraig73 closed 1 year ago
Most likely you haven't configured the second /dev/apex_1 to be passed to the frigate container.
Although this didn't appear to be an issue in previous releases, exposing device: /dev/apex_1 to the container addressed the issue in 0.12.0. Thank you for the quick fix!
Most likely you haven't configured the second /dev/apex_1 to be passed to the frigate container.
This needs to go into the documentation somewhere, unless I missed it. Thank you!
Right here: https://docs.frigate.video/configuration/object_detectors#multiple-pciem2-corals
I had that part in the config and the docker container was in a boot loop when it tried connecting to the second Coral. What fixed it was adding the /dev/apex_1:/dev/apex_1
to devices in the docker compose file. The documentation for the config,yml is fine, it was the additional piece in the docker-compose.yml that was the missing piece.
devices:
- /dev/apex_0:/dev/apex_0
- /dev/apex_1:/dev/apex_1
Edit: spelling is hard sometimes
Describe the problem you are having
Staring with minimal configuration, dual TPU detected yet immediately crashes saying no TPU detected. No errors when enabling only one TPU.
Version
0.12.0
Frigate config file
docker-compose file or Docker CLI command
Relevant log output
Operating system
UNRAID
Install method
Docker CLI
Coral version
M.2
Any other information that may be helpful
Under version previous to 0.12.0, no issues identified with Dual TPU.