Search results for query: gasket

...the following: mok_signing_key="/etc/dkms/dkms.key" mok_certificate="/etc/dkms/dkms.der" 6) follow the previous install steps: apt remove gasket-dkms apt install dkms lsb-release sudo git dh-dkms devscripts pve-headers git clone https://github.com/KyleGospo/gasket-dkms cd gasket-dkms...

well that error means that the gasket module is not signed or is signed with an untrusted key, so Secure Boot is rejecting it. Try disbabling Secure boot in the bios, then uinstall and reinstall the gasket-dkms if is necessary. You can also skip that step and try directly to sign the module...

I have nothing under /dev related to apex. No error messages at boot, but : :~# modprobe gasket modprobe: ERROR: could not insert 'gasket': Key was rejected by service

I tried both with KyleGospo on 6.8.4.3 and the google version on 6.5.13-5 with the same result (apex device not showing up but no visible error message). Is it possible this is related to using dkms and secureboot ? I'm definitely not familiar with secureboot and this is the first proxmox...

looks like you're using the kyle-gospo version of gasket-dkms which i believe is for 6.8 and above on 6.5.13-5 try following steps here the normal google version is what i am using & it's working fine albeit not surviving a reboot so i just have to run the code again i'm on 6.5.13-5-pve & it's...

...and reverted to kernel 6.5.13-5-pve but still a no show. Any idea what I've done wrong ? uname -r 6.5.13-5-pve Steps I've done : apt remove gasket-dkms apt install dkms lsb-release sudo git dh-dkms devscripts pve-headers git clone https://github.com/KyleGospo/gasket-dkms cd gasket-dkms...

this is fine, but could you tell me how or where to find a procedure to correctly install google coral on promox 8.2.2? I installed the gasket drivers but with lsusb I still see Global Unichip and not Google Coral, I have tried various solutions by reading on various forums but until now Proxmox...

...which downgrades the kernel proxmox-boot-tool kernel pin 6.5.13-5-pve which pins the 6.5 kernel for boot. then reboot. then retry installing gasket-dkms if still not working, you might need to uninstall the old kernels & pve-headers and retry gasket-dkms installation

...VM 100: UPID:proxmox:0003724E:0096B021:664C5B93:qmshutdown:100:root@pam: May 21 01:30:27 proxmox systemd-udevd[347]: /usr/lib/udev/rules.d/60-gasket-dkms.rules:1 Unknown group 'apex', ignoring May 21 01:30:28 proxmox kernel: tap100i0: left allmulticast mode May 21 01:30:28 proxmox kernel...

...VM 100: UPID:proxmox:0003724E:0096B021:664C5B93:qmshutdown:100:root@pam: May 21 01:30:27 proxmox systemd-udevd[347]: /usr/lib/udev/rules.d/60-gasket-dkms.rules:1 Unknown group 'apex', ignoring May 21 01:30:28 proxmox kernel: tap100i0: left allmulticast mode May 21 01:30:28 proxmox kernel...

Thanks for your reply. Yeah, I tried these instructions before, this is how I got to the current point. Kernel is 6.8.4-3-pve

...version are you on? You can verify by running uname -r Either way, try these instructions with updated repo from Post #69 above: apt remove gasket-dkms apt install dkms lsb-release sudo git dh-dkms devscripts pve-headers git clone https://github.com/KyleGospo/gasket-dkms cd gasket-dkms...

...repo and compiled / installed it again. I can confirm I can see it loaded with: root@pve:~# lsmod | grep apex apex 28672 0 gasket 126976 1 apex But I don't have anything one /dev/apex*: root@pve:~# ls -l /dev/apex* ls: cannot access '/dev/apex*': No such...

This is very helpfull. It worked. Thank you!!

...the Coral AI M.2 (B+M) module on my proxmox setup. I'm currently run the kernel version 6.8.4-2-pve and I followed this guide do install the gasket driver. The installation process completed successfully, I can load the kernel modules with: root@pve:~ # modprobe apex root@pve:~ # lsmod |...

Thank you for posting your container config. I believe I must've had something wrong in the lxc.mount.entry area that was stopping the tpu from getting recognized in frigate. Working now!

In your PVE shell, run "lsmod | grep apex" You should see the apex and gasket.. i.e: root@pve:~# lsmod | grep apex apex 28672 5 gasket 126976 6 apex ------ Also, in your PVE shell, run "ls -l /dev/apex*" This should output something like..: crw-rw---- 1...

Yes I've followed the above multiple times but I still can't get it going. In the lxc running below returns "/dev/apex_0" so which I think means the coral can be seen by the container? ls /dev/apex_0 Possibly something wrong with my container .conf file?

Did you follow the original instructions? If so, they are not working.. You need to use these instructions.. apt remove gasket-dkms apt install dkms lsb-release sudo git dh-dkms devscripts pve-headers git clone https://github.com/KyleGospo/gasket-dkms cd gasket-dkms debuild -us -uc -tc -b cd ...

Those instructions don't have anything to do with the status of the LXC container, they are for running in the PVE host because the kernel module gasket-dkms that the corul tpu uses has conflicts with the kernel 6.8.4.