mikey6283 Posted November 22, 2021 Share Posted November 22, 2021 The answer is there Yes I saw this post and unchecked the TPU in Dveice and rebooted . I also tried to unbind by echo "0000:01:00.0" > /sys/user/pci/drivers/vfio-pci/unbind. however, its not unbinding. I have tried this numerous times Quote Link to comment
mikey6283 Posted November 22, 2021 Share Posted November 22, 2021 44 minutes ago, mikey6283 said: Yes I saw this post and unchecked the TPU in Dveice and rebooted . I also tried to unbind by echo "0000:01:00.0" > /sys/user/pci/drivers/vfio-pci/unbind. however, its not unbinding. correction The script is incorrect i used /sys/bus/pci/drivers/vfio-pci/unbind Quote Link to comment
SavellM Posted November 22, 2021 Share Posted November 22, 2021 FYI for reference I ordered: Wifi Adapter: https://www.amazon.co.uk/dp/B089K499B5/ref=cm_sw_em_r_mt_dp_S288MH5GWCK9BVZV7PHP Coral: https://coral.ai/products/m2-accelerator-ae So far its all working and registered with unRAID and Frigate. 1 Quote Link to comment
ich777 Posted November 22, 2021 Share Posted November 22, 2021 1 hour ago, mikey6283 said: correction The script is incorrect i used /sys/bus/pci/drivers/vfio-pci/unbind Can you please share your Diagnostics, your Coral TPU is bound to VFIO and unRAID can't see it really. Quote Link to comment
mikey6283 Posted November 22, 2021 Share Posted November 22, 2021 17 minutes ago, ich777 said: Can you please share your Diagnostics, your Coral TPU is bound to VFIO and unRAID can't see it really. Diagnostics as requested. Thanks tower-diagnostics-20211122-1743.zip Quote Link to comment
ich777 Posted November 22, 2021 Share Posted November 22, 2021 1 minute ago, mikey6283 said: Diagnostics as requested. Thanks tower-diagnostics-20211122-1743.zip 58.56 kB · 0 downloads You have installed the VFIO plugin please remove it from there, also I would strongly suggest that you remove the VFIO plugin entierely and use the Tools -> System Devices to bind devices to VFIO. BIND=0000:01:00.0|1ac1:089a 0000:02:00.0|1ac1:089a This is from your /boot/config/vfio-pci.cfg Quote Link to comment
mikey6283 Posted November 22, 2021 Share Posted November 22, 2021 16 minutes ago, ich777 said: You have installed the VFIO plugin please remove it from there, also I would strongly suggest that you remove the VFIO plugin entierely and use the Tools -> System Devices to bind devices to VFIO. BIND=0000:01:00.0|1ac1:089a 0000:02:00.0|1ac1:089a This is from your /boot/config/vfio-pci.cfg Thank that fixed it , I only downloaded vfio-pci.cfg to see if there was a way to delete the original . Obviously i made it worst. Thanks i now see the TPU running now to sort out my config and FFMPEG For inforamtion only i binded the TPU in TOOL-> System Devices originally as i am struggling with Docker Frigate as it is Frigate is running in HASSIO but on CPU. so i was trying to,load the TPU's in a VM Quote Link to comment
jbrukardt Posted November 22, 2021 Share Posted November 22, 2021 On 11/19/2021 at 4:52 AM, ich777 said: I bought this Adapter for my Dual Edge TPU, this is basically a WiFi key (you don't need to plug in the USB cable). But keep in mind if you buy this adapter you only have a single PCIe lane so only one TPU will work. This adapter should also work with the module that @mikey6283 recommended... The pinout looks wrong on that for the e-key dual TPU. Is the picture bad, that looks like it has the block for where the a-key slot would be which would keep the e-key dual tpu from inserting. Quote Link to comment
ich777 Posted November 22, 2021 Share Posted November 22, 2021 1 hour ago, jbrukardt said: The pinout looks wrong on that for the e-key dual TPU. I think the picture is wrong, the description says: Support system: WINXP WIN7 WIN8 WIN10 32/64BIT /LINUX/MAC support interface: PCI-E 1X M.2 KEY-A/KEY A-E. But keep in mind this will only enable one TPU not both of them. I use this card with a Dual Edge TPU (as said only one enabled) and it works just fine. ) 1 Quote Link to comment
jbrukardt Posted November 22, 2021 Share Posted November 22, 2021 23 minutes ago, ich777 said: I think the picture is wrong, the description says: Support system: WINXP WIN7 WIN8 WIN10 32/64BIT /LINUX/MAC support interface: PCI-E 1X M.2 KEY-A/KEY A-E. But keep in mind this will only enable one TPU not both of them. I use this card with a Dual Edge TPU (as said only one enabled) and it works just fine. ) yep yep, just waiting until magic-blue-smoke gets his adapters back in stock in january and looking for something to hold me over. understand itll only leverage one 1 Quote Link to comment
jbrukardt Posted November 22, 2021 Share Posted November 22, 2021 On 11/19/2021 at 1:01 PM, jbrukardt said: Trying to get this setup while waiting for my tpu (have a dual m.2 already, but no adapter yet) Im having some trouble with it consuming massive CPU (50+ % of all the cores on a i5-6500) with only 1 camera, no detect, and using a substream at 5fps. Heres my config.yml: mqtt: host: 192.168.1.11 user: mqtt password: password cameras: back: ffmpeg: inputs: - path: rtsp://username:[email protected]/cam/realmonitor?channel=1&subtype=2 roles: # - detect - rtmp # detect: # width: 1920 # height: 1080 Here's my logs [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. [2021-11-19 09:57:33] frigate.app INFO : Starting Frigate (0.9.4-26ae608) Starting migrations [2021-11-19 09:57:33] peewee_migrate INFO : Starting migrations There is nothing to migrate [2021-11-19 09:57:33] peewee_migrate INFO : There is nothing to migrate [2021-11-19 09:57:33] detector.cpu INFO : Starting detection process: 217 [2021-11-19 09:57:33] frigate.mqtt INFO : MQTT connected [2021-11-19 09:57:33] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes. [2021-11-19 09:57:33] frigate.app INFO : Output process started: 219 [2021-11-19 09:57:33] ws4py INFO : Using epoll [2021-11-19 09:57:33] frigate.app INFO : Camera processor started for back: 224 [2021-11-19 09:57:33] frigate.app INFO : Capture process started for back: 226 [2021-11-19 09:57:33] ws4py INFO : Using epoll Standard frigate app right off the store, standard settings. All, I figured this out and wanted to post the solution. Here is the config you need to get QSV working with frigate in the frigate.yml database: path: /db/frigate.db mqtt: host: 192.168.0.100 user: frigate password: {MQTT_PASSWORD} detectors: coral: type: edgetpu device: usb birdseye: mode: continuous ffmpeg: hwaccel_args: - -hwaccel - qsv - -qsv_device - /dev/dri/renderD128 record: enabled: True retain_days: 60 cameras: garage_camera: ffmpeg: inputs: - path: rtsp://frigate:{FRIGATE_RTSP_PASSWORD}@192.168.0.173/live0 roles: - detect - rtmp hwaccel_args: - -c:v - h264_qsv detect: width: 1920 height: 1080 front_porch_camera: ffmpeg: inputs: - path: rtsp://frigate:{FRIGATE_RTSP_PASSWORD}@192.168.0.125/live0 roles: - detect - rtmp hwaccel_args: - -c:v - h264_qsv detect: width: 1920 height: 1080 The hwaccel_args: bit is the most important bit, it wont work without that, and most of the configs and tutorials dont show that bit. Quote Link to comment
mikey6283 Posted November 23, 2021 Share Posted November 23, 2021 12 hours ago, jbrukardt said: The hwaccel_args: bit is the most important bit, it wont work without that, and most of the configs and tutorials dont show that bit. This is sound advice i have spent weeks trying to sort out broken ffmep error . I use the hwaccel _args using the one for intel below <10th Gen which my system is run on until i noticed that you were using the same Chip i5-6500 so i tried your solution voila it work. leaving well alone for awhile before adding other cameras and tweeking. Thanks Quote Link to comment
jbrukardt Posted November 23, 2021 Share Posted November 23, 2021 4 hours ago, mikey6283 said: This is sound advice i have spent weeks trying to sort out broken ffmep error . I use the hwaccel _args using the one for intel below <10th Gen which my system is run on until i noticed that you were using the same Chip i5-6500 so i tried your solution voila it work. leaving well alone for awhile before adding other cameras and tweeking. Thanks Alternatively, the advice on this page also seems to work, with slightly different results https://docs.frigate.video/configuration/hardware_acceleration/ When using the less than 10th generation config there, it puts loads on both 3drender, and video in intel_gpu_top, whereas the config i posted above that uses QSV rather than VAAPI only put loads on the video bar. Im honestly not sure which one is better. Quote Link to comment
rob2021 Posted November 24, 2021 Share Posted November 24, 2021 Hi All, thanks to plenty of people on this forum and others - my frigate on unraid is working well. Sharing my config/setup here in case it helps someone else. Hardware: Intel® Core™ i7-4790 Nvidia 1030 Google Coral (USB) Software: unraid: 6.9.2 frigate: 0.9.4-26AE608 Cameras: 3 xiaomi/yi dome 1080p running yihackv4 Config: mqtt: # Required: host name host: 192.168.XX.XX # Optional: port (default: shown below) port: 1883 # Optional: topic prefix (default: shown below) # WARNING: must be unique if you are running multiple instances topic_prefix: frigate # Optional: client id (default: shown below) # WARNING: must be unique if you are running multiple instances client_id: frigateunraid # Optional: user user: XX password: XX # Optional: interval in seconds for publishing stats (default: shown below) stats_interval: 60 ########################################## # Optional: RTMP re-stream configuration rtmp: # Required: Enable the RTMP stream (default: True) enabled: True # # Optional: birdseye configuration birdseye: # Optional: Enable birdseye view (default: shown below) enabled: True # Optional: Width of the output resolution (default: shown below) #width: 768 # Optional: Height of the output resolution (default: shown below) #height: 1024 # Optional: Encoding quality of the mpeg1 feed (default: shown below) # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources. quality: 15 # Optional: Mode of the view. Available options are: objects, motion, and continuous # objects - cameras are included if they have had a tracked object within the last 30 seconds # motion - cameras are included if motion was detected in the last 30 seconds # continuous - all cameras are included always mode: objects # record: # Optional: Enable recording (default: shown below) enabled: True # Optional: Number of days to retain (default: shown below) retain_days: 1 # Optional: Event recording settings events: # Optional: Maximum length of time to retain video during long events. (default: shown below) # NOTE: If an object is being tracked for longer than this amount of time, the cache # will begin to expire and the resulting clip will be the last x seconds of the event unless retain_days under record is > 0. max_seconds: 300 # Optional: Number of seconds before the event to include (default: shown below) pre_capture: 15 # Optional: Number of seconds after the event to include (default: shown below) post_capture: 15 # Optional: Objects to save recordings for. (default: all tracked objects) objects: - person #- car - cat #- dog #- bird #- motorcycle #- bicycle # Optional: Restrict recordings to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Retention settings for events retain: # Required: Default retention days (default: shown below) default: 3 # Optional: Per object retention days objects: person: 7 cat: 7 # # Optional: Configuration for the jpg snapshots written to the clips directory for each event # NOTE: Can be overridden at the camera level snapshots: # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below) # This value can be set via MQTT and will be updated in startup based on retained value enabled: True # Optional: clean copy clean_copy: True # Optional: print a timestamp on the snapshots (default: shown below) timestamp: True # Optional: draw bounding box on the snapshots (default: shown below) bounding_box: True # Optional: crop the snapshot (default: shown below) crop: false # Optional: height to resize the snapshot to (default: original size) #height: 2048 # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Camera override for retention settings (default: global values) retain: # Required: Default retention days (default: shown below) default: 3 # Optional: Per object retention days objects: person: 7 cat: 7 # Optional: Object configuration # NOTE: Can be overridden at the camera level objects: # Optional: list of objects to track from labelmap.txt (default: shown below) track: - person #- car #- dog - cat #- bird #- bicycle #- motorcycle # Optional: mask to prevent all object types from being detected in certain areas (default: no mask) # Checks based on the bottom center of the bounding box of the object. # NOTE: This mask is COMBINED with the object type specific mask below #mask: 0,0,1000,0,1000,200,0,200 # Optional: filters to reduce false positives for specific object types filters: person: # Optional: minimum width*height of the bounding box for the detected object (default: 0) #min_area: 5000 # Optional: maximum width*height of the bounding box for the detected object (default: 24000000) #max_area: 100000 # Optional: minimum score for the object to initiate tracking (default: shown below) min_score: 0.5 # Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below) threshold: 0.8 # Optional: mask to prevent this object type from being detected in certain areas (default: no mask) # Checks based on the bottom center of the bounding box of the object #mask: 0,0,1000,0,1000,200,0,200 cat: # Optional: minimum width*height of the bounding box for the detected object (default: 0) #min_area: 5000 # Optional: maximum width*height of the bounding box for the detected object (default: 24000000) #max_area: 100000 # Optional: minimum score for the object to initiate tracking (default: shown below) min_score: 0.2 # Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below) threshold: 0.4 # Optional: mask to prevent this object type from being detected in certain areas (default: no mask) # Checks based on the bottom center of the bounding box of the object #mask: 0,0,1000,0,1000,200,0,200 # cameras: kitchen: ffmpeg: #input_args: -c:v h264_cuvid -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -use_wallclock_as_timestamps 1 #output_args: #record: -filter:v -fps 5 inputs: - path: rtsp://192.168.2.207/ch0_0.h264 roles: - rtmp - record - path: rtsp://192.168.2.207/ch0_1.h264 roles: - detect detect: enabled: True max_disappeared: 25 width: 640 height: 360 fps: 5 best_image_timeout: 10 livingroom: ffmpeg: #input_args: -c:v h264_cuvid -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -use_wallclock_as_timestamps 1 #output_args: #record: -filter:v -fps 5 inputs: - path: rtsp://192.168.2.206/ch0_0.h264 roles: - rtmp - record - path: rtsp://192.168.2.206/ch0_1.h264 roles: - detect detect: enabled: True max_disappeared: 25 width: 640 height: 360 fps: 5 best_image_timeout: 10 water: ffmpeg: #input_args: -c:v h264_cuvid -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -use_wallclock_as_timestamps 1 #output_args: #record: -filter:v -fps 5 inputs: - path: rtsp://192.168.2.205/ch0_0.h264 roles: - rtmp - record - path: rtsp://192.168.2.205/ch0_1.h264 roles: - detect detect: enabled: True max_disappeared: 25 width: 640 height: 360 fps: 5 best_image_timeout: 10 ########################################## # https://github.com/blakeblackshear/frigate/blob/v0.9.0-rc4/docs/docs/configuration/nvdec.md # Optional: ffmpeg configuration ffmpeg: # Optional: global ffmpeg args (default: shown below) #global_args: -hide_banner -loglevel warning # Optional: global hwaccel args (default: shown below) # NOTE: See hardware acceleration docs for your specific device hwaccel_args: -c:v h264_cuvid -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1 -c:v h264_cuvid # - -hwaccel # - vaapi # - -hwaccel_device # - /dev/dri/renderD128 # - -hwaccel_output_format # - yuv420p # Optional: global input args (default: shown below) #input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1 # Optional: global output args output_args: # Optional: output args for detect streams (default: shown below) #detect: -f rawvideo -pix_fmt yuv420p # Optional: output args for record streams (default: shown below) #record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy # Optional: output args for rtmp streams (default: shown below) #rtmp: -c copy -f flv # NEW # Optional: output args for detect streams (default: shown below) detect: -f rawvideo -pix_fmt yuv420p -filter:v fps=fps=5 # Optional: output args for record streams (default: shown below) record: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an # Optional: output args for clips streams (default: shown below) # clips: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an # Optional: output args for rtmp streams (default: shown below) #rtmp: -c copy -f flv rtmp: -c copy -map 0 -f flv # # detectors: coral: type: edgetpu device: usb # objects: track: - person - cat # logger: default: warning logs: frigate.mqtt: error frigate.edgetpu: info #frigate.mqtt: info # # Optional: in-feed timestamp style configuration # NOTE: Can be overridden at the camera level timestamp_style: # Optional: Position of the timestamp (default: shown below) # "tl" (top left), "tr" (top right), "bl" (bottom left), "br" (bottom right) position: "bl" # Optional: Format specifier conform to the Python package "datetime" (default: shown below) # Additional Examples: # german: "%d.%m.%Y %H:%M:%S" format: "%d/%m/%Y %H:%M:%S" # Optional: Color of font color: # All Required when color is specified (default: shown below) red: 255 green: 255 blue: 255 # Optional: Line thickness of font (default: shown below) thickness: 2 # Optional: Effect of lettering (default: shown below) # None (No effect), # "solid" (solid background in inverse color of font) # "shadow" (shadow for font) effect: solid # # Thanks all. Quote Link to comment
rob2021 Posted November 24, 2021 Share Posted November 24, 2021 One more thing - despite reading it several times, I still missed this one, so just to hopefully help someone else... If you run nvidia-smi and you don't see any processes listed, MAKE SURE you are using the UNRAID console. DO NOT USE the console of the docker image. DO Use the console of the parent OS/unraid. (this is probably obvious to most, but I wasted more time on this than I care to admit) The output should look like this: # nvidia-smi Wed Nov 24 14:44:58 2021 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 495.44 Driver Version: 495.44 CUDA Version: 11.5 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| | 0 NVIDIA GeForce ... Off | 00000000:01:00.0 Off | N/A | | N/A 48C P0 N/A / 30W | 134MiB / 1998MiB | 1% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=============================================================================| | 0 N/A N/A 27324 C ffmpeg 44MiB | | 0 N/A N/A 27333 C ffmpeg 44MiB | | 0 N/A N/A 27336 C ffmpeg 44MiB | +-----------------------------------------------------------------------------+ Enjoy Quote Link to comment
purplechris Posted November 24, 2021 Share Posted November 24, 2021 Having an issue where the usb is detected but just sits with found and doesnt progress, not sure if this log is enough to address my issue [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. [2021-11-24 18:32:51] frigate.app INFO : Starting Frigate (0.9.4-26ae608) Starting migrations [2021-11-24 18:32:51] peewee_migrate INFO : Starting migrations There is nothing to migrate [2021-11-24 18:32:51] peewee_migrate INFO : There is nothing to migrate [2021-11-24 18:32:51] frigate.mqtt INFO : MQTT connected [2021-11-24 18:32:51] frigate.app INFO : Output process started: 214 [2021-11-24 18:32:51] frigate.app INFO : Camera processor started for back: 216 [2021-11-24 18:32:51] frigate.app INFO : Camera processor started for entrance: 217 [2021-11-24 18:32:51] frigate.app INFO : Camera processor started for side: 218 [2021-11-24 18:32:51] frigate.app INFO : Capture process started for back: 219 [2021-11-24 18:32:51] frigate.app INFO : Capture process started for entrance: 220 [2021-11-24 18:32:51] frigate.app INFO : Capture process started for side: 221 [2021-11-24 18:32:51] ws4py INFO : Using epoll [2021-11-24 18:32:51] ws4py INFO : Using epoll [2021-11-24 18:32:51] detector.coral INFO : Starting detection process: 213 [2021-11-24 18:32:51] frigate.edgetpu INFO : Attempting to load TPU as usb [2021-11-24 18:32:54] frigate.edgetpu INFO : TPU found Quote Link to comment
yayitazale Posted November 24, 2021 Author Share Posted November 24, 2021 10 minutes ago, purplechris said: Having an issue where the usb is detected but just sits with found and doesnt progress, not sure if this log is enough to address my issue [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. [2021-11-24 18:32:51] frigate.app INFO : Starting Frigate (0.9.4-26ae608) Starting migrations [2021-11-24 18:32:51] peewee_migrate INFO : Starting migrations There is nothing to migrate [2021-11-24 18:32:51] peewee_migrate INFO : There is nothing to migrate [2021-11-24 18:32:51] frigate.mqtt INFO : MQTT connected [2021-11-24 18:32:51] frigate.app INFO : Output process started: 214 [2021-11-24 18:32:51] frigate.app INFO : Camera processor started for back: 216 [2021-11-24 18:32:51] frigate.app INFO : Camera processor started for entrance: 217 [2021-11-24 18:32:51] frigate.app INFO : Camera processor started for side: 218 [2021-11-24 18:32:51] frigate.app INFO : Capture process started for back: 219 [2021-11-24 18:32:51] frigate.app INFO : Capture process started for entrance: 220 [2021-11-24 18:32:51] frigate.app INFO : Capture process started for side: 221 [2021-11-24 18:32:51] ws4py INFO : Using epoll [2021-11-24 18:32:51] ws4py INFO : Using epoll [2021-11-24 18:32:51] detector.coral INFO : Starting detection process: 213 [2021-11-24 18:32:51] frigate.edgetpu INFO : Attempting to load TPU as usb [2021-11-24 18:32:54] frigate.edgetpu INFO : TPU found There is no issues/errors on that log... Quote Link to comment
purplechris Posted November 25, 2021 Share Posted November 25, 2021 20 hours ago, yayitazale said: There is no issues/errors on that log... my mistake buddy, IP issue Quote Link to comment
yayitazale Posted November 25, 2021 Author Share Posted November 25, 2021 23 minutes ago, purplechris said: my mistake buddy, IP issue Ok! Quote Link to comment
CryPt00n Posted November 26, 2021 Share Posted November 26, 2021 Hi, my Frigate stopped working, it cannot find the TPU. Everything was working fine, removed my GPU some days ago so i had to restart the server. Since then frigate was not starting. TPU is unchecked at Tools > System Devices, but if i hover over the green dot it says that "vfio-pci" driver is in use. Tried to unbind, checked and unchecked the tpu, rebooted and reinstalled the driver, but had no effect. frigate.edgetpu ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. Unraid 6.9.2 Frigate 0.9.4 Coral Driver 2021.10.01 M.2 Single TPU Any Ideas on this? Thanks in advance Quote Link to comment
yayitazale Posted November 26, 2021 Author Share Posted November 26, 2021 1 hour ago, CryPt00n said: Hi, my Frigate stopped working, it cannot find the TPU. Everything was working fine, removed my GPU some days ago so i had to restart the server. Since then frigate was not starting. TPU is unchecked at Tools > System Devices, but if i hover over the green dot it says that "vfio-pci" driver is in use. Tried to unbind, checked and unchecked the tpu, rebooted and reinstalled the driver, but had no effect. frigate.edgetpu ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. Unraid 6.9.2 Frigate 0.9.4 Coral Driver 2021.10.01 M.2 Single TPU Any Ideas on this? Thanks in advance Can we see your config entry of the edge? Did you bind the same folder on the container? Quote Link to comment
ich777 Posted November 26, 2021 Share Posted November 26, 2021 1 hour ago, CryPt00n said: Any Ideas on this? Is the TPU detected by the plugin? Please also post a picture from the Coral Driver plugin in addition to your template configuration. Quote Link to comment
CryPt00n Posted November 26, 2021 Share Posted November 26, 2021 (edited) TPU was mapped with apex_0, this one is no longer here. Docker: System Devices: Coral cant find the TPU: frigate config: detectors: coral: type: edgetpu device: pci 1 minute ago, ich777 said: Is the TPU detected by the plugin? Please also post a picture from the Coral Driver plugin in addition to your template configuration. No its not, thats the reason why i tried to reinstall etc. Sorry, forgot this in the initial post Edited November 26, 2021 by CryPt00n Quote Link to comment
ich777 Posted November 26, 2021 Share Posted November 26, 2021 1 hour ago, CryPt00n said: No its not, thats the reason why i tried to reinstall etc. Sorry, forgot this in the initial post Please reboot your server (with the Coral Driver plugin installed) and after it rebooted pull the Diagnostics and post them here. 1 hour ago, CryPt00n said: TPU was mapped with apex_0, this one is no longer here. You've also mapped the TPU wrong, you have it mapped as Path but instead you have to mount it as Device. Quote Link to comment
CryPt00n Posted November 26, 2021 Share Posted November 26, 2021 25 minutes ago, ich777 said: Please reboot your server (with the Coral Driver plugin installed) and after it rebooted pull the Diagnostics and post them here. You've also mapped the TPU wrong, you have it mapped as Path but instead you have to mount it as Device. Found the mapping path in a blog article for the setup, will set it correct then afterwards. Logs are attached server-diagnostics-20211126-1803.zip Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.