Keyboard and mouse not responding on usb ports

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
,
1

Hello,

I have encountered a problem with keyboard and mouse connected to usb (2.0?) ports. They worked fine, error occured after I installed gnome (later I removed it but problem remains; although not sure ghome was the reason). When I attach my usb camera to these usb ports, it works and Jetson identifies the camera in the ports - so, I guess there is some problem with some config files.

What I see via lsusb:
Bus 002 Device 001: ID xxxx:xxxx Linux Foundation 3.0 root hub
Bus 001 Device 008: ID c0f4:01b0 —> here is my keyboard attached
Bus 001 Device 003: ID xxxx:xxxx Terminus Technology Inc.
Bus 001 Device 002: ID xxxx:xxxx Realtek Semiconductor Corp.
Bus 001 Device 001: ID xxxx:xxxx Linux Foundation 2.0 root hub

What I see via usb-devices (no Driver - is this a problem??):
T: Bus=01 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#= 8 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=c0f4 ProdID=01b0 Rev=01.10
S: Manufacturer=USB
S: Product=usB keYboaRd
C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 0 Cls=03(HID ) Sub=01 Prot=01 Driver=(none)

What I see via dmesg:
[ 2401.483591] usb 1-3.1: config index 0 descriptor too short (expected 34, got 2)
[ 2401.490926] usb 1-3.1: invalid descriptor for config index 0: type = 0x2, length = 9
[ 2401.498687] usb 1-3.1: can’t read configurations, error -22
[ 2401.504358] usb 1-3-port1: unable to enumerate USB device
[ 2402.393500] usb 1-3.1: new low-speed USB device number 105 using tegra-xusb
[ 2402.415893] usb 1-3.1: config index 0 descriptor too short (expected 34, got 2)
[ 2402.423269] usb 1-3.1: invalid descriptor for config index 0: type = 0x2, length = 9
[ 2402.431051] usb 1-3.1: can’t read configurations, error -22
[ 2402.533461] usb 1-3.1: new low-speed USB device number 106 using tegra-xusb
[ 2402.555854] usb 1-3.1: config index 0 descriptor too short (expected 34, got 2)
[ 2402.563281] usb 1-3.1: invalid descriptor for config index 0: type = 0x2, length = 9
[ 2402.571043] usb 1-3.1: can’t read configurations, error -22
[ 2402.576704] usb 1-3-port1: attempt power cycle
[ 2403.197486] usb 1-3.1: new low-speed USB device number 107 using tegra-xusb
[ 2403.319470] usb 1-3.1: config index 0 descriptor too short (expected 34, got 2)
[ 2403.326819] usb 1-3.1: invalid descriptor for config index 0: type = 0x2, length = 9
[ 2403.334574] usb 1-3.1: can’t read configurations, error -22
[ 2403.437481] usb 1-3.1: new low-speed USB device number 108 using tegra-xusb
[ 2403.559420] usb 1-3.1: config index 0 descriptor too short (expected 34, got 2)
[ 2403.566772] usb 1-3.1: invalid descriptor for config index 0: type = 0x2, length = 9
[ 2403.574524] usb 1-3.1: can’t read configurations, error -22
etc. (it repeats for quite long)

I have added these blocks to via sudo gedit /etc/X11/xorg.conf:
Section “InputDevice”
Identifier “Keyboard0”
Driver “kbd”
Option “XkbRules” "xorg
Option “XkbModel” “pc105”
Option “XkbLayout” “us, ru”
Option “XkbOptions” “grp:caps_toggle,grp_led:caps”
EndSection

Section “InputDevice”
Identifier “USB Mouse”
Driver “mouse”
Option “Protocol” “IMPS/2”
Option “SendCoreEvents” “true”
Option “Device” “/dev/input/mice”
EndSection

Section “ServerLayout”
Identifier “Default Layout”
Screen 0 “Default Screen” 0 0
InputDevice “Keyboard0”
InputDevice “USB Mouse”
EndSection

I also commented these two line of code via sudo nano /etc/modprobe.d/blacklist.conf:

these drivers are very simple, the HID drivers are usually preferred

blacklist usbmouse —> commented

blacklist usbkbd —> commented

However, nothing helps.

Could any one recommend what else can I do (prefferably without reinstallation of the whole system)?
Anything esle should I check for the right connection of keyboard/mouse with usb ports (just a reminder that usb camera works being connected to the same usb ports)?

3

Hi,

Have you tried other usb keyboard and mouse and different port? Also, I don’t think you need to add those setting in your xorg.conf.

4

Hi @WayneWWW,

Thank you for your message.

Unfortunately, I don’t have other keyboard and mouse.

However, I checked available keyboard and mouse on my notebook (both keyboard and mouse work ok), and yes I tried a different port, this time USB 3.0 Type A (both keyboard and mouse work ok).
It seems that the problem appears only when connecting keyboard and mouse to two USB 2.0 Type A ports (position 5 @ Getting Started with Jetson Nano 2GB Developer Kit | NVIDIA Developer).

