[HW Accel Support]: EdgeTPU not detected, any way to test in host? #15787
Replies: 3 comments 5 replies
-
|
You're overriding input args when you shouldn't be, this will cause issues before frigate sends any images to the coral. |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Will any of those affect the TPU? I've been making all sorts of changes to this to try and get the TPU working and I was planning on coming back to all that when I have figured out what's wrong. |
Beta Was this translation helpful? Give feedback.
-
|
You haven't provided any information that shows the tpu is having issues, but it's clear no camera connection will work |
Beta Was this translation helpful? Give feedback.
-
|
I added those input args from a template config I found online, shall I just delete them all? I've had the camera working in the past but I've been making changes to try and get the TPU working for a while. Here's the output showing that the TPU isn't working: |
Beta Was this translation helpful? Give feedback.
-
|
What is the config when you are trying to use the coral? |
Beta Was this translation helpful? Give feedback.
-
|
This is the config I just used for thaterror message:
mqtt:
enabled: false
detectors:
coral:
type: edgetpu
device: pci
cameras:
Tapo:
enabled: true
ffmpeg:
inputs:
- path: rtsp://isdjfsfoisosif
roles:
- detect
detect:
enabled: true
width: 2304
height: 1296
fps: 5
version: 0.14
…On Sat, 4 Jan 2025 at 14:27, Nicolas Mowen ***@***.***> wrote:
What is the config when you are trying to use the coral?
—
Reply to this email directly, view it on GitHub
<#15787 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG6XCHVBNMENZMJ3EN77M6D2I7VUJAVCNFSM6AAAAABUQ3XKC2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZTGM3DENA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
can you confirm the contents of |
Beta Was this translation helpful? Give feedback.
-
|
I'm new to containers so I don't know how to get interactive on the Frigate
container, so I modded my compose file to start a Debian container instead
so I could get this, I don't know if it changes anything.
On the container I have:
***@***.***:/# ls /dev
apex_0 console core dri fd full mqueue null ptmx pts random shm
stderr stdin stdout tty urandom zero
***@***.***:/# ls -l /dev/apex_0
crw-r--r-- 1 nobody nogroup 120, 0 Jan 4 09:12 /dev/apex_0
And on the host:
server:~$ ls /dev
apex_0 core full kvm loop6 null random sdb snapshot tty10
tty18 tty25 tty32 tty4 tty47 tty54 tty61 ttyS2 vcs2 vcsa3
vcsu4 watchdog
autofs cpu_dma_latency fuse log loop7 nvram rfkill sdb1 snd
tty11 tty19 tty26 tty33 tty40 tty48 tty55 tty62 ttyS3 vcs3
vcsa4 vcsu5 watchdog0
block cuse hpet loop0 loop-control port rtc sdc stderr
tty12 tty2 tty27 tty34 tty41 tty49 tty56 tty63 uhid vcs4
vcsa5 vcsu6 watchdog1
bsg disk hugepages loop1 mapper ppp rtc0 sdc1 stdin
tty13 tty20 tty28 tty35 tty42 tty5 tty57 tty7 uinput vcs5 vcsa6
vfio zero
btrfs-control dri hwrng loop2 mei0 psaux sda sg0 stdout tty14
tty21 tty29 tty36 tty43 tty50 tty58 tty8 urandom vcs6 vcsu
vga_arbiter
bus drm_dp_aux0 initctl loop3 mem ptmx sda1 sg1 tty
tty15 tty22 tty3 tty37 tty44 tty51 tty59 tty9 userfaultfd vcsa
vcsu1 vhci
char drm_dp_aux1 input loop4 mqueue ptp0 sda2 sg2 tty0
tty16 tty23 tty30 tty38 tty45 tty52 tty6 ttyS0 vcs vcsa1 vcsu2
vhost-net
console fd kmsg loop5 net pts sda5 shm tty1 tty17
tty24 tty31 tty39 tty46 tty53 tty60 ttyS1 vcs1 vcsa2 vcsu3
vhost-vsock
server:~$ ls -l /dev/apex_0
crw-r--r-- 1 root root 120, 0 Jan 4 09:12 /dev/apex_0
On the host I've set the apex_0 permissions so that anyone has read
permissions.
…On Sat, 4 Jan 2025 at 14:52, Nicolas Mowen ***@***.***> wrote:
can you confirm the contents of ls /dev/ on the host and in the frigate
container
—
Reply to this email directly, view it on GitHub
<#15787 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BG6XCHTSGKVKQ7APZKGE2QD2I7YSPAVCNFSM6AAAAABUQ3XKC2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZTGM3TOMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
My Coral TPU isn't being detected and Frigate will not boot when it is in use.
Is there anyway of testing the Coral TPU in the host without having to get the old version of Python as it's proving tricky to do with the latest Debian? I just want to confirm that my TPU is working before I start troubleshooting my container.
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
Tapo
Screenshots of the Frigate UI's System metrics pages
n/a
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions