Wifi disconnected after reboot

Ask Fedora
1

When I boot the system wifi working for 5 min and popup error message wifi connection failed and wifi dissconnected. i install rtw88 driver but issue is not solved

here is some output to more understand the issue,
[

nikhil@localhost ~]$ uname -a
Linux localhost.localdomain 5.8.16-300.fc33.x86_64 #1 SMP Mon Oct 19 13:18:33 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

[nikhil@localhost ~]$ sudo dmesg | grep rtw_8822be
[ 4.239948] rtw_8822be 0000:02:00.0: enabling device (0000 → 0003)
[ 4.242968] rtw_8822be 0000:02:00.0: Firmware version 27.2.0, H2C version 13
[ 4.318890] Error: Driver ‘rtw_8822be’ is already registered, aborting…
[ 4.368374] rtw_8822be 0000:02:00.0 wlo1: renamed from wlan0
[ 5.673558] rtw_8822be 0000:02:00.0: start vif 80:91:33:0a:37:6b on port 0
[ 5.676585] rtw_8822be 0000:02:00.0: stop vif 80:91:33:0a:37:6b on port 0
[ 6.126361] rtw_8822be 0000:02:00.0: start vif 6e:d2:cb:37:0b:ae on port 0
[ 18.872243] rtw_8822be 0000:02:00.0: stop vif 6e:d2:cb:37:0b:ae on port 0
[ 19.321800] rtw_8822be 0000:02:00.0: start vif 80:91:33:0a:37:6b on port 0
[ 24.081042] rtw_8822be 0000:02:00.0: sta 98:da:c4:a0:86:14 joined with macid 0
[ 745.221460] rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
[ 745.224490] rtw_8822be 0000:02:00.0: failed to send h2c command
[ 745.334129] rtw_8822be 0000:02:00.0: firmware failed to restore hardware setting
[ 745.853687] rtw_8822be 0000:02:00.0: failed to send h2c command
[ 745.853693] rtw_8822be 0000:02:00.0: sta 98:da:c4:a0:86:14 with macid 0 left
[ 745.856956] rtw_8822be 0000:02:00.0: failed to send h2c command
[ 745.859982] rtw_8822be 0000:02:00.0: failed to send h2c command
[ 747.860055] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[ 747.860535] rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
[ 747.961409] rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
[ 749.961453] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[ 749.961458] rtw_8822be 0000:02:00.0: mac power on failed
[ 749.961459] rtw_8822be 0000:02:00.0: failed to power on mac
[ 749.961459] rtw_8822be 0000:02:00.0: leave idle state failed
[ 749.961629] rtw_8822be 0000:02:00.0: failed to leave ips state
[ 749.961631] rtw_8822be 0000:02:00.0: failed to leave idle state
[ 755.676467] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[ 755.676931] rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
[ 758.680087] rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
[ 760.680208] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[ 760.680214] rtw_8822be 0000:02:00.0: mac power on failed
[ 760.680215] rtw_8822be 0000:02:00.0: failed to power on mac
[ 760.680215] rtw_8822be 0000:02:00.0: leave idle state failed
[ 760.680409] rtw_8822be 0000:02:00.0: failed to leave ips state
[ 760.680410] rtw_8822be 0000:02:00.0: failed to leave idle state
[ 765.406105] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[ 765.406643] rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
[ 765.406747] rtw_8822be 0000:02:00.0: stop vif 80:91:33:0a:37:6b on port 0
[ 767.406813] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[ 769.409338] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[ 769.409343] rtw_8822be 0000:02:00.0: mac power on failed
[ 769.409344] rtw_8822be 0000:02:00.0: failed to power on mac
[ 1183.423522] rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
[ 1183.423527] rtw_8822be 0000:02:00.0: mac power on failed
[ 1183.423528] rtw_8822be 0000:02:00.0: failed to power on mac

here is lspci -v output,

02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter (rev ff) (prog-if ff)
DeviceName: WLAN
!!! Unknown header type 7f
Kernel driver in use: rtw_8822be
Kernel modules: rtw88_8822be, rtw_8822be

here is the ip link status,

nikhil@localhost ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
link/ether 96:37:bc:7d:08:0c brd ff:ff:ff:ff:ff:ff permaddr 80:91:33:0a:37:6b
altname wlp2s0
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:16:a7:2b brd ff:ff:ff:ff:ff:ff
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN mode DEFAULT group default qlen 1000
link/ether 16:86:bd:b1:2e:72 brd ff:ff:ff:ff:ff:ff
5: enp0s20f0u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
link/ether c6:01:14:cb:40:a1 brd ff:ff:ff:ff:ff:ff

2

And booting the previously kernel (5.8.15), your wifi works just fine?

3

no same issue. wifi connect and disconnect after a few minutes

4

Hello,
any solutions to this issue…

5

Same symptoms in fedora 32. Sometimes stopping and restarting Network Manager allows wifi connection for a few minutes sometimes it does not. nmcli shows available connections, but system fails to connect. The failure also occurs in Ubuntu 18.04 on the Lenovo 730. The 3rd partition is Windows 10 and failure does not appear to occur there.
Suspect driver
sudo dmesg | grep rtw_8822be
shows some failure mode:
1980.854677] rtw_8822be 0000:6c:00.0: firmware failed to restore hardware setting
[ 1990.902116] rtw_8822be 0000:6c:00.0: firmware failed to restore hardware setting
[ 2040.886241] rtw_8822be 0000:6c:00.0: firmware failed to restore hardware setting

