Yes, internet access is through wifi. To be honest I’m not sure exactly what type of fire-wall is included in the internet router I have. If it blocks the SDKM I don’t know. Can I check it somehow?
SDKM accesses NVIDIA’s web site, but I think it may also use some other ports related to file downloads. Would anyone from NVIDIA be able to confirm what ports must be accessible for SDKM? Or if a login to a particular web page is equivalent? All ssh access to the Jetson is working correctly, and so there must be an outside network access issue, e.g., proxy or firewall.
Hi,
Just a quick update. I have now also tried the exact same procedure without any fire-wall to the internet and with the exact same result. At the step “Install SDK components on your Jetson AGX Xavier”: it first displays in red that there is an error with the username or password and then stops responding. Anyone at NVIDIA, do you have any suggestions on how to solve this …?
Do be sure that you are selecting the right login portal. I forget what they are called, but there is a selection in SDKM which is either for the general developer login, or another for partners. The login for the regular software won’t work on the partner portal login.
Oh thanks. I was not aware of that. There are three different login portals:
- NVIDIA Developer (developer.nvidia.com)
- NVONLINE (partners.nvidia.com)
- OFFLINE (from local folder)
I have been using the NVIDIA Developer. Should I use one of the others instead?
Most people will use the one you used, “NVIDIA Developer (developer.nvidia.com)”. If you are working with a company which is an actual development partner, then you’d use the partners.nvidia.com one. So the real test is that if you go somewhere like [url]https://developer.nvidia.com/embedded/downloads[/url], does the login you use work there? If it does, then this is the same user/pass you’d use from SDK Manager for that step. At some point you’d also use a name/pass for the Xavier (unless you specifically set the Xavier to have the same name/pass as the web site the two will differ).
Hi, I can’t install the SDK Components onto my Xavier. Standard message: ‘Could not detect Nvidia Jetson device connected to USB.’
- I use SDK Manager 1.0.0.5517
- xavier and host connected via usb-C cable (checked other cables too)
- L4T-README folder visible on jetson
- l4t-usb-device-mode on xavier activated
- output from /sbin/ifconfig -a (xavier)
dummy0: flags=130<BROADCAST,NOARP> mtu 1500
ether f6:6c:32:a5:cc:82 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
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:04:4b:cb:e0:85 txqueuelen 1000 (Ethernet)
RX packets 4764 bytes 6523051 (6.5 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2455 bytes 196753 (196.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 40
l4tbr0: flags=4098<BROADCAST,MULTICAST> mtu 1500
inet 192.168.55.1 netmask 255.255.255.0 broadcast 192.168.55.255
inet6 fe80::1 prefixlen 128 scopeid 0x20
ether 1e:c1:2d:a8:32:c1 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 1 (Local Loopback)
RX packets 225 bytes 17398 (17.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 225 bytes 17398 (17.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
rndis0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 1e:c1:2d:a8:32:c1 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
usb0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 1e:c1:2d:a8:32:c3 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
- rndis module loaded on host:
lsmod | grep rndis
rndis_host 20480 0
cdc_ether 20480 1 rndis_host
usbnet 45056 2 rndis_host,cdc_ether
- lsusb on host:
lsusb
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
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 2357:010c
Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- ifconfig on host:
ifconfig
enp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.55.100 netmask 255.255.255.0 broadcast 192.168.55.255
ether 40:8d:5c:d1:cf:02 txqueuelen 1000 (Ethernet)
RX packets 7437 bytes 2737393 (2.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9060 bytes 1097399 (1.0 MB)
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 32302 bytes 2789912 (2.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 32302 bytes 2789912 (2.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wls1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 78:0c:b8:c3:be:69 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
wlx503eaa5a2dec: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.55.1.86 netmask 255.255.254.0 broadcast 10.55.1.255
inet6 fe80::c83f:2149:a5c3:cc70 prefixlen 64 scopeid 0x20
ether 50:3e:aa:5a:2d:ec txqueuelen 1000 (Ethernet)
RX packets 190983 bytes 81102593 (81.1 MB)
RX errors 0 dropped 9913 overruns 0 frame 0
TX packets 27877 bytes 3276862 (3.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
- route on host:
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default _gateway 0.0.0.0 UG 601 0 0 wlx503eaa5a2dec
default _gateway 0.0.0.0 UG 602 0 0 wls1
10.55.0.0 0.0.0.0 255.255.254.0 U 601 0 0 wlx503eaa5a2dec
10.55.0.0 0.0.0.0 255.255.254.0 U 602 0 0 wls1
link-local 0.0.0.0 255.255.0.0 U 1000 0 0 wls1
192.168.55.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0
- ssh on host:
ssh user@192.168.55.1
ssh: connect to host 192.168.55.1 port 22: No route to host
Xavier side seems to be fine (or am I wrong?) but what is missing on host?
Some notes, not in any particular order, and perhaps repeating at times since I’m just commenting on what I see as I see it. After you go through the notes, please describe if you are just adding packages, just flashing, or trying to do both, along with how the Xavier is wired to networking and monitor. I am guessing you are only adding packages and not flashing.
Xavier “ifconfig” indicates no address assigned to the wired ethernet. If you are using the virtual wired ethernet over USB, then this is ok so far as copy of packages from PC to Xavier is concerned, but there may be other steps for updates which are missing if you are booting up right after a flash has completed. Is the wired ethernet not connected to a router?
Even if ethernet is available, you have to be sure to add your login account on first boot (ethernet uses ssh to that account name for package additions). The README tells us networking over virtual USB is successful, but it doesn’t tell us if your login account exists (the README is a system service not requiring login).
Seeing the README says that the Xavier is fully booted (which is correct for package addition, but incorrect if flashing).
Any lsusb on the host PC, when looking for NVIDIA devices, will have an ID starting with “0955:”. This is the manufacturer ID. The serial device for serial console is FTDI (through the micro-B USB, not USB-C), and would have ID starting with “0403:”. The recovery mode Jetson will have a “0955:” prefix for ID a recovery mode Jetson, as this is a custom device from NVIDIA when in recovery mode.
If the Xavier is not in recovery mode, then flash cannot proceed and the Xavier would not be detected.
If the Xavier is not in recovery mode, and is fully booted, then extra packages can be added via either wired ethernet or the virtual wired ethernet over USB.
From the ifconfig on the host PC I see that virtual wired ethernet is completely successful. Any network operation between host PC and Xavier will be successful, but not necessarily Xavier to internet operations.
Actually xavier is connected to monitor via hdmi.
Host and xavier are connected to router and both have internet via ethernet.
Xavier has ip 192.168.55.1, host 192.168.55.100.
Both can ping each other, as root I can do ssh to user@192.168.55.1
Both can ping nvidia.com
Xavier is not in recovery mode, I flashed and fully booted it. Also performed incomming updates via Software Updater.
ONLY what I concern is how to install target components:
- CUDA
- AI
- Computer Vision
- NVIDIA Container Runtime
- Multimedia
- DeepStream
Even if ethernet connection between host and xavier works SDK Manager still looking for device on usb port. Running SDK Manager with flash option (initially) or later omitting flashing step (when xavier is already fully booted, login etc.) I stuck trying install SDK components with message ‘Could not detect Nvidia Jetson device connected to USB.’
I see these components on host are downloaded into ~/Downloads/nvidia/sdkm_downloads .
My target is to get these components working. Is it enough to copy them all manually to xavier and install them all one by one? Is it SDK Manager exactly does at this step?
Again, not in any particular order, but some comments.
Address 192.168.55.x is not from the ethernet PHY, but is instead from virtual wired ethernet over USB. Thus it sounds like the wired ethernet is failing to retrieve an address from your router. Any attempts from the PC to talk through the wired ethernet would fail, but talking through virtual wired USB ethernet would succeed. I would be concerned with finding out why the router did not assign an address to the wired ethernet.
If for some reason your SDKM was not told to use the 192.168.55.1 address, then this would cause the failure. The USB port ethernet is the only one capable of working since the router never assigned an address to the Xavier’s wired ethernet.
It is possible to use scp or other methods to copy various “arm64” packages to the Jetson, and then install via dpkg. Do beware though that dpkg does not know about dependency resolving, and thus you would need to probably name all packages on the same dpkg command line, or else experiment with order of install.
Also beware that if the Jetson just booted and is updating packages, then the updates will interfere with adding packages until the update is complete.