And I don’t understand why anything else (USB camera or USB wifi wireless adapter) connected to these two USB 2.0 ports works fine…

5

Could you share below info to me?

ll /lib/aarch64-linux-gnu/libusb*

Not sure if your installation changed any libusb library here…

6

Here you are:

lrwxrwxrwx 1 root root 19 июн 25 2017 /lib/aarch64-linux-gnu/libusb-1.0.so.0 → libusb-1.0.so.0.1.0
-rw-r–r-- 1 root root 88736 июн 25 2017 /lib/aarch64-linux-gnu/libusb-1.0.so.0.1.0

P.S. I don’t know why, but today forum is very slow - I tried to send this message several times.

7

Please check if running below command will enumerate your usb device or not.

echo “1-3” > /sys/bus/usb/drivers/usb/unbind
echo “1-3” > /sys/bus/usb/drivers/usb/bind

Please replace the “1-3” to the device number if it gets changed.

8

Hi @WayneWWW,

Thank you for your support, unfortunately this didn’t help.
Is it safe to share here a part of kern.log file?
I found a place where there are “named” keyboard and mouse and after something happened keyboard became “unnamed” and I don’t see mouse anymore…

9

You already shared partial kernel log in the first comment. Why do you think it would be unsafe?

The kernel is also public source too.

10

Ok @WayneWWW - before the “doomsday” keyboard and mouse were like this:

Apr 19 19:10:27 jetson-22 kernel: [ 2.081474] cgroup: cgroup2: unknown option “nsdelegate”
Apr 19 19:10:27 jetson-22 kernel: [ 2.219122] usb 1-3.1: new low-speed USB device number 4 using tegra-xusb
Apr 19 19:10:27 jetson-22 kernel: [ 2.244906] usb 1-3.1: New USB device found, idVendor=c0f4, idProduct=01b0
Apr 19 19:10:27 jetson-22 kernel: [ 2.244912] usb 1-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 19 19:10:27 jetson-22 kernel: [ 2.244916] usb 1-3.1: Product: usb keyboard
Apr 19 19:10:27 jetson-22 kernel: [ 2.244919] usb 1-3.1: Manufacturer: USB
Apr 19 19:10:27 jetson-22 kernel: [ 2.248475] input: USB usb keyboard as /devices/70090000.xusb/usb1/1-3/1-3.1/1-3.1:1.0/0003:C0F4:01B0.0001/input/input2
Apr 19 19:10:27 jetson-22 kernel: [ 2.263114] tegra-pcie 1003000.pcie: link 0 down, retrying
Apr 19 19:10:27 jetson-22 kernel: [ 2.307571] hid-generic 0003:C0F4:01B0.0001: input,hidraw0: USB HID v1.10 Keyboard [USB usb keyboard] on usb-70090000.xusb-3.1/input0
Apr 19 19:10:27 jetson-22 kernel: [ 2.311003] input: USB usb keyboard as /devices/70090000.xusb/usb1/1-3/1-3.1/1-3.1:1.1/0003:C0F4:01B0.0002/input/input3
Apr 19 19:10:27 jetson-22 kernel: [ 2.367471] hid-generic 0003:C0F4:01B0.0002: input,hidraw1: USB HID v1.10 Device [USB usb keyboard] on usb-70090000.xusb-3.1/input1
Apr 19 19:10:27 jetson-22 kernel: [ 2.467126] usb 1-3.2: new low-speed USB device number 5 using tegra-xusb
Apr 19 19:10:27 jetson-22 kernel: [ 2.479768] random: systemd: uninitialized urandom read (16 bytes read)
Apr 19 19:10:27 jetson-22 kernel: [ 2.481796] random: systemd: uninitialized urandom read (16 bytes read)
Apr 19 19:10:27 jetson-22 kernel: [ 2.481943] random: systemd: uninitialized urandom read (16 bytes read)
Apr 19 19:10:27 jetson-22 kernel: [ 2.492508] usb 1-3.2: New USB device found, idVendor=1c4f, idProduct=0034
Apr 19 19:10:27 jetson-22 kernel: [ 2.492514] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 19 19:10:27 jetson-22 kernel: [ 2.492518] usb 1-3.2: Product: Usb Mouse
Apr 19 19:10:27 jetson-22 kernel: [ 2.492521] usb 1-3.2: Manufacturer: SIGMACHIP
Apr 19 19:10:27 jetson-22 kernel: [ 2.496105] input: SIGMACHIP Usb Mouse as /devices/70090000.xusb/usb1/1-3/1-3.2/1-3.2:1.0/0003:1C4F:0034.0003/input/input4
Apr 19 19:10:27 jetson-22 kernel: [ 2.496417] hid-generic 0003:1C4F:0034.0003: input,hidraw2: USB HID v1.10 Mouse [SIGMACHIP Usb Mouse] on usb-70090000.xusb-3.2/input0
Apr 19 19:10:27 jetson-22 kernel: [ 2.583401] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
Apr 19 19:10:27 jetson-22 kernel: [ 2.676354] tegra-pcie 1003000.pcie: link 0 down, retrying

