[RTL8822BE] WiFi is unable to find surrounding networks, and keeps on loading

Recently, I have removed windows 10 from my system, and installed Fedora 39, instead. After installing has been done, my WiFi was working fine, and able to connect to my home network. But, once I started the initial upgrade. After that, the problem begins.

I’ve also tried the cold boot. In the login screen, for the very small moment it got connected to WiFi, and after 3 seconds or so, it got disconnected. And again, the same problem. it keeps on searching for networks, but unable to do so.

I’ve gone through with the fedora discussion, but didn’t find any helpful results.

I’m attaching a screenshot containing information of my WiFi driver.

P.S. I’m new to Fedora

Added wifi

Run the command lspci -nnk | grep -iE -A4 "ether|wifi|network" and post the result here as preformatted text using the </> button on the toolbar so we can see the details of that adapter.

I seem to remember that many may have had issues with that realtek adapter but we need more detailed info to be sure

1 Like

Do you have a way to use a wired network connection? Do you have another system where you can post text generated on the broken system, or are you limited to posting with a smartphone? It is helpful if you can avoid posting images as they don’t support text searches.

Note that when pasting text from a terminal the </> button will preserve the original formatting.

WiFi problems with new linux kernels are not unusual, so I find it important to have a USB WiFi dongle so I can download updates when the internal WiFi isn’t working. There also wifi devices that allow you to connect over wifi from an ethernet-only system.

It is good practice to include the output from running inxi -Fzxx in a terminal. This allows others with the hardware to find your post – they may be trying to solve teh same problem or may be able to offer a solution.

You should search for details of the issue using journalctl. Other forum posts have examples of journactl filters and resulting output. Another useful resource is the LHDB where you can search for probes of systems that have the same WiFi chip. Users sometimes add comments about problems and solutions with specific hardware.

1 Like
02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
	DeviceName: WLAN
	Subsystem: AzureWave Device [1a3b:2950]
	Kernel driver in use: rtw_8822be
	Kernel modules: rtw88_8822be

I’m currently using USB tethering as an alternative.

System:
  Kernel: 6.8.6-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-14.fc39
  Desktop: GNOME v: 45.5 tk: GTK v: 3.24.41 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 39 (Workstation Edition)
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X430FA_S430FA
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: X430FA v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: X430FA.308 date: 05/28/2019
Battery:
  ID-1: BAT0 charge: 21.3 Wh (63.8%) condition: 33.4/42.2 Wh (79.3%)
    volts: 11.6 min: 11.6 model: ASUSTeK ASUS Battery serial: N/A
    status: discharging
