Skip to content

Add MacBookPro13,1 camera and audio packages - #182

Open
gjinali wants to merge 5 commits into
omacom:masterfrom
gjinali:feat/macbookpro13-1-compat-packages
Open

gjinali wants to merge 5 commits into
omacom:masterfrom
gjinali:feat/macbookpro13-1-compat-packages

Conversation

@gjinali

@gjinali gjinali commented Aug 21, 2026 •

Copy link
Copy Markdown

Summary

Compatibility packages for the MacBookPro13,1's camera and audio:

facetimehd-firmware        FaceTime HD firmware, verified source inputs
facetimehd-dkms            upstream 0.7.2 (AUR ca34f817) + Omarchy patches:
                             pinned release archive · build deps · post-DKMS verifier
snd-hda-macbookpro-dkms    offline DKMS source for the Cirrus CS8409 driver
                             prepared at build time from a pinned driver commit
                             and pinned kernel.org archives, per kernel series (7.1, 7.2)

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-omarchy kernel and the Arch linux fallback, and they ignore other kernels:

75-*-verify.hook (PostTransaction, NeedsTargets)
  /usr/lib/omarchy/verify-{facetimehd,snd-hda-macbookpro} --modules-root DIR < targets
    for each target kernel whose pkgbase is linux-omarchy or linux
      missing updates/dkms/<module>.ko* → "Missing <module> for <pkgbase> kernel <version>", exit 1

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-omarchy patches some private HDA headers. Two checks guard that:

 tests/build-macbookpro13-1-dkms      per target kernel
   dkms build + install (network commands stubbed)
+  compare-hda-btf-layouts: module BTF vs the kernel's own HDA modules
 tests/macbookpro13-1-packages
+  linux-omarchy patches touching hda_local.h, hda_auto_parser.h, hda_jack.h,
+  codecs/generic.h or side-codecs/hda_component.h must match a reviewed hash

Evidence

  • Before: on 2026-09-09, a MacBookPro13,1 moved from Linux 7.1.9 to 7.2.3, and both DKMS builds failed. The audio package shipped only 7.1 source, and the camera driver's strncpy no longer compiled. Since 2026-09-14 the stock kernel has been linux-omarchy, which the verifiers didn't check.
  • After:
    • tests/macbookpro13-1-packages, bin/sync-rebuilds --self-test and bin/omarchy-pkgs self-test pass.

    • bin/package-worktree facetimehd-dkms reproduces the checked-in package from AUR ca34f817 exactly.

    • bin/build --package facetimehd-firmware facetimehd-dkms snd-hda-macbookpro-dkms built 3 packages with 0 failures.

    • tests/build-macbookpro13-1-dkms built and installed both drivers offline:

      Kernel HDA layouts Audio srcversion Camera srcversion
      7.2.8-9-omarchy 87 shared, 0 mismatched 187219E63B2FD3188B97CA6 588C32006F782098AA4B943
      7.2.11-arch1-1 87 shared, 0 mismatched 187219E63B2FD3188B97CA6 588C32006F782098AA4B943
    • When the reviewed linux-omarchy sound 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-omarchy sound 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

@gjinali

gjinali commented Aug 21, 2026

Copy link
Copy Markdown
Author

Reference-device smoke test completed on a physical MacBookPro13,1 running linux 7.1.8.arch1-3.

  • Installed facetimehd-dkms 0.7.0.2-1.1
  • Installed facetimehd-firmware 1:1.43_5-2.1
  • Installed snd-hda-macbookpro-dkms 0.1-1
  • Both post-DKMS verification hooks passed
  • Reboot loaded both modules from updates/dkms
  • FaceTime HD captured five 1280×720 frames successfully
  • Built-in speaker playback confirmed
  • NVMe d3cold_allowed remained 0 after reboot

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.

gjinali and others added 4 commits October 18, 2026 23:46
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>
@gjinali

gjinali commented Oct 18, 2026

Copy link
Copy Markdown
Author

The body is updated for linux-omarchy and facetimehd-dkms 0.7.2, and the branch now includes current master.

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:

  • tests/build-macbookpro13-1-dkms <audio pkg> <camera pkg> <linux-omarchy-headers pkg> <linux-headers pkg> builds both drivers offline and checks the HDA layouts. It needs each kernel package next to its headers package, and runs on any x86_64 machine.
  • On a MacBookPro13,1, after installing the packages:
    • cat /sys/module/{facetimehd,snd_hda_codec_cs8409}/srcversion should match the table above;
    • v4l2-ctl -d /dev/video0 --stream-mmap --stream-count=5 --stream-to=/dev/null streams the camera;
    • speaker-test -c 2 -t wav -l 1 plays on both speakers.

I can also test any other build you want checked on this device.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants