Omarchy 4.0.4 switches users to the project’s own Linux kernel by default, with desktop responsiveness, gaming, Btrfs, power management, and hardware fixes cited as the focus.

Maintaining a kernel is a serious commitment

This is the part worth dwelling on. Shipping your own kernel is one of the more demanding things a distribution can take on.

It means tracking upstream releases, rebasing your patches every cycle, and backporting security fixes yourself rather than inheriting them. Arch ships a well-maintained kernel; choosing not to use it means accepting that work permanently.

It also means you now own a class of bug reports. When something does not work on Omarchy and does work on Arch, the kernel is a suspect, and narrowing that down is time nobody was spending before.

Distributions that do this successfully, and there are several, generally have paid staff for it. Omarchy hired Krzysztof Wilczyński as Head of Omarchy Kernel last week, which is presumably what made this possible and is a fairly direct demonstration of what the foundation money is buying.

What a desktop-tuned kernel actually changes

The usual levers, and they are real but modest:

Scheduler tuning for interactivity over throughput. A desktop wants the process you are typing into to respond immediately, even at some cost to aggregate work done. Server kernels tune the other way.

A higher timer frequency, typically 1000Hz rather than 300Hz, which reduces scheduling latency and costs a little efficiency.

Preemption settings allowing the kernel to interrupt itself more readily, lowering worst-case latency.

Patches from outside mainline. Alternative schedulers and gaming-oriented patch sets that upstream has not taken.

Expect this to feel better under load rather than faster in benchmarks. The difference shows when something is compiling in the background and your cursor still moves smoothly, which is exactly the situation a throughput-tuned kernel handles worst.

Anyone wanting to understand what is being adjusted will find our kernel parameters guide and sysctl tuning explainer relevant, since several of these are settings rather than patches.

Btrfs focus

Sensible for a distribution wanting snapshot-and-rollback as a default safety net, which is increasingly the expectation. Our Btrfs snapshots guide covers the subvolume layout that makes rollback useful rather than all-or-nothing.

The wider Omarchy question

This site has covered Omarchy’s foundation launch at $8 million and its climb to $18.5 million, including the criticism that followed.

4.0.4 is the first release where the money is visibly producing engineering rather than announcements. A maintained kernel with a dedicated person on it is a concrete thing that did not exist a month ago.

Whether it is the right thing to spend it on is a fair question. A distribution this young taking on kernel maintenance is ambitious, and the counter-argument is that the same funding directed at upstream Hyprland, Arch, or the shell ecosystem would benefit more people. The foundation has said it intends to fund upstream projects Omarchy depends on, and that remains the commitment to watch.

For users, the practical note is that you are now on a kernel with a smaller testing population than Arch’s. If something hardware-related breaks after updating, booting the stock Arch kernel is the first diagnostic step.