Thanks for this thread — it pointed me in the right direction. I had a similar experience but with some additional twists that might help others.
My setup
- Intel Wireless 8265 / 8275
- Upgraded from a working 14.x installation (using
iwm driver)
The confusing symptom: only SSH dies
After the update, my symptoms were:
- ping → worked fine
- Web browsing → worked fine
- SSH → silently hung, no error message
This was very confusing. The reason turns out to be that without proper firmware, the WiFi chip cannot handle large packets. SSH key exchange requires large packets and silently fails, while ping (small packets) and web browsing (TCP auto-adjusts packet size) appear to work normally.
The fix was the same as yours — running fwget installed the missing wifi-firmware-iwlwifi-kmod base package. Interestingly, all the variant packages (7000, 8000, 9000, 22000, ax210, bz, sc) were already installed; only the base package for older chips was missing.
An extra trap: legacy loader.conf causes kernel panic
While troubleshooting, I tried adding if_iwlwifi_load="YES" to /boot/loader.conf, which is suggested in older documentation and forum posts.
Don't do this. iwlwifi is now loaded automatically via devmatch(8) and must not be listed in loader.conf. Having this line causes a kernel panic due to double-loading.
Why this happened
This update involved two simultaneous changes:
- iwm → iwlwifi driver migration
- src → ports firmware migration (WiFi firmware was removed from the FreeBSD src tree and is now managed separately via
fwget)
Long-term users who had iwm-related entries in loader.conf or rc.conf from older setups are particularly likely to hit this combination of issues.
The real danger: WiFi-only systems
The correct order is:
1. Run fwget first
2. Then update via Software Station
3. Reboot
If you reboot after a kernel update before running fwget, WiFi stops working. Without WiFi and no wired LAN fallback, recovery becomes very difficult.
It would be great if Software Station could run fwget automatically before rebooting after a kernel update.
Hope this helps someone!