No wifi since 5.19.0-40 kernel update with asus AC88 wireless adapter
When booting with 5.19.0-40 kernel, I have no wifi connectivitiy
rfkill list shows no devices
Booting with previous 5.19.0-39 kernel solves the issue
related:
* https:/
* https:/
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
For diagnostic purposes, what is the output of the following commands:
uname -a
lsb_release -crid
sudo lshw -C network
sudo dmesg | grep brcm
It might be helpful to run these commands twice, once with the old (working) version of the kernel and once with the new one, to allow comparison.
Revision history for this message
|
#2 |
with wifi ok:
uname -a
lsb_release -crid
sudo lshw -C network
sudo dmesg | grep brcm
Linux gunter 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy
*-network
description: Interface réseau sans fil
produit: Broadcom Inc. and subsidiaries
fabricant: Broadcom Inc. and subsidiaries
identifiant matériel: 0
information bus: pci@0000:03:00.0
nom logique: wlp3s0
version: 04
numéro de série: 2c:fd:a1:cf:12:43
bits: 64 bits
horloge: 33MHz
ressources : irq:101 mémoire:
*-network
description: Ethernet interface
produit: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
fabricant: Realtek Semiconductor Co., Ltd.
identifiant matériel: 0
information bus: pci@0000:04:00.0
nom logique: enp4s0
version: 15
numéro de série: a8:5e:45:50:e1:dc
capacité: 1Gbit/s
bits: 64 bits
horloge: 33MHz
ressources : irq:24 portE/S:
[41681.314995] ieee80211 phy2: brcmf_inetaddr_
[41683.712329] brcmfmac: brcmf_fw_
[41683.712370] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[41683.712386] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[41683.712398] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[41684.577096] brcmfmac: brcmf_fw_
[41684.577111] brcmfmac: brcmf_c_
[41684.577334] brcmfmac: brcmf_c_
[41686.847868] brcmfmac 0000:03:00.0 wlp3s0: renamed from wlan0
[41687.985574] ieee80211 phy3: brcmf_p2p_
[41687.985768] ieee80211 phy3: brcmf_p2p_
[41687.985771] ieee80211 phy3: brcmf_cfg80211_
[41692.544947] ieee80211 phy3: brcmf_inetaddr_
Revision history for this message
|
#3 |
wifi not ok:
Release: 22.04
Codename: jammy
*-network NON-RÉCLAMÉ
description: Network controller
produit: Broadcom Inc. and subsidiaries
fabricant: Broadcom Inc. and subsidiaries
identifiant matériel: 0
information bus: pci@0000:03:00.0
version: 04
bits: 64 bits
horloge: 33MHz
ressources : mémoire:
*-network
description: Ethernet interface
produit: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
fabricant: Realtek Semiconductor Co., Ltd.
identifiant matériel: 0
information bus: pci@0000:04:00.0
nom logique: enp4s0
version: 15
numéro de série: a8:5e:45:50:e1:dc
capacité: 1Gbit/s
bits: 64 bits
horloge: 33MHz
ressources : irq:24 portE/S:
[ 4.565881] usbcore: registered new interface driver brcmfmac
[ 4.672325] brcmfmac: brcmf_fw_
[ 4.682136] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[ 4.687022] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[ 4.687039] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[ 5.516066] brcmfmac 0000:03:00.0: brcmf_pcie_
Revision history for this message
|
#4 |
The main difference that I see:
With the 5.19.0-38 version of the kernel the firmware is loaded, with 5.19.0-40 it isn't.
I assume that the file that is (respectively should be) loaded is /lib/firmware/
What output do you receive fir the following commands (again with both kernel versions, if possible)
sudo modprobe -rv brcmfmac
sudo modprobe -v brcmfmac
sudo dmesg | tail
Revision history for this message
|
#5 |
With old kernel , wifi works
uname -a
Linux gunter 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
sudo modprobe -rv brcmfmac
[sudo] Mot de passe de rodolphe :
rmmod brcmfmac
rmmod cfg80211
rmmod brcmutil
*wifi dies*
sudo modprobe -v brcmfmac
insmod /lib/modules/
insmod /lib/modules/
insmod /lib/modules/
*wifi works again*
sudo dmesg | tail
[ 4203.022891] brcmfmac: brcmf_fw_
[ 4203.022931] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[ 4203.023156] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[ 4203.023177] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[ 4203.887838] brcmfmac: brcmf_fw_
[ 4203.887878] brcmfmac: brcmf_c_
[ 4203.888120] brcmfmac: brcmf_c_
[ 4203.905847] brcmfmac 0000:03:00.0 wlp3s0: renamed from wlan0
[ 4206.416601] IPv6: ADDRCONF(
[ 4206.458511] ieee80211 phy0: brcmf_inetaddr_
Revision history for this message
|
#6 |
With new kernel, wifi not working
rodolphe@gunter:~$ uname -a
Linux gunter 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
rodolphe@gunter:~$ sudo modprobe -rv brcmfmac
rmmod brcmfmac
rmmod cfg80211
rmmod brcmutil
rodolphe@gunter:~$ sudo modprobe -v brcmfmac
insmod /lib/modules/
insmod /lib/modules/
insmod /lib/modules/
rodolphe@gunter:~$ sudo dmesg | tail
[ 71.485498] [drm:nv_
[ 1378.490343] usbcore: deregistering interface driver brcmfmac
[ 1460.215248] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 1460.215364] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 1460.226371] usbcore: registered new interface driver brcmfmac
[ 1460.332307] brcmfmac: brcmf_fw_
[ 1460.332330] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[ 1460.332489] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[ 1460.332501] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43
[ 1461.196491] brcmfmac 0000:03:00.0: brcmf_pcie_
Revision history for this message
|
#7 |
this is consistent with the message from the redditor:
> UPDATE 1/14/2023: I fixed it. The driver fails to load because there is a variable call max_flowrings which, for this model of card, takes the value 264. Ordinarily, such a high value would be a sign of a hardware problem, so the kernel update that caused this crash introduced a sanity check that caused the driver to fail if max_flowrings exceeds 256. A workaround solution is to apply this patch, which increases the threshold for failure to 512. I applied this patch and now the card works perfectly. Alternatively, one could wait until kernel 6.2 is released, since that kernel version will include this patch.
Revision history for this message
|
#8 |
Ok, that seems to be an explanation, see also
https:/
I can only hope that this is corrected in one of the next kernel versions. Eventually it makes sense to create a bug report in Ubuntu for a temporary patch.
Revision history for this message
|
#9 |
> create a bug report in Ubuntu for a temporary patch
I'm not sure I understand. Isn't this already a bug report in Ubuntu ? Do I need to create another one ?
Revision history for this message
|
#10 |
I did not find a bug report in the Ubuntu bug tracker (only messages in kernel.org).
It seems that my last comment was poorly formulated. I meant the following:
... it makes sense to create a bug report in Ubuntu's bug tracker to request that a patch (e.g. increase the limit from 256 to 512 or revert the related commit) is added to the next Ubuntu package, until a correction is included in the upstream source.
Can you help with this problem?
Provide an answer of your own, or ask BiAiB for more information if necessary.