Jetson Nano fails to connect in head-less mode

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
1

I have a Jetson Nano (2GB) connected to a HP (EliteBook) laptop running Ubuntu 18.04.5. With a HDMI monitor along with a keyboard/mouse, I completed the DLI class “Intro to AI on Jetson Nano”. With the next class I’m attempting to connect the Nano in a head-less mode (USB-C for power and USB microB for data). I’ve completely erased the 64G micro-SD card and completed a fresh install of the “jp451” image and verified this with a monitor and keyboard. With the Nano powered up I see the “L4T-README” disk on my laptop GUI and I can view the README files. I can also run “screen” and login to the Nano from the laptop using the “/dev/ttyACM0” device. What I cannot do is connect Firefox on the laptop to the Nano using the 192.168.55.1 address. The connection fails. Digging a little further I noticed that no Ethernet interface on the laptop gets a 192.168.55.100 address as the documentation suggests. I tried manually setting the “enp0s29u1u1i5” interface to 192.168.55.100 and confirmed I can ping in each direction on the USB cable. However the Web page connection still fails.

Here is the Tegra version from the Nano:

R32 (release), REVISION: 5.1, GCID: 26202423, BOARD: t210ref, EABI: aarch64, DATE: Fri Feb 19 16:45:52 UTC 2021

Here are “ifconfig -a” listings from before and after USB cable connect:
BEFORE:
root@hp1:~# ifconfig -a
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.30 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::6631:50ff:fe9c:1c4e prefixlen 64 scopeid 0x20
ether 64:31:50:9c:1c:4e txqueuelen 1000 (Ethernet)
RX packets 2538 bytes 1439604 (1.4 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 761 bytes 72348 (72.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xd7400000-d7420000

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 1000 (Local Loopback)
RX packets 170 bytes 14468 (14.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 170 bytes 14468 (14.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlo1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 00:24:d7:c2:23:08 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

AFTER:
root@hp1:~# ifconfig -a
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.30 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::6631:50ff:fe9c:1c4e prefixlen 64 scopeid 0x20
ether 64:31:50:9c:1c:4e txqueuelen 1000 (Ethernet)
RX packets 5694 bytes 3878077 (3.8 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2512 bytes 270529 (270.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xd7400000-d7420000

enp0s29u1u1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether e6:ae:33:9b:04:da 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

enp0s29u1u1i5: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 92:0b:c7:48:74:72 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

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 1000 (Local Loopback)
RX packets 435 bytes 43849 (43.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 435 bytes 43849 (43.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlo1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 00:24:d7:c2:23:08 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

Here is the dmesg output after a USB cable connect:
root@hp1:~# cat dm1
[ 1483.613311] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[ 1504.098290] usb 2-1.1: new high-speed USB device number 4 using ehci-pci
[ 1504.208263] usb 2-1.1: New USB device found, idVendor=0955, idProduct=7020
[ 1504.208268] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1504.208270] usb 2-1.1: Product: Linux for Tegra
[ 1504.208273] usb 2-1.1: Manufacturer: NVIDIA
[ 1504.208275] usb 2-1.1: SerialNumber: 1424320071556
[ 1504.351750] cdc_acm 2-1.1:1.2: ttyACM0: USB ACM device
[ 1504.352220] usbcore: registered new interface driver cdc_acm
[ 1504.352222] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 1504.405710] usbcore: registered new interface driver cdc_ether
[ 1504.426843] cdc_ncm 2-1.1:1.5: MAC-Address: 92:0b:c7:48:74:72
[ 1504.427311] cdc_ncm 2-1.1:1.5 usb0: register ‘cdc_ncm’ at usb-0000:00:1d.0-1.1, CDC NCM, 92:0b:c7:48:74:72
[ 1504.428036] usbcore: registered new interface driver cdc_ncm
[ 1504.431243] rndis_host 2-1.1:1.0 usb1: register ‘rndis_host’ at usb-0000:00:1d.0-1.1, RNDIS device, 3e:63:aa:45:a0:a1
[ 1504.432069] usbcore: registered new interface driver rndis_host
[ 1504.434015] usb-storage 2-1.1:1.4: USB Mass Storage device detected
[ 1504.437621] scsi host7: usb-storage 2-1.1:1.4
[ 1504.437790] usbcore: registered new interface driver usb-storage
[ 1504.446222] usbcore: registered new interface driver cdc_wdm
[ 1504.463373] usbcore: registered new interface driver rndis_wlan
[ 1504.481053] usbcore: registered new interface driver uas
[ 1504.489462] usbcore: registered new interface driver cdc_mbim
[ 1504.497048] rndis_host 2-1.1:1.0 enp0s29u1u1: renamed from usb1
[ 1504.511560] cdc_ncm 2-1.1:1.5 enp0s29u1u1i5: renamed from usb0
[ 1505.455171] scsi 7:0:0:0: Direct-Access Linux File-Stor Gadget 0409 PQ: 0 ANSI: 2
[ 1505.455802] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 1505.456378] sd 7:0:0:0: Power-on or device reset occurred
[ 1505.457114] sd 7:0:0:0: [sdb] 32768 512-byte logical blocks: (16.8 MB/16.0 MiB)
[ 1505.458027] sd 7:0:0:0: [sdb] Write Protect is on
[ 1505.458033] sd 7:0:0:0: [sdb] Mode Sense: 0f 00 80 00
[ 1505.458749] sd 7:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
[ 1505.461997] sdb:
[ 1505.464753] sd 7:0:0:0: [sdb] Attached SCSI removable disk

Is there something I’m missing on the laptop (Ubuntu) side to allow the usb-dev-mode connection. Is there something I can check on the Nano side using the “screen” login?
Thanks!

2

Sorry that I don’t quite understand your purpose here. What do you want to see on the firefox browser?

3

I was hoping to see a login prompt and see a Jupiter (sp?) page like I did for the previous DLI class.

4

No matter what kind of service it is. The web interface requires host and client.

If you want the client side browser can access the host side webpage or something else, you need a server that can initiate http protocol on specific port on the host side.

I am not sure what kind of image you are using now. But if it is pure jetpack 4.5.1 sdcard image, there is no such server running by default.

If it is an image specific for DLI course, then it shall have something different. However, I am not sure the content of DLI course, so cannot provide direct guide. Maybe you should check the tutorial of DLI course first.

5

Thanks Wayne!
The DLI class I’m attempting to take is “Getting Started with DeepStream for Video Analytics on Jetson Nano” I’ve followed the intro and the instructor setup video and I do not think I’ve missed any steps shown. The video shows the instructor using a browser to connect with the 55.1 address. I realize there needs to be http server to talk to the client. The first class detailed a container “pull” before making the firefox connection. This class didn’t mention anything like that?
Thanks for the help!

7

Thanks Wayne for the pointer. Turns out this class does require a particular SD card image. Sorry for wasting your time. Consider this issue resolved.