AGX cannot detect USB network card during boot up

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
,
1

Hi，
I’m working on Jetpack 4.6 with AGX, a new issue pop up, the USB network card cannot be detected automatically during L4T boot up, I have to unplug the usb cable and plug again, the NIC worked properly.
here is the dmesg with “USB device” related, we can see during 1st time boot up, only usb hub ([ 2.069463] usb 1-1: New USB device found, idVendor=2109, idProduct=2817) was found, and no usb NIC info. when I re-plug the usb NIC, firstly USB hub found ([ 233.649439] usb 1-1: New USB device found, idVendor=2109, idProduct=2817), then the USB NIC was found and configured properly.([ 234.389436] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8153).
Highly appreciation for any comments or help.
Willian

attachment:
~$ dmesg | grep “USB device”
[ 1.715809] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.715816] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.717316] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 1.717322] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.043488] usb 1-1: new high-speed USB device number 2 using tegra-xusb
[ 2.069463] usb 1-1: New USB device found, idVendor=2109, idProduct=2817
[ 2.069470] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.783449] usb 1-1.3: new high-speed USB device number 3 using tegra-xusb
[ 2.804198] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8151
[ 2.804202] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 3.769655] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 3.769660] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.770436] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 3.770440] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 233.627505] usb 1-1: new high-speed USB device number 4 using tegra-xusb
[ 233.649439] usb 1-1: New USB device found, idVendor=2109, idProduct=2817
[ 233.649452] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 234.367552] usb 1-1.3: new high-speed USB device number 5 using tegra-xusb
[ 234.389436] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=8153
[ 234.389464] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 234.528052] usb 1-1.3: reset high-speed USB device number 5 using tegra-xusb

3

Is this on NV developer kit or your custom board?

Please also attach the full log.

4

Hi，
It’s my custom board, full dmesg attached, this time a 8152 usb NIC was used.
Thanks in advance.
Willian
agxboot.log (69.4 KB)

5

Could you use NV devkit to see if this issue is reproducible?

6

devkit ok (Type-A port), you can see after 2s this NIC was found. here is the log.
BR,
Willian

agxboot_devkit.log (71.8 KB)

7

Probably the board design here. What if other usb device?

What is the requirement of this NIC? USBSS? If so, will other usb SS device also hits this issue?

8

seems a bit error, you can see at the same time (8152 was found on devkit) a reltek 8151 NIC was found, obviously it’s a bit error. Might be caused by hw design?
BTW, can we force the system to detect all usb device again with a cli command?
Thanks.
Willian

9

From your logs the USB side was working without error. It was just that nothing decided it could work as a driver to the device. The RTL devices are pretty common though. What do you see from:
zcat /proc/config.gz | egrep 'CONFIG_USB_RTL8152='

Possibly, if you have that as “=y” (and default is “=y”), then something about the device’s response to USB query makes the driver think this is not a “stock” 8152 and might need some other driver.

If you don’t have command “/sbin/udevadm”, then you can install with “sudo apt-get install udevadm”. Then to force rescan this probably works (I did not test on a Jetson):
sudo udevadm trigger

10

hi，
Thanks for your kindly mentoring. zcat to check ‘CONFIG-USB-RTL8152’, the result is ‘y’.
And udevadm trigger could not trigger re-scan the USB device, I had to unplug and plug USB NIC again to get it work.
From the picture attached, you can see at 2.56s a USB device (idVendor=0bda, idProduct=8151) found, but indeed no this NIC attached, or even RTL has no this model. what happened?
After I unplug and plug again, the right product id (8152) was identified.
any issue can cause this product id wrong?
thanks.
Willian
image

11

If you monitor “dmesg --follow” on a unit which booted without the NIC being connected, and then insert the USB cable, what shows up in the logs? FYI, what little there was in the previous screenshot of the log was without error, but this was only a tiny fraction of what would go on.

Incidentally, instead of a screenshot for “lsusb”, you can create a log file which can be attached to the forum (which has the advantage of being searchable for text). Examples:

lsusb 2>&1 | tee log_lsusb.txt
sudo lsusb -t 2>&1 | tee log_lsusb-tree.txt
dmesg 2>&1 | tee log_dmesg.txt
13

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