TX2 eth0 can not work

The TX2 eth0 can not ping other ip,and other pc can not ping the TX2.
In kern.log I find the eth0 is only 100Mbps, it is abnormally.
How can I debug this problem,and How to know the hardware is normal?

[    9.735625]eqos 2490000.ether_qos eth0:Link is Up - 100Mbps/Full - flow control rx/tx

Thanks!

Are the two going through a switch? Router? Direct?

On both systems, what is the output from “ifconfig” and “route”?

Thanks for help.
Direct by cable betwwen TX2 and PC.
ifconfig

docker0   Link encap:Ethernet  HWaddr 02:42:87:42:b2:1e  
          inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0      Link encap:Ethernet  HWaddr 00:04:4b:a5:d0:ae  
          inet addr:192.168.1.69  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::204:4bff:fea5:d0ae/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:116 errors:0 dropped:0 overruns:0 frame:0
          TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:13022 (13.0 KB)  TX bytes:5211 (5.2 KB)
          Interrupt:42 

l4tbr0    Link encap:Ethernet  HWaddr b2:bb:2b:a9:bb:96  
          inet addr:192.168.55.1  Bcast:192.168.55.255  Mask:255.255.255.0
          inet6 addr: fe80::9068:62ff:fee2:5e8c/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:857 (857.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2069 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2069 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:290925 (290.9 KB)  TX bytes:290925 (290.9 KB)

usb0      Link encap:Ethernet  HWaddr f2:24:b2:a4:54:9f  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

usb1      Link encap:Ethernet  HWaddr b2:bb:2b:a9:bb:96  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:04:4b:a5:d0:ac  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

route

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
link-local      *               255.255.0.0     U     1000   0        0 eth0
172.17.0.0      *               255.255.0.0     U     0      0        0 docker0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
192.168.55.0    *               255.255.255.0   U     0      0        0 l4tbr0

TX2 can only ping 127.0.0.1 , 192.168.1.69 normally!
PC is windows system ,ip config correctly

Some ethernet cards will require a “crossover” cable to connect directly. I’d suggest first adding a switch in if you can, or if not, then try a crossover cable. Possibly this is an issue.

I’ll need to the “ifconfig” and “route” output from both the Jetson and the host PC (the two work together). Also, verify that you’ve set your host PC up to act as a DHCP server (or that you’ve assigned a static IP address to the Jetson…without a router this is mandatory for the Jetson to have an address). Also verify if the micro-B USB cable is connected from Jetson to host PC.

Hi,

Direct Ethernet connection between Jetson-PC requires a crossover cable as linuxdev mentioned, also a switch connection between devices should work.

Regards.

The TX2 has some problem with the hardware of eth0 that is confirmed by my supplier.
But the supplier have no more detail about the problem.
Thanks to linuxdev,greivin.fallas for help!

There have been cases in the past where some high end managed switches have options not compatible with all ethernet, and there have also been rare cases where inexpensive older network hardware has had some unidentifiable fluke causing an error. Were you able to confirm eth0 works with different network hardware? I’m not sure if you consider this closed from your view or not.