CPU:
  Info: quad core model: Intel Core i5-8265U bits: 64 type: MT MCP
    arch: Whiskey Lake rev: B cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 1100 high: 1801 min/max: 400/3900 cores: 1: 1801 2: 1800
    3: 400 4: 1800 5: 400 6: 1800 7: 400 8: 400 bogomips: 28800
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: HDMI-A-1
    bus-ID: 00:02.0 chip-ID: 8086:3ea0
  Device-2: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-6:2 chip-ID: 13d3:56c1
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.4
    compositor: gnome-shell driver: gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x07f7 res: 1920x1080 dpi: 158
    diag: 355mm (14")
  API: OpenGL v: 4.6 vendor: intel mesa v: 23.3.6 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel UHD Graphics 620 (WHL GT2)
    device-ID: 8086:3ea0 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Cannon Point-LP High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9dc8
  API: ALSA v: k6.8.6-200.fc39.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: AzureWave
    driver: rtw_8822be v: N/A pcie: speed: Unknown lanes: 63 port: 3000
    bus-ID: 02:00.0 chip-ID: 10ec:b822
  IF: wlo1 state: down mac: <filter>
  IF-ID-1: enp0s20f0u2 state: unknown speed: -1 duplex: half mac: <filter>
Bluetooth:
  Device-1: Google Nexus/Pixel Device (tether) driver: rndis_host v: kernel
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-2:5 chip-ID: 18d1:4ee3
  Device-2: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-8:3 chip-ID: 13d3:3526
  Report: ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2 lmp-v: 8
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 bus-ID: 00:17.0 chip-ID: 8086:282a
Drives:
  Local Storage: total: 931.51 GiB used: 226.42 GiB (24.3%)
  ID-1: /dev/sda vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB
    speed: 6.0 Gb/s serial: <filter> temp: 31 C
Partition:
  ID-1: / size: 929.93 GiB used: 226.11 GiB (24.3%) fs: btrfs dev: /dev/sda3
  ID-2: /boot size: 973.4 MiB used: 306.5 MiB (31.5%) fs: ext4
    dev: /dev/sda2
  ID-3: /boot/efi size: 598.8 MiB used: 19 MiB (3.2%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 929.93 GiB used: 226.11 GiB (24.3%) fs: btrfs
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: zram size: 7.6 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 43.0 C pch: 41.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 0
Info:
  Memory: total: 8 GiB available: 7.6 GiB used: 1.76 GiB (23.1%)
  Processes: 310 Power: uptime: 8m wakeups: 0 Init: systemd v: 254
    target: graphical (5) default: graphical
  Packages: Compilers: gcc: 13.2.1 Shell: Bash v: 5.2.26
    running-in: gnome-terminal inxi: 3.3.33

I do have external wifi adapter but it also not working.

Good internet access is important to get software updates (which may solve your wifi issue) as well as to participate in this forum. You may want to investigate the external adapter issue in the hope you can at least get one working right away.

It would be good to have the full output from running inxi -Fzxx in a terminal as it may help others with the same hardware find this thread. The next step is to gather details related to wifi using the journalctl program in a terminal. Use man journalctl to get explanations for the following suggested “incantations”:

  • journalctl --no-hostname -b -p 3 |cat to select “log level” 0-3 messages and get wrapped lines suitable for forum posts

  • journalctl --no-hostname -b -g rtw88

  • journalctl --no-hostname -b -p 4 -g wifi

anmolkumar@fedora:~$ journalctl --no-hostname -b -p 3 |cat
Apr 22 17:38:37 kernel: x86/cpu: SGX disabled by BIOS.
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS07._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS07._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS08._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS08._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS09._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS09._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS10._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS10._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.USR1._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.USR1._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.USR2._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.USR2._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS01._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS01._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS02._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS02._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS03._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS03._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS04._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS04._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS05._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS05._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS06._UPC], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS06._PLD], AE_ALREADY_EXISTS (20230628/dswload2-326)
Apr 22 17:38:37 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220)
Apr 22 17:38:37 systemd-vconsole-setup[291]: /usr/bin/setfont failed with exit status 71.
Apr 22 17:38:38 systemd-vconsole-setup[474]: /usr/bin/setfont failed with exit status 71.
Apr 22 17:38:38 kernel: i2c_hid_acpi i2c-ELAN1300:00: device returned incorrect report (2 vs 14 expected)
Apr 22 12:08:55 bluetoothd[921]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Apr 22 12:08:55 bluetoothd[921]: Failed to clear UUIDs: Failed (0x03)
Apr 22 12:08:55 bluetoothd[921]: Failed to add UUID: Failed (0x03)
Apr 22 12:08:55 bluetoothd[921]: Failed to add UUID: Failed (0x03)
Apr 22 12:08:55 bluetoothd[921]: Failed to add UUID: Failed (0x03)
Apr 22 12:09:06 thermald[937]: Unsupported condition 50 (User_presence)
Apr 22 12:09:06 thermald[937]: Unsupported conditions are present
Apr 22 12:09:18 kernel: rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
Apr 22 12:09:18 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:18 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:18 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:18 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:18 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:24 abrt-notification[1303]: System encountered a non-fatal error in rtw_dbi_read8()
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:25 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:27 abrt-notification[1341]: System encountered a non-fatal error in rtw_dbi_read8()
Apr 22 12:09:27 kernel: rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
Apr 22 12:09:27 kernel: rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
Apr 22 12:09:27 kernel: rtw_8822be 0000:02:00.0: failed to read ASPM, ret=-5
Apr 22 12:09:28 abrt-notification[1352]: System encountered a non-fatal error in rtw_dbi_read8()
Apr 22 12:09:29 kernel: rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
Apr 22 12:09:29 kernel: rtw_8822be 0000:02:00.0: mac power on failed
Apr 22 12:09:29 kernel: rtw_8822be 0000:02:00.0: failed to power on mac
Apr 22 12:09:29 kernel: rtw_8822be 0000:02:00.0: leave idle state failed
Apr 22 12:09:29 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:29 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:29 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:29 kernel: rtw_8822be 0000:02:00.0: failed to leave ips state
Apr 22 12:09:29 kernel: rtw_8822be 0000:02:00.0: failed to leave idle state
Apr 22 12:09:30 abrt-notification[1371]: System encountered a non-fatal error in rtw_dbi_read8()
Apr 22 12:09:31 abrt-notification[1380]: System encountered a non-fatal error in rtw_dbi_read8()
Apr 22 12:09:35 kernel: rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
Apr 22 12:09:35 kernel: rtw_8822be 0000:02:00.0: mac power on failed
Apr 22 12:09:35 kernel: rtw_8822be 0000:02:00.0: failed to power on mac
Apr 22 12:09:35 kernel: rtw_8822be 0000:02:00.0: leave idle state failed
Apr 22 12:09:35 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:35 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:35 kernel: rtw_8822be 0000:02:00.0: failed to send h2c command
Apr 22 12:09:35 kernel: rtw_8822be 0000:02:00.0: failed to leave ips state
Apr 22 12:09:35 kernel: rtw_8822be 0000:02:00.0: failed to leave idle state
Apr 22 12:09:44 kernel: rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
Apr 22 12:09:46 kernel: rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
Apr 22 12:09:46 kernel: rtw_8822be 0000:02:00.0: mac power on failed
Apr 22 12:09:46 kernel: rtw_8822be 0000:02:00.0: failed to power on mac
Apr 22 12:12:53 gdm-password][1970]: gkr-pam: unable to locate daemon control file
Apr 22 12:12:56 systemd[1996]: Failed to start app-gnome-xdg\x2duser\x2ddirs-2250.scope - Application launched by gnome-session-binary.
Apr 22 12:12:58 systemd[1996]: Failed to start app-gnome-spice\x2dvdagent-2431.scope - Application launched by gnome-session-binary.
Apr 22 12:16:40 kernel: rtw_8822be 0000:02:00.0: failed to poll offset=0x5 mask=0x2 value=0x0
Apr 22 12:16:40 kernel: rtw_8822be 0000:02:00.0: mac power on failed
Apr 22 12:16:40 kernel: rtw_8822be 0000:02:00.0: failed to power on mac
anmolkumar@fedora:~$ journalctl --no-hostname -b -g rtw88
Apr 22 12:09:18 kernel: WARNING: CPU: 6 PID: 678 at drivers/net/wireless/realte>
Apr 22 12:09:18 kernel: Modules linked in: nf_conntrack_netbios_ns nf_conntrack>
Apr 22 12:09:18 kernel: Workqueue: phy0 rtw_watch_dog_work [rtw88_core]
Apr 22 12:09:18 kernel: RIP: 0010:rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pc>
Apr 22 12:09:18 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:18 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:18 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:18 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:18 kernel:  rtw_pci_link_ps.part.0+0x8b/0x100 [rtw88_pci]
Apr 22 12:09:18 kernel:  rtw_leave_lps+0x83/0x190 [rtw88_core]
Apr 22 12:09:18 kernel:  rtw_watch_dog_work+0x1d4/0x260 [rtw88_core]
Apr 22 12:09:25 kernel: WARNING: CPU: 7 PID: 678 at drivers/net/wireless/realte>
Apr 22 12:09:25 kernel: Modules linked in: nf_conntrack_netbios_ns nf_conntrack>
Apr 22 12:09:25 kernel: Workqueue: phy0 rtw_watch_dog_work [rtw88_core]
Apr 22 12:09:25 kernel: RIP: 0010:rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pc>
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  rtw_pci_link_ps.part.0+0x8b/0x100 [rtw88_pci]
Apr 22 12:09:25 kernel:  rtw_enter_lps+0x78/0xf0 [rtw88_core]
Apr 22 12:09:25 kernel:  rtw_watch_dog_work+0x228/0x260 [rtw88_core]
Apr 22 12:09:25 kernel: WARNING: CPU: 7 PID: 678 at drivers/net/wireless/realte>
Apr 22 12:09:25 kernel: Modules linked in: nf_conntrack_netbios_ns nf_conntrack>
Apr 22 12:09:25 kernel: Workqueue: phy0 rtw_watch_dog_work [rtw88_core]
Apr 22 12:09:25 kernel: RIP: 0010:rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pc>
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  rtw_pci_link_ps.part.0+0x8b/0x100 [rtw88_pci]
Apr 22 12:09:25 kernel:  rtw_leave_lps+0x83/0x190 [rtw88_core]
Apr 22 12:09:25 kernel:  rtw_watch_dog_work+0x1d4/0x260 [rtw88_core]
Apr 22 12:09:25 kernel: WARNING: CPU: 7 PID: 678 at drivers/net/wireless/realte>
Apr 22 12:09:25 kernel: Modules linked in: nf_conntrack_netbios_ns nf_conntrack>
Apr 22 12:09:25 kernel: Workqueue: phy0 rtw_watch_dog_work [rtw88_core]
Apr 22 12:09:25 kernel: RIP: 0010:rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pc>
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  rtw_pci_link_ps.part.0+0x8b/0x100 [rtw88_pci]
Apr 22 12:09:25 kernel:  rtw_enter_lps+0x78/0xf0 [rtw88_core]
Apr 22 12:09:25 kernel:  rtw_watch_dog_work+0x228/0x260 [rtw88_core]
Apr 22 12:09:25 kernel: WARNING: CPU: 4 PID: 581 at drivers/net/wireless/realte>
Apr 22 12:09:25 kernel: Modules linked in: nf_conntrack_netbios_ns nf_conntrack>
Apr 22 12:09:25 kernel: RIP: 0010:rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pc>
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:25 kernel:  rtw_pci_link_ps.part.0+0x8b/0x100 [rtw88_pci]
Apr 22 12:09:25 kernel:  rtw_leave_lps+0x83/0x190 [rtw88_core]
Apr 22 12:09:25 kernel:  rtw_recalc_lps+0x7c/0xc0 [rtw88_core]
Apr 22 12:09:25 kernel:  rtw_ops_bss_info_changed+0x1f5/0x2c0 [rtw88_core]
Apr 22 12:09:27 kernel: WARNING: CPU: 5 PID: 581 at drivers/net/wireless/realte>
Apr 22 12:09:27 kernel: Modules linked in: nf_conntrack_netbios_ns nf_conntrack>
Apr 22 12:09:27 kernel: RIP: 0010:rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pc>
Apr 22 12:09:27 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:27 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:27 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:27 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:27 kernel:  rtw_pci_link_ps.part.0+0x8b/0x100 [rtw88_pci]
Apr 22 12:09:27 kernel:  rtw_enter_ips+0x43/0x50 [rtw88_core]
Apr 22 12:09:27 kernel:  rtw_ops_config+0xa8/0xd0 [rtw88_core]
Apr 22 12:09:27 kernel: WARNING: CPU: 1 PID: 1113 at drivers/net/wireless/realt>
Apr 22 12:09:27 kernel: Modules linked in: nf_conntrack_netbios_ns nf_conntrack>
Apr 22 12:09:27 kernel: RIP: 0010:rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pc>
Apr 22 12:09:27 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:27 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:27 kernel:  ? rtw_dbi_read8.constprop.0+0xa4/0xc0 [rtw88_pci]
Apr 22 12:09:27 kernel:  rtw_pci_link_ps.part.0+0x8b/0x100 [rtw88_pci]
Apr 22 12:09:27 kernel:  rtw_leave_ips+0x2c/0xc0 [rtw88_core]
Apr 22 12:09:27 kernel:  rtw_ops_config+0x8b/0xd0 [rtw88_core]

