Mouse and keyboard don't start on boot or stop after awhile

I installed Jetpack 4.5 on the Xavier NX, however had numerous issues with wireless keyboard and mouse (all new) not being identified during boot or stop working after moving along with the installation.

Switched to hardwired mouse and keyboard into USB ports and worked a little longer then just stopped. After doing more reboots, I may see the mouse appear during the boot process but never actually appear when fully booted.

I confirmed the wireless keyboard and mouse work fine on regular windows machine. It seems the USB ports kind of work but then don’t. Is there anything else I can do to get it running properly? I am very disappointed with this and it doesn’t seem to be related to the ports themselves but perhaps the USB detection algo’s/driver… I don’t know enough to identify as one thing or another.

Hi

same issue since the Jetpack 4.5 OTA upgrade.
the same wireless receiver works on a windows machine but nothing on the Jetson.
Picked up in dmesg but nothing more.
[ 4051.966209] usb 1-2.3: new full-speed USB device number 10 using tegra-xusb
[ 4051.990603] usb 1-2.3: New USB device found, idVendor=046d, idProduct=c52b
[ 4051.990615] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4051.990622] usb 1-2.3: Product: USB Receiver
[ 4051.990628] usb 1-2.3: Manufacturer: Logitech

Hi,

This sounds an new issue that we don’t know on jetpack4.5.

Thus, need your kind help to share below info or do some test. I will firstly focus on wired keyboard and mouse case first because they are the easiest ones to get.

  1. Could you boot up the device, plug the mouse and keyboard after system is up and share me the result of “dmesg” and “lsusb”? If you cannot debug because no usb is available, please check if you can still access your device through ssh (ethernet/wireless) and then use that interface to dump log.

  2. Please also check if usb keyboard and mouse has powered up after you connect it to NX. Checking the LED indicator on them.

Wireless side of things (and camera in another post)

re dmesg do you need the full output or a grep -i usb ?

lsusb
xaviernx:~$ lsusb
Bus 002 Device 002: ID 0bda:0489 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:3549 IMC Networks
Bus 001 Device 006: ID 046d:081d Logitech, Inc. HD Webcam C510
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 0bda:5489 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

usb-devices:
xaviernx:~$ usb-devices

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 4
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev=04.09
S: Manufacturer=Linux 4.9.140-tegra xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=3610000.xhci
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=480 MxCh= 4
D: Ver= 2.10 Cls=09(hub ) Sub=00 Prot=02 MxPS=64 #Cfgs= 1
P: Vendor=0bda ProdID=5489 Rev=01.40
S: Manufacturer=Generic
S: Product=4-Port USB 2.0 Hub
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 1 #EPs= 1 Cls=09(hub ) Sub=00 Prot=02 Driver=hub

T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=32 #Cfgs= 1
P: Vendor=046d ProdID=c52b Rev=24.10
S: Manufacturer=Logitech
S: Product=USB Receiver
C: #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=98mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid
I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
I: If#= 2 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid

T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=02 Dev#= 6 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=046d ProdID=081d Rev=00.10
S: SerialNumber=49E1F0A0
C: #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio
I: If#= 1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio
I: If#= 2 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=(none)
I: If#= 3 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=(none)

T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=13d3 ProdID=3549 Rev=00.00
S: Manufacturer=Realtek
S: Product=Bluetooth Radio
S: SerialNumber=00e04c000001
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=10000 MxCh= 4
D: Ver= 3.10 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
P: Vendor=1d6b ProdID=0003 Rev=04.09
S: Manufacturer=Linux 4.9.140-tegra xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=3610000.xhci
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=02 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=10000 MxCh= 4
D: Ver= 3.20 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
P: Vendor=0bda ProdID=0489 Rev=01.40
S: Manufacturer=Generic
S: Product=4-Port USB 3.0 Hub
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

Hello,

Always attach the full one on this forum please. We don’t want to miss any info there.

Please use the upload button to attach the text files.

