Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
linux-omarchy 7.2.5-3 ships a truncated vmlinux (missing .BTF section), breaks nvidia-open-dkms build
Reported by wilcastel · filed Sep 22, 2026Closed upstream on 2026-10-12 by its own reporter wilcastel. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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
What happened
After omarchy update migrated the system to the new linux-omarchy kernel package,dkms install for nvidia-open-dkms against 7.2.5-3-omarchy fails deterministically
(reproduced twice, identical failure both times) at the BTF-linking step ofMakefile.modfinal:
libbpf: failed to get e_shstrndx from /usr/lib/modules/7.2.5-3-omarchy/build/vmlinux
Failed to parse base BTF '/usr/lib/modules/7.2.5-3-omarchy/build/vmlinux': -4001
FAILED: load base BTF from .../vmlinux: Unknown error 4001
make[5]: *** [.../Makefile.modfinal:52: nvidia.ko] Error 255
The actual driver objects (nvidia.ko, nvidia-uvm.ko, nvidia-modeset.ko, nvidia-drm.ko,
nvidia-peermem.ko) compile and link fine — only the BTF finalization step fails.
Root cause found
readelf -S on the shipped vmlinux for this kernel errors out and shows no .BTF
section at all:
$ readelf -S /usr/lib/modules/7.2.5-3-omarchy/build/vmlinux
readelf: Error: Reading 3264 bytes extends past end of file for section headers
By comparison, the vanilla linux package's vmlinux for the same machine
(7.2.3-arch1-3) has healthy .BTF/.BTF_ids sections and no readelf errors. Both
kernels have identical CONFIG_DEBUG_INFO_BTF=y / CONFIG_DEBUG_INFO_BTF_MODULES=y,
and pahole is up to date (1:1.31-2) on both, ruling out a local config/tooling
mismatch. pacman -Qkk linux-omarchy reports 0 altered files, so the vmlinux
appears to ship broken in the package itself, not corrupted locally.
Confirmed: sudo dkms install --no-depmod nvidia/610.57.04 -k 7.2.3-arch1-3
(same dkms/pahole toolchain, same machine) builds and installs successfully against
the vanilla kernel's healthy vmlinux — isolating the defect entirely to thelinux-omarchy package's vmlinux.
Expected
linux-omarchy should ship a complete, non-truncated vmlinux with valid BTF data,
so DKMS modules (nvidia-open-dkms and others) can build against it like they do
against the vanilla linux kernel.
Steps to reproduce
omarchy updateon a system withnvidia-open-dkmsinstalled, pulling in
linux-omarchy 7.2.5-3 + linux-omarchy-headers 7.2.5-3.
2. sudo dkms install --no-depmod nvidia/610.57.04 -k 7.2.5-3-omarchy
3. Build fails at the BTF step above.
Environment
- Omarchy: 4.0.4-1
- CPU: Intel Core i5-10400
- GPU: NVIDIA GeForce RTX 3060 (nvidia-open-dkms 610.57.04)
- pahole: 1:1.31-2
- Kernel packages involved: linux-omarchy 7.2.5-3 (broken), linux 7.2.3-arch1-3 (unaffected, used as comparison)
View raw text
## What happened
After `omarchy update` migrated the system to the new `linux-omarchy` kernel package,
`dkms install` for `nvidia-open-dkms` against `7.2.5-3-omarchy` fails deterministically
(reproduced twice, identical failure both times) at the BTF-linking step of
`Makefile.modfinal`:
libbpf: failed to get e_shstrndx from /usr/lib/modules/7.2.5-3-omarchy/build/vmlinux
Failed to parse base BTF '/usr/lib/modules/7.2.5-3-omarchy/build/vmlinux': -4001
FAILED: load base BTF from .../vmlinux: Unknown error 4001
make[5]: *** [.../Makefile.modfinal:52: nvidia.ko] Error 255
The actual driver objects (nvidia.ko, nvidia-uvm.ko, nvidia-modeset.ko, nvidia-drm.ko,
nvidia-peermem.ko) compile and link fine — only the BTF finalization step fails.
## Root cause found
`readelf -S` on the shipped vmlinux for this kernel errors out and shows no `.BTF`
section at all:
$ readelf -S /usr/lib/modules/7.2.5-3-omarchy/build/vmlinux
readelf: Error: Reading 3264 bytes extends past end of file for section headers
By comparison, the vanilla `linux` package's vmlinux for the same machine
(7.2.3-arch1-3) has healthy `.BTF`/`.BTF_ids` sections and no readelf errors. Both
kernels have identical `CONFIG_DEBUG_INFO_BTF=y` / `CONFIG_DEBUG_INFO_BTF_MODULES=y`,
and `pahole` is up to date (1:1.31-2) on both, ruling out a local config/tooling
mismatch. `pacman -Qkk linux-omarchy` reports 0 altered files, so the vmlinux
appears to ship broken in the package itself, not corrupted locally.
**Confirmed**: `sudo dkms install --no-depmod nvidia/610.57.04 -k 7.2.3-arch1-3`
(same dkms/pahole toolchain, same machine) builds and installs successfully against
the vanilla kernel's healthy vmlinux — isolating the defect entirely to the
`linux-omarchy` package's vmlinux.
## Expected
`linux-omarchy` should ship a complete, non-truncated vmlinux with valid BTF data,
so DKMS modules (nvidia-open-dkms and others) can build against it like they do
against the vanilla `linux` kernel.
## Steps to reproduce
1. `omarchy update` on a system with `nvidia-open-dkms` installed, pulling in
`linux-omarchy 7.2.5-3` + `linux-omarchy-headers 7.2.5-3`.
2. `sudo dkms install --no-depmod nvidia/610.57.04 -k 7.2.5-3-omarchy`
3. Build fails at the BTF step above.
## Environment
- Omarchy: 4.0.4-1
- CPU: Intel Core i5-10400
- GPU: NVIDIA GeForce RTX 3060 (nvidia-open-dkms 610.57.04)
- pahole: 1:1.31-2
- Kernel packages involved: linux-omarchy 7.2.5-3 (broken), linux 7.2.3-arch1-3 (unaffected, used as comparison)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 17:04 UTC