154

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.

https://github.com/google/gasket-driver is the original driver which was archived on April 18, 2026

You can try the driver https://github.com/feranick/gasket-driver or https://github.com/dude84/gasket-driver-coral or search through the forks of the original gasket-dkms driver https://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.

you are viewing a single comment's thread
view the rest of the comments
[-] amateurcrastinator@lemmy.world 1 points 1 week ago
[-] MuttMutt@lemmy.world 1 points 1 week ago

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.

[-] amateurcrastinator@lemmy.world 1 points 1 week ago

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

this post was submitted on 03 May 2026
154 points (98.1% liked)

Selfhosted

59284 readers
576 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS