Has anyone been able to fully connect the DGX Spark to the Framework Desktop via Nvidia Sync?
Here’s the problem I’m having…
1. Environment Specification
• Client (Local): Framework Desktop, AMD AI MAX+ 395, 128GB Unified Memory.
• OS/DE: Kubuntu 25.10 (Kernel 6.14+), KDE Plasma 6.5.2 (Wayland-exclusive/default).
• Host (Remote): NVIDIA DGX Spark (GB10 Grace Blackwell), NVIDIA OS (Ubuntu-based).
• Software: NVIDIA Sync Client (for DGX Spark), OpenSSH 9.x.
2. Primary Technical Blockers
A. Proprietary GSP/NV-Sync Handshake Failure on AMD-GCN/RDNA Hardware
The NVIDIA Sync utility utilizes a proprietary discovery and handshake protocol (relying on mDNS and the nvidia-sync-daemon) designed for a strict “NVIDIA-to-NVIDIA” ecosystem. On the Framework/AMD platform, the binary attempts to call specific hardware-bound libraries (related to the NVIDIA GSP firmware offload) to encrypt the automated SSH key exchange. Since the AMD AI MAX+ utilizes the amdgpu kernel driver and lacks the nvidia-uvm or nvidia-modeset kernel modules, the Sync client fails to initialize its secure vault, resulting in “Invalid Argument” errors or silent terminal hangs.
B. KDE 6.5 Wayland “Explicit Sync” and Terminal Emulation Regression
KDE Plasma 6.5 introduced strict Explicit Sync protocols for Wayland. NVIDIA Sync’s terminal bridge attempts to hijack the local PTY (Pseudo-Terminal) to inject SSH credentials automatically. The combination of KDE’s konsole (under Wayland) and the Sync client’s lack of support for non-NVIDIA explicit sync protocols causes a race condition. This leads to the terminal window opening but failing to attach the standard input stream (stdin), effectively freezing the session before the login prompt appears.
C. mDNS (.local) Resolution Conflict on Kubuntu 25.10
Kubuntu 25.10 features an updated avahi-daemon configuration that, by default, restricts multicast DNS resolution when a non-standard hardware abstraction layer (like the AMD AI MAX firmware) is detected as the primary network interface controller. NVIDIA Sync expects spark-xxxx.local resolution. When this fails due to the Kubuntu security policy, the Sync client enters a retry loop that blocks the SSH bridge.
I was able to set up a manual ssh tunnel but this is not optimal. My question is, has anyone got Nvidia Sync to connect the terminal app (CLI) to the DGX Spark via Nvidia Sync without having to do a manual ssh tunnel and if so what OS and desktop are you using and did it work “out of the box” or was there some modifications needed? Thanks in advance for any replies that might shed some light on the situation! 