PCIe Corals Issue #918
Replies: 9 comments
-
What about this? detectors:
coral_pci1:
type: edgetpu
device: pci:1 |
Beta Was this translation helpful? Give feedback.
-
Yep, tried that and it is the second one 'pci:1' that isn't working. I figured that would be the easy part since I already got the first one in. The lxc recognizes the second module and I passed through the entire /dev to docker. Not sure what I can or should do differently for the second one. Is Frigate using the pipeline for multiple tpus? |
Beta Was this translation helpful? Give feedback.
-
In case I'm just blind to something obvious.... frigate:
container_name: frigate
privileged: true # this may not be necessary for all setups
restart: unless-stopped
image: blakeblackshear/frigate:stable-amd64
devices:
- /dev/apex_0:/dev/apex_0
- /dev/apex_1:/dev/apex_1
- /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime:ro
- /docker/frigate/config/config.yml:/config/config.yml:ro
- /docker/frigate/media:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- '5000:5000'
- '1935:1935' # RTMP feeds
environment:
FRIGATE_RTSP_PASSWORD: '000000' |
Beta Was this translation helpful? Give feedback.
-
Running shows something interesting that I don't know what to make of. Flags are different and the memory shows disabled on the second module.
|
Beta Was this translation helpful? Give feedback.
-
I re-did the coral driver install and everything started working again. Walked away, came back, and it was throwing the same error about failed to detect the second one again. |
Beta Was this translation helpful? Give feedback.
-
So, I finally had the bright idea to move the coral device to a new pcie slot and now it is working. Running '''dmesg | grep apex''' was the final clue that it had to be hardware. |
Beta Was this translation helpful? Give feedback.
-
Spoke to soon. It crashed again overnight. To rule out the proxmox complexity I did a fresh install of Linux and then straight to docker and installing frigate. Same issue. At this point I'm throwing in the towel but if anyone else has this issue and figures it out, please let me know. Thanks. These logs are after the TPUs are found and start working. Detections will work just fine. Then, after some random amount of time (seconds, minutes, or hours) it starts throwing this error:
|
Beta Was this translation helpful? Give feedback.
-
Was this ever resolved? I never got my pcie coral tpu to work inside my docker. I'm using a Win10 PC. |
Beta Was this translation helpful? Give feedback.
-
Hi Justahobby01, |
Beta Was this translation helpful? Give feedback.
-
When I enable a second Coral PCIe like this:
I am getting this error:
Commenting out the second coral gets things back up and running. Should I be specifying which camera should use which detector?
Beta Was this translation helpful? Give feedback.
All reactions