11

Actually, I consult with our usb team and they have no idea why install “gnome” will cause this problem too. Do you remember the command you are using to hit this problem?

12

kern_log.docx (60.2 KB) @WayneWWW,

Please find attached the abstract from the kern.log file - the last lines show “unidentified” keyboard and no mouse; these lines I see now all the time.
So, something happend before that - is it possible to find out what looking in this log?

13

Hi,

Sorry I don’t see that line. Is it from syslog or dmesg? If the syslog still valid there, could you share it and point out the timestamp where the error happened?

14

This is what I did:

sudo apt install gnome
sudo systemctl restart gdm3
sudo service gdm start
sudo apt remove gnome

15

Please look into the kern_log file, page 55 close to the bottom of the page starting with line:

Apr 20 10:39:14 jetson-22 kernel: [ 2.226035] usb 1-3.1: new low-speed USB device number 4 using tegra-xusb

And I don’t know what caused this change, I suppose it is possible to guess looking into the logs on previous pages…

16

I checked your log.

In 4/20 10:22, the usb device is still alive.

Apr 20 10:22:22 jetson-22 kernel: [  637.329853] usb 1-3.2: New USB device found, idVendor=1c4f, idProduct=0034
Apr 20 10:22:22 jetson-22 kernel: [  637.329858] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 20 10:22:22 jetson-22 kernel: [  637.329861] usb 1-3.2: Product: Usb Mouse
Apr 20 10:22:22 jetson-22 kernel: [  637.329863] usb 1-3.2: Manufacturer: SIGMACHIP
Apr 20 10:22:22 jetson-22 kernel: [  637.333616] input: SIGMACHIP Usb Mouse as /devices/70090000.xusb/usb1/1-3/1-3.2/1-3.2:1.0/0003:1C4F:0034.0005/input/input6
Apr 20 10:22:22 jetson-22 kernel: [  637.334206] hid-generic 0003:1C4F:0034.0005: input,hidraw2: USB HID v1.10 Mouse [SIGMACHIP Usb Mouse] on usb-70090000.xusb-3.2/input0
Apr 20 10:22:26 jetson-22 kernel: [  640.607708] usb 1-3.2: USB disconnect, device number 7
Apr 20 10:22:26 jetson-22 kernel: [  640.884078] usb 1-3.2: new low-speed USB device number 8 using tegra-xusb

and it was still alive after 10min

Apr 20 10:33:27 jetson-22 kernel: [ 1301.907018] usb 1-3.2: New USB device found, idVendor=1c4f, idProduct=0034

Apr 20 10:33:27 jetson-22 kernel: [ 1301.907022] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

Apr 20 10:33:27 jetson-22 kernel: [ 1301.907025] usb 1-3.2: Product: Usb Mouse

Apr 20 10:33:27 jetson-22 kernel: [ 1301.907027] usb 1-3.2: Manufacturer: SIGMACHIP

Apr 20 10:33:27 jetson-22 kernel: [ 1301.910803] input: SIGMACHIP Usb Mouse as /devices/70090000.xusb/usb1/1-3/1-3.2/1-3.2:1.0/0003:1C4F:0034.0008/input/input9

Apr 20 10:33:27 jetson-22 kernel: [ 1301.911047] hid-generic 0003:1C4F:0034.0008: input,hidraw2: USB HID v1.10 Mouse [SIGMACHIP Usb Mouse] on usb-70090000.xusb-3.2/input0

Then, it seems you do a reboot in 4/20 10:39 and the device is gone. Are you sure you install gnome at this point?

17

Besides my previous comment, there is one thing to mention, the jetson nano-2gb does not use gdm3 but lxde, thus, I have no idea why you have to enable/disable gdm3.

18

I had a problem with my display (see my previous post) - I made a mistake with screen resolution while setting up a VNC. I installed gnome thinking it would help resore the display. After I realised that I can corrrect the resolution with nano in ssh mode, I reactivated the display and saw a different initial screen on Jetson (I think because of gnome). So I decided to reactivate gdm (maybe I had to reactivate lxde) - and got the dysplay as it was before. I think somewhere at that time I lost keyboard and mouse. A horror story, I should say…

19

Hi,

Is the syslog still there? And did you remember when did you install gnome ? Need to compare the log around that time.

21

Hi @WayneWWW,

Here you are, attached is a syslog file for this day. I think you were right about time when something happend: between 10:33 and 10:39.
syslog.3.gz (2.4 MB)

22

I think you can try to disable gdm3 or remove gnome at this moment and see if the usb device would be back or not.

Your last gdm log was on 4/20 10:35. After that one, gdm never appeared and just full of usb error log.

Also, if possible, you can try to find another empty card and reflash it with fresh sdcard image, use it to verify that this issue is really something in software.