Hello,
I’ve just bought Asus version of DGX Spark.
Is it possible to download ISO of DGX OS?
I’m tried to get from Nvidia Site, but I have authentication error. It seems, I don’t have enterprise support.
Tomasz, You don’t need to be signed in.
I saw this, but there is note “Founders Edition Only”.
It should work on Asus too?
I had power outage during OS update and I have some problems now. I prefer reinstall entire OS instead of trying to resole all problems.
Yes , all of our 8 units are Asus Ascent running on it. Other vendors just customise the interface (or only desktop background image).
Great. Thank you very much. I’ll do it tomorrow.
Just in case you prefer the ISO image produced by ASUS directly to restore what you had initially: NVIDIA DGX OS for ASUS Ascent GX10 7.4.0-3
@adi-sonusflow since I bought one I always wondered if switching the ISO image to NVIDIA would change who manages the UEFI firmware updates; as yours are migrated to the NVIDIA ISO, would you mind sharing the output of sudo fwupdmgr get-devices ?
Here is for reference the one I have:
ASUSTeK COMPUTER INC. GX10
│
├─ESL01TBTLCZ-27J2-TYN:
│ Device ID: 7de5ffdca08fa52d95fd4bb42aa5d07a4b35d2dd
│ Summary: NVM Express solid state drive
│ Current version: ERFM12.0
│ Vendor: Phison Electronics Corporation (NVME:0x1987)
│ Serial Number: [REDACTED]
│ GUIDs: 3d29962d-a81b-5b11-bd43-aec65c7e9e60 ← NVME\VEN_1987&DEV_5027
│ 18fbf8a9-d429-57e9-b174-ea8afd7e6877 ← NVME\VEN_1987&DEV_5027&SUBSYS_19875027
│ ed9808fe-4f78-5d97-ab19-c0e627af31bf ← ESL01TBTLCZ-27J2-TYN
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs shutdown after installation
│ • Device is usable for the duration of the update
│
├─Embedded Controller:
│ Device ID: 798397787f4afcf1e2bb8575cb19630f12180584
│ Summary: UEFI System Resource Table device (Updated via capsule-on-disk)
│ Current version: 0x02000003
│ Minimum Version: 0x01000000
│ Vendor: Asus (DMI:American Megatrends International, LLC.)
│ Update State: Success
│ GUID: c3cccaf0-9a3e-4ee2-992e-9f0cf9b55fa0
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Supported on remote server
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Signed Payload
│ Device Requests: • Message
│
├─MT2910 Family [ConnectX-7]:
│ Device ID: ce4c74a5188d5b9cdb1e72ed32dad2d313c1c999
│ Current version: 01
│ Vendor: Mellanox Technologies (PCI:0x15B3, PCI:0x10DE)
│ GUIDs: 12029307-5bb1-5200-99a5-536f1be9d081 ← PCI\VEN_15B3&DEV_1021
│ b5e95689-ad65-5e57-8778-897f04396256 ← PCI\VEN_15B3&DEV_1021&SUBSYS_15B321EC
│ cfc0de0b-adb3-5060-ba22-e4010a78368f ← PCI\VEN_10DE&DEV_22CE
│ 59007998-a3d7-54a3-b30e-eb3b77e2f351 ← PCI\VEN_10DE&DEV_22CE&SUBSYS_15B321EC
│ Device Flags: • Internal device
│ • Cryptographic hash verification is available
│
├─MT2910 Family [ConnectX-7]:
│ Device ID: 7d29f2075dcafb4488b40c73f199cf46bb76bddb
│ Current version: 01
│ Vendor: Mellanox Technologies (PCI:0x15B3, PCI:0x10DE)
│ GUIDs: 12029307-5bb1-5200-99a5-536f1be9d081 ← PCI\VEN_15B3&DEV_1021
│ b5e95689-ad65-5e57-8778-897f04396256 ← PCI\VEN_15B3&DEV_1021&SUBSYS_15B321EC
│ cfc0de0b-adb3-5060-ba22-e4010a78368f ← PCI\VEN_10DE&DEV_22CE
│ 59007998-a3d7-54a3-b30e-eb3b77e2f351 ← PCI\VEN_10DE&DEV_22CE&SUBSYS_15B321EC
│ Device Flags: • Internal device
│ • Cryptographic hash verification is available
│
├─MT2910 Family [ConnectX-7]:
│ Device ID: 024ec185fcba9289f4336862423686455165d68a
│ Current version: 01
│ Vendor: Mellanox Technologies (PCI:0x15B3, PCI:0x10DE)
│ GUIDs: 12029307-5bb1-5200-99a5-536f1be9d081 ← PCI\VEN_15B3&DEV_1021
│ b5e95689-ad65-5e57-8778-897f04396256 ← PCI\VEN_15B3&DEV_1021&SUBSYS_15B321EC
│ cfc0de0b-adb3-5060-ba22-e4010a78368f ← PCI\VEN_10DE&DEV_22CE
│ 59007998-a3d7-54a3-b30e-eb3b77e2f351 ← PCI\VEN_10DE&DEV_22CE&SUBSYS_15B321EC
│ Device Flags: • Internal device
│ • Cryptographic hash verification is available
│
├─MT2910 Family [ConnectX-7]:
│ Device ID: fd0f3bbe941288a4198e7476ae94fd87b6e58b15
│ Current version: 01
│ Vendor: Mellanox Technologies (PCI:0x15B3, PCI:0x10DE)
│ GUIDs: 12029307-5bb1-5200-99a5-536f1be9d081 ← PCI\VEN_15B3&DEV_1021
│ b5e95689-ad65-5e57-8778-897f04396256 ← PCI\VEN_15B3&DEV_1021&SUBSYS_15B321EC
│ cfc0de0b-adb3-5060-ba22-e4010a78368f ← PCI\VEN_10DE&DEV_22CE
│ 59007998-a3d7-54a3-b30e-eb3b77e2f351 ← PCI\VEN_10DE&DEV_22CE&SUBSYS_15B321EC
│ Device Flags: • Internal device
│ • Cryptographic hash verification is available
│
├─UEFI Device Firmware:
│ Device ID: 1df564c6ffffdc355893f9d0ec29813e0a1141b5
│ Summary: UEFI System Resource Table device (Updated via capsule-on-disk)
│ Current version: 0x03000004
│ Minimum Version: 0x02000000
│ Vendor: Asus (DMI:American Megatrends International, LLC.)
│ Update State: Success
│ GUID: f1392323-3920-4598-a932-ef06360cf403
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Supported on remote server
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Signed Payload
│ Device Requests: • Message
│
├─UEFI Device Firmware:
│ Device ID: 7fd0410f4194ca73faaa60d3392bcd91ef4ee070
│ Summary: UEFI System Resource Table device (Updated via capsule-on-disk)
│ Current version: 0x00000500
│ Minimum Version: 0x00000309
│ Vendor: Asus (DMI:American Megatrends International, LLC.)
│ Update State: Success
│ GUID: fe75bb1c-5ccc-4936-b603-cc7cf945dc30
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Supported on remote server
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Signed Payload
│ Device Requests: • Message
│
└─UEFI dbx:
Device ID: 362301da643102b9f38477387e2193e57abaa590
Summary: UEFI revocation database
Current version: 20230501
Minimum Version: 20230501
Vendor: UEFI:Microsoft
Install Duration: 1 second
GUIDs: 026c46fa-db36-5397-883d-047809df980a ← UEFI\CRT_103560ADA2E78C48DDA52A2D71A00FC1D30F469E1E20332FDA01CDE9B796B049&ARCH_AA64
67d35028-ca5b-5834-834a-f97380381082 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_AA64
10ec82f4-ff64-5362-9e5d-688febf5dbb0 ← UEFI\CRT_3CD3F0309EDAE228767A976DD40D9F4AFFC4FBD5218F2E8CC3C9DD97E8AC6F9D&ARCH_AA64
Device Flags: • Internal device
• Updatable
• Needs a reboot after installation
• Device is usable for the duration of the update
• Only version upgrades are allowed
• Signed Payload
Switching to the NVIDIA DGX Spark OS ISO is a kernel and driver stack change only — UEFI and EC firmware management remains with ASUS/AMI via uefi-capsule/LVFS, identical to stock Ubuntu.
Same for other DB10 vendors
Thank you very much for this precision - much appreciated!
As you probably guessed I wasn’t much familiar with how those uefi-capsule/LVFS aspects works - now I learnt a bit more thanks to you! 🧑🎓
Great. Thank you. At the time I wrote the post, there was no ISO file on the Asus website.
No worries! 🤗 Yeah, the latest ISO image has been literally published yesterday! I had quite some troubles in finding the previous version last month when I wanted to re-image… I had explicitly to set the “US” region of ASUS website to find this download ISO/Firmware page 🤷
The new firmware just announced by Nvidia is now also available on the GX10
@AoE is this something other than 5.0? I updated a few days ago and am now at:
Firmware Versions:
EC 2.75.3.3
PD0 FW1 5.0
PD0 FW2 5.0
PD1 FW1 5.0
PD1 FW2 5.0
UEFI FW ASUS_UEFI_0102
SoC FW 3.0.4
GOP Driver 9000AE0
NVMe Config
ESL01TBTLCZ-27J2-TYN
I downloaded the new Ascent iso image, put in on a usb stick, and tried to boot. But BIOS on my gx10 only shows the same 2 boot options, (ubuntu ESL01TBTLCZ-27J2-TYN and UEFI: PXE IPv4…). Do I have to do something special (like turn off secure boot) to get it to recognize the usb stick as a boot option?
You’re still on the old version. I had to reboot one of the boxes 3-4 times before it accepted all the updates.
This will show you if an update didn’t work: fwupdmgr get-history
Do you mean just reboot, without doing anything in between boots? My dashboard says I’m up-to-date.
You have to get the updates first. The DGX Dashboard shows you when they are ready to be installed, but you can also use fwupdmgr get-updates
fwupdmgr get-updates looks like this:
Devices with no available firmware updates:
• ESL01TBTLCZ-27J2-TYN
• UEFI dbx
Devices with the latest available firmware version:
• Embedded Controller
• UEFI Device Firmware
• UEFI Device Firmware
────────────────────────────────────────────────
Devices that have been updated successfully:
• UEFI Device Firmware (0x00000001 → 0x00000500)
• Embedded Controller (0x02000003 → 0x02000004)
• UEFI Device Firmware (0x03000004 → 0x03000005)
So what’s out of date?
Now do fwupdmgr upgradeand reboot a few times.