Ethernet interface isn't working on TX1 w/ Jetpack 2.3

Autonomous Machines Jetson & Embedded Systems Jetson TX1
1

I have a freshly flashed TX1 with Jetpack 2.3 and the ethernet adapter is not working. It was apparently able to complete the installation with the device connected to the network, but the ethernet interface has not worked since then.

When I run ifconfig I get a very strange looking interface name instead of the normal eth0. I’ve tried powering off the board completely and restarting, but the problem remains.

ubuntu@tegra-zac-2:~$ ifconfig
enx00044b5abce0 Link encap:Ethernet  HWaddr 00:04:4b:5a:bc:e0
          inet6 addr: fe80::204:4bff:fe5a:bce0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3306 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:366 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:427541 (427.5 KB)  TX bytes:1161 (1.1 KB)

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:559 errors:0 dropped:0 overruns:0 frame:0
          TX packets:559 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:40908 (40.9 KB)  TX bytes:40908 (40.9 KB)

wlan0     Link encap:Ethernet  HWaddr 00:04:4b:5a:bc:de
          inet addr:192.168.1.190  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::204:4bff:fe5a:bcde/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3676 errors:0 dropped:0 overruns:0 frame:0
          TX packets:310 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:538334 (538.3 KB)  TX bytes:31441 (31.4 KB)
2

I have that same wired ethernet naming on R24.2. It works fine…I don’t know which udev rule changed to get that naming, but udev tends to muck with naming rules. I wouldn’t consider that name to be part of the issue unless something is hard wired to the older naming scheme.

It does say it received a lot of packets without error, but sent a few with all error. That interface has an IPv6 address, but no IPv4. Quite possibly whatever that interface connects to is not expecting IPv6. Is it wired to a router? Or to the host via switch?

3

Thanks for the reply. I ended up reflashing the TX1 and the interface started working again. Same physical setup and the interface name is also the same as above.