[HW Accel Support]: Cannot get Coral to be detected by Frigate #15632
Replies: 2 comments 2 replies
-
definitely shouldn't be mapping /dev/bus/usb as a volume and device at the same time. Does it work if you do either by itself? |
Beta Was this translation helpful? Give feedback.
-
I'm having a similar issue. I can get the Coral to work with /dev/bus/usb/003/00X passed through to the container, but I'm encountering some issues due to USB bus numbers changing on me. I made a udev rule to symlink the device to /dev/coral1, but I can't seem to get Frigate to see that device. I've tried mapping /dev/coral1 to /dev/coral1 in the container or /dev/bus/usb/003/002 in the container. In both cases, removing the ~/.config/containers/systemd/frigate.container
/etc/udev/rules.d/90-coral.rules
|
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
I've been fighting this issue for over a week now and am pulling my hair out over it. Coral is detected on my Proxmox and in docker, but when I run lsusb in the frigate all I get is this is no device name. Frigate crashes saying there's no edgeTPU found. On hardware acceleration with GPU it works just fine.
Frigate container:
On Proxmox with lsusb:
In Docker with lsusb:
My mappings all correctly point to bus 002 and device 002, however frigate cannot detect coral. I've tried multiple USB cables and my Mini PC USB 3.0 port should power Coral enough to be used.
Version
0.14.1-f4f3cfa
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Install method
Docker Compose
Object Detector
Coral
Network connection
Wired
Camera make and model
Wyze
Screenshots of the Frigate UI's System metrics pages
No screenshots needed
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions