Fail to load firmware brcm/bcm43xx-0.fw
Describe the issue you are experiencing
The WiFi card firmware cannot be loaded
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
16.2
Did the problem occur after upgrading the Operating System?
No
Hardware details
It's an Asus F201E laptop (https://www.asus.com/supportonly/f201e/helpdesk_download/) with a ZBT-1 connected
Steps to reproduce the issue
Install HA OS on the laptop
Anything in the Supervisor logs that might be useful for us?
I don't think there's anything regarding this issue
Anything in the Host logs that might be useful for us?
2025-09-09 22:01:56.150 homeassistant kernel: brcmsmac bcma0:1: Direct firmware load for brcm/bcm43xx-0.fw failed with error -2
2025-09-09 22:01:56.151 homeassistant kernel: ieee80211 phy0: brcmsmac: fail to load firmware brcm/bcm43xx-0.fw
2025-09-09 22:01:56.152 homeassistant NetworkManager[396]: <warn> [1757455316.1520] platform-linux: do-change-link[3]: failure 2 (No such file or directory), firmware not found
System information
System Information
| version | core-2025.9.2 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| container_arch | amd64 |
| user | root |
| virtualenv | false |
| python_version | 3.13.7 |
| os_name | Linux |
| os_version | 6.12.43-haos |
| arch | x86_64 |
| timezone | Europe/Berlin |
| config_dir | /config |
Home Assistant Cloud
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 16.2 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2025.09.0 |
| agent_version | 1.7.2 |
| docker_version | 28.3.3 |
| disk_total | 54.3 GB |
| disk_used | 9.1 GB |
| nameservers | 2003:d0:1f01:ec00:96dc:ba42:8d1b:c822, 192.168.188.33 |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | |
| board | generic-x86-64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | AdGuard Home (5.3.2), Matter Server (8.1.0), Music Assistant Server (2.5.8), Speech-to-Phrase (1.4.1), Piper (1.6.4), ESPHome Device Builder (2025.8.4) |
Dashboards
| dashboards | 2 |
|---|---|
| resources | 0 |
| views | 0 |
| mode | storage |
Network Configuration
| adapters | lo (disabled), enp3s0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth83e2734 (disabled), vethe2fb52e (disabled), veth80c902d (disabled), veth31019ec (disabled), vethc830469 (disabled), veth51af325 (disabled) |
|---|---|
| ipv4_addresses | lo (127.0.0.1/8), enp3s0 (192.168.188.33/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth83e2734 (), vethe2fb52e (), veth80c902d (), veth31019ec (), vethc830469 (), veth51af325 () |
| ipv6_addresses | lo (::1/128), enp3s0 (2003:d0:1f14:cd00:d6ac:ea21:39bd:f733/64, fe80::a96b:98fa:468d:e5d7/64), hassio (fe80::9093:7cff:fe6f:c0e0/64), docker0 (fe80::94c3:4bff:fe86:ba61/64), veth83e2734 (fe80::dc6a:3aff:fe6a:1146/64), vethe2fb52e (fe80::841e:aeff:fec3:38de/64), veth80c902d (fe80::c851:18ff:fe77:50f2/64), veth31019ec (fe80::700c:5aff:fe9e:cbf2/64), vethc830469 (fe80::bc40:a6ff:febe:cea2/64), veth51af325 (fe80::cff:84ff:fea4:af74/64) |
| announce_addresses | 192.168.188.33, 2003:d0:1f14:cd00:d6ac:ea21:39bd:f733, fe80::a96b:98fa:468d:e5d7 |
Recorder
| oldest_recorder_run | 24. August 2025 um 14:34 |
|---|---|
| current_recorder_run | 13. September 2025 um 13:14 |
| estimated_db_size | 110.73 MiB |
| database_engine | sqlite |
| database_version | 3.48.0 |
Additional information
No response
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Not resolved