Sure boss :D
but again mine is for wireless although looks to impact my wired usb webcam too.

dmesg_dump.txt (60.7 KB)

1 Like

Hi,

Unfortunately, there is no fatal error from usb driver here. I can see the receiver appeared.

According to the dmesg, can I confirm that this log is the case that you plug the device and boot up NX, right?
This is not a usb hotplug case which you plug the device after OS is ready.

Do you really see error under such case? Actually, our usb team has seen such error on same Logitech mouse on his laptop before. So we suspect this is Logitech wireless mouse problem. If you only connect webcam, will you see problem?

And is your webcam still working when mouse error happens?

yep fresh boot with devices already plugged.
That said it was working fine on 4.4.

Just removed the wireless receiver and triggered reboot.

lsusb
lsusb
Bus 002 Device 002: ID 0bda:0489 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:3549 IMC Networks
Bus 001 Device 004: ID 046d:081d Logitech, Inc. HD Webcam C510
Bus 001 Device 002: ID 0bda:5489 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

still no /dev/video0 device

dmesg_dump_camera_only.txt (60.3 KB)

Could you also try both cold boot(remove power cable and plug it back) and warm boot (sudo reboot) under such case and see when will webcam has video0 node and when does not?

Need to find a way to reproduce this issue on my side for further debug.

all cases so far were warm reboots. Just tried cold (sudo shutdown 0, wait, unplugged, plugged back) and same result.
No /dev/video0
lxaviernx:~$ lsusb
Bus 002 Device 002: ID 0bda:0489 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:3549 IMC Networks
Bus 001 Device 004: ID 046d:081d Logitech, Inc. HD Webcam C510
Bus 001 Device 002: ID 0bda:5489 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg_dump_camera_only_coldboot.txt (60.5 KB)

Does video0 ever appear after you upgrade to rel-32.5?

before I was on JetPack 4.4 and rel-32 only from memory.
did the OTA rel32.5 and apt install jetpack then rebooted.
Prior to that I was using cheese or the deepstreamapp with usb source with no issues.
Since the update to rel32.5 and 4.5 neither do work, be it the wireless keyboard and mouse or the webcam.

Cheers
Manu

Hello @ManuInNZ,

I notice there is no uvc driver from your dmesg. Tried with two webcam on my side with jetpack4.5, but cannot reproduce error.

According to your description, it sounds that you did OTA upgrade to jp4.5 but not directly flash it. Maybe there is some problem in OTA. Not sure if @jd_silver2010 also uses OTA upgrade but not reflash the board with sdkmanager?

I would suggest maybe you can try to re-flash (if it is okay for you) the board and see if issue is still.

dmesg --level=err output
the message the same for boot up with connected mouse and keyboard and when boot up without mouse/keyboard hookup till after fully booted.

imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 2.018027] imx219 9-0010: board setup failed
[ 2.041895] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)
[ 2.042204] imx219 10-0010: board setup failed
[ 2.969745] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[ 3.844332] cgroup: cgroup2: unknown option “nsdelegate”
[ 4.009786] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[ 5.221779] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[ 6.113781] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[ 6.114155] usb usb1-port2: unable to enumerate USB device
[ 6.801709] usb 1-3: device not accepting address 6, error -71
[ 7.341758] usb 1-3: device not accepting address 7, error -71
[ 7.897876] usb 1-3: device descriptor read/64, error -71
[ 8.133959] usb 1-3: device descriptor read/64, error -71
[ 8.481856] usb 1-3: device descriptor read/64, error -71
[ 8.709866] usb 1-3: device descriptor read/64, error -71

Then after some iterations with power up and the mouse/keyboard worked (for how long is ?) got this from SSH with dmesg

dmesg --level=err
[ 2.003539] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 2.004212] imx219 9-0010: board setup failed
[ 2.028279] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)
[ 2.028631] imx219 10-0010: board setup failed
[ 3.522412] cgroup: cgroup2: unknown option “nsdelegate”
jdc@xaviernx:~$ lsusb
Bus 002 Device 002: ID 0bda:0489 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:3549 IMC Networks
Bus 001 Device 005: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 004: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 002: ID 0bda:5489 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Hello,

