<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Boot on Nalar</title>
    <link>https://nalar.dev/tags/boot/</link>
    <description>Recent content in Boot on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 28 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/boot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux 7.3 on Fedora: Why Kernel, Modules, and Initramfs Must Match</title>
      <link>https://nalar.dev/linux-7-3-fedora-kernel-modules-initramfs-boot/</link>
      <pubDate>Wed, 28 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/linux-7-3-fedora-kernel-modules-initramfs-boot/</guid>
      <description>&lt;p&gt;Compiling Linux 7.3 produces a kernel image, but that image is only one part of a bootable Fedora installation. On a typical Fedora system, boot also depends on kernel modules, an initramfs assembled for the correct release, and a boot entry pointing to those artifacts. A mismatch can leave a perfectly compiled kernel unable to mount its root filesystem.&lt;/p&gt;&#xA;&lt;p&gt;This matters when using the upstream source from kernel.org rather than Fedora&amp;rsquo;s kernel RPMs. Fedora&amp;rsquo;s package installation normally coordinates several boot artifacts. A manual upstream build leaves that coordination to the administrator. The example below assumes an ordinary x86_64 Fedora installation managed with GRUB and &lt;code&gt;grubby&lt;/code&gt;, not an rpm-ostree-based desktop.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
