[Not Accepted] Coral gasket-dkms drivers

Any update on this simple feature request?

2 Likes

Have you tried using Developer Mode

It would be good to have a proof of concept and a write-up for early adopters.

1 Like

Adding my support to this, I use the procedure below, the problem is with each update it get’s wiped out and a different method is needed to install. I’m pretty sure there is a big use group out there given frigate, photoprism and other pattern recognition needs.

apt install dh-dkms devscripts git
git clone GitHub - google/gasket-driver
cd gasket-driver
debuild -us -uc -tc -b -d
cd …
dpkg -i gasket-dkms_1.0-18_all.deb

1 Like

The code from @PuppaBriggy or on other threads work.

Just FYI, this is what I apply on each SCALE update since 23.10

install-dev-tools
apt install dkms devscripts debhelper dh-dkms -y
git clone https://github.com/heitbaum/gasket-driver
cd gasket-driver
debuild -us -uc -tc -b -d
cd ..
dpkg -i gasket-dkms_1.0-18_all.deb
systemd-sysext merge

Can use the upstream Google repository but no_llseek has been dropped by Linux Kernel 6.12 so this repo does the change, see GitHub - heitbaum/gasket-driver and it’s one commit

2 Likes

I support this as well… I understand not wanting to bloat the OS with something many won’t need, so maybe a compromise would be to add consistency – any easy way to install it so people don’t have to troubleshoot the install for every release.

1 Like

So basically, Google is selling a product that doesnt work.

Product page: Mini PCIe Accelerator | Coral
Requirements: Linux: 64-bit version of Debian 10 or Ubuntu 16.04 (or newer), and an x86-64 or ARMv8 system architecture

Google claims this works on new Linux distros which is obviously false if it doesnt work with kernel 6.12 and newer.
And I dont count community forked versions. Google should support their own hardware if they sell it to you.

They just sell faulty product and it doesnt even bother them.

I guess I would rather put my money on Hailo.

We are declining this feature request to add Google Coral TPU drivers for the following reasons:

1. Abandoned Project - Google has effectively abandoned Coral. The official gasket driver hasn’t been updated for Linux kernels 6.4+, GitHub activity has ceased, and the Linux kernel maintainers removed the driver from staging due to lack of Google support.

2. Unsustainable Maintenance - Supporting these drivers would require TrueNAS to maintain unofficial community patches indefinitely and rebuild drivers with every kernel update—an unsustainable burden for abandoned hardware.

3. Security Risk - Maintaining out-of-tree kernel modules from abandoned projects poses security and stability risks.

Alternative Solutions

Users can pass through the device to a VM running an older Linux distribution or manually compile community patches at their own risk.

3 Likes