As I said in previous comment, please share us the full dmesg and attach as a text file.

Also, please go through previous discussion and see if OTA is related to your issue.

Hi Wayne, for my particular situation I was in 10W Desktop mode and had noticed on jtop that the thermal readings were around 50 C. I thought that was a little warm and maybe bump up to 15W mode (mode 2 I think) so there would be adequate current for the USB ports … did that.

Inadvertently of course, the fan operation started keeping temps to 30 to 33 C instead of the 50 C it was running at in the 10W Desktop mode with ‘quiet’ fan. Everything worked … mouse/keyboard and they acted perfectly normal. When I rebooted, as the system retains that power mode (15W), everything booted just fine with everything working.

However, I rebooted again and, even though the NX booted in 15W mode as before… the fan did not come on. That seems to be a bug with an intermittent characteristic in there. I watched the temps creep up checking for mouse and keyboard activity and when the thermals got to around 44 C… they stopped working as some thermal shutting down of board elements seemed to come into play. The mouse/keyboard USB does not recover until a shutdown, cool off period and reboot.

I wonder if I should modify the fan config to make sure it always come up in a certain PWM setting but don’t know how to do that yet. Perhaps you can help with that ( I saw the temp trip points in the documentation) but this entire scenario may be affecting our friend here as well.

Hope this helps… I don’t believe it is a OTA or kernel thing anymore … perhaps you can confirm. Thanks

I think I found my issue which is not being careful.

I have used the “rootOnNVMe” hack but did not fully recopy the files to the SD after the OTA.
I flashed again the SD with a brand new 4.5 and I am all good now.
So, so far so good.

Cheers
Manu

Hi @jd_silver2010 ,

First, thanks for your analysis. You can use below node to control the PWM fan. You can echo 0~255 to this node to control.

root@nvidia-desktop:/sys/devices/pwm-fan# cat cur_pwm
130

Second, I still need your full dmesg when error happens. Honestly, I cannot confirm anything with current info. Even if you don’t think kernel thing is related to your issue, please still share the full dmesg to us. It should not take you too much time by just reproducing the error and then type command “dmesg”. If you have any difficulty in doing that, please let us know.

Also, if you think OTA is not related to your issue, how about reflashing your board and see if above behavior is still?

We need you to provide precise steps so that we can reproduce your issue.
If you think all those stuff are not related to your issue except the temperature, I will just push my device temperature to 44C with Jetpack4.5 and see if it can reproduce issue or not.

I understand regarding the dmesg request. When I saw those messages it was an error -71. However, I know it is a temperature issue as I’ve replicated it several yesterday and is a very simple experiment for you to replicate as well and you will see. I had no issues after understanding this since yesterday.

It doesn’t matter what power mode the xavier nx is in. I executed 'sudo sh -c ‘echo 0 > /sys/devices/pwm-fan/target_pwm’ to shut off the fan. Then watch the temps increase to around 42-45 C on jtop… and like ‘clockwork’ the functionality of the mouse and keyboard stopped. I replicated this just before I sent this to you. I don’t know if this is expected by the NVIDIA Xavier folks and is engineered this way but it is what it does. You should have fun replicating it, I think it is normal operation at those temps but that is for your team to decide. Thanks so much for your responses… have fun with the replication and let me know, if you would, if this truly is expected USB function disabling or whatever.

If it is an engineered expectation by NVIDIA perhaps a note somewhere in documentation is called for so others understand it as well. Here in Texas I have to wonder how a quadcopter or other device using the Xavier manages thermals when the outside temperature is high as 95 to 105 F is not uncommon and the 44 C or so is only 129F or so… The temperature differential may make it difficult for the quadcopter or UAV to continue operating during a flight cycle with dependencies on USB which they all likely use.