Wifi disconnecting randomly

Ask Fedora
, , ,
1

My wifi is disconnecting randomly, I tried using a USB wifi dongle and that also disconnects randomly. I’m not entirely sure how to troubleshoot this issue.

Here is output from lsusb

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader
Bus 001 Device 005: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 001 Device 003: ID 2357:0138 TP-Link 802.11ac NIC
Bus 001 Device 009: ID 0c45:6723 Microdia Integrated_Webcam_HD
Bus 001 Device 008: ID 1532:0067 Razer USA, Ltd Naga Trinity
Bus 001 Device 006: ID 0d8c:0005 C-Media Electronics, Inc. Blue Snowball
Bus 001 Device 004: ID 1532:0221 Razer USA, Ltd RZ03-0203 Gaming Keyboard [BlackWidow Chroma V2]
Bus 001 Device 002: ID 2109:2811 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here is what ifconfig output looks like

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1333  bytes 238064 (232.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1333  bytes 238064 (232.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp0s20f0u2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.68.68  netmask 255.255.252.0  broadcast 192.168.71.255
        inet6 fe80::d57a:c49e:473d:aa3  prefixlen 64  scopeid 0x20<link>
        ether 6c:5a:b0:81:74:0c  txqueuelen 1000  (Ethernet)
        RX packets 216668  bytes 251563415 (239.9 MiB)
        RX errors 0  dropped 676  overruns 0  frame 0
        TX packets 13604  bytes 2488100 (2.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp59s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.68.62  netmask 255.255.252.0  broadcast 192.168.71.255
        inet6 fe80::80ce:b1ae:8253:c0f4  prefixlen 64  scopeid 0x20<link>
        ether 50:eb:71:25:c8:1c  txqueuelen 1000  (Ethernet)
        RX packets 70035  bytes 66829147 (63.7 MiB)
        RX errors 0  dropped 664  overruns 0  frame 0
        TX packets 103337  bytes 17404619 (16.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Here is what my system logs say

12:48:48 PM kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f0u2: link becomes ready
12:48:48 PM kernel: rtw_8822bu 1-2:1.0: failed to get tx report from firmware
12:48:47 PM kernel: wlp0s20f0u2: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:48:32 PM kernel: wlp59s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:48:32 PM kernel: wlp0s20f0u2: 48:22:54:2f:9c:97 denied authentication (status 37)
12:48:29 PM kernel: wlp59s0: 48:22:54:2f:9c:8e denied authentication (status 37)
12:36:27 PM kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f0u2: link becomes ready
12:36:27 PM kernel: rtw_8822bu 1-2:1.0: failed to get tx report from firmware
12:36:26 PM kernel: wlp0s20f0u2: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:36:19 PM kernel: rtw_8822bu 1-2:1.0: timed out to flush queue 2
12:36:19 PM kernel: wlp0s20f0u2: deauthenticating from 48:22:54:2f:9c:8f by local choice (Reason: 3=DEAUTH_LEAVING)
12:36:19 PM kernel: rtw_8822bu 1-2:1.0: failed to get tx report from firmware
12:36:18 PM kernel: wlp0s20f0u2: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:36:14 PM kernel: rtw_8822bu 1-2:1.0: failed to leave idle state
12:36:13 PM kernel: wlp0s20f0u2: 48:22:54:2f:9c:8e denied authentication (status 37)
12:36:11 PM kernel: wlp59s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:36:08 PM kernel: wlp0s20f0u2: 48:22:54:2f:9c:97 denied authentication (status 37)
12:36:03 PM kernel: wlp59s0: Connection to AP 48:22:54:2f:9c:8f lost
12:16:50 PM kernel: wlp0s20f0u2: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:16:33 PM kernel: rtw_8822bu 1-2:1.0: timed out to flush queue 2
12:16:33 PM kernel: wlp0s20f0u2: deauthenticated from 48:22:54:2f:9c:8f (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
12:16:32 PM kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f0u2: link becomes ready
12:16:32 PM kernel: rtw_8822bu 1-2:1.0: failed to get tx report from firmware
12:16:31 PM kernel: wlp0s20f0u2: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:16:15 PM kernel: wlp59s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:16:14 PM kernel: wlp0s20f0u2: 48:22:54:2f:9c:8e denied authentication (status 37)
12:16:11 PM kernel: wlp59s0: 48:22:54:2f:9c:8e denied authentication (status 37)
12:07:51 PM kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
12:07:51 PM kernel: wlp59s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:03:34 PM kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f0u2: link becomes ready
12:03:33 PM kernel: rtw_8822bu 1-2:1.0: failed to get tx report from firmware
12:03:32 PM kernel: wlp0s20f0u2: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:03:23 PM kernel: wlp59s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
12:03:18 PM kernel: wlp0s20f0u2: 48:22:54:2f:9c:97 denied authentication (status 37)
12:03:15 PM kernel: rtw_8822bu 1-2:1.0: failed to get tx report from firmware
12:03:14 PM kernel: wlp0s20f0u2: 48:22:54:2f:9c:8e denied authentication (status 37)
12:03:12 PM kernel: wlp59s0: 48:22:54:2f:9c:da denied authentication (status 37)
11:34:32 AM kernel: warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
11:33:54 AM kernel: rfkill: input handler disabled
11:33:48 AM kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f0u2: link becomes ready
11:33:48 AM kernel: rfkill: input handler enabled
11:33:48 AM kernel: rtw_8822bu 1-2:1.0: failed to get tx report from firmware
11:33:47 AM systemd-journal: /var/log/journal/776696ecfcfe42c1bd7614fb4f8459c3/user-1000.journal: Monotonic clock jumped backwards relative to last journal entry, rotating.
11:33:47 AM kernel: rtw_8822bu 1-2:1.0: failed to get tx report from firmware
11:33:46 AM kernel: wlp0s20f0u2: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
11:33:45 AM kernel: wlp59s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 48:22:54:2f:9c:8f
11:33:45 AM kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
11:33:44 AM kernel: wlp59s0: associated
11:33:42 AM kernel: Bluetooth: RFCOMM ver 1.11
11:33:42 AM kernel: rfkill: input handler disabled
11:33:40 AM kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1

And here are my hardware logs

12:48:48 PM kernel: rtw_8822bu 1-2:1.0: failed to get tx report from firmware
11:33:40 AM kernel: iwlwifi 0000:3b:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0
11:33:40 AM kernel: nvidia 0000:01:00.0: enabling device (0000 -> 0003)
11:33:38 AM kernel: rtw_8822bu 1-2:1.0 wlp0s20f0u2: renamed from wlan0
11:33:38 AM kernel: iwlwifi 0000:3b:00.0 wlp59s0: renamed from wlan1
11:33:37 AM kernel: snd_hda_codec_realtek hdaudioC1D0:      Internal Mic=0x12
11:33:37 AM kernel: thermal thermal_zone13: failed to read out thermal zone (-61)
11:33:37 AM kernel: iwlwifi 0000:3b:00.0: Detected Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW), REV=0x340
11:33:37 AM kernel: iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
11:33:37 AM kernel: ee1004 10-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
11:33:37 AM kernel: rtw_8822bu 1-2:1.0: Firmware version 27.2.0, H2C version 13
11:33:37 AM kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
11:33:37 AM kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
11:33:37 AM kernel: iwlwifi 0000:3b:00.0: loaded firmware version 77.2df8986f.0 cc-a0-77.ucode op_mode iwlmvm
11:33:37 AM kernel: usb 1-12: Found UVC 1.00 device Integrated_Webcam_HD (0c45:6723)
11:33:37 AM kernel: iwlwifi 0000:3b:00.0: enabling device (0000 -> 0002)
11:33:37 AM kernel: i2c i2c-10: Successfully instantiated SPD at 0x50
11:33:37 AM kernel: i801_smbus 0000:00:1f.4: Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration
11:33:37 AM kernel: proc_thermal 0000:00:04.0: enabling device (0000 -> 0002)
11:33:37 AM kernel: mei_me 0000:00:16.0: enabling device (0000 -> 0002)
11:33:37 AM kernel: idma64 idma64.1: Found Intel integrated DMA 64-bit
11:33:37 AM kernel: intel-hid INT33D5:00: platform supports 5 button array
 5:33:34 AM kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
 5:33:34 AM kernel: rc rc0: DP-3 as /devices/pci0000:00/0000:00:02.0/rc/rc0
 5:33:32 AM kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
 5:33:32 AM kernel: usb 1-12: Manufacturer: CN09357G8LG00983A6J7A01
 5:33:32 AM kernel: hid-generic 0003:1532:0067.0008: input,hidraw7: USB HID v1.11 Keyboard [Razer Razer Naga Trinity] on usb-0000:00:14.0-1.3/input2
 5:33:32 AM kernel: usb 1-12: new high-speed USB device number 9 using xhci_hcd
 5:33:32 AM kernel: hid-multitouch 0018:06CB:7A13.0005: input,hidraw6: I2C HID v1.00 Mouse [SYNA2393:00 06CB:7A13] on i2c-SYNA2393:00
 5:33:32 AM kernel: hid-generic 0003:1532:0067.0007: input,hidraw5: USB HID v1.11 Keyboard [Razer Razer Naga Trinity] on usb-0000:00:14.0-1.3/input1
 5:33:32 AM kernel: nvme nvme0: 12/0/0 default/read/poll queues
 5:33:32 AM kernel: usb 1-1.3: SerialNumber: 00000000001A
 5:33:32 AM kernel: hid-generic 0018:06CB:7A13.0005: input,hidraw4: I2C HID v1.00 Mouse [SYNA2393:00 06CB:7A13] on i2c-SYNA2393:00
 5:33:32 AM kernel: usb 1-1.3: new full-speed USB device number 8 using xhci_hcd
 5:33:31 AM kernel: rtsx_pci 0000:3c:00.0: enabling device (0000 -> 0002)
 5:33:31 AM kernel: usb 1-7: SerialNumber: HTK32
 5:33:31 AM kernel: wmi_bus wmi_bus-PNP0C14:05: WQBC data block query control method not found
 5:33:31 AM kernel: usb 1-7: new full-speed USB device number 7 using xhci_hcd
 5:33:31 AM kernel: hid-generic 0003:0D8C:0005.0004: hidraw3: USB HID v1.11 Device [BLUE MICROPHONE Blue Snowball ] on usb-0000:00:14.0-1.2/input2
 5:33:31 AM kernel: usb 1-1.2: SerialNumber: AYM_2018/05/08_63389
 5:33:31 AM kernel: hid-generic 0003:1532:0221.0003: input,hidraw2: USB HID v1.11 Mouse [Razer Razer BlackWidow Chroma V2] on usb-0000:00:14.0-1.1/input2
 5:33:31 AM kernel: usb 1-4: new full-speed USB device number 5 using xhci_hcd
 5:33:31 AM kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x0, board id: 3125, fw id: 2378871
 5:33:31 AM kernel: hid-generic 0003:1532:0221.0001: input,hidraw0: USB HID v1.11 Keyboard [Razer Razer BlackWidow Chroma V2] on usb-0000:00:14.0-1.1/input0
 5:33:31 AM kernel: psmouse serio1: synaptics: Your touchpad (PNP: DLL0905 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org.
 5:33:31 AM kernel: usb 1-1.1: Manufacturer: Razer
 5:33:31 AM kernel: hub 1-1:1.0: 4 ports detected
 5:33:31 AM kernel: usb 1-1: Manufacturer: VIA Labs, Inc.         
 5:33:31 AM kernel: pci_bus 0000:01: hash matches
 5:33:31 AM kernel: intel_pmc_core INT33A1:00:  initialized
 5:33:31 AM kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram

Anyone with any suggestions/ideas? I’m a bit at a loss as to what is going on. On a side note, I recently dual booted Kali and I have the exact same issue in Kali. Makes me wonder if it’s something weird with my hardware or just straight up hardware failure.

1 Like
3

Forgot to mention I tried this solution a few days ago and it did not change anything. There was another post stating to name the file wifi-powersave-off.conf I tried both and neither worked.

1 Like
4

TP-Link 802.11ac NIC lists rtw_8822bu but also 88x2bu. The latter
was patched this year and tested on Fedora 38.

1 Like
5

I’m fairly confident this solved my issue. I’ve had no disconnects for the past hour. I usually get a disconnect every 20 minutes or so. Going to do some further testing before I mark this as the solution.

6

It is wise to test over a period of time to make sure it meets your needs. Maybe we should have a category such as “workaround” or “bodge” in addition to “solution”. I think a real solution requires a vendor to step up. Loading a driver ( rtw_8822bu) that fails is a bug.

7

I agree! If the driver is provided by the hardware vendor they should fix the bug. If the driver is only available as open source – reverse engineered – then there may often be problems. It would be a bug but the fix may not be available in a timely manner for OS drivers that are reverse engineered.

The more pressure that can be applied to the vendors to provide linux compatible drivers for their hardware the better our needs will be met. That is a win – win combo because the hardware mfgrs get more sales → more happy customers → more sales → etc.