L4tbr0 USB Serial/Ethernet bridge does not work after update to JetPack 5.0.2

I updated my Orin developer kit to JetPack 5.0.2 following Jetpack 5.0.2 with Jetson Linux 35.1 is now live! and I am able to log in to the developer kit after the upgrade through a display, but I do not see the USB-Ethernet bridge come up on my Ubuntu PC connected over the provided USB-C cable plugged into the USB-C port (same side as the exposed header and 2 USB-A ports). I see the following error in dmesg -w:

[264863.566008] usb 1-10.1: USB disconnect, device number 18
[264863.788642] usb 1-10.1: new high-speed USB device number 19 using xhci_hcd
[264863.889549] usb 1-10.1: New USB device found, idVendor=0955, idProduct=7023, bcdDevice= 4.01
[264863.889552] usb 1-10.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[264863.889555] usb 1-10.1: Product: APX
[264863.889557] usb 1-10.1: Manufacturer: NVIDIA Corp.
[297221.983547] usb 1-10.1: USB disconnect, device number 19
[297243.870100] usb 2-10-port1: config error

And on the Jetson I see ifconfig -a showing l4tbr0 as not up or running and dmesg -w showing:

l4tbr0: port 1(rndis0) entered blocking state
l4tbr0: port 1(rndis0) entered disabled state
device rndis0 entered promiscuous mode
l4tbr0: port 2(usb0) entered blocking state
l4tbr0: port 2(usb0) entered disabled state
device usb0 entered promiscuous mode

and nothing after that shows that either l4tbr0 port properly activates/configures itself.

Could someone give me an idea of what to look for to see why the serial port ttyACM0 and the Ethernet interface are not showing up on my connected Ubuntu PC?

1 Like

Sorry for the late response, have you managed to get issue resolved or still need the support? Thanks


There is a known issue. We are still checking the firx.

@kayccc I have not managed to resolve this issue.

I have encountered the same problem. Programming L4T R35.1 to my Orin devkit does not enumerate /dev/ttyACM0 on my host upon reboot. If I reprogram L4T R34.1.1, then /dev/ttyACM0 comes up as expected and I can complete the installation.

Is it possible that this behavior is the same for the AGX Xavier with JetPack 5.0.2?

This issue has already done some clarification on this post. So please check it first.

Your patch fixed my issue. Thanks!

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