g810-led
g810-led copied to clipboard
MatMoul
Getting 'Matching or compatible device not found !' when keyboard is connected via USB hub.
Hello guys,
I have a set-up where I flip my USB devices between two computers with the use of USB HUB. I have noticed that with my G610 your library works fine but only when the keyboard is plugged directly into the computer's USB port. When I plug it into the HUB they keyboard lights up only in the default mode (some areas are lit, but most like the letters are unlit) - which means the driver works but no fully (if it would not work I would have the keyboard's default wave effect).
When I do the --list-keyboards when connected via the USB hub I get the proper listing:
Device: Logitech - Gaming Keyboard G610 Vendor ID: 046d Product ID: c333 Serial Number: 1078354C3033
but any other command gives me
Matching or compatible device not found !
any idea on how to fix this?
Thanks for return, I never tested it on USB hub. I'll try it when I found time
I had the same issue with USB port on my motherboard, but after switching to another port it fixed itself.
[konserw@antegros gseries-tools]$ g610-led --list-keyboards
Device: Logitech - Gaming Keyboard G610
Vendor ID: 046d
Product ID: c333
Serial Number: 187235663130
[konserw@antegros gseries-tools]$ g610-led --print-device
Matching or compatible device not found !
I see the same issue with my keyboard when it's connected trough a USB-C hub
I also observed this behaviour when I connected my G610 to a USB-C port (no hub).
Tested with a passive USB hub and it work... For those that have a problem with USB hub, is it an active HUB ? For usb-c, at this time, I don't have it...
Having same issue with a Logitech G Pro keyboard. The USB hub is an active hub.
$ gpro-led --list-keyboards
Device: Logitech - Pro Gaming Keyboard
Vendor ID: 046d
Product ID: c339
Serial Number: 178E36573635
$ gpro-led --print-device
Matching or compatible device not found !
$ lsusb -tv
[...]
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ID 0bda:5411 Realtek Semiconductor Corp.
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
ID 2109:2812 VIA Labs, Inc. VL812 Hub
|__ Port 4: Dev 9, If 0, Class=Hub, Driver=hub/4p, 480M
ID 2109:2812 VIA Labs, Inc. VL812 Hub
|__ Port 4: Dev 10, If 2, Class=Audio, Driver=snd-usb-audio, 12M
ID 046d:0a5b Logitech, Inc. G933 Wireless Headset Dongle
|__ Port 4: Dev 10, If 0, Class=Audio, Driver=snd-usb-audio, 12M
ID 046d:0a5b Logitech, Inc. G933 Wireless Headset Dongle
|__ Port 4: Dev 10, If 3, Class=Human Interface Device, Driver=usbhid, 12M
ID 046d:0a5b Logitech, Inc. G933 Wireless Headset Dongle
|__ Port 4: Dev 10, If 1, Class=Audio, Driver=snd-usb-audio, 12M
ID 046d:0a5b Logitech, Inc. G933 Wireless Headset Dongle
|__ Port 2: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
ID 046d:c339 Logitech, Inc.
|__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
ID 046d:c339 Logitech, Inc.
|__ Port 3: Dev 7, If 2, Class=Human Interface Device, Driver=usbhid, 12M
ID 046d:c53a Logitech, Inc.
|__ Port 3: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 12M
ID 046d:c53a Logitech, Inc.
|__ Port 3: Dev 7, If 1, Class=Human Interface Device, Driver=usbhid, 12M
ID 046d:c53a Logitech, Inc.
[...]
Having same issue with a Logitech G Pro keyboard. The USB hub is an active hub.
$ gpro-led --list-keyboards Device: Logitech - Pro Gaming Keyboard Vendor ID: 046d Product ID: c339 Serial Number: 178E36573635 $ gpro-led --print-device Matching or compatible device not found !
Try again with sudo, that worked for me.
What the state if this issue? sudo or not... An other possibillity is that you use libusb. Is it the case ?
I had the same problem. Then I restarted my computer (with keyboard plugged in the docking through USB-C) and now it works without sudo.
Had same problem. Program must be run with sudo to avoid permission problems.
I had the same permissions issue. The program should check for write permissions to the USB device and report something like No write permission for /dev/foo rather than the misleading message Matching or compatible device not found !
The program seems to not see the keyboard which is attached through a KVM. Probably has a built-in hub. I think this is the situation:
$ lsusb Bus 001 Device 086: ID 0c45:7403 Microdia Foot Switch Bus 001 Device 085: ID 1a40:0101 Terminus Technology Inc. Hub
$ lsusb -t /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 2: Dev 85, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 86, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 86, If 0, Class=Human Interface Device, Driver=usbhid, 12M
$ sudo bin/g810-led -dv 0c45 -dp 7403 -tuk 1 --list-keyboards Device: - Vendor ID: 0c45 Product ID: 7403 Serial Number: Device: - Vendor ID: 0c45 Product ID: 7403 Serial Number:
Same result with all protocols. Trying the '-a 000000' has no effect but I see the caps-lock light blinking briefly.
This is a G512 CARBON (GX BROWN TACTILE). Connected directly to PC:
$ bin/g810-led --list-keyboards Device: Logitech - G512 RGB MECHANICAL GAMING KEYBOARD Vendor ID: 046d Product ID: c33c Serial Number: xxxxxxxxxxxx
[added] The KVM is a "TESmart 4-port HDMI KVM Switch" like this https://www.ebay.com.au/itm/303922503408
TIA
@elvismdev Was this a reply to my preceding note? If so, is your kbrd attached through a 1a40:0101 hub?
@elvismdev Was this a reply to my preceding note? If so, is your kbrd attached through a 1a40:0101 hub?
No, sorry no relation with your note, just posted for the whole thread that with sudo it worked for me.
