Restore Broadcom Wi-Fi after an update swapped broadcom-wl for a DKMS build with no headers
Re-read issue #10975 and both comments: they support the symptom, the pacman.log lines, the --noconfirm scroll-past, the snapshot plus pacman -U recovery and the stock-linux gap in migration 1789444024. Arch's package JSON shows broadcom-wl-dkms 6.30.223.271-50 with replaces=['broadcom-wl'] and depends on dkms, and the broadcom-wl JSON now 404s. On this 4.0.4-1 workstation, migrations 1789325478.sh (linux-omarchy plus headers, old kernel kept) and 1789444024.sh (headers for linux-omarchy or linux-t2 only), install/hardware/fix-bcm43xx.sh (broadcom-wl-dkms only) and the --noconfirm in omarchy-update-system-pkgs all match the cause. linux-omarchy-headers 7.2.5-3 is in the omarchy repo. The dkms 3.4.3-2 hook triggers on usr/src/*/dkms.conf and usr/lib/modules/*/build/include/, so installing headers and reinstalling broadcom-wl-dkms each fire 70-dkms-install.hook, as the fix says. The fix uses pacman -S without -y after a full update, so it is not a partial upgrade and the ALPM guard does not block it. No field needed changing. Status kept as corrected so the previous audit's correction of the dkms autoinstall step stays recorded. Not exercised.
Installing linux-headers from a sync database newer than the installed linux gives headers for a kernel you are not running, which is a partial upgrade in effect. Finish omarchy update (or pacman -Syu on plain Arch) first, so kernel and headers come from the same database.
Symptom
After omarchy update (4.0.2 to 4.0.3) and a reboot, Wi-Fi is gone on a Broadcom BCM4331, BCM4360 or BCM4313 laptop or desktop. nmcli device lists no Wi-Fi device and lsmod | grep wl is empty. /var/log/pacman.log from the update shows:
removed broadcom-wl (6.30.223.271-722)
installed broadcom-wl-dkms (6.30.223.271-49)
70-dkms-install.hook: ==> ERROR: Missing 7.2.3-arch1-3 kernel headers for module broadcom-wl/6.30.223.271.
Cause
Arch retired the prebuilt broadcom-wl and gave broadcom-wl-dkms a replaces=broadcom-wl, so an upgrade swaps one for the other. DKMS can only build the module if headers matching each installed kernel are present. Machines without them got no wl module, and because omarchy update runs pacman with --noconfirm, the error scrolled past. On 4.0.4, migration 1789325478 installs linux-omarchy with its headers and 1789444024 adds headers for linux-omarchy or linux-t2. A stock linux kernel kept alongside still has no linux-headers, and fix-bcm43xx.sh now installs only broadcom-wl-dkms.
Fix
Get any network first (ethernet, or USB tethering from a phone).
Omarchy 4: update through the supported path so the headers match the installed kernels:
omarchy update
Plain Arch:
sudo pacman -Syu
Check which kernels are installed and what DKMS built:
uname -r
pacman -Q | grep -E '^linux(-omarchy|-t2)?(-headers)? '
dkms status
Install the headers for every installed kernel that lacks them. Installing headers triggers 70-dkms-install.hook, which builds the module for that kernel:
sudo pacman -S --needed linux-omarchy-headers # Omarchy kernel
sudo pacman -S --needed linux-headers # only if the stock linux package is installed
If dkms status still does not show broadcom-wl installed for every kernel, reinstall the package. That re-runs the hook for all kernels that have headers. dkms autoinstall alone builds only for the running kernel:
sudo pacman -S broadcom-wl-dkms
dkms status
sudo modprobe wl
If the machine has no network at all, boot the previous Limine snapshot. One reporter recovered by downloading linux and linux-headers into the pacman cache from the snapshot and installing them with pacman -U after booting the upgraded system.
Verify
dkms status shows broadcom-wl/6.30.223.271, <kernel>, x86_64: installed for the running kernel. lsmod | grep -w wl lists the module. nmcli device shows a wifi device.