Skip to content

Install the FaceTime HD camera driver on Intel Macs that have one - #12067

Open
MrBazzieB wants to merge 1 commit into
omacom:quattrofrom
MrBazzieB:fix/facetimehd
Open

MrBazzieB wants to merge 1 commit into
omacom:quattrofrom
MrBazzieB:fix/facetimehd

Conversation

@MrBazzieB

Copy link
Copy Markdown

What

Detect the Broadcom FaceTime HD PCIe webcam (14e4:1570) and install facetimehd-firmware, facetimehd-data, and facetimehd-dkms during hardware setup. A migration covers existing installs.

This is the 720p camera in 2013–2015 Intel Macs (this machine is a MacBookPro12,1). There is no in-tree driver.

Packaging

facetimehd-dkms is not in [omarchy] yet. Please add it to the ISO/repo from current patjak/facetimehd master (after 54fb8f2), not AUR 0.7.0.2.

Linux 7.2 removed strncpy from the kernel API. AUR 0.7.0.2 still calls it in fthd_v4l2.c and DKMS fails on linux-omarchy 7.2 with:

error: implicit declaration of function ‘strncpy’

Upstream already guards that call for kernels >= 4.2. I compiled c5c7fac against 7.2.5-3-omarchy on this MacBook and it built cleanly.

Also cache facetimehd-firmware and facetimehd-data (already listed in omarchy-other.packages).

Test plan

  • test/shell.d/facetimehd-test.sh
  • ./test/cli
  • ISO/package: facetimehd-dkms from current git is in [omarchy]
  • On a Mac with 14e4:1570, modinfo facetimehd and /dev/video0 after install or omarchy update

The Broadcom 1570 has no in-tree driver. Detect PCI 14e4:1570 and install
facetimehd firmware, calibration data, and the DKMS module so new and
existing Omarchy Macs get /dev/video0 after setup or omarchy update.

The packaged facetimehd-dkms must be built from patjak/facetimehd after
54fb8f2; AUR 0.7.0.2 still calls strncpy and fails to compile on Linux 7.2.
@murdawkmedia

Copy link
Copy Markdown

Confirmed working on another supported Intel Mac, with one packaging update that may simplify this PR.

Test system:

  • MacBookAir6,2
  • Broadcom FaceTime HD Camera 14e4:1570
  • Omarchy 4.0.4-1
  • linux-omarchy 7.2.5-3

Installed and tested:

  • facetimehd-dkms 0.7.2-1
  • facetimehd-firmware 1:1.43_5-2
  • facetimehd-data 5.1.5769-2

DKMS built successfully for 7.2.5-3-omarchy, modprobe facetimehd initialized the ISP and created /dev/video0, and V4L2 identified it as Apple Facetime HD. A fresh capture completed 30/30 frames at 1280x720 YUYV and 29.97 fps. Installing facetimehd-data also supplied the requested 1871_01XX.dat calibration file, removing the missing-calibration warning.

The PR body's warning about stable AUR 0.7.0.2 appears to be stale now: the current stable package is 0.7.2-1 and compiles cleanly against Omarchy's 7.2.5 kernel. That may remove the need to package a separate current-master build in [omarchy].

Strong support for the PCI-ID-gated install and migration. The exact package set proposed here works on MacBookAir6,2 and produces real 720p video, not just a loaded module.

@drbree82

drbree82 commented Oct 3, 2026

Copy link
Copy Markdown

Hi,

I was working on PR #13192 which partially fixed this, but was late.

I have an A1466 with the Broadcom 14e4:1570 camera available for testing. The camera has already been verified manually on this machine: /dev/video0 appears and mpv captures 1280×720 at 30 fps. Once the package is available in [omarchy], I can validate it through a normal omarchy update.

@calebl

calebl commented Oct 4, 2026

Copy link
Copy Markdown

