View previous topic :: View next topic |
Author |
Message |
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Sun Jun 10, 2018 6:51 am Post subject: Keyboard only gets detected sometimes when booting |
|
|
I have been having this issue for a while, but haven't really tried to fix it since I barely ever reboot and it's mostly just a mild inconvenience. I also had this issue when I was using Arch at the start of the year and it's followed me to Gentoo when I installed that over Arch a few months ago. Everytime my PC boots I have to unplug and plug back in my keyboard until it wants to work (which sometimes can take a few minutes, or it can start working straight away). Here is the output of right after getting it to work (this time it started to work straight away)
It looks like the issue is towards the end of the output. My keyboard is a Corsair K70 LUX.
Code: | [ 1.211427] usbcore: registered new interface driver usbfs
[ 1.211979] usbcore: registered new interface driver hub
[ 1.212559] usbcore: registered new device driver usb
[ 1.239572] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.240347] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.240348] usb usb1: Product: xHCI Host Controller
[ 1.240348] usb usb1: Manufacturer: Linux 4.16.8-ck xhci-hcd
[ 1.240349] usb usb1: SerialNumber: 0000:00:14.0
[ 1.246289] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 1.246784] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.247265] usb usb2: Product: xHCI Host Controller
[ 1.247729] usb usb2: Manufacturer: Linux 4.16.8-ck xhci-hcd
[ 1.248180] usb usb2: SerialNumber: 0000:00:14.0
[ 1.252684] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.253110] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.253536] usb usb3: Product: xHCI Host Controller
[ 1.253959] usb usb3: Manufacturer: Linux 4.16.8-ck xhci-hcd
[ 1.254384] usb usb3: SerialNumber: 0000:07:00.0
[ 1.256857] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 1.257227] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.257603] usb usb4: Product: xHCI Host Controller
[ 1.257983] usb usb4: Manufacturer: Linux 4.16.8-ck xhci-hcd
[ 1.258370] usb usb4: SerialNumber: 0000:07:00.0
[ 1.610003] usb 1-4: new high-speed USB device number 2 using xhci_hcd
[ 1.781400] usb 1-4: New USB device found, idVendor=054c, idProduct=05ba
[ 1.781792] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.782185] usb 1-4: Product: Storage Media
[ 1.782572] usb 1-4: Manufacturer: Sony
[ 1.782949] usb 1-4: SerialNumber: CB4001211230035893
[ 1.783990] usb-storage 1-4:1.0: USB Mass Storage device detected
[ 1.784394] scsi host6: usb-storage 1-4:1.0
[ 1.784799] usbcore: registered new interface driver usb-storage
[ 1.940003] usb 1-5: new full-speed USB device number 3 using xhci_hcd
[ 2.613138] usbcore: registered new interface driver usbhid
[ 2.613727] usbhid: USB HID core driver
[ 14.960081] usb 1-5: string descriptor 0 read error: -110
[ 14.960084] usb 1-5: New USB device found, idVendor=1b1c, idProduct=1b36
[ 14.960084] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 20.010220] usb 1-5: can't set config #1, error -110
[ 20.170004] usb 1-6: new full-speed USB device number 4 using xhci_hcd
[ 20.601766] usb 1-6: New USB device found, idVendor=10f5, idProduct=2123
[ 20.601766] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 20.601767] usb 1-6: Product: Turtle Beach Elite 800 Chat
[ 20.601767] usb 1-6: Manufacturer: Turtle Beach
[ 20.601768] usb 1-6: SerialNumber: 00000000
[ 20.613084] input: Turtle Beach Turtle Beach Elite 800 Chat as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.3/0003:10F5:2123.0001/input/input16
[ 20.690044] hid-generic 0003:10F5:2123.0001: input,hiddev96,hidraw0: USB HID v1.00 Device [Turtle Beach Turtle Beach Elite 800 Chat] on usb-0000:00:14.0-6/input3
[ 20.840006] usb 1-8: new full-speed USB device number 5 using xhci_hcd
[ 21.011055] usb 1-8: New USB device found, idVendor=046d, idProduct=c332
[ 21.011056] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 21.011056] usb 1-8: Product: Gaming Mouse G502
[ 21.011057] usb 1-8: Manufacturer: Logitech
[ 21.011057] usb 1-8: SerialNumber: 137036593132
[ 21.011973] input: Logitech Gaming Mouse G502 as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/0003:046D:C332.0002/input/input17
[ 21.012007] hid-generic 0003:046D:C332.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech Gaming Mouse G502] on usb-0000:00:14.0-8/input0
[ 21.012681] input: Logitech Gaming Mouse G502 as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.1/0003:046D:C332.0003/input/input18
[ 21.080032] hid-generic 0003:046D:C332.0003: input,hiddev97,hidraw2: USB HID v1.11 Keyboard [Logitech Gaming Mouse G502] on usb-0000:00:14.0-8/input1
[ 21.230003] usb 1-9: new full-speed USB device number 6 using xhci_hcd
[ 21.380011] usb 1-9: device descriptor read/64, error -71
[ 21.650008] usb 1-9: device descriptor read/64, error -71
[ 21.920005] usb 1-9: new full-speed USB device number 7 using xhci_hcd
[ 22.070018] usb 1-9: device descriptor read/64, error -71
[ 22.340013] usb 1-9: device descriptor read/64, error -71
[ 22.460024] usb usb1-port9: attempt power cycle
[ 23.170006] usb 1-9: new full-speed USB device number 8 using xhci_hcd
[ 23.170097] usb 1-9: Device not responding to setup address.
[ 23.400095] usb 1-9: Device not responding to setup address.
[ 23.620004] usb 1-9: device not accepting address 8, error -71
[ 23.770004] usb 1-9: new full-speed USB device number 9 using xhci_hcd
[ 23.770094] usb 1-9: Device not responding to setup address.
[ 24.000097] usb 1-9: Device not responding to setup address.
[ 24.230003] usb 1-9: device not accepting address 9, error -71
[ 24.230021] usb usb1-port9: unable to enumerate USB device
[ 24.889102] usb 1-6: 1:1: cannot get freq at ep 0x81
[ 24.900198] usbcore: registered new interface driver snd-usb-audio
[ 100.167790] usb 1-6: 1:1: cannot get freq at ep 0x81
[ 323.677097] usb 1-5: USB disconnect, device number 3
[ 324.850016] usb 1-5: new full-speed USB device number 10 using xhci_hcd
[ 327.260930] usb 1-5: New USB device found, idVendor=1b1c, idProduct=1b36
[ 327.260931] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 327.260932] usb 1-5: Product: Corsair Gaming K70 LUX Keyboard
[ 327.260933] usb 1-5: Manufacturer: Corsair
[ 327.260934] usb 1-5: SerialNumber: 0801F00DAEC78440567F7902F5001941
[ 327.262030] input: Corsair Corsair Gaming K70 LUX Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/0003:1B1C:1B36.0004/input/input20
[ 327.330085] hid-generic 0003:1B1C:1B36.0004: input,hidraw3: USB HID v1.11 Keyboard [Corsair Corsair Gaming K70 LUX Keyboard ] on usb-0000:00:14.0-5/input0
[ 327.330895] input: Corsair Corsair Gaming K70 LUX Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.1/0003:1B1C:1B36.0005/input/input21
[ 327.400064] hid-generic 0003:1B1C:1B36.0005: input,hiddev98,hidraw4: USB HID v1.11 Keyboard [Corsair Corsair Gaming K70 LUX Keyboard ] on usb-0000:00:14.0-5/input1
[ 327.400092] usbhid 1-5:1.2: couldn't find an input interrupt endpoint
|
|
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54028 Location: 56N 3W
|
Posted: Sun Jun 10, 2018 8:18 am Post subject: |
|
|
Sol33t303,
Please post the output of lspci and put the output of onto a pastebin.
I suspect USB bus power issues.
As a test of this theory, boot with only the keyboard and mouse connected to USB.
I 'll look at your bus power distribution on the pastebin. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Sun Jun 10, 2018 9:26 am Post subject: |
|
|
Here is the output of lsusb -vvv without any other usb peripherals connected and while the keyboard isn't working (I used a ps/2 keyboard to type in the command) https://pastebin.com/GzDcw0V9
and here is the output of lspci https://pastebin.com/ndXDC1QT
I disconnected all peripherals and nothing changed, the keyboard still didn't want to work without unplugging it and plugging it back in multiple times. Also, I forgot to mention that it seems to work fine everytime with the bootloader, so it seems unlikely to me for it to be a hardware issue (I can also tell it's at least getting some power from the USB bus because it's RGB is always working) |
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Sun Jun 10, 2018 9:46 am Post subject: |
|
|
Code: | input: Corsair Corsair Gaming K70 |
You're not really the only user having trouble with a Corsair keyboard (search the forum for corsair keyboard or your model)
I'm afraid you should be point to this guide https://wiki.gentoo.org/wiki/Corsair_Strafe_RGB and people are instruct to use the app-misc/ckb tool.
And looking at source, you can sadly see it's a common problem https://github.com/ccMSC/ckb#troubleshooting
Don't miss the Be sure to follow Corsair's USB connection requirements. link in there.
For me, Corsair is doing shit with their keyboards.
Good luck. |
|
Back to top |
|
|
KintaroBC n00b
Joined: 15 Feb 2014 Posts: 63 Location: Australia
|
Posted: Sun Jun 10, 2018 10:14 am Post subject: |
|
|
Have you tried different keyboards? Sounds like a faulty cable/connector or some hardware issue. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54028 Location: 56N 3W
|
Posted: Sun Jun 10, 2018 10:48 am Post subject: |
|
|
Sol33t303,
You have two USB root hubs.
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
07:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge]
As they are USB 3, they are permitted to supply 900mA each for all connected bus powered devices.
Your lsusb says
Code: | (Bus Powered)
Remote Wakeup
MaxPower 500mA |
Such a power rating for a keyboard will be all the backlights.
lsusb also says
Code: | Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1b1c:1b36 Corsair |
That's odd as lspci says nothing about USB 2 root hubs. A USB 2 root hub is only permitted to provide 500mA for all bus powered devices.
Your keyboard wants all of that, so you can't connect any more bus powered devices to Bus 001 or it will be overloaded.
Depending on the overcurrent protection implementation in your PC several things can happen to overloaded USB buses.
1. Nothing at all until the overload damages the motherboard.
2. The overloaded root hub shuts down completely.
3. The root hub does load shedding so that some devices work.
In the case of your keyboard, I suspect it lies about the 500mA and tries to draw more. That upsets the overcurrent protection which turns it off.
As it works sometimes and not others, its marginal.
Try it on a USB 3 port. lsusb (without the -vvv) will tell you when that happens.
-- edit --
Code: | Bus 001 Device 001: ..
No power switching (usb 1.0)
Per-port overcurrent protection
| Thats from the root hub driving your keyboard, so it does have overcurrent protection of some sort. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Sol33t303 n00b
Joined: 23 Mar 2018 Posts: 65
|
Posted: Sun Jun 10, 2018 1:16 pm Post subject: |
|
|
After both installing the driver and plugging it into a USB 3.1 port it seems to be working a lot better. However, after rebooting 5 times to test 2 out of the 5 times it took probably between 20-30s for the keyboard to be detected, which is weird. But it seems to be getting detected a lot more often though which is good. Also, even though I have it plugged into a USB 3.1 port lsusb it says that the keyboard is using the USB 2.0 root hub bus. Which is very strange.
Code: | Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 1b1c:1b36 Corsair
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c332 Logitech, Inc. G502 Proteus Spectrum Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub |
Here is the output lsusb -vvv https://pastebin.com/5UNr2YWf
Edit: It looks like for the times when the keyboard isn't detected immediately, it seems to be detected as I log in, the keyboard started working both times while KDE was loading, but it could just be a coincidence. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|