Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-270GitHub issuePublicDecided· Out of scope

Tracking: Raptor Lake SR-IOV Breakage on kernel 7.2 / 7.3 (i915-sriov-dkms incompatibility)

Reported by THE-KINGDOM · filed Sep 20, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Tracking: Raptor Lake SR-IOV Breakage on kernel 7.2 / 7.3 (i915-sriov-dkms incompatibility)revision 1 · captured 2026-09-28 21:23 UTC via poll

Bug Description

The recent mainline Linux kernel changes to the DRM (Direct Rendering Manager) subsystem in version 7.2 (and inherited by 7.3) have fundamentally broken compatibility with the i915-sriov-dkms out-of-tree module required for Intel Alder Lake and Raptor Lake (UHD 770) GPU virtualization (SR-IOV).

Because the bespoke Omarchy kernel (linux-omarchy 7.2.5) rebases on mainline 7.2, it inherently includes these breaking changes. Any user relying on GPU slicing for virtual machines will experience total initialization failure upon upgrading to this kernel.

Steps to Reproduce

  1. Install Omarchy with linux-omarchy 7.2.5 (or standard Arch linux 7.2.x).
  2. Attempt to build the i915-sriov-dkms module via DKMS.
  3. Observe compilation failures due to missing/changed DRM hooks.
  4. Virtual Functions (VFs) fail to initialize, breaking Proxmox / KVM GPU passthrough.

Expected Behavior

DKMS module compiles successfully, and VFs are instantiated at boot.

Actual Behavior

Module fails to compile. Users are forced to pin an older kernel (e.g. 7.1.9) in their bootloader and ignore kernel updates via pacman.conf to maintain functionality.

Environment

  • OS: Omarchy 4.0.4
  • Kernel: linux-omarchy 7.2.5 (and mainline 7.2/7.3)
  • Hardware: Intel Raptor Lake (e.g., UHD 770)
  • Module: i915-sriov-dkms

Proposed Action / Upstream Tracking

This is an upstream issue in the open-source community module, not strictly an Omarchy bug. However, Omarchy users need a clear tracking mechanism.

  1. Monitor upstream PRs on the i915-sriov-dkms repository for 7.2/7.3 support.
  2. When upstream patches are available, ensure they compile smoothly against Omarchy's bespoke linux-omarchy kernel headers without conflicts from custom Omarchy tweaks.
  3. Consider maintaining a stable 7.1.x LTS kernel option in the official Omarchy repos until the upstream transition to the xe driver or DKMS fixes are finalized for SR-IOV.
View raw text
## Bug Description
The recent mainline Linux kernel changes to the DRM (Direct Rendering Manager) subsystem in version 7.2 (and inherited by 7.3) have fundamentally broken compatibility with the `i915-sriov-dkms` out-of-tree module required for Intel Alder Lake and Raptor Lake (UHD 770) GPU virtualization (SR-IOV).

Because the bespoke Omarchy kernel (`linux-omarchy 7.2.5`) rebases on mainline 7.2, it inherently includes these breaking changes. Any user relying on GPU slicing for virtual machines will experience total initialization failure upon upgrading to this kernel.

## Steps to Reproduce
1. Install Omarchy with `linux-omarchy 7.2.5` (or standard Arch `linux 7.2.x`).
2. Attempt to build the `i915-sriov-dkms` module via DKMS.
3. Observe compilation failures due to missing/changed DRM hooks.
4. Virtual Functions (VFs) fail to initialize, breaking Proxmox / KVM GPU passthrough.

## Expected Behavior
DKMS module compiles successfully, and VFs are instantiated at boot.

## Actual Behavior
Module fails to compile. Users are forced to pin an older kernel (e.g. `7.1.9`) in their bootloader and ignore kernel updates via `pacman.conf` to maintain functionality.

## Environment
- **OS:** Omarchy 4.0.4
- **Kernel:** linux-omarchy 7.2.5 (and mainline 7.2/7.3)
- **Hardware:** Intel Raptor Lake (e.g., UHD 770)
- **Module:** i915-sriov-dkms

## Proposed Action / Upstream Tracking
This is an upstream issue in the open-source community module, not strictly an Omarchy bug. However, Omarchy users need a clear tracking mechanism.

1. Monitor upstream PRs on the `i915-sriov-dkms` repository for 7.2/7.3 support.
2. When upstream patches are available, ensure they compile smoothly against Omarchy's bespoke `linux-omarchy` kernel headers without conflicts from custom Omarchy tweaks.
3. Consider maintaining a stable `7.1.x` LTS kernel option in the official Omarchy repos until the upstream transition to the `xe` driver or DKMS fixes are finalized for SR-IOV.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 16:41 UTC