anmolkumar@fedora:~$ journalctl --no-hostname -b -p 4 -g wifi
Apr 22 12:13:24 geoclue[2670]: Failed to query location: No WiFi networks found
Apr 22 12:14:37 geoclue[2670]: WiFi scan failed
Apr 22 12:16:40 geoclue[2670]: WiFi scan failed
Apr 22 12:16:41 geoclue[2670]: WiFi scan failed
Apr 22 12:16:45 geoclue[2670]: WiFi scan failed
Apr 22 12:16:50 geoclue[2670]: WiFi scan failed
Apr 22 12:16:57 geoclue[2670]: WiFi scan failed
Apr 22 12:17:07 geoclue[2670]: WiFi scan failed
Apr 22 12:17:21 geoclue[2670]: WiFi scan failed
Apr 22 12:17:41 geoclue[2670]: WiFi scan failed
Apr 22 12:18:10 geoclue[2670]: WiFi scan failed
Apr 22 12:18:53 geoclue[2670]: WiFi scan failed
Apr 22 12:19:57 geoclue[2670]: WiFi scan failed
Apr 22 12:21:32 geoclue[2670]: WiFi scan failed
Apr 22 12:23:35 geoclue[2670]: WiFi scan failed
Apr 22 12:23:36 geoclue[2670]: WiFi scan failed
Apr 22 12:23:40 geoclue[2670]: WiFi scan failed
Apr 22 12:23:45 geoclue[2670]: WiFi scan failed
Apr 22 12:23:52 geoclue[2670]: WiFi scan failed
Apr 22 12:24:02 geoclue[2670]: WiFi scan failed
Apr 22 12:24:16 geoclue[2670]: WiFi scan failed
Apr 22 12:24:36 geoclue[2670]: WiFi scan failed

