BOOT LOOP ISSUE RESOLVED

I do have one other keyboard. It is kind of a weird configuration since it is an old ADB keyboard with a TinkerBoy USB adapter but it worked! Thank you, kberger.

I’m hung at exactly the same step 7 in the System Recovery where my wired keyboard Enter or Esc does nothing and it’s stuck on this screen

Found another keyboard lying around which got past the issue. The keyboard that didn’t work was a Microsoft ergonomic, the keyboard that did work was Dynex, both 102+ keys with dedicated arrow keys and number pads. It should be noted the keyboard worked up to that screen and the lights had blinked off and then back to on while hung on that screen. Hope this helps others that may encounter this issue.

I know you got past the problem, but I wonder if you might have tried a keyboard that needed extra power for LEDs. I have one keyboard that sometimes requires a dual USB connection (it has a split cable). Sometimes it’s good keep around a plain old non-LED wired keyboard for times like these. I’m still waiting for the Spark bundle to become available (I reserved on the first day back in March, but the bundles are in limbo).

1 Like

I’m using a Logi G413 SE, and my initial setup was not a smooth as I had hoped (started with HDMI, then moved to USB-C). The Spark was powered-on, but the display outputs were kinda confused.

The Logi keys were fully-lit, and remained so during the display cable-switching.

I went through initial setup at 7:00pm Pacific on October 17th.
My machine will not boot after the update rebooted itself.

I have created the usb recovery media. I am not getting video signal on device power on.
I am deeply annoyed that this is my first experience with DGX Spark…

1 Like

james_s Whst model and type of monitor are you using? Is it a direct connection?

@james_s Did you ever get the Spark reimaged?

I went through all the recovery steps and i just get a black screen when i select my ISO for the boot override please help was super excited for this hopefull I can get it working I created the ISO on a mac i see there is some issue with the script trying to figure it out now any help would be freatly appreciated

Hi allen61310,

The MacOS script has been fixed already. Please make sure you are using the most updated recovery image from the support site

1 Like

@aniculescu That was the issue—thank you! I just started exploring and I can’t get over what this thing is capable of. I was originally planning to build a separate machine for fine-tuning, but this does everything I need. Aside from the boot issue, it’s been amazing and is already working really well. Great job, Nvidia!

1 Like

@MackenzieNVIDIA Any chance NVIDIA can update the recovery image so it leaves you with a fully running system that doesn’t force you to take online updates? It makes sense to be able to get the DGX Spark restored to a working state without relying on servers and files that likely won’t exist in future, and of course avoids issues like this one by allowing people to at least restore to a basic system that boots.

1 Like

Hello, I am facing a hardware-level failure that needs to be escalated. My issue is different from the common boot loops, as the standard recovery method is impossible.

My situation:

  1. The DGX Spark powers on and displays the ā€œWelcome to DGX Sparkā€ message on my HDMI monitor.

  2. It is completely frozen on this screen.

  3. Critically, all USB ports are non-functional. The system does not recognize any USB keyboard (wired), mouse, or USB drive.

How this happened (The missing documentation gap):

I followed the ā€œNetwork Appliance Setupā€ (headless mode) from the Quick Start Guide.

  1. I connected to the Spark’s hotspot and provided my WLAN credentials.

  2. The hotspot then disconnected (as expected).

  3. This is where the failure occurred: The DGX Spark never became accessible on my local network. Both the hostname (spark-xxxx.local) and the direct IP address (found via my router) refused all connections, including HTTP and SSH.

  4. The Quick Start Guide and the ā€œFirst Bootā€ documentation provide NO instructions for this failed state.

After a long wait with an unresponsive device, I was forced to perform a hard reboot (power cycle). The device is now permanently bricked in the state described above.

Conclusion:

It is clear the device was performing a critical, silent background update (likely firmware) when the network setup failed. The lack of documentation for this failure state led to the unavoidable, damaging power cycle.

Since all USB ports are dead, I cannot access the UEFI/BIOS or boot from the System Recovery USB. The device is non-recoverable.

Should I proceed with a hardware replacement (RMA) from Germany/Europe?

Hi, have you tried connecting a monitor to the device? If you see the NVIDIA splash logo can you try accessing the UEFI by pressing the Delete key multiple times while logo is visible?

Hi aniulescu, Many thanks for your response. Yes, to both of your questions. The HDMI port connect to a monitor fine. However, all the USB ports are none responsive.

So you see the NVIDIA splash logo, and then does it go to the OOBE setup screen or the login screen? And the keyboard is not functioning at any point in this process? Trying to figure out the exact state of your machine to see how we can help.