After entering the boot screen, the mouse and keyboard cannot be used, and you cannot click to switch other usb ports

hello
After the system is started, the mouse and keyboard cannot be clicked when the password input screen is displayed. After the system is entered through the debugging serial port, dmesg -w detects the following usb information:
[ 131.157995] usb 2-1.2: new SuperSpeed USB device number 5 using tegra-xusb
[ 131.189372] usb 2-1.2: Devi[ ce .18is 9372] usb 2-1.2: Dnotevi auce thonot aurizthorized forfor usage
age
[ 131.261708] usb 1-2.2: new high-speed USB device number 8 using tegra-xusb
[ 131.368119] usb 1-2.2: Device is not authorized for usage[
131.368119] usb 1-2.2: Device is not authorized for usage
1.txt (59.3 KB)

The dmesg -w information is saved in 1.txt
The system startup date is listed in 2.txt
2.txt (40.6 KB)

Hi yc13,

Are you using the devkit or custom board for Orin NX?
What’s the Jetpack version in use?

Are you connecting a DP display?
Could you interact with the board through serial console?

Thank you for your reply
I’m using a self-developed carrier,Jetpack version is 6.0,l4t version is 36.3
My dev board only has hdmi ports. I couldn’t click anything after connecting the display, and then I found the device unauthorized in dmesg-w through the debug serial port

I would like to add that I have confirmed that the usb interface of the development board is good

How did you flash the board?
Please share the flash command and full log for further check.

Do you mean that the issue is specific to your custom carrier board?

Thank you for your reply
1.I am using the following command flash:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–showlogs --network usb0 y-c11f1e2-orin-nx-363 internal
2There’s no flash log anymore. It was done a long time ago
3.Because the system is now in the hard disk, we brush a set of normal equipment, and then exclude through the control variable method, and finally ensure that the module and development board are no problem, it should be the system problem, and then enter the system through the debugging serial port, dmesg -w plug and unplug usbhub, and then report an error unauthorized

It seems you are using a custom carrier board config.
Is your custom board config derived from jetson-orin-nano-devkit.conf or p3509-a02-p3767-0000.conf?

Do you mean that the USB have issue from long time before?

Could you reproduce the same behavior on the devkit?

Thank you for your reply
1.The conf file I used was modified based on jetson-orin-nano-devkit.conf
2.The system was flash long time ago,but the usb problem was only recently discovered
3.I’m sorry, I don’t have Devkit in hand now, do you have any investigation ideas or solutions

Is the board designed by you?

Do you have another board w/o the issue?
If so, could you compare the dmesg between them?

Thank you for your reply
1.We designed the board ourselves
2.I have made a comparison, I use the same set of equipment to write the same system, the other one is normal, but there is a problem that the mouse and keyboard of this system cannot be clicked, after entering the system through the debugging serial port, dmesg-w displays
[ 131.189372] usb 2-1.2: Devi[ ce .18is 9372] usb 2-1.2: Dnotevi auce thonot aurizthorized forfor usage
age
[ 131.261708] usb 1-2.2: new high-speed USB device number 8 using tegra-xusb
[ 131.368119] usb 1-2.2: Device is not authorized for usage[
131.368119] usb 1-2.2: Device is not authorized for usag

Do you have any custom design in USB may cause this issue?
We don’t hit this issue on the devkit so that you can also get a devkit to compare the USB related logs.

Could you run the following command to check the list of blocked device?

$ sudo apt install usbguard
$ sudo usbguard list-devices

And please share the result of the following command.

grep . /sys/bus/usb/devices/usb*/authorized_default

Thank you for your reply
1.I suspect that one of the rules under udev has been changed, but I have compared a normal system and the USB-related rules under udev are the same
2.I will execute the command and return the value to you later

