FS#47834 - [linux] Razer Deathadder Chroma fails to operate if plugged into motherboard USB

Attached to Project: Arch Linux
Opened by altiris (altiris) - Wednesday, 20 January 2016, 17:22 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 06 October 2017, 02:32 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have an MSI P67A-G43 motherboard with 10 available USB ports. I also have a PCIe card that plugs into the PCIe port of the motherboard and gives me two USB 3.0 ports.

The issue goes as follows, if I plug in the Razer Deathadder Chroma USB mouse into one of the 10 USB ports from the motherboard, the mouse fails to operate and also causes my plugged in keyboard to not operate (I tried plugging in the keyboard after plugging in the mouse and the keyboard would also not work, unplugging the mouse made the keyboard work so it is something with the mouse). HOWEVER, if I plug the Razer Deathadder Chroma USB mouse into the PCIe card that offers two USB 3.0 ports, the mouse operates fine. I can then plug in the keyboard into EITHER the second USB 3.0 port on the PCIe card OR a port available on the motherboard and everything will work fine. There seems to be a bandwidth issue? I know this is Linux specific as I do not encounter this issue on Windows 7.


Additional info:
There is an attached file which is a picture of the error messages that display when plugging the mouse in to a USB port on the motherboard.

Steps to reproduce:
Requires a Razer Deathadder Chroma
Plug into a USB port on motherboard.
   az3iTiH.jpg (825 KiB)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 06 October 2017, 02:32 GMT
Reason for closing:  Fixed
Comment by altiris (altiris) - Wednesday, 20 January 2016, 18:30 GMT
Okay, after doing further tests I have a few more conclusions to make. I can have either the mouse OR keyboard plugged into the USB ports on the motherboard. If I plug in both that is when problems happen. For example, I plug in the mouse first, all is fine, I plug in the keyboard, and both stop working. If I move the keyboard's USB to the PCIe card then the keyboard works but the mouse still does not work. If I then move the mouse's USB also to the PCIe card (it has 2 parts) both keyboard and mouse work fine. However, if I now to try to move the keyboard out from the PCIe card and back into the motherboard port, the keyboard will not work. This also goes for other keyboard that I have such as a Logitech K360, however for some odd reason, Flashdrives still work fine so it isn't something like the USB port just stops working.

I have provided some dmesg output via SSH and will have them attached.
   Plugging_in_Blackwidow_Keyboa... (75.6 KiB)
Comment by altiris (altiris) - Wednesday, 20 January 2016, 18:50 GMT
Here is the second dmesg output, this one is plugging in the mouse after plugging in the keyboard (with the keyboard still plugged in)
   Plugging_in_RazerDeathadderCh... (72 KiB)
Comment by Jan Sordid (sor) - Friday, 12 February 2016, 13:34 GMT
I have a very similar problem with my Razer Blackwidow and Logi G400 connected to an ASUS P8Z77-V LX Motherboard. Kernel 4.0.5.
Did you find a solution @altiris?
My temporary solution was similar to yours attaching the keyboard to the onboard USB3 ports.

Log is like this booting with all devices attached:
[ 25.814985] usb 2-1.8: reset full-speed USB device number 5 using ehci-pci (10 times)
[ 26.307549] usb 2-1.8: device not accepting address 5, error -32
[ 26.374269] usb 2-1.8: reset full-speed USB device number 5 using ehci-pci (2 times)
[ 27.170498] usb 2-1.8: can't restore configuration #1 (error=-32)
[ 27.170740] usb 2-1.8: USB disconnect, device number 5
[ 27.372984] usb 2-1.8: new full-speed USB device number 6 using ehci-pci
[ 27.543809] usb 2-1.8: New USB device found, idVendor=1532, idProduct=011a
[ 27.543813] usb 2-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 27.543815] usb 2-1.8: Product: Razer BlackWidow Ultimate
[ 27.543817] usb 2-1.8: Manufacturer: Razer
[ 27.571959] input: Razer Razer BlackWidow Ultimate as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/0003:1532:011A.000B/input/input11
[ 27.622750] hid-generic 0003:1532:011A.000B: input,hidraw5: USB HID v1.11 Keyboard [Razer Razer BlackWidow Ultimate] on usb-0000:00:1d.0-1.8/input0
[ 27.641795] input: Razer Razer BlackWidow Ultimate as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.1/0003:1532:011A.000C/input/input12
[ 27.719068] input: failed to attach handler kbd to device input12, error: -16
[ 27.785666] sysrq: Failed to open input device, error -16
[ 27.808954] input: failed to attach handler sysrq to device input12, error: -16
[ 27.809159] hid-generic 0003:1532:011A.000C: input,hidraw6: USB HID v1.11 Keyboard [Razer Razer BlackWidow Ultimate] on usb-0000:00:1d.0-1.8/input1
[ 27.837623] input: Razer Razer BlackWidow Ultimate as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.2/0003:1532:011A.000D/input/input13
[ 27.837901] hid-generic 0003:1532:011A.000D: input,hidraw7: USB HID v1.11 Mouse [Razer Razer BlackWidow Ultimate] on usb-0000:00:1d.0-1.8/input2
[ 28.255213] usb 2-1.8: reset full-speed USB device number 6 using ehci-pci (5 times)
[ 31.212217] usb 2-1.8: device descriptor read/all, error -32
[ 31.281379] usb 2-1.8: reset full-speed USB device number 6 using ehci-pci (keeps printing this)
Comment by altiris (altiris) - Saturday, 13 February 2016, 17:46 GMT
@Jan Sordid

I still have not found a solution to this, I think it is something out of my scope of knowledge and something Arch Linux devs need to fix or push to the kernel developers for them to fix it.
Comment by mattia (nTia89) - Monday, 02 October 2017, 19:56 GMT
is this issue still valid?
Comment by altiris (altiris) - Wednesday, 04 October 2017, 23:13 GMT
@mattia

I am happy to say that the issue no longer occurs. I am not sure exactly how long, I stopped using Linux for a while and started using it around June...so around then it seemed the issue was resolved. Thank you for keeping up with my issue though all is good now!

Loading...