The issues suggest your BIOS is outdated.

You appear to be using BIOS American Megatrends v: X430FA.308 date: 05/28/2019, but ASUS has BIOS Update for Windows Version 309 7.05 MB 2021/02/02. You can try fwupdtool --get-updates to see if the BIOS update is can be done with Fedora. If you don’t dual boot Windows there are workarounds, but some internet research will be needed. With luck, another user will have found a workaround for your model.

1 Like

I’ve checked for the BIOS updates, but unfortunately, there is no update available. And you’re right I haven’t dual booted Windows.

I would create a new thread with a title like “ASUS (AMI Megatrends) BIOS updates without Windows” so someone who has done this will respond. If that doesn’t get a response, there have been workarounds posted on the web. I recall one that used a Windows limited-time license installed on an external drive with lots of detail for the dozens of steps needed.

1 Like

Will the dnf update is not enough to resolve this issue?

Also, am I the only one getting this WiFi issue?

If lots of people were having the problem there would be a bunch of “me too” posts. WiFi issues with a new linux kernel are not unusual, so it is useful t have an alternative internet connection (tethered phone, wired network, or US dongle).

You would have a better chance of a response if you had mentioned your hardware in the title.

I do have alternate to connect to the internet, but it’s kind of annoying to rely on the usb/bluetooth tethering.

Do you think upgrading kernel could be the cause of this WiFi malfunction?

Because when I install fedora on my device, WiFi is working fine, but when I upgraded the packages, kernal also got upgraded. That’s when the WiFi issue begins.

Hardware drivers are implemented as kernel modules, so kernel upgrade is a common cause for hardware related issues, often affecting some models of Wi-Fi adapters.

You can also try downgrading the kernel or upgrading to Fedora 40 if the problem persists.

Fedora 40 is not a stable release as far as I know, do you still want me to upgrade to the beta release?

With the current threat environment, stability is only available to systems that are turned off. Fedora 40 is officially released, which means known issues have been triaged and those remaining are not considered serious enough to warrant a delay. Fedora is a community project, so relies heavily on user experience to find issues. If you have ways to maintain internet access with broken wifi, you are better off upgrading. If the issue remains, provide details needed understand it. Someone may already have a solutiion, or you may need to prepare a bug report (which will be more likely to get attention if the issue affects the current release).

2 Likes

Announcing Fedora Linux 40

1 Like