Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm using a Microsoft wireless optical mouse and keyboard, which has stopped working following a reboot. If I look in /var/log/dmesg and grep for "Microsoft", I see a lot of entries like this

[   10.409714] input: Microsft Microsoft Wireless Optical Desktop� 2.10 as /devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0/input/input4
[   10.437651] microsoft 0003:045E:009D.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsft Microsoft Wireless Optical Desktop� 2.10] on usb-0000:00:12.0-2/input0
[   10.466601] input: Microsft Microsoft Wireless Optical Desktop� 2.10 as /devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.1/input/input6
[   10.509592] microsoft 0003:045E:009D.0002: input,hidraw1: USB HID v1.11 Mouse [Microsft Microsoft Wireless Optical Desktop� 2.10] on usb-0000:00:12.0-2/input1
[   11.070913] input: Microsft Microsoft Wireless Optical Desktop� 2.10 as /devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0/input/input7
[   11.105600] microsoft 0003:045E:009D.0003: input,hidraw0: USB HID v1.11 Keyboard [Microsft Microsoft Wireless Optical Desktop� 2.10] on usb-0000:00:12.0-2/input0
[   11.134844] input: Microsft Microsoft Wireless Optical Desktop� 2.10 as /devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.1/input/input8
[   11.193649] microsoft 0003:045E:009D.0004: input,hidraw1: USB HID v1.11 Mouse [Microsft Microsoft Wireless Optical Desktop� 2.10] on usb-0000:00:12.0-2/input1
[   12.036975] input: Microsft Microsoft Wireless Optical Desktop� 2.10 as /devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.0/input/input10

This pattern is repeated all the way to input41, not sure if that's relevant.

Ideas for further diagnosis or a fix are welcomed!

share|improve this question

1 Answer 1

up vote 1 down vote accepted

That's basically a sign that the device isn't initialising correctly so it's getting repeatedly duplicated on USB. Try using a different USB port/controller or connecting via PS/2 and see if that helps.

Otherwise, try on another machine, I suspect it may be broken. :(

share|improve this answer
    
As it turned out, the keyboard started working again in karmic. Accepting this answer as it's an old question! –  Paul Dixon Jun 24 '10 at 10:58

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.