Hi,
Yesterday I connected my Windows computer to the TX2 with an ethernet cable. Then I used the ssh command to successfully access the TX2. Basically I just did ssh nvidia@[ip address]
Woke up today and no idea what happened except that both computers have restarted. SSH no longer works. The TX2 no longer shows an ip address when using ifconfig. Googled the problem a bit but did not get anywhere. Tried rebooting, ifdown, ifup, modifying /etc/network/interfaces with auto eth0 and iface eth0 inet dhcp. No luck and I don’t know what I am doing, just trying whatever I see on Google and thought I’d ask here as well.
Could you boot up the device, check if the ethernet interface is alive or not and then dump the dmesg log?
This is what is outputted after running dmesg after plugging in the ethernet cable
[ 172.177582] eqos 2490000.ether_qos eth0: Link is Up - 10Mbps/Full - flow control off
[ 172.187183] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 173.510981] eqos 2490000.ether_qos eth0: Link is Down
[ 176.352166] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control off
Are you plugging in the cable only after it boots? I am guessing the above log “after plugging in the ethernet cable” was for testing purposes, and that normally the cable is always plugged in, but need to confirm. In the case where that log shows up after plugging in the cable, what do you see from “ifconfig
” and “route
”? Do you ever use WiFi (I ask because NetworkManager can interfere with wired when WiFi is enabled)?
At the end of the ifconfig
output for eth0
you will see a line similar to this:
device interrupt 41
If you adjust for any different interrupt number (I’ll use “41
” as an example, adjust for your case), then what do you see from:
egrep '(CPU0| 41:|IPI|Err:)' /proc/interrupts
In the previous reply, I plugged in the ethernet cable after the Jetson has booted up. I was also using WiFi. In response to your suggested commands to run, I have disabled WiFi, plugged in the ethernet cable, and rebooted. Thanks for the help.
nvidia@tegra-ubuntu:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:4b:a7:da:ce
inet6 addr: fe80::7635:d166:2f8c:cb90/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2330 (2.3 KB) TX bytes:1684 (1.6 KB)
Interrupt:42
l4tbr0 Link encap:Ethernet HWaddr ae:dc:e4:69:3a:31
inet addr:192.168.55.1 Bcast:192.168.55.255 Mask:255.255.255.0
inet6 addr: fe80::bcfd:fff:fee5:1f3d/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1148 (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:164 errors:0 dropped:0 overruns:0 frame:0
TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:12080 (12.0 KB) TX bytes:12080 (12.0 KB)
usb0 Link encap:Ethernet HWaddr ae:dc:e4:69:3a:31
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 fa:ac:67:52:9b:45
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)
nvidia@tegra-ubuntu:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
link-local * 255.255.0.0 U 1000 0 0 l4tbr0
192.168.55.0 * 255.255.255.0 U 0 0 0 l4tbr0
nvidia@tegra-ubuntu:~$ egrep ‘(CPU0| 42:|IPI|Err:)’ /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
42: 818 0 0 0 0 0 GICv2 226 Level ether_qos.common_irq
IPI0: 57932 12804 17405 87451 81939 79177 Rescheduling interrupts
IPI1: 41 33 29 33 23 31 Function call interrupts
IPI2: 0 0 0 0 0 0 CPU stop interrupts
IPI3: 0 0 0 0 0 0 Timer broadcast interrupts
IPI4: 4164 481 531 2766 2972 2782 IRQ work interrupts
Err: 0
nvidia@tegra-ubuntu:~$
According to the kernel log
[ 176.352166] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control off
and your ifconfig result,
eth0 Link encap:Ethernet HWaddr 00:04:4b:a7:da:ce
inet6 addr: fe80::7635:d166:2f8c:cb90/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2330 (2.3 KB) TX bytes:1684 (1.6 KB)
Interrupt:42
It looks like kernel side is still working fine.
Also, re-check the comment and I found you are doing device to device connection but not through a router.
What was IP that made yoru ssh work in the last time? Generally, if your Windows host has dhcp server installed, the IP will be assigned to your tx2 from the windows machine. However, the later test result feels like it does not have IP assignment from Windows computer.
You can try to manually assign the IP to tx2 by using the Ubuntu GUI. And do such setting over Windows and try to ping each other.
Hi Wayne,
That is correct, it is just a plain old ethernet cable going from Jetson to a Windows PC. Nothing in between.
The IP that made it work last time was 192.168.137.36
Not quite sure about what to do regarding this:
You can try to manually assign the IP to tx2 by using the Ubuntu GUI. And do such setting over Windows and try to ping each other.
But will try to add that IP in Ubuntu GUI as a static IP and see if it works.
Yes, what I mean is just set static IP through ubuntu GUI. Since ethernet connection involves both side devices to work, you cannot only configure the tx2 side. The Windows side machine is also necessary. The Windows machine should also set a static IP manually.
And that has fixed it! I set the Jetson back to 192.168.137.36 and the Windows machine to 192.168.137.37. Now everything works as it did. No idea how it worked last time with everything automatic.
Thanks for the help Wayne! Perhaps this was a simple question for a lot of people but for someone like me with no networking knowledge it was definitely a big help
1 Like