Selfhosted

61126 readers

434 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

152

Google has abandoned the Coral TPU (lemmy.world)

submitted 3 months ago by MuttMutt@lemmy.world to c/selfhosted@lemmy.world

38 comments fedilink hide all child comments

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

[–] paraphrand@lemmy.world 7 points 3 months ago* (last edited 3 months ago) (2 children)

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.

[–] MuttMutt@lemmy.world 14 points 3 months ago (1 children)

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.

[–] frongt@lemmy.zip 7 points 3 months ago

For a few cameras with basic detection, an Intel 6th gen processor or newer is sufficient to run openvino on the iGPU. Works great. https://docs.frigate.video/configuration/object_detectors/#openvino-detector

[–] non_burglar@lemmy.world 7 points 3 months ago

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.