This source has a strong official verification chain. The user could not install Google's Coral PCIe driver with apt or dpkg because ZimaOS ships hardware drivers as part of the system image. Zima-Jerry therefore built a dedicated kernel/update package containing the gasket driver, the user installed it, and the Coral Edge TPU began working.
IceWhale then confirmed that the gasket driver was integrated into the official ZimaOS 1.4.1 release. Current users should therefore not download the old test RAUCB or try to install Debian Coral packages on the ZimaOS host.
The Original Debian Driver Instructions Did Not Fit ZimaOS
Google's Linux Coral PCIe setup traditionally assumes a general-purpose distribution where packages and kernel modules can be installed after the OS is deployed. ZimaOS is different: Zima-Jerry explicitly said hardware drivers are pre-built into the system and cannot normally be added later with package-manager commands.
IceWhale Built a Dedicated Gasket-Driver Test Image
Zima-Jerry produced a special kernel-6.12 ZimaOS update bundle with the gasket driver and told the user to install it with RAUC. He also warned that it was a beta build and that the alternate system slot could be used if the test failed.
That test RAUCB was created for validation in May 2025. It should not be treated as a current installation package.
The Source User Confirmed the Coral PCIe TPU Worked
This is user-verified success, not merely a proposed driver patch.
Official ZimaOS 1.4.1 Integrated the Gasket Driver
After 1.4.1 was released, the user asked whether upgrading would remove the working driver. Zima-Jerry replied that version 1.4.1 had already integrated the gasket driver and that the user could upgrade with confidence.
That is the durable source conclusion.
Do Not Reinstall the Old Test Driver on Current ZimaOS
Current ZimaOS releases inherit the later kernel/system-driver line rather than the May 2025 custom test image. First check whether the PCIe TPU is detected:
lspci -nn
ls /dev/apex_*If the device is missing on a current release, collect the exact PCI ID and ZimaOS version instead of layering the old beta bundle over the system.
Frigate Still Needs Access to the TPU Device
Host driver support is only the first layer. The Frigate container must also receive the appropriate Edge TPU device, commonly an Apex device node for PCIe Coral, and Frigate's detector configuration must match the hardware.
Use the current Coral PCIe hardware guidance together with the Frigate release you actually run.
USB Coral Is a Separate Driver and Device Path
The same forum thread later expanded into USB Coral requests. USB devices can appear first as 1a6e:089a and later as 18d1:9302 after initialization. That USB path does not use the same PCIe gasket/apex flow.
The Thread Demonstrates How ZimaOS Driver Requests Work
On ZimaOS, a missing kernel driver is normally a system-image integration problem rather than a reason to apt install packages into the host. Provide IceWhale with the device ID, required upstream driver/module, and current ZimaOS version so the driver can be validated in the system build.
Verify Both PCI Enumeration and the Apex Device Node
A useful current check is not only whether lspci lists the Global Unichip/Coral device, but whether the gasket/apex driver has created the expected device node such as /dev/apex_0. PCI enumeration without the device node can mean the hardware is visible while the runtime driver is not fully bound.
Frigate Must Use the PCIe Coral Detector Type Correctly
After the host exposes the TPU, map the Apex device into the Frigate container and configure the detector according to the current Frigate Edge TPU syntax. Do not reuse the later USB example device: usb for a PCIe Coral.
Do Not Pin the NAS Forever to the Old Test RAUCB
The source user was understandably worried that a normal update might remove the new driver. IceWhale resolved that concern by integrating gasket into official 1.4.1. Once a tested driver becomes part of the normal system build, staying on the private beta image creates more risk than moving back to the supported release line.
Coral on ZimaOS FAQ
Did the Coral PCIe gasket-driver test actually work?
Yes. The original poster confirmed the PCIe TPU was detected and working.
Was gasket support later included in an official ZimaOS release?
Yes. Zima-Jerry explicitly confirmed it was integrated into ZimaOS 1.4.1.
Does that automatically prove every Coral USB TPU works?
No. USB Coral follows a separate USB driver/device path discussed later in the thread.
