Machine Vision, Part 1: Nvidia Jetson Xavier NX Initial setup

I purchased the following:

  • Nvidia Jetson Xavier NX. I want to be able to experiment with both Cuda and Tensor cores — this is their smallest model that meets that requirement. At Amazon
  • 128G MicroSD — the one that NVidia recommends. At Amazon
  • 250G NVMe SSD Drive — I’ll be building of lots of libraries. Doing that on an SSD drive as much as possible should move things along considerably. 250G SSD is at a good price/size tradeoff. At Amazon.
  • Case — I’m a big believer in protective cases! At Amazon

Initial setup of the Nvidia Jetson Xavier NX is described here and works fine.

Samba Share Issues

I have a Samba drive shared amongst my various Linux and Windows machines, so I wanted the Jetson to be able to access it as well. Getting this to work on the Jetson required some fiddling I haven’t had to do elsewhere.

On all my other Linux, in /etc/fstab I specified iocharset=utf8 for sharing the Samba drive (because all of computer-dom is moving to UTF8). However, I had to omit this (giving me only ASCII file names — I’ll get over it). With iocharset=utf8 omitted, the Samba share mounted just fine.

The Samba share also failed to automount on boot (although ‘mount -a’ worked fine after boot.) Simply adding ‘_netdev’ to the /etc/fstab line didn’t work. What did work was:

[1] Create a new file at: /etc/network/if-up.d/fstab

[2] Add this content:

#!/bin/sh
mount -a

[3] Make the file executable:

sudo chmod +x /etc/network/if-up.d/fstab

Any script placed in /etc/network/if-up.d will run only after the network is up and operational so this fixed the timing issue, that /etc/fstab was apparently being read too early in the boot process. (Thanks to this post.)