Tested on a MacBookPro12,1 (Early 2015 13"), 14e4:1570, running 7.2.5-3-omarchy.

On packaging: AUR facetimehd-dkms is now at 0.7.2 (updated Sep 17), and the 0.7.2 tag is exactly 54fb8f2. It built cleanly through DKMS against linux-omarchy 7.2.5-3 here, so [omarchy] can take the stock AUR recipe instead of a git snapshot.

On facetimehd-data: with only facetimehd-firmware and facetimehd-dkms installed, the driver logs Direct firmware load for facetimehd/1871_01XX.dat failed with error -2. After installing facetimehd-data and reloading the module, that error is gone and /dev/video0 captures at 1280×720. So including it in the leaf is correct.

Small note: the migration doesn't modprobe facetimehd, so on existing installs the camera only appears after a reboot. That may be fine, but it could be worth mentioning in the post-update output.

Happy to validate through omarchy update once the packages are in [omarchy].

@murdawkmedia

Copy link
Copy Markdown

Follow-up to the recent camera reports: I ran bash test/shell.d/facetimehd-test.sh against the exact PR revision 8bb9e8e663e5decc4bae299f8ba0177adb3fe256. All 7 checks passed, including detection with a large PCI listing, skipping unrelated hardware, and requesting firmware, calibration data, and DKMS from both the install script and migration.

bash test/cli also completed successfully at that revision, with 112 checks passed.

Fresh hardware retest on MacBookAir6,2, PCI 14e4:1570, Omarchy 4.0.4-1 and 7.2.5-3-omarchy:

  • facetimehd 0.7.2 is installed through DKMS for both the running Omarchy kernel and the installed Arch kernel. All files in the three camera packages are present.
  • A 300-frame V4L2 stream completed at 1280×720 YUYV and approximately 29.97 fps. Reopening the device for another 30 frames also succeeded. Frame data was discarded.
  • I ran the exact PR migration twice on the already-provisioned machine. Both runs detected the camera and returned success without a package transaction; the package log and camera device were unchanged.

This validates current capture and the already-installed migration path. A fresh package installation through a normal omarchy update remains untested.

The reboot observation matches the code at this revision: neither the install script nor migration calls modprobe facetimehd or prints a reboot reminder. A post-install message would help existing users understand why the camera may not appear immediately after updating.

One packaging detail for the remaining validation: this revision's omarchy-pkg-add invokes pacman -S; it does not fall back to AUR. The working AUR 0.7.2 recipe therefore still needs to be published in a configured binary repository before a fresh normal-update installation can pass. I have not verified current repository availability.

@omarchybot

Copy link
Copy Markdown
Collaborator

Reviewed at 8bb9e8e against quattro. The approach is right, but it can't land until facetimehd-firmware, facetimehd-data and facetimehd-dkms are published in [omarchy]. Until then it breaks the ISO build and fresh installs on these Macs, and it stalls omarchy update on them.

What was checked. On a disposable Omarchy VM (7.2.5-3-omarchy), ./test/cli passes, and so do facetimehd-test.sh (7/7), brcmfmac-supplicant-test.sh, t2-hardware-test.sh, migrate-scope-test.sh, migrate-wrapper-test.sh and unowned-system-paths-test.sh. The VM has no 1570 camera, so I stubbed lspci to report one and ran the leaf as root and the migration as the user, with the real omarchy-pkg-add:

  • On quattro, nothing installs the driver, which is the gap this PR fills.
  • On this head, the leaf and the migration both detect the camera and both exit 1 with error: target not found for all three packages. pacman -Si does not find them in any configured repository, and omacom/omarchy-pkgs has no recipe for them yet.

What that means if it merged today:

  • install/omarchy-other.packages:75-77 adds the three packages as offline-mirror targets. builder/build-iso.sh in omarchy-iso passes every name in that list to pacman explicitly, and a missing one fails with "target not found". So every ISO build would fail, including one for a machine with no camera.
  • install/hardware/apple/fix-facetimehd.sh:9: omarchy-apply-hardware sources install/hardware/all.sh under set -euo pipefail, so on a Mac with this camera, hardware setup aborts the install.
  • migrations/1789542390.sh: the migration fails, stays pending and stops the migration queue on every existing Mac with this camera.

None of this is a defect in this branch's code. It is an ordering dependency on packaging in another repository, which is the maintainer's call. That includes redistributing Apple's camera firmware, and which facetimehd-dkms to build: as @calebl notes above, AUR is now at 0.7.2, which is 54fb8f2. omacom/omarchy-pkgs#556 and #182 both propose recipes.

Smaller points, not pushed:

  • The migration installs the module but neither loads it nor sets reboot-required, so on an existing install the camera only appears after a reboot that nothing asks for. sudo modprobe facetimehd (best effort) or omarchy-state set reboot-required would close that.
  • The comment at fix-facetimehd.sh:1-4 names AUR 0.7.0.2, which is now stale.

Competing PRs. #11381 (older) targets the same camera. It installs from the AUR with omarchy-pkg-aur-add, which can't run as root during an ISO install, so a fresh install never gets the driver. This PR's omarchy-pkg-add route is the one that works on both paths once the packages exist, so this is the one to carry forward. #11381's best-effort live modprobe is worth taking. #7732 bundles the camera with audio and SPI for MacBookPro13,1 only, so it misses the 2013-2015 models this PR detects. Both also address #11373. I have not linked it here, because the fix hasn't been seen working on hardware.

Hardware. The camera itself could not be reproduced on a VM. The reports above from @drbree82 and @calebl were made with packages they built themselves, not from this head through [omarchy]. Once the packages are published, a test of this head on a 14e4:1570 Mac through omarchy update is what would verify it.

Second opinion: Codex Medium reviewed the same head. It agreed on the package dependency and on #11381's root-install gap (independence not guaranteed). It found on its own the ISO build failure, which I then confirmed in the omarchy-iso builder, and the missing module load. It also suggested making facetimehd-data optional. I have not taken that up, because the reports above say the driver logs a firmware-load error without it.

Next: this waits on the maintainer to publish the facetimehd packages in [omarchy]. After that, it needs a hardware confirmation of this head.

@murdawkmedia

Copy link
Copy Markdown

Follow-up to the October 7 packaging review at unchanged head 8bb9e8e.

The dependency is still visible in the available metadata: pacman -Si facetimehd-dkms facetimehd-firmware facetimehd-data finds none of the three in this machine's configured sync databases, and a fresh recursive tree read of omacom/omarchy-pkgs master contains no FaceTime recipe paths. #556 and #182 remain open package proposals. The live stable mirror database request returned HTTP 403, so I cannot claim a fresh mirror-level availability check from that request.

The earlier AUR/DKMS and camera-capture reports demonstrate that the hardware can work, but do not validate this PR's fresh binary-repository installation path. I have not repeated a physical Mac capture in this follow-up or run the installer on unrelated hardware.

Which package proposal should hardware testers follow for the coordinated install/update check? Once the binary packages are available, the remaining useful test is a normal install/update on 14e4:1570, including the module-load or reboot path already noted above.

@jandrusk

Copy link
Copy Markdown

Overlaps #11381 and the consolidator #12686 (Intel Mac P08). Also blocked on getting facetimehd-dkms into [omarchy] as you noted.

Suggest closing or redirecting energy into #12686 so we don't maintain three FaceTime install paths.

@omarchybot

Copy link
Copy Markdown
Collaborator

The head is unchanged since the review above (8bb9e8e), so this only covers what is new: #12686, and whether quattro has moved under it.

#12686 is not a reason to close this one. It carries this PR's change and adds an Apple DMI vendor check before the PCI match (install/hardware/apple/fix-facetimehd.sh:6-9 on its branch). The 14e4:1570 camera only ships in Macs, and nothing shows this PR installing the driver anywhere it shouldn't, so the extra check is a narrowing rather than a fix. It also installs the same three packages the same way, so it has the same packaging blocker. The older fix wins unless the newer one fixes a real defect in it, so this stays the one to carry forward. Nothing in #11381 or #7732 changes the earlier assessment. #12686's test showing that a failed package install leaves the migration pending, and that a retry completes it (test/shell.d/camera-consolidation-test.sh:66-91), is worth having here, but it is not needed for this to land.

Still blocked on packaging. facetimehd-firmware, facetimehd-data and facetimehd-dkms are still not in [omarchy], and omacom/omarchy-pkgs#556 and #182 are still open. The new first-boot hardware queue on quattro changes how a failed leaf is retried on an image install (it exits 75 and tries again next boot). It does not change the ISO build failure or the stuck migration described above. This is a read of the code, not a new run on a worker.

Who checked it: Codex Medium compared all four PRs separately, without being told my answer. It reached the same conclusion and found the migration-retry test in #12686 without being pointed to it. Independence is not guaranteed. It also re-read this head against the current quattro and found nothing that conflicts with or replaces it.

Next: this waits on the maintainer to publish the facetimehd packages, then on a hardware test of this head through omarchy update.

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

Labels

bug Something isn't working compatibility Make Omarchy work better on everything!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants