Google has abandoned the Coral TPU
from MuttMutt@lemmy.world to selfhosted@lemmy.world on 03 May 10:55
https://lemmy.world/post/46390410
from MuttMutt@lemmy.world to selfhosted@lemmy.world on 03 May 10:55
https://lemmy.world/post/46390410
The Coral TPU driver has basically been abandoned by Google so if you are running a Linux kernel newer than 6.2 it will not function.
github.com/google/gasket-driver is the original driver which was archived on April 18, 2026
You can try the driver github.com/feranick/gasket-driver or github.com/dude84/gasket-driver-coral or search through the forks of the original gasket-dkms driver github.com/google/gasket-driver/forks
So in the future your options are to pin your kernel to 6.2, upgrade your hardware, hope that someone will keep a gasket-dkms fork updated for newer kernel versions, or make your own fork to do so yourself.
threaded - newest
I wonder, is it due to architecture limitations? They don’t see a roadmap ahead for it anymore in light of changing AI hardware demands?
I assume the hardware is end of life and not just the Linux driver.
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.
For a few cameras with basic detection, an Intel 6th gen processor or newer is sufficient to run openvino on the iGPU. Works great. docs.frigate.video/…/object_detectors/#openvino-d…
This is great, if it works, on my 8500t I had nothing but problems.
I use it on a 12th gen CPU and it worked first try. ¯\_(ツ)_/¯
Yeah it seemed to work for me and would then hard lock the system between 24h and a week later requiring a manual power cycle. Several people experienced the same, we had a couple of issues on the frigate github but I don’t think anyone ever figured out why. Definitely openvino on the igpu though, openvino on CPU was fine.
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.
that’s fine, I’m abandoning Google
Technology websites should just add a top level menu - “Google Abandoned”
https://killedbygoogle.com/
Man, why did they buy Tenor just to kill it?
What the fuck.
So they could sell you something else, duh…
P.S. They probably wanted to add the IP to their portfolio.
Common pattern - the acqui-hire.
“These people are working in a problem area that we want to do better in. We’ll buy their company for their expertise.”
Whether they keep existing products or not is not a major factor in the decision and gets evaluated later. Often, because they want the people working on something new the existing products are put into maintenance mode or shut down.
Source: Have been acquired for both talent and for product. Seen both.
Google is running out of naming schemes for their projects.
Not enough words in the dictionary.
even though they have the full alphabet??
As much as you may dislike Google, I got to hand it to them, they have and always have a ton of skunk works projects.
Well, good to know. I planned to buy one and attach it to my homeserver ಠ╭╮ಠ
I think this plan needs to be replaced.
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.
Do you know whether they plan to introduce a newer TPU instead?
Not that I know of.
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.
Unfortunatly this is not possible for my setup. I have a Asrock J4050 with its soldered cpu. So I need something like a separate device. USB, SBC with lan, anything like that… Because of that, I was happy when i discovered coral. And to be honest: I did not researched deeply. So I am unaware of its limitation to frigate. I wanted to create my own model and run it on coral. The training was planned to be done on another device.
Now I need to check if a raspi could be sufficent or if anything else comes up.
Great, I bought one like 6mo ago and have it running on frigate…
<sigh>
Bought mine 3 weeks ago, I haven’t had the time to add it to my frigate…
Exact same boat as you… Urgh. Maybe community drivers are possible?
github.com/feranick/gasket-driver is the best option for now. But you also need the same gcc version installed as what was used to compile the kernel.
The frigate container comes with the drivers for it. So its probably fine for the time being
It’s only Google
The feranick fork works just fine, even on kernel v7
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.
Glad Google decided to kill this before I got one for frigate lol
What is a good m. 2 alternative? I was looking to use my old rx580 but it appears that rocm dropped support for it
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. reddit.com/…/has_anyone_successfully_used_the_goo…
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.
Perhaps the RX580 is usable via Vulkan? I tried Vulkan with llama.cpp on a R9700 recently and it was generally faster than ROCm.
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 saw the hailo. It is a bit pricey but it seems to be the only option. It is cheaper than a good gpu
Yes. They have two options, I have the 8, there is also the 8L which is cheaper and still 3X the coral so surely more than enough.
If you install the official .deb, it’s a set-and-forget type experience, pretty great. 6ms inference with 5 full HD cams. I don’t even bother with the substreams.
Of course. Because I just got one setup.
have you guys seen this discussion? github.com/blakeblackshear/frigate/…/18564#discus…
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.
I agree with you completely! My only hope for the short term at least is that the majority of frigate users until now rely on these devices and I hope they will keep it going as long as possible. The alternatives are way too expensive at the moment