Repository navigation
Description
Generated with my good buddy Antigravity + Gemini 3 Pro High
Description
I am running nvtop on the new NVIDIA GB10 (Grace Blackwell) platform (Dell Pro Max Workstation Gb10 = Nvidia DGX Spark). While it correctly detects the GPU name and utilization, several metrics are reported incorrectly or as N/A, likely due to the SoC nature of the architecture (NVLink-C2C instead of traditional PCIe).
System Information
Hardware: NVIDIA GB10 (Grace Blackwell Superchip)
Architecture: ARM64 (aarch64)
OS: Ubuntu 24.04.3 LTS
NVIDIA Driver: 580.95.05
CUDA Version: 13.0
Kernel: Linux 6.8.0-49-generic (aarch64)
Observed Issues
PCIe Misreporting:
Reported as: PCIe GEN 1@ 1x
Context: This is an SoC (System on Chip) where the GPU is connected via NVLink-C2C to the Grace CPU, not a standard PCIe slot. It seems nvtop is falling back to a default/placeholder value.
Memory Usage (Header):
Reported as: MEM[ N/A] in the bar gauge.
Context: nvidia-smi also reports "Not Supported" for memory usage on this platform (Unified Memory architecture). However, the process list at the bottom of nvtop does correctly show memory usage (e.g., 63931MiB for my python process). It would be great if the header gauge could aggregate the process memory or use the same source as the process list.
Fan Speed:
Reported as: FAN N/A%
Context: Likely managed by the chassis controller or SoC thermal subsystem, not exposed via standard NVML fan APIs for discrete cards.
Memory Clock:
Reported as: MEM N/A MHz
Working Metrics
GPU Utilization: Correctly shows load (e.g., 96%).
Power Usage: Correctly shows wattage (e.g., 58 W).
Process List: Correctly identifies processes and their per-process memory usage.
Additional Context
The GB10 uses the Unified Memory architecture (LPDDR5X) shared between CPU and GPU. The standard NVML queries for "FB Memory" might need to be adjusted or replaced with queries for the unified memory pool on this architecture.
Output of nvidia-smi for reference:
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.95.05 Driver Version: 580.95.05 CUDA Version: 13.0 |
|-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
|=========================================+========================+======================|
| 0 NVIDIA GB10 On | 0000000F:01:00.0 Off | N/A |
| N/A 32C P8 3W / N/A | Not Supported | 0% Default |
+-----------------------------------------+------------------------+----------------------+
I have attached a screenshot of nvtop running under load to demonstrate the issue.
Screenshot

Activity
mhillebrand commentedon Jan 7, 2026
For the RTX 6000 Pro, it's showing my 256GB of RAM, not my 96 GB of GPU VRAM. Also the full name of my GPU is
NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition, which is so long that I have to increase the width of my terminal window by 50% to see the erroneous VRAM stats. Ugh.avirtuos commentedon Mar 5, 2026
Same issue for me. My DGX Spark is running the lastest updates from nvidia and still no accurate vram usage in nvtop
raziel2001au commentedon Mar 16, 2026
They haven't updated the version of nvtop available via apt on the DGX Spark, but DGX Spark support has been broken since nvtop 3.3.1, see the issue I raised here: #449
If you don't mind running an older version of nvtop, which seems to be the only option at the moment, you can use the one I compiled here: https://forums.developer.nvidia.com/t/nvtop-with-dgx-spark-unified-memory-support
robolamp commentedon Mar 30, 2026
Same issue for me, thanks @raziel2001au for instruction
nvidia: don't report fake PCIe link on unified-memory SoC GPUs
Archmonger commentedon Oct 4, 2026
AI generated comment (by a locally hosted LLM), but was human-verified.
Two DGX Spark nodes here (driver 580.178.04, aarch64). Root-caused both header fields; PR with a fix at #523.
Memory
N/A— the driver has no versioned memory ABI, sonvmlDeviceGetMemoryInfo_v2answersNVML_ERROR_FUNCTION_NOT_FOUND(13). The UMA probe only treatsNOT_SUPPORTEDas "shares memory with the host", so this falls through toelse ifand leavesmemory_shared_with_hostfalse; the dedicated-FB path then fails too and memory rendersN/Awhile the process list already accounts ~100 GiB for the same GPU. Treating 13 as "not probed" makes the v1 query run, which answersNOT_SUPPORTEDand selects the existing/proc/meminfopath →MEM[100.241Gi/121.686Gi](MemTotal+ per-process NVML).PCIe GEN 1@ 1x— gating onnvmlDeviceGetBusTypeisn't enough: GB10 reportsNVML_BUS_TYPE_PCIE(2) despite the on-die C2C attach, so the link queries returnNVML_SUCCESSwith placeholders (Current 1vsDevice Max 5/Host Max 5;Width Current 1xvsMax 16x). It isn't a real degraded link — the root port has no maintained link state:nvmlDeviceGetC2cModeInfoValready exists innvml.hand returnsisC2cEnabled = 1here, so it's the direct signal. Suppressed the link on that (a failed probe is not read as a C2C attach, so discrete GPUs keep their readout — checked against a real RTX 2000 Ada, where the call returnsNOT_SUPPORTED).RX/TXstayN/Aand that looks unfixable client-side:nvmlDeviceGetPcieThroughputand every candidate field value (138/139, 252-254NVML_FI_DEV_C2C_LINK_ERROR_*, 14, 1011) returnNOT_SUPPORTED, matchingnvidia-smi dmonprinting-.nvidia: fix unified-memory and C2C reporting on DGX Spark / GB10
Syllo commentedon Nov 14, 2026
Several GB10 fixes have landed since this report and are included in the latest 3.4.0 release:
d198238— stop reporting a fabricated PCIe link on unified-memory SoC GPUsCould you retest with 3.4.0 (or current master) and let us know whether the memory and PCIe problems are resolved? If the fan reading is still incorrect, please include the relevant
sensors/sysfs output so we can keep this open specifically for that.Archmonger commentedon Nov 14, 2026
Using the 3.4.0 appimage, there are still a few N/A values shown
raziel2001au commentedon Nov 15, 2026
I haven't tried it, but just looking at the total GPU memory from that screenshot, it also seems wrong... 121.6GB is the maximum theoretical VRAM assuming that nothing has been allocated to CPU processes. The actual total VRAM should be smaller than that, since if you allocated over 4GB to CPU processes, which is what that screenshot shows, then it should display around 117GB as the GPU's total VRAM. Keep in mind there is a single memory pool, if memory is allocated by CPU processes, it should reduce the total VRAM the system has access to, which I'm not seeing in this screenshot. From what I've seen, version 3.3.0 is the one and only release that has worked correctly on the DGX Spark, I'll try 3.4.0 out myself later, but on the surface this doesn't look right.
raziel2001au commentedon Nov 15, 2026
Okay, I compiled 3.4.0 myself and can confirm that it's not correct, below I've got 3.3.0 running on the left, and 3.4.0 running on the right so you can see the differences clearly.
As you will note, the total VRAM is displayed correctly in 3.3.0, but not in 3.4.0 on the right:

