[ 12.184868] tegra-xusb 3610000.usb: Adding to iommu group 56
[ 12.199835] tegra-xusb 3610000.usb: Firmware timestamp: 2023-02-10 03:48:10 UTC
[ 12.199846] tegra-xusb 3610000.usb: xHCI Host Controller
[ 12.199863] tegra-xusb 3610000.usb: new USB bus registered, assigned bus number 1
[ 12.200607] tegra-xusb 3610000.usb: hcc params 0x0180ff05 hci version 0x120 quirks 0x0000000000010810
[ 12.200636] tegra-xusb 3610000.usb: irq 127, io mem 0x03610000
[ 12.200761] tegra-xusb 3610000.usb: xHCI Host Controller
[ 12.200765] tegra-xusb 3610000.usb: new USB bus registered, assigned bus number 2
[ 12.200769] tegra-xusb 3610000.usb: Host supports USB 3.1 Enhanced SuperSpeed
[ 12.201055] hub 1-0:1.0: USB hub found
[ 12.201071] hub 1-0:1.0: 4 ports detected
[ 12.201444] hub 2-0:1.0: USB hub found
[ 12.201454] hub 2-0:1.0: 4 ports detected
What is the result of “lsusb” in this situation?
Also, what is the dmesg and lsusb result after you plug in a USB mouse? Will you see dmesg print something new or lsusb give you a new device there?
And one more test, could you use a type C to type A adapter and put your mouse on it to the type C port on Jetson? Again check dmesg and lsusb give you anything new after that.
I am surprised that this issue has persisted since being originally reported, and a fix being proposed.
In any case, I am satisfied with this solution even though it does not appear to address the most recent problem I have been having with connecting physical peripherals (and apologize to anyone else experiencing the same issue for stopping here).
No, it’s not. But, from a big picture standpoint, it satisfies my desire to get graphical access to the device. I will continue to troubleshoot the DisplayPort and mouse/keyboard issues over time, but for now, I am satisfied.
Just to clarify. If this turns out to be a hardware issue, I would suggest you to do the RMA (return the board for new one). It is not a good idea to use a broken hardware while your warranty is still valid.