Wifi interface not detected after kernel upgrade

nic-obert · 2025-10-30 11:45:54

Hello there.
I use Arch on an Asus X205T laptop. Wifi stopped working after the kernel upgrade from 6.16.10 to 6.17.5. Reverting back to 6.16.10 is a temporary workaround, but I wouldn't want to remain on an old kernel forever.

After the kernel upgrade:

ip link

only shows the loopback interface

journalctl -b

The full output is available here: https://0x0.st/K_xm.txt
In particular, the following journal lines look suspicious

Oct 30 11:16:34 asus kernel: brcmfmac: F1 signature read @0x18000000=0x1602a94c
Oct 30 11:16:34 asus kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43340-sdio for chip BCM43340/2
Oct 30 11:16:34 asus kernel: brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43340-sdio.ASUSTeK COMPUTER INC.-X205TA.bin failed with error -2
Oct 30 11:16:34 asus kernel: usbcore: registered new interface driver brcmfmac
Oct 30 11:16:34 asus kernel: brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43340-sdio.txt failed with error -2
Oct 30 11:16:34 asus kernel: ------------[ cut here ]------------
Oct 30 11:16:34 asus kernel: WARNING: CPU: 1 PID: 262 at arch/x86/platform/efi/efi_64.c:169 efi_thunk_get_variable+0x25f/0x3e0
Oct 30 11:16:34 asus kernel: Modules linked in: uvc snd_intel_dspcfg kvm(+) snd_intel_sdw_acpi videobuf2_memops snd_soc_acpi_intel_match videobuf2_v4l2 irqbypass brcmfmac videobuf2_common snd_soc_acpi_intel_sdca_quirks snd_intel_sst_core snd_soc_rt5645(+) asus_nb_wmi videodev ghash_clmulni_intel snd_soc_sst_atom_hifi2_platform asus_wmi int3401_thermal aesni_intel brcmutil snd_soc_acpi platform_profile processor_thermal_device intel_cstate pcspkr cfg80211 sparse_keymap snd_soc_sdca processor_thermal_wt_hint snd_soc_rl6231 mc hci_uart platform_temperature_control snd_soc_core btqca pwrseq_core processor_thermal_rfim btrtl snd_compress mei_txe processor_thermal_rapl btintel ac97_bus mei snd_hdmi_lpe_audio lpc_ich btbcm snd_pcm_dmaengine intel_rapl_common snd_pcm processor_thermal_wt_req vfat bluetooth soc_button_array processor_thermal_power_floor dptf_power dw_dmac fat snd_timer int3400_thermal int3406_thermal int3403_thermal processor_thermal_mbox intel_int0002_vgpio int340x_thermal_zone acpi_thermal_rel asus_wireless rfkill acpi_pad
Oct 30 11:16:34 asus kernel:  intel_soc_pmic_chtdc_ti elan_i2c snd i2c_hid_acpi pwm_lpss_platform soundcore i2c_hid pwm_lpss 8250_dw mac_hid dm_mod loop nfnetlink ip_tables x_tables i915 mmc_block rpmb_core i2c_algo_bit drm_buddy ttm intel_gtt drm_display_helper video cec wmi sdhci_acpi sdhci mmc_core
Oct 30 11:16:34 asus kernel: CPU: 1 UID: 0 PID: 262 Comm: kworker/1:2 Not tainted 6.17.5-arch1-1 #1 PREEMPT(full)  01c39fc421df2af799dd5e9180b572af860b40c1
Oct 30 11:16:34 asus kernel: Hardware name: ASUSTeK COMPUTER INC. X205TA/X205TA, BIOS X205TA.205 10/06/2014
Oct 30 11:16:34 asus kernel: Workqueue: events request_firmware_work_func
Oct 30 11:16:34 asus kernel: RIP: 0010:efi_thunk_get_variable+0x25f/0x3e0
Oct 30 11:16:34 asus kernel: Code: 8c fe ff ff 45 31 ff e9 b4 fe ff ff 48 89 df e8 67 5e ff ff 49 01 c5 48 89 c3 49 31 c5 49 81 fd ff 0f 00 00 0f 86 df fe ff ff <0f> 0b 31 db 4d 85 f6 0f 85 da fe ff ff 48 83 7d 90 00 0f 84 53 ff
Oct 30 11:16:34 asus kernel: RSP: 0018:ffffd0604080fcd0 EFLAGS: 00010012
Oct 30 11:16:34 asus kernel: RAX: 000000000483cff8 RBX: 000000000483cff8 RCX: 000fffffffe00000
Oct 30 11:16:34 asus kernel: RDX: 0000000000000000 RSI: 000fffffffe00000 RDI: 800000000483c021
Oct 30 11:16:34 asus kernel: RBP: ffffd0604080fd50 R08: ffffd0604080fcb3 R09: ffffffffa08d40ff
Oct 30 11:16:34 asus kernel: R10: ffffffffc118de60 R11: fffff2bb00122e40 R12: ffffd0604080fd78
Oct 30 11:16:34 asus kernel: R13: 0000000000001ffa R14: 0000000000000000 R15: 00000000072a9d00
Oct 30 11:16:34 asus kernel: FS:  0000000000000000(0000) GS:ffff8894d8d86000(0000) knlGS:0000000000000000
Oct 30 11:16:34 asus kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 30 11:16:34 asus kernel: CR2: 00007fff31388b10 CR3: 0000000008726000 CR4: 00000000001006f0
Oct 30 11:16:34 asus kernel: Call Trace:
Oct 30 11:16:34 asus kernel:  <TASK>
Oct 30 11:16:34 asus kernel:  brcmf_fw_complete_request+0x25f/0x3f0 [brcmfmac 9b07066c5916e74d495d6a7c5b63f37e7a46970a]
Oct 30 11:16:34 asus kernel:  brcmf_fw_request_done+0xdc/0x190 [brcmfmac 9b07066c5916e74d495d6a7c5b63f37e7a46970a]
Oct 30 11:16:34 asus kernel:  request_firmware_work_func+0x54/0xa0
Oct 30 11:16:34 asus kernel:  process_one_work+0x193/0x350
Oct 30 11:16:34 asus kernel:  worker_thread+0x2d7/0x410
Oct 30 11:16:34 asus kernel:  ? __pfx_worker_thread+0x10/0x10
Oct 30 11:16:34 asus kernel:  kthread+0xfc/0x240
Oct 30 11:16:34 asus kernel:  ? __pfx_kthread+0x10/0x10
Oct 30 11:16:34 asus kernel:  ? __pfx_kthread+0x10/0x10
Oct 30 11:16:34 asus kernel:  ret_from_fork+0x1c4/0x1f0
Oct 30 11:16:34 asus kernel:  ? __pfx_kthread+0x10/0x10
Oct 30 11:16:34 asus kernel:  ret_from_fork_asm+0x1a/0x30
Oct 30 11:16:34 asus kernel:  </TASK>
Oct 30 11:16:34 asus kernel: ---[ end trace 0000000000000000 ]---
# -- some log lines later -- #
Oct 30 11:16:35 asus kernel: brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

