Minimal rootfs get strange net port

Hi,
My dev is Agx orin devkit 64GB.And use Jetson Linux 36.4.3.
I am trying to use minimal rootfs.I follow Root File System — NVIDIA Jetson Linux Developer Guide to build minimal rootfs and it is success.Here is log:
build_rfs.txt (449.9 KB)
Then I unzip it to Linux_for_Tegra/rootfs.Follow Quick Start — NVIDIA Jetson Linux Developer Guide to flash image to my dev.

$ tar xf ${L4T_RELEASE_PACKAGE}
$ sudo tar xpf ${SAMPLE_FS_PACKAGE} -C Linux_for_Tegra/rootfs/
$ cd Linux_for_Tegra/
$ sudo ./tools/l4t_flash_prerequisites.sh
$ sudo ./apply_binaries.sh
$ sudo ./flash.sh jetson-agx-orin-devkit internal

apply.txt (25.0 KB)
flash.txt (99.1 KB)

After flash finish and system boot,I got strange net port like this:

nvidia@tegra-ubuntu:~$ ifconfig 
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 88  bytes 6568 (6.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 88  bytes 6568 (6.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether e6:3f:f6:8d:a4:e1  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether e6:3f:f6:8d:a4:e3  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I have connect ethernet port to my router,but eth0 do not auto up.Which step is wrong?Here is dmesg:
dmesg.txt (62.3 KB)

Thanks.

Correct a mistake:I do not run “sudo tar xpf ${SAMPLE_FS_PACKAGE} -C Linux_for_Tegra/rootfs/”.

I can’t answer, but will add an observation: There are no TX bytes and no RX bytes on either USB Ethernet device. Loopback is not the interface you are asking about, and it appears to be correct.

Auto configuration is via DHCP, and the Ethernet would have needed to send some bytes to request DHCP assignment, then the interface would have received some bytes. Nothing was ever sent or received. This tends to imply the interface was not configured to ask for an address.

The fact that the usb0 and usb1 exist tends to say the driver is installed and working. My thought is that you might need some further setup or configuration.

Thanks for your response.I had found that because minimal rootfs do not install networkmanager so that ethx can not auto up.Now it can work.

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