On 15/07/2023 09:30, Todd Gruhn wrote:
UUUUUH KAY.
Found this:
port 7 addr 9: full speed, power 98 mA, config 1, USB
Receiver(0xc52b), Logitech(0x046d), rev 12.11(0x1211)
port 8 powered
port 9 powered
port 10 powered
port 11 addr 10: full speed, power 98 mA, config 1, USB
Receiver(0xc52b), Logitech(0x046d), rev 12.03(0x1203)
port 12 powered
Unless its very unusual you should have ended up with something like
this in your dmesg:
[ 1631769.331114] uhidev1: Logitech (0x046d) USB Receiver (0xc534), rev
2.00/29.01, addr 17, iclass 3/1
[ 1631769.334114] uhidev1: 17 report ids
[ 1631769.334114] ums0 at uhidev1 reportid 2: 16 buttons, W and Z dirs
[ 1631769.334114] wsmouse0 at ums0 mux 0
You can also do:
usbdevs -vd
Which will give you the output above and should also list the device
drivers attached by the OS (usbhid hopefully).
From memory you can reference a specific mouse as /dev/wsmouse0 or
/dev/wsmouse1 but there is also a /dev/wsmouse that merges all the mouse
inputs together. /dev/wsmouse is normally what the X server references
which allows you to use any mouse on the system.
I'd be astonished if this didn't just work assuming you have USB HID
support compiled into your kernel (its in GENERIC and has been for
years). Most USB mice are of this type (wired and wireless) as it means
they work out of the box on pretty much every operating system under the
sun.
Other things to check:
1. Is the mouse turned on? (they usually have a sneaky power switch on
the underside).
2. Is the battery inside the mouse okay?
From a quick check with mine I still get the ums device even with the
mouse turned off but obviously it doesn't make the pointer move.
Mike