It looks like there's an issue with the Broadcom firmware. The `linux-firmware-broadcom` package is currently version 20251021-1

Can anyone point me in the right direction?

seth · 2025-10-30 21:26:45

usr/lib/firmware/brcm/brcmfmac43340-sdio.ASUSTeK COMPUTER INC.-TF103CE.txt.zst
usr/lib/firmware/brcm/brcmfmac43340-sdio.Insyde-VESPA2.txt.zst
usr/lib/firmware/brcm/brcmfmac43340-sdio.bin.zst
usr/lib/firmware/brcm/brcmfmac43340-sdio.meegopad-t08.txt.zst
usr/lib/firmware/brcm/brcmfmac43340-sdio.pov-tab-p1006w-data.txt.zst
usr/lib/firmware/brcm/brcmfmac43340-sdio.predia-basic.txt.zst

And the targeted FW is also not in https://gitlab.com/kernel-firmware/linu … type=heads so the problem is likely that

Oct 30 11:16:34 asus kernel: brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43340-sdio.txt failed with error -2

isn't brcm/brcmfmac43340-sdio.bin which also is a symlink to ../cypress/cyfmac43340-sdio.bin.zst

nic-obert · 2025-10-31 10:13:24

One thing I forgot to mention is that booting in the 6.16.10 kernel, where wifi works, also shows similar errors in the journal:

journalctl -b | grep brcmfmac

Oct 30 12:10:33 asus kernel: brcmfmac: F1 signature read @0x18000000=0x1602a94c
Oct 30 12:10:33 asus kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43340-sdio for chip BCM43340/2
Oct 30 12:10:33 asus kernel: brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43340-sdio.ASUSTeK COMPUTER INC.-X205TA.bin failed with error -2
Oct 30 12:10:33 asus kernel: usbcore: registered new interface driver brcmfmac
Oct 30 12:10:33 asus kernel: brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43340-sdio.txt failed with error -2
Oct 30 12:10:33 asus kernel: brcmfmac: brcmf_fw_nvram_from_efi: Using nvram EFI variable
Oct 30 12:10:33 asus kernel: brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43340-sdio.clm_blob failed with error -2
Oct 30 12:10:33 asus kernel: brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Oct 30 12:10:33 asus kernel: brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
Oct 30 12:10:33 asus kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43340/2 wl0: Apr 23 2021 05:48:34 version 6.10.190.91 (r728536) FWID 01-d45e96c4
Oct 30 12:10:33 asus NetworkManager[385]: <info>  [1761822633.7032] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/platform/INT33BB:00/mmc_host/mmc0/mmc0:0001/mmc0:0001:1/ieee80211/phy0/rfkill1) (driver brcmfmac)

