Search results for query: gasket

This did it for me, after the update to Proxmox 9

...coral-edgetpu-stable main" | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list apt update apt install libedgetpu1-std Add the gasket driver from the source as I couldn't find a Debian 13 package apt -y install make apt -y install build-essential linux-headers-$(uname -r) git apt -y...

...switched to the strategy of installing the drivers on the Proxmox host itself, and it was successful! My Proxmox host now correctly loads the gasket and apex modules, and the /dev/apex_0 device is present and stable on the host. The New Challenge: Getting /dev/apex_0 into the Home...

I figured out what the reason is. I bought an m.2 adapter for Dual TPU, but it doesn't have a Coral chip.o_O https://www.makerfabs.com/dual-edge-tpu-adapter-m2-2280-b-m-key.html

..../install_coral_tpu.sh --status Coral TPU PCIe hardware not detected (lspci | grep 1ac1:089a). Apex devices not found in /dev. DKMS Gasket module: gasket/1.0, 6.12.43+deb13-amd64, x86_64: installed gasket/1.0, 6.14.11-1-pve, x86_64: installed gasket/1.0, 6.14.11-2-pve, x86_64: installed...

Since I have 3 versions of gasket but am running 6.14.11 kernel, is it safe to boot to kernel 6.14.8 through grub? root@pve4:~# dkms status gasket/1.0, 6.12.43+deb13-amd64, x86_64: installed gasket/1.0, 6.14.11-1-pve, x86_64: installed gasket/1.0, 6.14.8-2-pve, x86_64: installed

maybe a problem with gasket/1.0, 6.14.11? on my site everything works fine: PVE 9.0.5 root@proxmox:/home# ./install_coral_tpu.sh --status Coral TPU PCIe hardware detected: 01:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a] Apex devices installed: /dev/apex_0...

...(16.0) ... Processing triggers for libc-bin (2.41-12) ... Installing driver from source... Cloning into '/tmp/coral-build/gasket-driver'... remote: Enumerating objects: 850, done. remote: Counting objects: 100% (230/230), done. remote: Compressing objects: 100% (24/24), done. remote: Total...

After reboot One interesting tidbit is that everything worked in PVE 8 and all these problems emerged after upgrading to PVE 9

Also: root@pve4:/home/coral-build/gasket-driver# dmesg |grep gasket [ 3.669543] gasket: module verification failed: signature and/or required key missing - tainting kernel

I ran the latest script on 6.14.11-1-pve and the system cannot find apex devices

...long ago so these recent posts are a lifesaver! @rekordskratch and @duindain, I'm running frigate on Docker on an Ubuntu VM. Do I install the gasket driver on Proxmox or on Ubuntu? @Di-We, If I'm going to download feranick's .deb file, can you confirm that I can skip the previous steps to...

If it returns an error at the last command, then download the image from here: wget https://github.com/feranick/gasket-driver/releases/download/1.0-18.4/gasket-dkms_1.0-18.4_all.deb And install it: dpkg -i gasket-dkms_1.0-18.4_all.deb

Thank you Jörg. Had the same problem and with the new scripts problem fixed.

...vfio-pci softdep snd_hda_intel pre: vfio-pci then ran update-initramfs -u -k all Ran the commands in rekordskratch's comment to install the gasket driver After that hopefully i haven't forgotten any commands Its as stable as it ever was which franky isn't amazing, (would have been better...

...apt-get update apt-get install pve-headers libedgetpu1-std dkms devscripts dh-make dh-dkms git -y git clone https://github.com/google/gasket-driver.git cd gasket-driver sed -i -e 's/no_llseek/noop_llseek/g' src/gasket_core.c sed -i -e...

Unfortunately I'm still getting the ls: cannot access '/dev/apex_0' : No such file or directory after following your script & instructions

...with apt update && apt upgrade -y and mess everything up. To prevent this, you can exclude the package from the apt-upgrade. apt-mark hold gasket-dkms However, this solution is not ideal. Is there a better solution? (Perhaps one should fork the GitHub repository and increase the version...

...Coral TPU drivers by following https://medium.com/@hendra.hartono/installation-coral-dual-edge-tpu-runtime-on-linux-proxmox-ve-6281c648a5a4 All seems OK until I reboot and get this: root@sirius:~# dmesg | grep gasket root@sirius:~# root@sirius:~# lsmod | grep apex root@sirius:~# Any ideas?