The broad sequence is firmware → bootloader → kernel and early system → graphical session. Limine and Plymouth occupy different positions: one selects and loads the boot target; the other presents graphical feedback during initialization after the kernel starts.
Firmware enters the configured bootloader. On a Limine installation, it offers system or snapshot entries.
The selected entry loads the kernel and boot resources. Plymouth presents the later startup experience; it does not select the kernel.
Example: recovery after an update.Snapper and Btrfs participate in snapshot management, Omarchy integrates snapshots with the boot workflow, and Limine provides a selection entry. Plymouth presents startup rather than creating or restoring snapshots.
A missing snapshot entry and a missing splash are different problems. This example follows the documented Limine workflow; other platforms and boot arrangements differ, and system snapshots do not replace personal-file backups.
Each catalogued component is explained below: purpose, architecture, configuration, troubleshooting, limitations and further reading. Use the component links to jump to its explanation.
Bootloader with the documented snapshot boot workflow. Boot arrangements differ across platforms.
Package
limine
Membership
Other install candidates
Purpose and everyday use
Selects a system boot entry before Linux starts. In the documented Omarchy snapshot workflow, it also offers bootable system snapshots for recovery after a broken update.
How it works and connects
Firmware starts the bootloader, which loads the selected kernel and boot resources. Snapper creates snapshots; Limine exposes boot entries. Neither component alone implements the entire recovery workflow.
Configuration and customization
Boot configuration belongs to the installed boot chain, not Hyprland dotfiles. Identify your active loader and partition layout before following configuration examples; use the Omarchy snapshot guide for its recovery integration.
Troubleshooting approach
First distinguish a missing firmware entry, a loader error, and a kernel that starts but fails later. Record the visible message and whether an older snapshot boots before changing entries.
Limits and change considerations
The documented root rollback excludes /home. Direct boot may hide the menu, and other platforms can use different boot chains. Keep a recovery route before changing boot settings.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi limine
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Graphical boot splash component, separate from the login manager.
Package
plymouth
Membership
Core manifest
Purpose and everyday use
Displays the early graphical boot experience and can present prompts during startup. It provides visual feedback while system services initialize, rather than selecting which system to boot.
How it works and connects
Runs after the kernel starts and uses available graphics support. Its lifecycle ends around the transition to the regular graphical session; SDDM handles login separately.
Configuration and customization
Themes, kernel boot options and early-boot integration affect the result. Theme changes may require rebuilding boot resources through the distribution’s supported workflow.
Troubleshooting approach
Use Escape during the splash to inspect detailed boot output where supported. A black splash with a working desktop differs from a boot failure; preserve the actual error text.
Limits and change considerations
A splash screen does not provide disk encryption or authentication itself. Do not remove boot integration merely to hide an animation without understanding the startup configuration.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi plymouth
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.