https://killedbygoogle.com/

Glad you found out before the purchase. I made my purchase September 2024 and still rely on it for FrigateNVR.

I'm hoping that somehow a few people will get together to keep it going for a while. I sadly don't understand most of the programming and such.

Nowadays just get an Intel Arc A380 for 150€ and you can use it for a lot more than only Frigate. That thing is a little beast for my server.

Bought mine 3 weeks ago, I haven't had the time to add it to my frigate...

The frigate container comes with the drivers for it. So its probably fine for the time being

Exact same boat as you.. Urgh. Maybe community drivers are possible?

That's the worst part about it - the fix is so simple. Google just completely abandoned it.

It was just a single kernel function call on a single line with slightly modified arguments. Just make a small update and it works perfectly fine.

I spent much more time researching the fix than I did applying it. But now I have to rebuild and reinstall it every single time I update my kernel.

Perhaps the RX580 is usable via Vulkan? I tried Vulkan with llama.cpp on a R9700 recently and it was generally faster than ROCm.

There aren't any. Nobody is manufacting or developing for these devices because they're slower than the rest of the hardware you already have, see e.g. https://reddit.com/r/frigate_nvr/comments/1os24t4/has_anyone_successfully_used_the_google_coral_m2/

Your CPU is probably good enough for some stuff like openvino, if it's at all recent. 6th gen Intel is the bare minimum, but obviously newer is better. Or, sell that card and buy a new one. I do, unfortunately, recommend nvidia, since that's what the vast majority of developers are targeting.

I replaced (sold) my coral usb late last year after using it for 3 years. I upgraded my home server and wanted to go M.2 and noticed that frigate started to support a new chip, with many times the performance of the coral. I went with a Hailo-8. It's been flawless.

Recommendation: use the .deb driver that Hailo provides, it gets installed via dkms and survives kernel updates.

I'm guessing it's because more powerful hardware is coming out all the time. But for a lot of homelabs more power isn't really needed to watch a few cameras for basic detection.

And yes the hardware hasn't been made in a while but new old stock is still being sold. Hence the reason for the post.

It's due to the inner workings of the Coral TPU being basically a black box, so even if the community wanted to, we can't just reverse engineer a driver.

I haven't seen that specific thread, but while Google making the driver open source is a noble gesture compared to the 'black box' approach of companies like Nvidia, open source isn't a magic fix. We’ve seen countless projects die simply because no one has the time or the specialized knowledge to maintain them.

​Right now, the community is handling minor patches, but we are one major Linux kernel architectural change away from needing a ground-up rewrite of the Gasket driver. If/or when that happens, and no one steps up to do the heavy lifting, thousands of these devices will become security risks or paperweights. It’s particularly frustrating because they are still being sold brand new to unsuspecting users who assume they’re buying a supported, plug-and-play product.