wired connection and then disconnecting seems to fix the problem until the next hibernation of wifi or reboot.

5.9.12-100.fc32.x86_64 #1 SMP Wed Dec 2 15:58:24 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

any ideas?

1 Like
6

Have you updated fedora32, because mine had same problem with rtw_8723de, but after I upgraded my system sudo dnf upgrade --refresh, everything is fine

1 Like
7

I have a new twist on the issue, now only the 2.4 GHZ won’t connect. I verified that Windows 10 can connect at both 2.4 and 5 GHZ. I did update with sudo dnf upgrade – refresh yesterday and there were updates… I reran today and the result was “nothing to do.” Also the dmesg included on at least one occasion a reference to H2c.
[ 5.617772] rtw_8822be 0000:6c:00.0: Firmware version 27.2.0, H2C version 13
[ 5.667130] rtw_8822be 0000:6c:00.0 wlp108s0: renamed from wlan0
[ 7.636934] rtw_8822be 0000:6c:00.0: start vif 48:5f:99:83:fb:87 on port 0
[ 7.640252] rtw_8822be 0000:6c:00.0: stop vif 48:5f:99:83:fb:87 on port 0
[ 8.080566] rtw_8822be 0000:6c:00.0: start vif 22:df:2a:d6:f8:af on port 0
[ 11.532186] rtw_8822be 0000:6c:00.0: stop vif 22:df:2a:d6:f8:af on port 0
[ 11.971570] rtw_8822be 0000:6c:00.0: start vif 48:5f:99:83:fb:87 on port 0
[ 15.875330] rtw_8822be 0000:6c:00.0: sta 06:93:97:39:c3:83 joined with macid 0
[ 90.950905] rtw_8822be 0000:6c:00.0: firmware failed to restore hardware setting
[ 873.802568] rtw_8822be 0000:6c:00.0: failed to send h2c command
[ 1123.955110] rtw_8822be 0000:6c:00.0: firmware failed to restore hardware setting
[ 1314.930338] rtw_8822be 0000:6c:00.0: firmware failed to restore hardware setting

Also the latest output looks like it shows multiple attempts to connect at 2.4 then the successful connection at 5 GHZ.

[ 5.222867] rtw_8822be 0000:6c:00.0: Firmware version 27.2.0, H2C version 13
[ 5.346915] rtw_8822be 0000:6c:00.0 wlp108s0: renamed from wlan0
[ 7.171593] rtw_8822be 0000:6c:00.0: start vif 48:5f:99:83:fb:87 on port 0
[ 7.178364] rtw_8822be 0000:6c:00.0: stop vif 48:5f:99:83:fb:87 on port 0
[ 7.638556] rtw_8822be 0000:6c:00.0: start vif a2:48:fa:d7:77:3a on port 0
[ 11.080852] rtw_8822be 0000:6c:00.0: stop vif a2:48:fa:d7:77:3a on port 0
[ 11.530519] rtw_8822be 0000:6c:00.0: start vif 48:5f:99:83:fb:87 on port 0
[ 15.457609] rtw_8822be 0000:6c:00.0: sta 06:93:97:39:c3:83 joined with macid 0
[ 51.281993] rtw_8822be 0000:6c:00.0: sta 06:93:97:39:c3:83 with macid 0 left
[ 51.321764] rtw_8822be 0000:6c:00.0: stop vif 48:5f:99:83:fb:87 on port 0
[ 51.772512] rtw_8822be 0000:6c:00.0: start vif 46:54:50:e4:5e:3a on port 0
[ 52.223304] rtw_8822be 0000:6c:00.0: stop vif 46:54:50:e4:5e:3a on port 0
[ 52.670952] rtw_8822be 0000:6c:00.0: start vif 48:5f:99:83:fb:87 on port 0
[ 60.466160] rtw_8822be 0000:6c:00.0: sta 28:80:88:f8:bc:55 joined with macid 0
[ 105.365549] rtw_8822be 0000:6c:00.0: sta 28:80:88:f8:bc:55 with macid 0 left
[ 105.366450] rtw_8822be 0000:6c:00.0: stop vif 48:5f:99:83:fb:87 on port 0
[ 105.813469] rtw_8822be 0000:6c:00.0: start vif ea:e6:ac:a5:47:cf on port 0
[ 109.219837] rtw_8822be 0000:6c:00.0: stop vif ea:e6:ac:a5:47:cf on port 0
[ 109.667656] rtw_8822be 0000:6c:00.0: start vif 48:5f:99:83:fb:87 on port 0
[ 113.836440] rtw_8822be 0000:6c:00.0: sta 06:93:97:39:c3:83 joined with macid 0
[ 314.138527] rtw_8822be 0000:6c:00.0: firmware failed to restore hardware setting
[ 324.185928] rtw_8822be 0000:6c:00.0: firmware failed to restore hardware setting

Thanks for the suggestion.

1 Like