Any idea about what could be wrong here and how to proceed?
What do these errors mean?

seth · 2025-10-31 12:42:32

The previous kernel wen't on to brcmfmac43340-sdio.clm_blob and probably later brcmfmac43340-sdio.bin (?) while 6.17 seems to abort the fw loading w/ a warning after not finding brcmfmac43340-sdio.txt
What if you just copy brcmfmac43340-sdio.bin.zst to brcmfmac43340-sdio.txt.zst ?

nic-obert · 2025-11-01 09:27:32

I symlinked `brcmfmac43340-sdio.ASUSTeK COMPUTER INC.-X205TA.bin.zst -> brcmfmac43340-sdio.bin.zst` and `brcmfmac43340-sdio.txt.zst -> brcmfmac43340-sdio.ASUSTeK COMPUTER INC.-TF103CE.txt.zst`. Now the network interface is successfully detected and I can connect to the internet.
However, I'm still getting some errors in the journal

journalctl -b | grep brcm

Oct 31 20:40:21 asus kernel: brcmfmac: F1 signature read @0x18000000=0x1602a94c
Oct 31 20:40:21 asus kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43340-sdio for chip BCM43340/2
Oct 31 20:40:21 asus kernel: usbcore: registered new interface driver brcmfmac
Oct 31 20:40:21 asus kernel: brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43340-sdio.clm_blob failed with error -2
Oct 31 20:40:22 asus kernel: brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Oct 31 20:40:22 asus kernel: brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
Oct 31 20:40:22 asus kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43340/2 wl0: Apr 23 2021 05:48:34 version 6.10.190.91 (r728536) FWID 01-d45e96c4

I have no broadcom or cypress clm_blob for 43340 (whatever that is) firmware on my system.
Is this going to be a problem? Will there be impacts on performance or functionality?

seth · 2025-11-01 14:15:16

The chip is actually a cypress one - broadcom wifi is a complete mess (therefore afforded its own wiki article …)

You had the same errors/warnings before the 6.17 kernel, so the (new) problem is "only" that the warning shortcuts the fallback chain.
Does it also already affec https://pkgbuild.com/~gromit/linux-bise … kg.tar.zst ?

nic-obert · 2025-11-01 16:08:33

seth wrote:

Does it also already affec https://pkgbuild.com/~gromit/linux-bise … kg.tar.zst ?

Without the symlink fix, the 6.17.0-rc1-1-mainline kernel encounters the same error as the 6.17.5 kernel (without the symlink fix) and results in no network card support.
With the symlink fix, the 6.17.0-rc1-1-mainline kernel shows the same warnings as the 6.17.5 kernel (with the symlink fix) and the network card is working.

seth · 2025-11-01 20:43:54

So it's already in the first rc, but I can't immediately see where
https://github.com/gregkh/linux/commits … 1/brcmfmac
https://github.com/gregkh/linux/commits … firmware.c hasn't changed in 2 years

You might have to https://wiki.archlinux.org/title/Bisect … s_with_Git
Pattern on how to build a custom kernel: https://bbs.archlinux.org/viewtopic.php … 4#p2270274
You can also test the random (to your situation) bisection kernel loqs has already compiled to shortcut the builds.

Arch Linux

#1 2025-10-30 11:45:54

Wifi interface not detected after kernel upgrade

#2 2025-10-30 21:26:45

Re: Wifi interface not detected after kernel upgrade

#3 2025-10-31 10:13:24

Re: Wifi interface not detected after kernel upgrade

#4 2025-10-31 12:42:32

Re: Wifi interface not detected after kernel upgrade

#5 2025-11-01 09:27:32

Re: Wifi interface not detected after kernel upgrade

#6 2025-11-01 14:15:16

Re: Wifi interface not detected after kernel upgrade

#7 2025-11-01 16:08:33

Re: Wifi interface not detected after kernel upgrade

#8 2025-11-01 20:43:54

Re: Wifi interface not detected after kernel upgrade

Board footer