After I first ran into the issue, I retured the mouse to the retailer because I thought it faulty. I tested with fast, ultra-fast and normal boot modes and all available USB-Ports. What motherboard do you have in your desktop PC?
![logitech setpoint for m500 mouse logitech setpoint for m500 mouse](https://1.bp.blogspot.com/-97agikvQaLw/VTXt7A5BjbI/AAAAAAAAEv8/x34mQhz7XBw/s1600/2014-New-font-b-Logitech-b-font-font-b-M505-b-font-Wireless-Mouse-2-4G-776354.jpg)
I have the same issue as you with my Sabre RGB. So I booted the system, unplugged and plugged again the mouse and displayed the last kernel messages, we can see the same error: If I use my Logitech M500 mouse, this detection is really fast (like 1 second) without error, but if I use the Corsair mouse the detection takes around 10 seconds and displays an error: I also found an error, when Udev automatically detects hardware at OS boot. * I recently installed Arch Linux and found the same issue. * Under Ubuntu 16.04, I get the same issue.
![logitech setpoint for m500 mouse logitech setpoint for m500 mouse](https://techgage.com/reviews/logitech/m705/screenshot2.jpg)
I have to unplug the mouse, plug it again then wait 10-20 seconds to get a working mouse. Lights are off and I don't have a mouse cursor. * Under Windows 10, when the desktop is loaded, it sometimes happens that the mouse is off. I haven't any issue with my other mice (a Logitech M500 and a cheap mouse), Corsair Utility and Corsair mouse firmware are updated, and I tested the Corsair mouse on 3 different computers and 3 different OS, always getting the same problem. I bought a Corsair Gaming SABRE RGB Mouse and found it has an initialization issue. I don't know if this is only on my mouse or a more general firmware issue, but actually I can't recommend and won't plan to buy any other Corsair product, until we can fix this. If you need more informations, or have some tests to do under Windows or Linux, I'll help you.īut let me tell you that I'm quite disapointed that a 50 € mouse has this kind of major issue.
![logitech setpoint for m500 mouse logitech setpoint for m500 mouse](http://3.bp.blogspot.com/-c82FlFAWtj4/UMeonbeofZI/AAAAAAAABG4/-YqUNzefUjc/s1600/logitech+setpoint.png)
I also tried USB v3 port, front and back.
![logitech setpoint for m500 mouse logitech setpoint for m500 mouse](https://eshop.macsales.com/imgs/ndesc/Logitech/LOG910001204/LOG910001204_gall3.jpg)
* To be sure that I don't get an issue with my motherboard (running with last BIOS update), I tested the mouse on a HP Pavillon A6220 desktop and on an Packard Bell PAV80 netbook, running the Arch Linux USB installer and saw the same kernel error. "Well given all the above, it looks like either the mouse is defective or just poorly designed, so really the only option is to swap it out for another mouse." I made a search on the web and found this, from someone who seems trustable (moderator on with 3600+ answers): 08 15:40:36 fractal kernel: usbhid 3-6:1.2: couldn't find an input interrupt endpoint 08 15:40:26 fractal kernel: usb 3-6: new full-speed USB device number 5 using xhci_hcdĭéc.