Sorry to wake an old post but I thought it should be updated given the eLinux.org "R-Pi Troubleshooting" guide (http://elinux.org/R-Pi_Troubleshooting# ... rd_trouble
) cites this discussion specifically regarding the Microsoft Wireless Keyboard 800 having issues:
Wireless Keyboard trouble
Some wireless keyboards, for example the Microsoft Wireless Keyboard 800 are reported to fail even though the current drawn by the wireless adaptor is within the R-Pi USB spec limit of 100 mA. This may be a software driver problem.
I can add to this now to confirm that the dwc_otg.speed=1 work-around does also work specifically for the Microsoft Wireless Keyboard 800
- though at the cost of forcing USB 1.1 for all usb devices as noted by efflandt:
efflandt wrote:A common solution for dropped or sticky keys or dropped mouse clicks is to add dwc_otg.speed=1 to the end of the line in /boot/cmdline.txt. But that has to remain one long line (make sure it does not wordwrap). The problem is apparently sensing key down and key up events (split transactions) depending upon what all you have connected to USB and how it is connected.
Note that this forces USB 1.1 which may slow networking and external USB flash or disk access, but at least it fixes dropped or repeated keys that make it difficult to blindly enter passwords with no feedback.
[Above quote taken from this this discussion http://www.raspberrypi.org/phpBB3/viewt ... 99#p244250
relating to same problem for a different keyboard.]
Using the above work-around I can now use my Microsoft Wireless Keyboard 800 without any problems of keystrokes missing and without any keys randomly repeating. Downside is USB will be slower - but pick your trade off between that and a new keyboard (hopefully just for the time being until a proper solution can be found).
N.B. I'm using Arch Linux ARM (a.k.a. alarmpi) with fully up to date system.