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.

  • paraphrand@lemmy.worldEnglish
    4·
    23 days ago

    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.worldOPEnglish
      7·
      23 days ago

      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.

    • non_burglar@lemmy.worldEnglish
      3·
      22 days 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.

    • MuttMutt@lemmy.worldOPEnglish
      1·
      20 days 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.worldEnglish
        1·
        20 days 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