The ethernet port not work

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

ifconfig -a shows
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:b1:61:9f:01 txqueuelen 0 (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

dummy0: flags=130<BROADCAST,NOARP> mtu 1500
ether e2:0a:28:af:c9:1d 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

eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 48:b0:2d:5a:85:3c 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
device interrupt 37

l4tbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.55.1 netmask 255.255.255.0 broadcast 192.168.55.255
inet6 fe80::d882:6dff:fe55:abb1 prefixlen 64 scopeid 0x20
inet6 fe80::1 prefixlen 128 scopeid 0x20
ether da:82:6d:55:ab:b1 txqueuelen 1000 (Ethernet)
RX packets 523 bytes 100150 (100.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 934 bytes 101807 (101.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1 (Local Loopback)
RX packets 1713 bytes 119333 (119.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1713 bytes 119333 (119.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

rndis0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::d882:6dff:fe55:abb1 prefixlen 64 scopeid 0x20
ether da:82:6d:55:ab:b1 txqueuelen 1000 (Ethernet)
RX packets 253 bytes 41645 (41.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 106 bytes 16834 (16.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::d882:6dff:fe55:abb3 prefixlen 64 scopeid 0x20
ether da:82:6d:55:ab:b3 txqueuelen 1000 (Ethernet)
RX packets 299 bytes 63036 (63.0 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 934 bytes 170532 (170.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lspci -v shows:
0005:03:00.0 Ethernet controller: Intel Corporation Device 15f3 (rev 03)
Subsystem: Intel Corporation Device 0000
Flags: fast devsel
Memory at 1f40c00000 (32-bit, non-prefetchable) [disabled] [size=1M]
Memory at 1f40e00000 (32-bit, non-prefetchable) [disabled] [size=16K]
[virtual] Expansion ROM at 1f40d00000 [disabled] [size=1M]
Capabilities:

0005:04:00.0 Ethernet controller: Intel Corporation Device 15f3 (rev 03)
Subsystem: Intel Corporation Device 0000
Flags: fast devsel
Memory at 1f40f00000 (32-bit, non-prefetchable) [disabled] [size=1M]
Memory at 1f41100000 (32-bit, non-prefetchable) [disabled] [size=16K]
[virtual] Expansion ROM at 1f41000000 [disabled] [size=1M]
Capabilities:

0005:05:00.0 Ethernet controller: Intel Corporation Device 15fd (rev 01)
Subsystem: Intel Corporation Device 0000
Flags: fast devsel
Memory at 1f40000000 (32-bit, non-prefetchable) [disabled] [size=8M]
Memory at 1f40800000 (32-bit, non-prefetchable) [disabled] [size=16K]
Capabilities:

0005:06:00.0 Ethernet controller: Intel Corporation Device 15f3 (rev 03)
Subsystem: Intel Corporation Device 0000
Flags: fast devsel
Memory at 1f41200000 (32-bit, non-prefetchable) [disabled] [size=1M]
Memory at 1f41400000 (32-bit, non-prefetchable) [disabled] [size=16K]
[virtual] Expansion ROM at 1f41300000 [disabled] [size=1M]
Capabilities:

the four ethernet port in the carrier board can not be found in system, any solution?

2

Is it Xavier NX devkit or custom carrier board?
Which JetPack version you used on this device?

4

custom carrier board,
jetpack 4.6 ,l4t32.72

5

Have you followed the Xavier NX adaptation guide to bring up your devcie?
See NVIDIA Jetson Linux Driver Package Software Features : Jetson Module Adaptation and Bring-Up | NVIDIA Docs

7

Since you are telling PCIe. Which means this is not going through NV native ethernet driver/controller.

And lspci can show your Intel card. Which means this is not NV issue. Please contact the card vendor for help.

8

the ethernet chip is intel i225 , should I install the driver?

10

OK , it’s i225 chip driver problem

11

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