After Flushing Jetpack 4.3 to Xavier with latest sdk manager can not connect to eth0

Hello , I have successfully installed latest Jetpack with latest sdk manager into the xavier
but after that when i connect Ethernet cable to xavier it is not receive network , i can not change manually the ip address and there is no led lights near the connector.

How this can be fixed ?
Thanks in advnce

Hi, sabi

The host is supposed to be a ubuntu 1804/1604. The issue happened on ubuntu right?
Since you can successfully install the jetpack, so you can keep the usb cabe connected and ssh into the xavier with ‘ssh user@192.168.55.1’ to get the states of the ethernet and also the dmesg log. After that pls share the information here.

Just some notes: As long as SDK Manager knows what user account name and address to use it won’t care about how this is actually accomplished. The default is via the USB cable which is emulating wired ethernet. Not only does this emulate an ethernet adapter, it also emulats a router and is able to assign address 192.168.55.100 to the host PC and 192.168.55.1 to the Xavier. So long as the host PC does not have some sort of security setup interfering this is the simplest way to go since it has no special requirements.

If you use wired ethernet, then this must be connected to a router to assign it a route, and the host PC has to be on that same router and able to reach the Xavier.

In both cases you must have completed the first boot account setup since ssh is useless without an account to connect to.

You might check ifconfig on the host and see if it has an interface with 192.168.55.100 showing (you’d need to leave the USB cable connected). Be certain you’ve completed the first boot account creation. If you use the external ethernet, then run “ifconfig” on the Jetson to see what the address is that was assigned by the router for eth0, and try to ping that from the host PC (and try to ping 192.168.55.1).

The are no lights on the connector , I have connected USB to Ethernet dongle and it works great in addition i have tested with usb cellular modem and it works also , I think the problem is in the connector

i have attached dmesg.log in following link

In my opinion the problem is with connector only , I have plugged usb to Ethernet connector and it is working fine

Thanks

@sabi

It’s know issue for the no lights of ethernet. I found nothing related to the ethernet from your logs. The usefull information has been buried in.

Could you share your log with command $ ifconfig ?

On my Xavier I could get two nodes. eth0 is for ethernet cable. l4tbr0 is simulated by the usb cable

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 192.168.7.111  netmask 255.255.255.0  broadcast 192.168.7.255
    inet6 fe80::e942:fe40:c9f4:47e4  prefixlen 64  scopeid 0x20<link>
    ether 00:04:4b:cb:d8:b0  txqueuelen 1000  (Ethernet)
    RX packets 72277  bytes 11796432 (11.7 MB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 119926  bytes 71108179 (71.1 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    device interrupt 40  
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::10ce:39ff:feb4:a301  prefixlen 64  scopeid 0x20<link>
    inet6 fe80::1  prefixlen 128  scopeid 0x20<link>
    ether 12:ce:39:b4:a3:01  txqueuelen 1000  (Ethernet)
    RX packets 1107064  bytes 405174674 (405.1 MB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 1106635  bytes 384240792 (384.2 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0