You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Macbook Air 7,2 2015/2017 Webcam driver doesn't load on install #12331
The webcam kernel module doesn't load on the 2015 macbook air. The agent loaded it just fine but it probably should load during the initial omarchy install. I tried to get the agent to create a PR but did have any luck. Here the gist of what the big pickle had to say.
Final Plan
Phase 1 — Load kernel driver on this machine
Install facetimehd-dkms + facetimehd-firmware via yay -S
DKMS builds the module against the current kernel (7.2.5-3-omarchy)
Requires sudo (will prompt for password)
Load with sudo modprobe facetimehd
Verify — v4l2-ctl --list-devices lists the FaceTime camera, /dev/video0 appears
Same missing driver as #11373, and the pending fix already covers this machine: #11381 gates on Apple vendor + PCI 14e4:1570 (no model list), so the Air 7,2 gets it automatically once merged — installer leaf for fresh installs plus a migration for existing ones like yours.
Your manual path (AUR facetimehd-dkms-git + facetimehd-firmware, DKMS build, modprobe facetimehd, /dev/video0 at 720p) matches the verified stack exactly — confirmed end-to-end on MacBookPro11,5 including DKMS rebuild across a kernel upgrade. Nothing to change there; this comment is just to link the issue to its fix.
This is the same bug as #11373, so I'm closing it as a duplicate there. Both are pre-T2 Macs whose built-in FaceTime HD camera (Broadcom 14e4:1570) has no in-tree driver, and Omarchy installs nothing for it, so the camera sits driverless with no /dev/video0. The fix is the same in both: install facetimehd-dkms-git and facetimehd-firmware and load facetimehd. Your report that modprobe facetimehd brought the camera up confirms your Air 7,2 has that same part, because that driver binds only to 14e4:1570.
The open fix is #11381. Its installer step and migration are gated on an Apple system vendor plus a 14e4:1570 PCI device, not on a list of models, so it covers the MacBookAir7,2 for fresh installs and existing ones alike. Whether it merges is the maintainer's call. If your machine turns out to differ from #11373 in a way that matters, this can be reopened.
Checked by reading both reports and the diff of #11381 against quattro; nothing was run, since this needs the Mac's camera. The duplicate call was checked separately by Codex Medium.
Activity
rand0mdud3 commentedon Oct 12, 2026
Same missing driver as #11373, and the pending fix already covers this machine: #11381 gates on Apple vendor + PCI
14e4:1570(no model list), so the Air 7,2 gets it automatically once merged — installer leaf for fresh installs plus a migration for existing ones like yours.Your manual path (AUR
facetimehd-dkms-git+facetimehd-firmware, DKMS build,modprobe facetimehd,/dev/video0at 720p) matches the verified stack exactly — confirmed end-to-end on MacBookPro11,5 including DKMS rebuild across a kernel upgrade. Nothing to change there; this comment is just to link the issue to its fix.omarchybot commentedon Oct 12, 2026
This is the same bug as #11373, so I'm closing it as a duplicate there. Both are pre-T2 Macs whose built-in FaceTime HD camera (Broadcom
14e4:1570) has no in-tree driver, and Omarchy installs nothing for it, so the camera sits driverless with no/dev/video0. The fix is the same in both: installfacetimehd-dkms-gitandfacetimehd-firmwareand loadfacetimehd. Your report thatmodprobe facetimehdbrought the camera up confirms your Air 7,2 has that same part, because that driver binds only to14e4:1570.The open fix is #11381. Its installer step and migration are gated on an Apple system vendor plus a
14e4:1570PCI device, not on a list of models, so it covers the MacBookAir7,2 for fresh installs and existing ones alike. Whether it merges is the maintainer's call. If your machine turns out to differ from #11373 in a way that matters, this can be reopened.Checked by reading both reports and the diff of #11381 against
quattro; nothing was run, since this needs the Mac's camera. The duplicate call was checked separately by Codex Medium.