On Fri, 5 Oct 2007, Jonas Nicolaisen wrote: > On Fri, Oct 05, 2007 at 02:56:40PM -0400, Alan Stern wrote: > > > What does the status -84 mean? > > > > It means there was a low-level USB communications error. Maybe the > > cable connection isn't firm, or maybe the mouse just stops working > > every few seconds. > > > > Wow. That's heavy. These mice are sold at a relatively high price to a > target audience of "professional gamers". The mouse was new from the > factory. Wouldn't you think they had some kind of QC? > > When you look around the internet, lots of people are reporting > unplug-replug style problems with Razer mice, especially the Diamondback > which has the same sensor technology as the Krait. This problem > apparently hasn't been fixed for years. But those mice are going at over > 40 euros. Target market is Windows gamers, of course. > > Razer does use very thin cables; it's part of their marketing blurb > because it supposedly makes the mice better for gaming. Before I toss > the mouse away, would it be worth it to replace the cable with the one > from my cheap (working) laptop mouse? I can solder and the cable > terminates at a simple connector plug on the mouse's board.
I really don't know. It might more sense to try using that mouse on other computers first, to see if the errors still occur. If they don't, maybe you can trade it to somebody. > Can you say something about the possibility of this being a > protocol/standards issue? i.e. is it possibly a firmware issue, or would > a three-button mouse even have firmware? The mouse definitely has firmware. But this error code doesn't indicate a high-level protocol problem; it is very low-level. > It's not connected to current draw or overcurrent protection, no? It could be. Unlikely but possible. You could try putting a powered hub between the computer and the mouse. > > > Any hope to really fix this? > > > > It's a hardware problem. Probably the easiest way to fix it is to > > replace the mouse. > > > > Hardware problem on the side of the USB hub or the mouse? In theory it could be either one -- or even a weird incompatibility where each is off by just a little bit, so they can work with other devices but not with each other. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
