Closed gibait closed 2 years ago
Just passing through, but perhaps I could help.
[13971.356610] hid-generic 0003:0483:A2CA.0008: device has no listeners, quitting
Just passing through, but perhaps I could help.
1. Can you show logs from solo1?
I'm sorry, how do i obtain logs from solo1?
- This sounds interesting to follow:
[13971.356610] hid-generic 0003:0483:A2CA.0008: device has no listeners, quitting Is this a driver problem? I tried to recompile WSL kernel with HID/USBIP modules.
giba@Thinkpad-T480:~/solo1-cli$ ls -al /sys/bus/usb/drivers/usbhid total 0 drwxr-xr-x 2 root root 0 Mar 17 11:32 . drwxr-xr-x 8 root root 0 Mar 17 11:32 .. lrwxrwxrwx 1 root root 0 Mar 17 13:27 1-1:1.0 -> ../../../../devices/platform/vhci_hcd.0/usb1/1-1/1-1:1.0 --w------- 1 root root 4096 Mar 17 11:32 bind lrwxrwxrwx 1 root root 0 Mar 17 11:32 module -> ../../../../module/usbhid -rw-r--r-- 1 root root 4096 Mar 17 11:32 new_id -rw-r--r-- 1 root root 4096 Mar 17 11:32 remove_id --w------- 1 root root 4096 Mar 17 11:32 uevent --w------- 1 root root 4096 Mar 17 11:32 unbind
EDIT: Managed to make it working after rebooting. For anyone who may get here, recompile kernel with
CONFIG_HIDRAW
set. Only problem now issolo ls
showing only with root, something is wrong with my udev rule.
This is a very long shot but i need to try one more time before giving up.. My setup is kinda complicated: WSL2 on Windows 10,
usbipd
to allow USB passthrough in WSL. Mylsusb
ouput is this:So i suppose that the solo key is recognized. However,
dmesg
says:And
udevadm monitor
shows some wicked output:Udev rules were installed correctly
Now, i know this is a a complicated mess but i don't have the necessary knowledge to understand the source of the problem, so i turn to you. Feel free to move this to discussions. Thanks