-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No /dev/apex_0 device #19
Comments
Did you check if secure boot is turned on? 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:
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:
|
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 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
The text was updated successfully, but these errors were encountered: