You are not logged in.
I have a Logitech G502 Hero mouse and would like to make it work through my monitor's usb hub, but for some reason the mouse is not identified properly when connected to the monitor, only when connected directly to my computer.
`lsusb` with mouse connected through monitor's usb:
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 013 Device 002: ID 045e:070f Microsoft Corp. LifeChat LX-3000 Headset
Bus 013 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 003: ID 0451:8340 Texas Instruments, Inc.
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 017: ID 0451:82ff Texas Instruments, Inc.
Bus 005 Device 016: ID 275d:0a29
Bus 005 Device 015: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 005 Device 018: ID 046d:c08b Logitech, Inc.
Bus 005 Device 013: ID 0451:8342 Texas Instruments, Inc.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub`lsusb` with mouse connected directly:
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 013 Device 006: ID 046d:c08b Logitech, Inc. G502 HERO Gaming Mouse
Bus 013 Device 002: ID 045e:070f Microsoft Corp. LifeChat LX-3000 Headset
Bus 013 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 003: ID 0451:8340 Texas Instruments, Inc.
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 017: ID 0451:82ff Texas Instruments, Inc.
Bus 005 Device 016: ID 275d:0a29
Bus 005 Device 015: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 005 Device 013: ID 0451:8342 Texas Instruments, Inc.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubOffline
If it does not work with a different cable to the monitor's hub, It's most likely an issue in the hub itself.
You can try plugging the hub into a different port on your machine.
Do other devices work when plugged into the monitor's hub?
If you can get a stick to work, try doing some speed tests on it when in monitor and when in machine directly. Check if there are huge differences. Also, use big files (200-1000MB) to test bus stability.
Offline
I tried connecting in all usb ports in my monitor, and also changing the monitor usb cable to my computer.
I also have some cheap mouse devices that I was using before through the monitor's hub and they always worked, including USB sticks. This is actually the only device that I couldn't get to work with my monitor. =/
Offline
In this case I am afraid there's nothing that can be realistically done.
Out of curiosity, what does dmesg say when you plug it in through the monitor?
Offline
`dmesg` when connecting directly:
[11334.875328] usb 13-4: new full-speed USB device number 8 using ohci-pci
[11335.071067] usb 13-4: New USB device found, idVendor=046d, idProduct=c08b, bcdDevice=27.02
[11335.071073] usb 13-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[11335.071077] usb 13-4: Product: G502 HERO Gaming Mouse
[11335.071079] usb 13-4: Manufacturer: Logitech
[11335.071082] usb 13-4: SerialNumber: 0A6339613233
[11335.081412] input: Logitech G502 HERO Gaming Mouse as /devices/pci0000:00/0000:00:16.0/usb13/13-4/13-4:1.0/0003:046D:C08B.004D/input/input166
[11335.081534] hid-generic 0003:046D:C08B.004D: input,hidraw7: USB HID v1.11 Mouse [Logitech G502 HERO Gaming Mouse] on usb-0000:00:16.0-4/input0
[11335.087642] input: Logitech G502 HERO Gaming Mouse Keyboard as /devices/pci0000:00/0000:00:16.0/usb13/13-4/13-4:1.1/0003:046D:C08B.004E/input/input167
[11335.142205] input: Logitech G502 HERO Gaming Mouse Consumer Control as /devices/pci0000:00/0000:00:16.0/usb13/13-4/13-4:1.1/0003:046D:C08B.004E/input/input168
[11335.142269] input: Logitech G502 HERO Gaming Mouse System Control as /devices/pci0000:00/0000:00:16.0/usb13/13-4/13-4:1.1/0003:046D:C08B.004E/input/input169
[11335.142376] hid-generic 0003:046D:C08B.004E: input,hiddev2,hidraw8: USB HID v1.11 Keyboard [Logitech G502 HERO Gaming Mouse] on usb-0000:00:16.0-4/input1`dmesg` through the monitor:
[11405.630503] usb 2-2.2: new full-speed USB device number 16 using xhci_hcd
[11405.827923] usb 2-2.2: New USB device found, idVendor=046d, idProduct=c08b, bcdDevice=27.02
[11405.827925] usb 2-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[11405.827927] usb 2-2.2: Product: G502 HERO Gaming Mouse
[11405.827928] usb 2-2.2: Manufacturer: Logitech
[11405.827929] usb 2-2.2: SerialNumber: 0A6339613233
[11405.835341] input: Logitech G502 HERO Gaming Mouse as /devices/pci0000:00/0000:00:09.0/0000:04:00.0/usb2/2-2/2-2.2/2-2.2:1.0/0003:046D:C08B.004F/input/input172
[11405.835455] hid-generic 0003:046D:C08B.004F: input,hidraw7: USB HID v1.11 Mouse [Logitech G502 HERO Gaming Mouse] on usb-0000:04:00.0-2.2/input0
[11405.836790] input: Logitech G502 HERO Gaming Mouse Keyboard as /devices/pci0000:00/0000:00:09.0/0000:04:00.0/usb2/2-2/2-2.2/2-2.2:1.1/0003:046D:C08B.0050/input/input173
[11405.890642] input: Logitech G502 HERO Gaming Mouse Consumer Control as /devices/pci0000:00/0000:00:09.0/0000:04:00.0/usb2/2-2/2-2.2/2-2.2:1.1/0003:046D:C08B.0050/input/input174
[11405.890721] input: Logitech G502 HERO Gaming Mouse System Control as /devices/pci0000:00/0000:00:09.0/0000:04:00.0/usb2/2-2/2-2.2/2-2.2:1.1/0003:046D:C08B.0050/input/input175
[11405.890837] hid-generic 0003:046D:C08B.0050: input,hiddev2,hidraw8: USB HID v1.11 Keyboard [Logitech G502 HERO Gaming Mouse] on usb-0000:04:00.0-2.2/input1Offline
Some ideas about what to check:
The Xorg log file is by default "/var/log/Xorg.0.log", it will show messages when you connect the mouse. The system log in "journalctl -b" might show more than dmesg.
There is a package named "evtest" with a tool that can show raw data from an input device. You run "sudo evtest" and follow instructions on screen, then just move around the mouse and click buttons to see if it sends coordinates and button events. Does the mouse data show up correctly in evtest?
Your computer (probably) has two USB controllers from two different manufacturers. Maybe only one of those controllers causes the problem so try plugging the monitor USB hub into different ports on the PC side to test both controllers.
Offline