There are things which can go wrong after a successful flash such that JetPack still does not find the correct IP address. Examples are firewall, proxy, or router issues. It is somewhat common to see questions on this forum due to lack of IP address in the context of both failed flash and successful flash. According to the last of the logs the flash was successful and the most likely failure is network setup. The first failure log was because two attempts were made to use “/mnt” without removing the first user of “/mnt”…two processes can’t control “/mnt” at the same time. JetPack itself won’t have this issue, but something you did before used “/mnt” and then didn’t release it. If you mounted something there and you did a “cd” to go there and look around, then you need to “cd” out of the directory before it can “sudo umount /mnt” (the command to unmount is spelled “umount”).
Beware that JetPack only sets up for wired ethernet…the setup of WiFi after flash is beyond JetPack since it involves the router and SSIDs. This would cause additional package install to fail even when flash succeeds. For this reason only wired ethernet is supported for package installs. However, read on…
Despite WiFi not being supported it is possible for it to work. You would have to log in to the Jetson after the flash and manually set up WiFi, and then guarantee your host PC can access the IP address using ssh to the “nvidia” account. If your IP address turns out to be something like “192.168.1.3” (a contrived example), then your host could verify the address with this on a text console:
ping 192.168.1.3
Or, you could log in to the Jetson’s “nvidia” account via (default pass for use “ubuntu” is “ubuntu”, and default pass for user “nvidia” is “nvidia”…something you will want to change after you are done):
ssh nvidia@192.168.1.3
Note that first contact to another system from the host will prompt you to answer yes or no as to whether to trust the connection, and you would need to say yes. After that this IP address should work.
As for finding the IP address, if you log in directly to the Jetson (either the “nvidia” or “ubuntu” account), then run these commands and show the result after WiFi has been configured:
# For wired ethernet:
ifconfig
# For WiFi:
iwconfig
The actual WiFi configuration is the same on this Ubuntu as any other Ubuntu…I mention this because any topics you see on the internet for Ubuntu 16.04 WiFi will be valid. I personally attempt to avoid WiFi and will not be the best person to give advice on its setup, but the tool bar along the top will have two icons you are interested in. The first is the icon with the two arrows (one up, one down…for enabling and disabling networking), and the other with the gear (for a control panel if you click the “system settings”, then “network”).
If you plan to be doing any development on the TX2, then you will likely want to invest in a serial console cable early on. These are inexpensive. See:
http://www.jetsonhacks.com/2017/03/24/serial-console-nvidia-jetson-tx2/
(serial console functions well even when a large part of the system is missing or failed)