<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Initramfs on Alessandro Sangiorgi — GPU Performance Engineer</title><link>https://contact.alessandrosangiorgi.net/tags/initramfs/</link><description>Recent content in Initramfs on Alessandro Sangiorgi — GPU Performance Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 28 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://contact.alessandrosangiorgi.net/tags/initramfs/index.xml" rel="self" type="application/rss+xml"/><item><title>Unboxing Two DGX Sparks, and Recovering One From a Kernel Panic on First Boot</title><link>https://contact.alessandrosangiorgi.net/posts/dgx-spark-kernel-panic-recovery/</link><pubDate>Sun, 28 Jun 2026 00:00:00 +0000</pubDate><guid>https://contact.alessandrosangiorgi.net/posts/dgx-spark-kernel-panic-recovery/</guid><description>&lt;p&gt;I recently took delivery of &lt;strong&gt;two NVIDIA DGX Sparks&lt;/strong&gt; (the GB10 units I later wired together for the &lt;a href="https://contact.alessandrosangiorgi.net/posts/dgx-spark-nccl-collective-latency/"&gt;small-message NCCL latency benchmark&lt;/a&gt;). The out-of-box experience is genuinely slick — right up until one of the two bricked itself on the very first software update and dropped me into a kernel panic. This post is the other half of the story: the setup flow, and exactly how I brought the dead one back.&lt;/p&gt;</description></item></channel></rss>