Repository navigation
Conversation
|
Reference-device smoke test completed on a physical MacBookPro13,1 running linux 7.1.8.arch1-3.
The rollback bundle remains preserved. This was the package-level hardware smoke test; headphones, microphone, suspend cycles, hardware replay, and fresh-install validation remain part of the later distribution validation matrix. |
linux-omarchy is now the stock kernel and Arch linux the fallback kept for recovery, so both post-DKMS verifiers check either kernel and name the kernel package in their errors. Move facetimehd-dkms to 0.7.2, which builds on Linux 7.2 upstream, and drop the string-copy patch. The pkgrel suffix keeps the Omarchy build ahead of the identical AUR release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The audio package compiles private HDA headers prepared from vanilla Linux, while linux-omarchy patches some of them. The offline DKMS test now compares the built module's BTF type layouts with each target kernel's own HDA modules, and the package checks fail when a linux-omarchy patch changes a private header the module compiles until that change is reviewed. Use bin/build for the build-order check now that bin/repo is gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The body is updated for Hardware confirmation. The hardware results above come from my own MacBookPro13,1, and I know the project wants confirmation from a maintainer or the person who reported the problem, not the PR author. Who should confirm, and how? To make that cheap, everything is reproducible without me:
I can also test any other build you want checked on this device. |
Summary
Compatibility packages for the MacBookPro13,1's camera and audio:
Installing and rebuilding with DKMS need only the target kernel's headers. Nothing fetches from the network, reads a home directory, or infers the target kernel from
uname.After each kernel or driver transaction, both packages verify their module for the stock
linux-omarchykernel and the Archlinuxfallback, and they ignore other kernels:omacom/omarchy#15905 runs these same verifiers to hold back the reboot when a DKMS build failed.
The prepared audio headers are vanilla Linux, and
linux-omarchypatches some private HDA headers. Two checks guard that:Evidence
strncpyno longer compiled. Since 2026-09-14 the stock kernel has beenlinux-omarchy, which the verifiers didn't check.tests/macbookpro13-1-packages,bin/sync-rebuilds --self-testandbin/omarchy-pkgs self-testpass.bin/package-worktree facetimehd-dkmsreproduces the checked-in package from AURca34f817exactly.bin/build --package facetimehd-firmware facetimehd-dkms snd-hda-macbookpro-dkmsbuilt 3 packages with 0 failures.tests/build-macbookpro13-1-dkmsbuilt and installed both drivers offline:7.2.8-9-omarchy187219E63B2FD3188B97CA6588C32006F782098AA4B9437.2.11-arch1-1187219E63B2FD3188B97CA6588C32006F782098AA4B943When the reviewed
linux-omarchysound patch was altered, the header check failed.On the reference MacBookPro13,1, the container-built packages are installed from a local repository. Both verifiers pass, the camera streams 1280×720, and the loaded modules match the srcversions above.
Hardware results come from the author's own device. Confirming them is the maintainer's call; see the comment below.
Merge Danger
Door: two-way
These are new packages that no default package list installs yet. Unpublishing them removes them from the repository; machines that installed them keep them until removed.
Blast Radius: narrow
Only machines that install these packages are affected, which today means MacBookPro13,1 owners who opt in. A new
linux-omarchysound patch that touches the listed headers fails the package check until someone reviews it. That's deliberate, but it can block this package's build when the kernel package changes.🤖 Generated with Claude Code