I carried out the steps you gave and the results are as follows:
nvidia@tegra-ubuntu:~$ sudo apt install usbguard
[sudo] password for nvidia:
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
usbguard is already the newest version (1.1.1+ds-3).
The following packages were automatically installed and are no longer required:
gdal-data libaec0 libarmadillo10 libarpack2 libavcodec-dev libavformat-dev
libavutil-dev libblosc1 libcfitsio9 libcharls2 libdc1394-dev libdeflate-dev
libdouble-conversion3 libevent-core-2.1-7 libevent-pthreads-2.1-7
libexif-dev libfabric1 libfreexl1 libfyba0 libgdal30 libgdcm-dev libgdcm3.0
libgeos-c1v5 libgeos3.10.2 libgeotiff5 libgl2ps1.4 libglew2.2 libgphoto2-dev
libhdf4-0-alt libhdf5-103-1 libhdf5-hl-100 libheif1 libhwloc-plugins
libhwloc15 libilmbase-dev libjbig-dev libjpeg-dev libjpeg-turbo8-dev
libjpeg8-dev libjsoncpp25 libkmlbase1 libkmldom1 libkmlengine1 liblept5
libminizip1 libmysqlclient21 libnetcdf19 libodbc2 libodbcinst2 libogdi4.1
libopencv-calib3d4.5d libopencv-contrib4.5d libopencv-dnn4.5d
libopencv-features2d4.5d libopencv-flann4.5d libopencv-highgui4.5d
libopencv-imgcodecs4.5d libopencv-imgproc4.5d libopencv-ml4.5d
libopencv-objdetect4.5d libopencv-photo4.5d libopencv-shape4.5d
libopencv-stitching4.5d libopencv-superres4.5d libopencv-video4.5d
libopencv-videoio4.5d libopencv-videostab4.5d libopencv-viz4.5d
libopenexr-dev libopenmpi3 libpmix2 libpng-dev libpq5 libproj22
libraw1394-dev librttopo1 libsocket++1 libspatialite7 libsuperlu5
libswresample-dev libswscale-dev libsz2 libtbb-dev libtesseract4 libtiff-dev
libtiffxx5 libucx0 liburiparser1 libvtk9.1 libwpe-1.0-1
libwpebackend-fdo-1.0-1 libxerces-c3.2 libxnvctrl0 mysql-common proj-data
python-pkg-resources python-setuptools unixodbc-common
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
nvidia@tegra-ubuntu:~$ sudo usbguard list-devices
16: allow id 1d6b:0002 serial “3610000.usb” name “xHCI Host Controller” hash “X9UjuczllGLsNEHLlK9LKX+bNQKe0VBOlCYL81NvfTk=” parent-hash “8JqgBXaM8v6JuZRvegrUEXCQ8GB4pS4GIYenP2Y4oPc=” via-port “usb1” with-interface 09:00:00 with-connect-type “”
17: allow id 1d6b:0003 serial “3610000.usb” name “xHCI Host Controller” hash “rPjAHzsMp5wSYD51bVEgLHYS0OA6LVupcmhGZILZ1lI=” parent-hash “8JqgBXaM8v6JuZRvegrUEXCQ8GB4pS4GIYenP2Y4oPc=” via-port “usb2” with-interface 09:00:00 with-connect-type “”
18: allow id 047c:650a serial “” name “” hash “GjbfrFPvCPl9QJrazom1lJp+/j28YBn9jbFqz/1WHic=” parent-hash “X9UjuczllGLsNEHLlK9LKX+bNQKe0VBOlCYL81NvfTk=” via-port “1-2” with-interface { 09:00:01 09:00:02 } with-connect-type “unknown”
19: allow id 047c:6508 serial “” name “” hash “febK1U8PNy7tCaXUvUOaMmfow9lBJtaqZrPLfWoTK1Y=” parent-hash “rPjAHzsMp5wSYD51bVEgLHYS0OA6LVupcmhGZILZ1lI=” via-port “2-1” with-interface 09:00:00 with-connect-type “unknown”
20: allow id 0424:2514 serial “” name “” hash “npSDT1xuEIOSLNt2RT2EbFrE8XRZoV29t1n7kg6GxXg=” parent-hash “GjbfrFPvCPl9QJrazom1lJp+/j28YBn9jbFqz/1WHic=” via-port “1-2.4” with-interface { 09:00:01 09:00:02 } with-connect-type “unknown”
21: allow id 0424:7800 serial “” name “” hash “ns76jMEfaA0pwhcFEH3TMPJtuoNZEpI1xI9qHmWoA9o=” parent-hash “febK1U8PNy7tCaXUvUOaMmfow9lBJtaqZrPLfWoTK1Y=” via-port “2-1.1” with-interface ff:00:ff with-connect-type “unknown”
nvidia@tegra-ubuntu:~$ grep . /sys/bus/usb/devices/usb*/authorized_default
/sys/bus/usb/devices/usb1/authorized_default:0
/sys/bus/usb/devices/usb2/authorized_default:0
nvidia@tegra-ubuntu:~$

Do you still have the issue or you’ve managed to get it work?

Thank you for your reply
This problem has not been solved, a few days ago I needed to use that hard disk to refresh the machine without this problem. But are there any good ideas for the next time

Do you mean the issue disappear after you reflash the board?
If so, we would like to know the exact reproduce steps so that we can debug it in details.
Or you can monitor this issue for a while.

Thank you for your reply
Yeah, same equipment. After I re-flash, the mouse and keyboard are normal。
I’ll keep using it for a while to see if that’s the case again

okay~ please let us know if the similar issue come up, and you can provide the full serial console log at that moment for further check.

ok
thanks

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.