Can you ssh from your host machine to 192.168.55.1 (target IP) with the username and password?
Could you please provide the screenshot and files in ~/.nvsdkm/ folder?
Nope. I cannot ssh to that IP. I see that IP in the jetson Tx2 configured on the l4trb0 interface.
I have my usb cable connected (the same with I flashed the board).
Can you please paste the IP address of the usb-ethernet ports on your host machine? The usb-ethernet ports name may be usb0/usb1 or enps[Y]u[Z]; X, Y, and Z here may be different numbers on different machines.
You may use ip addr command on your host machine to check it.
The expected result is that 192.168.55.100 assigned to one of the ports. And it should be assigned when below two conditions are met:
USB cable is connected between host and target.
Ubuntu desktop is shown on jetson device after login.
With ip addr, I cannot see any usb-ethernet interface…
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether ec:f4:bb:16:6e:49 brd ff:ff:ff:ff:ff:ff
inet 10.50.83.32/16 brd 10.50.255.255 scope global eno1
valid_lft forever preferred_lft forever
inet 192.168.3.232/24 brd 192.168.3.255 scope global eno1
valid_lft forever preferred_lft forever
inet 192.168.55.232/24 brd 192.168.55.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::af07:f07e:4d06:780a/64 scope link
valid_lft forever preferred_lft forever
3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether c4:d9:87:4e:b4:fc brd ff:ff:ff:ff:ff:ff
Also with lsusb this is the output.
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:649d Microdia
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Can you please check if the usb cable is connected between host and jetson device? It seems the usb hardware connection is broken.
Please also make sure the device is booted up and you have logged in device with the newly created username and password.
Yeah. The cable is connected… (if I put the board in recovery mode then the sdkmanager says board is in recovery mode)
Is the same usb cable I used for flashing the Tegra…
If I try to ssh with the ethernet interface… For example ssh ubuntu@10.50.84.70 (Manual ip) then it works. I can enter…
So is there any way to manual install this debs?? Maybe the script that use sdkmanager?? Before with Jetpack I could check to install the SDK Components individually and now I have to install all…
SDK manager is using usb cable only to flash device and install all target components. Could you please change a different USB port on host, or change another USB cable to try to fix the problem?
Run “dmesg” on the host and provide the full output. This might show any errors the host might have had when enumerating the Jetson USB device.
Now, connect jetson device with a ethernet cable, get its IP address, ssh to Jetson and:
Run “journalctl -u nv-l4t-usb-device-mode” to show any errors configuring the USB device mode service on Jetson, during boot.
As root, run “/opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode-stop.sh”. This is expected to show some errors; ignore them.
As root, run “bash -x /opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode.sh” and provide the entire output that prints. This should (a) show the same errors as in (2) above, and/or (b) actually make L4T USB device mode work, if the reason it failed the first time was due to some missing dependency that wasn’t available right when the script ran at boot.
/usr/sbin/dhcpd -cf /opt/nvidia/l4t-usb-device-mode/dhcpd.conf -pf /opt/nvidia/l4t-usb-device-mode/dhcpd.pid -lf /opt/nvidia/l4t-usb-device-mode/dhcpd.leases
Internet Systems Consortium DHCP Server 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit ISC DHCP - ISC
Config file: /opt/nvidia/l4t-usb-device-mode/dhcpd.conf
Database file: /opt/nvidia/l4t-usb-device-mode/dhcpd.leases
PID file: /opt/nvidia/l4t-usb-device-mode/dhcpd.pid
Wrote 0 leases to leases file.
Listening on LPF/l4tbr0/62:6e:b3:35:3e:61/192.168.55.0/24
Sending on LPF/l4tbr0/62:6e:b3:35:3e:61/192.168.55.0/24
No subnet declaration for usb0 (no IPv4 addresses).
** Ignoring requests on usb0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface usb0 is attached. **
No subnet declaration for rndis0 (no IPv4 addresses).
** Ignoring requests on rndis0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface rndis0 is attached. **
No subnet declaration for wlan0 (no IPv4 addresses).
** Ignoring requests on wlan0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface wlan0 is attached. **
No subnet declaration for eth0 (10.1.15.35).
** Ignoring requests on eth0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface eth0 is attached. **
Sending on Socket/fallback/fallback-net
‘[’ -n 192.168.55.100 ‘]’
route add default gw 192.168.55.100 dev l4tbr0 metric 32766
Hi nrj127 & isra601988,
I had the same problem which you are going through. I was able to flash the Jetson board but the sdk components failed with the message “jetson is in recovery mode”.
This failure is due to the USB ethernet connection between the Host PC and Jetson board. Kindly follow these steps and your issue might be resolved.
Disconnect and Connect the USB cable connecting the jetson and Host-PC, and check the dmesg log.
You might see a log similar to this:
Hi nrj127,
The command output looks good. If your run “ip addr” command on your host machine, can you see “192.168.55.100”? If not, can you please check if Waiss’s suggestion above can solve your issue? (Thanks Waiss for sharing the experience.)
I had the same problem. I was able to flash the Jetson board but the sdk components failed with the message.
B cable. 2. Ubuntu ‘System configuration wizard’ is completed on the device. 3. Jetson’s Ubuntu OS is up and running.
21:44:22 DEBUG : running command < ip addr | grep 192.168.55.100/24 >
21:44:22 ERROR : command terminated with error
Hi stevefoy, chenscottusa & benelgiac,
Are you still running into this issue after enabling the USB ethernet in the network settings? I have shared my work around in the previous comment.