This creates the illusion that we have a lot of VRAM free, when we really don't, as almost all of the VRAM displayed in the total has already been allocated to CPU processes. So the view on the left (3.3.0) correctly shows that we've used 112GB out of 114GB of VRAM so we're close to hitting the ceiling. Looking at 3.4.0 on the right, it incorrectly indicates that we've only used 112GB out of 121.6GB of VRAM, but we don't actually have 121.6GB of VRAM, as some of that memory has been lost to CPU processes.
Archmonger commentedon Nov 15, 2026
I've made a follow-up PR to fix all possible GB10 issues in #558
There are some firmware-level limitations that have no viable solution, and thus remained N/A: Memory clocks, power limit (and therefore effective load), ECC, and PCIe throughput.
raziel2001au commentedon Nov 15, 2026
In your screenshot, the total VRAM is still wrong.
EDIT: Okay, I can see what you did... you increased the 'used' amount instead of decreasing the amount of VRAM available. The issue with that approach is that it hides issues in software. For example, if a program allocates more in system ram than it should, then you can't see that in nvtop. The way it should work is that when you allocate memory on the CPU, it should decrease the total amount of VRAM available. Refer to my screenshot on the left in: #426 (comment)
Archmonger commentedon Nov 15, 2026
I took a different approach compared to your suggestion to VRAM calculation. Due to the unified memory architecture, I've effectively emulated the equivalent memory readout from
btop/nvidia spark dashboard. More specifically, the top-most memory readout is the combined CPU+GPU memory usage, which is what an end-user would actually care about to help them determine how much more "VRAM" they have remaining. Hence why Nvidia and BTOP show metrics this way.In my opinion, the UX would feel awkward for the "max memory" to be dynamically changing around alongside "used memory".
Will defer the final decision to the repo maintainer.
raziel2001au commentedon Nov 15, 2026
That's not useful though as you can't see how much of your RAM is actually available as VRAM. So if all you can see is that in total you've used X amount of memory, then you can't tell if there's something in system ram that shouldn't be there. It completely hides how much actual VRAM you have access to. I've used this in the past to identify issues in software, as you can quickly tell there's a problem when your available VRAM drops to 70GB for example, as it suggests a model was loaded and then not unloaded after uploading it to VRAM, so you basically have multiple copies of the same model sitting in RAM. With the current approach, you lose that insight completely. The approach used for 3.3.0 feels correct, as it shows the actual VRAM available once taking other things in memory into account.
Archmonger commentedon Nov 15, 2026
Easy to change the printout, but will let @Syllo make the decision on how he wants this information represented.
raziel2001au commentedon Nov 15, 2026
Good to hear it's an easy change. Let's see what @Syllo says.
From my perspective, the way it was done in 3.3.0 is the correct way to do it, since nvtop is supposed to monitor the GPU, and more specifically: the VRAM of that GPU. This gives insights you don't get from tools like btop, which just monitors total system memory, which is different from monitoring the VRAM of the GPU, which is where I feel nvtop should be doing something different from btop, which is a different tool with a different purpose. nvtop should monitor GPU resources, and if you've allocated memory in a CPU process, it ceases to be a GPU resource in a unified memory system, nvtop should reflect that.