Open MrMEEE opened 8 months ago
Did you check if secure boot is turned on?
mokutil --sb-state
If so, you need to create a key and sign the module yourself. As I'm a lazy fedora user getting frequent kernel updates, I just turned SB off and gave up on this stuff...
I have slightly more encouraging output from dmesg than @MrMEEE above:
root@pve:~# dmesg |grep apex
[ 21.359736] apex 0000:65:00.0: enabling device (0140 -> 0142)
[ 26.492924] apex 0000:65:00.0: Apex performance not throttled due to temperature
root@pve:~# dmesg |grep gasket
[ 21.324419] gasket: module verification failed: signature and/or required key missing - tainting kernel
However, like them, I do not have any apex in /dev
@robertzaage I have checked the secure boot status and confirmed it is disabled via the command you provided.
M.2 Coral device on AMD64 system on Debian based OS (Proxmox) kernel 6.5.11-7
dkms status output:
root@pve:~# dkms status
Deprecated feature: REMAKE_INITRD (/var/lib/dkms/gasket/1.0/source/dkms.conf)
gasket/1.0, 6.5.11-7-pve, x86_64: installed
I have slightly more encouraging output from dmesg than @MrMEEE above:
root@pve:~# dmesg |grep apex [ 21.359736] apex 0000:65:00.0: enabling device (0140 -> 0142) [ 26.492924] apex 0000:65:00.0: Apex performance not throttled due to temperature root@pve:~# dmesg |grep gasket [ 21.324419] gasket: module verification failed: signature and/or required key missing - tainting kernel
However, like them, I do not have any apex in /dev
@robertzaage I have checked the secure boot status and confirmed it is disabled via the command you provided.
M.2 Coral device on AMD64 system on Debian based OS (Proxmox) kernel 6.5.11-7
I am experiencing the same issue on Proxmox kernel 6.5.11-8. This is very frustrating. I have spent a good few hours troubleshooting this today.
Has a solution been found?
Having the same issue with 6.5.13-5-pve kernel. Secure boot is confirmed to be disabled.
I think that the gasket driver is needed only for the PCIe-based Edge TPU devices. In other words, you don't need it for an USB Coral.
I think that the gasket driver is needed only for the PCIe-based Edge TPU devices. In other words, you don't need it for an USB Coral.
I can confirm that this is correct (something I didn't realise at the time when I posted above). I have the USB coral functioning now without the gasket driver. It turned out to be a faulty unit, once I had swapped it out, everything magically worked again.
Description
I have a USB Coral connected to a XCP-NG server, which does redirects the device as a virtual usb device to a virtual machine.
I have successfully loaded the firmware to the device from the virtual machine (running RHEL9), using the webcoral "make reset"..
I'm using the dkms package from here: https://download.copr.fedorainfracloud.org/results/kylegospo/google-coral-dkms/epel-9-$basearch/
and the drivers seems to be build correctly:
There is almost nothing in dmesg:
and no device:
Any suggestions?
Click to expand!
### Issue Type Support ### Operating System Linux ### Coral Device USB Accelerator ### Other Devices _No response_ ### Programming Language Other ### Relevant Log Output _No response_