USB keyboards no longer work

Which Khadas SBC do you use?

VIM 3L

Which system do you use? Android, Ubuntu, OOWOW or others?

CoreELEC

Which version of system do you use? Khadas official images, self built images, or others?

20.2 (though had the problem with previous version 19.2, also)

Please describe your issue below:

My USB keyboard stopped working a week or so ago. I tried a different keyboard with the same result, and the other USB port for both keyboards. Tried a third keyboard that I know works (the one I am currently typing on) in both USB ports. No response. Only the IR remote currently works on the box. I tried every conceivable setting in CoreELEC to get it working, but it is not.

Am I missing something? Or is there a way to get some better info on the potential problem? There is some sort of problem communicating with the keyboard/remotes.

Post a console log of your issue below:

CoreELEC:~ # dmesg | grep usb
[    0.471221@1]- usbcore: registered new interface driver usbfs
[    0.471272@1]- usbcore: registered new interface driver hub
[    0.471315@1]- usbcore: registered new device driver usb
[    0.647539@2]- usbcore: registered new interface driver cdc_acm
[    0.647617@2]- usbcore: registered new interface driver usb-storage
[    0.647730@2]- usbcore: registered new interface driver usbserial
[    0.647769@2]- usbcore: registered new interface driver usbserial_generic
[    0.647792@2]- usbserial: USB Serial support registered for generic
[    0.652164@3]- usbcore: registered new interface driver usbhid
[    0.652169@3]- usbhid: USB HID core driver
[    0.775002@3]- amlogic-new-usb2-v2 ffe09000.usb2phy: USB2 phy probe:phy_mem:0xffe09000, iomap phy_base:0xffffff80084dd000
[    0.775612@3]- amlogic-new-usb3-v2 ffe09080.usb3phy: USB3 phy probe:phy_mem:0xffe09080, iomap phy_base:0xffffff80084fb080
[    1.006100@1]- usbcore: registered new interface driver snd-usb-audio
[    1.256813@3]- usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.256817@3]- usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.256819@3]- usb usb1: Product: xHCI Host Controller
[    1.256822@3]- usb usb1: Manufacturer: Linux 4.9.269 xhci-hcd
[    1.256824@3]- usb usb1: SerialNumber: xhci-hcd.0.auto
[    1.257530@0]- usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.257593@0]- usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    1.257597@0]- usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.257599@0]- usb usb2: Product: xHCI Host Controller
[    1.257601@0]- usb usb2: Manufacturer: Linux 4.9.269 xhci-hcd
[    1.257604@0]- usb usb2: SerialNumber: xhci-hcd.0.auto
[    1.258923@0]- dwc_otg: usb0: type: 2 speed: 0, config: 0, dma: 0, id: 0, phy: ffe09000, ctrl: 0
[    1.583528@0]- usb 1-1: new full-speed USB device number 2 using xhci-hcd
[    1.703569@0]- usb 1-1: device descriptor read/64, error -71
[    1.931563@0]- usb 1-1: device descriptor read/64, error -71
[    2.159526@0]- usb 1-1: new full-speed USB device number 3 using xhci-hcd
[    2.279566@0]- usb 1-1: device descriptor read/64, error -71
[    2.507563@0]- usb 1-1: device descriptor read/64, error -71
[    2.615622@0]- usb usb1-port1: attempt power cycle
[    3.259573@0]- usb 1-1: new full-speed USB device number 4 using xhci-hcd
[    3.259690@0]- usb 1-1: Device not responding to setup address.
[    3.467625@0]- usb 1-1: Device not responding to setup address.
[    3.675525@0]- usb 1-1: device not accepting address 4, error -71
[    3.795530@0]- usb 1-1: new full-speed USB device number 5 using xhci-hcd
[    3.795614@0]- usb 1-1: Device not responding to setup address.
[    4.003608@0]- usb 1-1: Device not responding to setup address.
[    4.211546@0]- usb 1-1: device not accepting address 5, error -71
[    4.211596@0]- usb 1-1: the parent's name is usb1
[    4.211650@0]- usb usb1-port1: Device no response
[    4.211701@0]- usb usb1-port1: unable to enumerate USB device

Hello @jdsmofo, does the issue persist in other firmware ?

This seems like a hardware issue.

Yes, it persists, in that it happened in 19.2 and I updated to 20.2. It was in both. I also suspected hardware, but is there something in dmesg that tells you that?