The DGX Spark profile in docs/tutorials/system_configuration.md has two inaccuracies found during a hands-on walkthrough:
1. ipv4.mtu is not a valid nmcli property — should be ethernet.mtu
In the "Configure the IP addresses of the NIC ports" section, the nmcli connection add commands use ipv4.mtu 9000. NetworkManager rejects this — MTU is a link-layer setting, not an IPv4 property. The correct property is ethernet.mtu 9000 (alias for 802-3-ethernet.mtu).
Affected lines: both nmcli connection add commands in that section.
2. Step 7 (GPU clocks): nvidia-smi -lmc fails on GB10
Step 7 shows the same three nvidia-smi commands as the IGX tab, including -lmc to lock memory clocks. On GB10, memory clocks report as N/A (unified memory architecture — no separate VRAM clock domain), and the -lmc command fails:
The DGX Spark profile in
docs/tutorials/system_configuration.mdhas two inaccuracies found during a hands-on walkthrough:1.
ipv4.mtuis not a valid nmcli property — should beethernet.mtuIn the "Configure the IP addresses of the NIC ports" section, the
nmcli connection addcommands useipv4.mtu 9000. NetworkManager rejects this — MTU is a link-layer setting, not an IPv4 property. The correct property isethernet.mtu 9000(alias for802-3-ethernet.mtu).Affected lines: both
nmcli connection addcommands in that section.2. Step 7 (GPU clocks):
nvidia-smi -lmcfails on GB10Step 7 shows the same three
nvidia-smicommands as the IGX tab, including-lmcto lock memory clocks. On GB10, memory clocks report as N/A (unified memory architecture — no separate VRAM clock domain), and the-lmccommand fails: