[SOLVED] AX210 cannot connect wifi normally

KafCoppelia · 2022-07-14 08:42:34

My situation maybe a litte tortuous. I switched RTL8852BE to AX210 because the driver of RTL8852BE has worked abnormally since kernel 5.17. I think.

But AX210 cannot connect wifi succeeded with networkmanager.

                   -`                    username@username-arch 
                  .o+`                   ---------------------------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: 21CX ThinkBook 14 G4+ IAP 
               `+oooooo:                 Kernel: 5.18.11-arch1-1 
               -+oooooo+:                Uptime: 1 hour, 18 mins 
             `/:-:++oooo+:               Packages: 1345 (pacman) 
            `/++++/+++++++:              Shell: bash 5.1.16 
           `/++++++++++++++:             Resolution: 1920x1080 
          `/+++ooooooooooooo/`           DE: Plasma 5.25.3 
         ./ooosssso++osssssso+`          WM: kwin 
        .oossssso-````/ossssss+`         WM Theme: Breeze 微风 
       -osssssso.      :ssssssso.        Theme: [Plasma], Breeze [GTK2/3] 
      :osssssss/        osssso+++.       Icons: [Plasma], breeze-dark [GTK2/3] 
     /ossssssss/        +ssssooo/-       Terminal: konsole 
   `/ossssso+/:-        -:/+osssso+-     CPU: 12th Gen Intel i7-12700H (20) @ 4.600GHz 
  `+sso+:-`                 `.-/+oso:    GPU: Intel Alder Lake-P 
 `++:.                           `-/+/   Memory: 5421MiB / 31827MiB 
 .`                                 `/

There is a wifi icon, but when I try to connect to wifi, it get stuck in "waiting for verification". When using RTL8852BE the problem is the same, so I bought AX210. However, I can get connection by "nmtui", but that's really inconvenient. Besides, using this method, I don't feel the speed of wifi is so-called WIFI6(or 6E) event my family router is WIFI6 supported.

journalctl -b | grep iwlwifi:

7月 14 15:15:27 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: enabling device (0000 -> 0002)
7月 14 15:15:27 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-72.ucode failed with error -2
7月 14 15:15:27 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: api flags index 2 larger than supported by driver
7月 14 15:15:27 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
7月 14 15:15:27 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: loaded firmware version 71.058653f6.0 ty-a0-gf-a0-71.ucode op_mode iwlmvm
7月 14 15:15:27 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
7月 14 15:15:27 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: loaded PNVM version 881c99e1
7月 14 15:15:27 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: Detected RF GF, rfid=0x10d000
7月 14 15:15:27 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: base HW address: a0:80:69:f5:8c:ff
7月 14 15:15:27 kafcoppelia-arch kernel: WARNING: CPU: 8 PID: 706 at drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c:711 iwl_init_he_hw_capab+0x372/0x390 [iwlwifi]
7月 14 15:15:27 kafcoppelia-arch kernel: Modules linked in: snd_sof_pci_intel_tgl snd_sof_intel_hda_common nft_fib_inet soundwire_intel nft_fib_ipv4 nft_fib_ipv6 soundwire_generic_allocation nft_fib soundwire_cadence snd_sof_intel_hda snd_sof_pci nft_reject_inet snd_sof_xtensa_dsp nf_reject_ipv4 snd_sof nf_reject_ipv6 snd_sof_utils nft_reject snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus ledtrig_audio snd_soc_core snd_compress nft_ct iwlmvm(+) ac97_bus snd_pcm_dmaengine snd_hda_intel mac80211 snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec libarc4 nft_chain_nat snd_hda_core snd_hwdep iwlwifi snd_pcm snd_timer e1000e(+) iwlmei snd spi_intel_pci i2c_i801 spi_intel i2c_smbus soundcore cfg80211 nf_tables ip6table_nat mei_me intel_lpss_pci mei ip6table_mangle intel_lpss idma64 ip6table_raw intel_ish_ipc(+) intel_ishtp i915(+) thunderbolt ip6table_security iptable_nat nf_nat intel_vsec nf_conntrack drm_buddy processor_thermal_device_pci processor_thermal_device ttm
7月 14 15:15:27 kafcoppelia-arch kernel: RIP: 0010:iwl_init_he_hw_capab+0x372/0x390 [iwlwifi]
7月 14 15:15:27 kafcoppelia-arch kernel:  iwl_init_sbands+0x674/0x6e0 [iwlwifi 2c850c2e8aa647011f0d966be785676beccc08ed]
7月 14 15:15:27 kafcoppelia-arch kernel:  iwl_get_nvm+0x24e/0x2c0 [iwlwifi 2c850c2e8aa647011f0d966be785676beccc08ed]
7月 14 15:15:27 kafcoppelia-arch kernel:  ? iwl_read32+0x20/0x80 [iwlwifi 2c850c2e8aa647011f0d966be785676beccc08ed]
7月 14 15:15:27 kafcoppelia-arch kernel:  _iwl_op_mode_start+0x98/0xc0 [iwlwifi 2c850c2e8aa647011f0d966be785676beccc08ed]
7月 14 15:15:27 kafcoppelia-arch kernel:  iwl_opmode_register+0x6c/0xe0 [iwlwifi 2c850c2e8aa647011f0d966be785676beccc08ed]
7月 14 15:15:32 kafcoppelia-arch NetworkManager[530]: <info>  [1657782932.0117] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:2c:00.0/ieee80211/phy0/rfkill2) (driver iwlwifi)

Maybe there is a problem:

Direct firmware load for iwlwifi-ty-a0-gf-a0-72.ucode failed with error -2

lspci -k:

2c:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a)
        Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

rfkill:

ID TYPE      DEVICE                 SOFT      HARD
 0 wlan      ideapad_wlan      unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan      phy0              unblocked unblocked
 3 bluetooth hci0              unblocked unblocked

If you need more info just tell me, I will get it ASAP

Last edited by KafCoppelia (2022-08-10 03:53:51)

seth · 2022-07-14 15:20:11

7月 14 15:15:27 kafcoppelia-arch kernel: RIP: 0010:iwl_init_he_hw_capab+0x372/0x390 [iwlwifi]

iwlwifi.disable_11ax=true

https://wiki.archlinux.org/title/Kernel_parameters

KafCoppelia · 2022-07-14 16:07:09

seth wrote:

7月 14 15:15:27 kafcoppelia-arch kernel: RIP: 0010:iwl_init_he_hw_capab+0x372/0x390 [iwlwifi]

iwlwifi.disable_11ax=true

https://wiki.archlinux.org/title/Kernel_parameters

Thank you for your reply. I did so, then rebooted.

journalctl -b | grep iwlwifi:

7月 14 23:56:20 kafcoppelia-arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=747991bf-f24a-4e35-9315-1706bc8b5f93 rw loglevel=3 quiet splash i915.enable_psr=0 ibt=off iwlwifi.disable_11ax=true
7月 14 23:56:20 kafcoppelia-arch kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=747991bf-f24a-4e35-9315-1706bc8b5f93 rw loglevel=3 quiet splash i915.enable_psr=0 ibt=off iwlwifi.disable_11ax=true
7月 14 23:56:22 kafcoppelia-arch kernel: iwlwifi: `true' invalid for parameter `disable_11ax'

Wifi died.

seth · 2022-07-14 16:14:06

7月 14 23:56:22 kafcoppelia-arch kernel: iwlwifi: `true' invalid for parameter `disable_11ax'

Try "iwlwifi.disable_11ax=1"

KafCoppelia · 2022-07-14 16:55:42

seth wrote:

7月 14 23:56:22 kafcoppelia-arch kernel: iwlwifi: `true' invalid for parameter `disable_11ax'

Try "iwlwifi.disable_11ax=1"

Problem stays the same:

7月 15 00:33:20 kafcoppelia-arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=747991bf-f24a-4e35-9315-1706bc8b5f93 rw loglevel=3 quiet splash i915.enable_psr=0 ibt=off iwlwifi.disable_11ax=1
7月 15 00:33:20 kafcoppelia-arch kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=747991bf-f24a-4e35-9315-1706bc8b5f93 rw loglevel=3 quiet splash i915.enable_psr=0 ibt=off iwlwifi.disable_11ax=1
7月 15 00:33:22 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: enabling device (0000 -> 0002)
7月 15 00:33:22 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-72.ucode failed with error -2
7月 15 00:33:22 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: api flags index 2 larger than supported by driver
7月 15 00:33:22 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
7月 15 00:33:22 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: loaded firmware version 71.058653f6.0 ty-a0-gf-a0-71.ucode op_mode iwlmvm
7月 15 00:33:22 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
7月 15 00:33:22 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: loaded PNVM version 881c99e1
7月 15 00:33:22 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: Detected RF GF, rfid=0x10d000
7月 15 00:33:22 kafcoppelia-arch kernel: iwlwifi 0000:2c:00.0: base HW address: a0:80:69:f5:8c:ff
7月 15 00:33:27 kafcoppelia-arch NetworkManager[517]: <info>  [1657816407.0419] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:2c:00.0/ieee80211/phy0/rfkill2) (driver iwlwifi)

It pop a prompt finally when connection failed, which says "cannot get password from my-wifi-ssid". But that's occasional I cannot catch it now.

seth · 2022-07-14 19:13:03

The previous warning is gone, though.
Please post the complete system journal, not some random excerpt

sudo journalctl -b | curl -F 'file=@-' 0x0.st

KafCoppelia · 2022-07-15 03:49:22

Complete journal is here

seth · 2022-07-15 06:49:59

7月 15 11:38:37 kafcoppelia-arch NetworkManager[516]: <warn>  [1657856317.0447] device (wlan0): no secrets: No agents were available for this request.
7月 15 11:38:37 kafcoppelia-arch NetworkManager[516]: <info>  [1657856317.0447] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
7月 15 11:38:37 kafcoppelia-arch NetworkManager[516]: <info>  [1657856317.0470] device (wlan0): set-hw-addr: set MAC address to F6:49:8D:BB:58:E0 (scanning)
7月 15 11:38:37 kafcoppelia-arch NetworkManager[516]: <warn>  [1657856317.0505] device (wlan0): Activation: failed for connection 'cfpzr'

Though the polkit-kde-authentication-agent-1 seems to be running:

7月 15 11:36:37 kafcoppelia-arch polkit-kde-authentication-agent-1[1116]: New PolkitAgentListener  0x7f026c003da0
7月 15 11:36:37 kafcoppelia-arch polkit-kde-authentication-agent-1[1116]: Adding new listener  PolkitQt1::Agent::Listener(0x558fb0784910) for  0x7f026c003da0
7月 15 11:36:37 kafcoppelia-arch polkit-kde-authentication-agent-1[1116]: Listener online
7月 15 11:36:37 kafcoppelia-arch polkitd[713]: Registered Authentication Agent for unix-session:2 (system bus name :1.35 [/usr/lib/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale zh_CN.UTF-8)
7月 15 11:36:37 kafcoppelia-arch polkit-kde-authentication-agent-1[1116]: Authentication agent result: true

There're no further errors - do you simply miss the password input dialog?
Maybe this is a wayland issue (failing you to show the password input), there's also

7月 15 11:38:38 kafcoppelia-arch blueman-tray[1356]: Unable to connect to the Notification Watcher: 已到超时限制
7月 15 11:38:38 kafcoppelia-arch blueman-tray[1356]: Unable to connect to the Notification Watcher: 已到超时限制
7月 15 11:38:38 kafcoppelia-arch blueman-tray[1356]: Unable to connect to the Notification Watcher: 已到超时限制

=> Try KDE on X11

KafCoppelia · 2022-07-16 03:35:50

Sorry for my late reply. Yesterday was a busy Friday(UTC+8).

There're no further errors - do you simply miss the password input dialog?

I don't think password input dialog is the problem. I can delete the wifi which I'm trying to connect, and connect it from the password input dialog.But the result is the same, stuck in "waiting for verification" then failed(but without any prompt, just failed in silence)

And, how can I switch Wayland to X11.I'm using XWayland perhaps. I only see Wayland when I login. Any wiki I can follow?

seth · 2022-07-16 07:30:04

Just select the X11 session on the SDDM greeter when logging in?

KafCoppelia · 2022-07-16 11:55:35

seth wrote:

Just select the X11 session on the SDDM greeter when logging in?

Oh I see it. But unfortunately, when I using plasma x11, the whole desktop is working abnormally, screen flickering, wrong zoom rate of layout. My mouse cannot operate smoothly. Anyway, that is another problem.

Today in plasma wayland, when trying to connect wifi, it gave me this feedback: (which I mentioned before)

Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Last edited by KafCoppelia (2022-07-16 11:56:22)

seth · 2022-07-16 14:30:38

Possible causes include:
- the remote application did not send a reply
- the message bus security policy blocked the reply
- the reply timeout expired, or
- the network connection was broken.

There seems some issue w/ your session dbus - or the polkit agent or whatever.
Can you connect w/ nmcli?
https://wiki.archlinux.org/title/Networ … i_examples

KafCoppelia · 2022-07-16 14:51:58

Can you connect w/ nmcli

Yes, I can connect to wifi by nmtui or nmcli (I tried it after you mentioned), but both need me forget/delete the wifi then I start a fresh connection.

The speed of wifi connected by this method, is less than 5MiB/s. I don't think it's WIFI6 speed.

Last edited by KafCoppelia (2022-07-16 14:53:20)

seth · 2022-07-16 15:02:16

That has nothing to do w/ the "method" - if the KDE GUI wouldn't fail to talk to NM, NM would get you the same connection.
You had to

iwlwifi.disable_11ax=true

=> https://wiki.archlinux.org/title/Networ … _interface to see the actual connection.

KafCoppelia · 2022-07-16 16:46:12

seth wrote:

That has nothing to do w/ the "method" - if the KDE GUI wouldn't fail to talk to NM, NM would get you the same connection.
You had to
iwlwifi.disable_11ax=true
=> https://wiki.archlinux.org/title/Networ … _interface to see the actual connection.

It worked but partially.

I've already changed the kernel parameters, and now it still is:

iwlwifi.disable_11ax=1

Using nmcli can scan wifi and connect to wifi. Then I "ip link set wlan0 up" (section of "Activate the interface" in wiki you mentioned). From this time, I can disconnect/connect to wlan0 smoothly and fast, even I rebooted. Unsure about long-term stability.

But it failed again when I connect to new hotspot(or new wifi) at the first time, from the icon wifi lower right corner of the desktop, instead of using nmcli.

I don't know whether it was connecting to a wifi by nmcli at first time or "ip link set wlan0 up" for a wifi works.

Here are some information about wlan0 or AX210:

iw dev:

phy#0
        Unnamed/non-netdev interface
                wdev 0x2
                addr a0:80:69:f5:8c:ff
                type P2P-device
                txpower 0.00 dBm
        Interface wlan0
                ifindex 2
                wdev 0x1
                addr a0:80:69:f5:8c:ff
                ssid cfpzr
                type managed
                channel 157 (5785 MHz), width: 80 MHz, center1: 5775 MHz
                txpower 22.00 dBm
                multicast TXQ:
                        qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes tx-packets
                        0       0       0       0       0       0       0       0        0

iw dev wlan0 link:

Connected to c0:b1:01:24:fa:2d (on wlan0)
        SSID: cfpzr
        freq: 5785
        RX: 143640 bytes (617 packets)
        TX: 126108 bytes (788 packets)
        signal: -51 dBm
        rx bitrate: 780.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 2
        tx bitrate: 234.0 MBit/s VHT-MCS 3 80MHz VHT-NSS 2

        bss flags:      short-preamble short-slot-time
        dtim period:    1
        beacon int:     100

Last edited by KafCoppelia (2022-07-16 16:49:51)

KafCoppelia · 2022-07-16 17:02:48

Also when connect to wlan0 successfully, the settings of "All users can connect to this wifi" and "Save password for all users(unencrypted)"(this two were translated from Chinese) should keep still. Otherwise next time I connect to wlan0, it will stuck in "waiting for verification" again.

Is it possible that kwallet is related?

Last edited by KafCoppelia (2022-07-16 17:03:17)

V1del · 2022-07-16 18:22:16

Possible. plasma-nm relies on it for storing the secret if you don't use the mentioned options. Did you disable it?

seth · 2022-07-16 19:09:57

The speed of wifi … is less than 5MiB/s

rx bitrate: 780.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 2
tx bitrate: 234.0 MBit/s VHT-MCS 3 80MHz VHT-NSS 2

How exactly did you measure that?

KafCoppelia · 2022-07-17 06:34:21

V1del wrote:

Possible. plasma-nm relies on it for storing the secret if you don't use the mentioned options. Did you disable it?

I don't disable kwallet. I use kwallet to store my passwords of chrome, github...

KafCoppelia · 2022-07-17 06:39:22

seth wrote:

The speed of wifi … is less than 5MiB/s
rx bitrate: 780.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 2
tx bitrate: 234.0 MBit/s VHT-MCS 3 80MHz VHT-NSS 2
How exactly did you measure that?

My judgment of wifi speed is based on my feelings when watching youtube, streaming, not exact measurement. If the speed doesn't affect my experience of daily use(downloading movies, youtube, streaming...), it dosen't matter actually. But AX210 has to be worth what I cost.

But I suspect we have not got the crux of the problem. Maybe it's a symptoms of another problem...

Last edited by KafCoppelia (2022-07-17 06:40:27)

seth · 2022-07-17 06:52:30

My judgment of wifi speed is based on my feelings

I'm gonna break a forum rule for this.
il_570xN.701495995_em32.jpg

How about basing it on, i don't know, metric facts?
https://bbs.archlinux.org/viewtopic.php … 6#p2017886

KafCoppelia · 2022-07-17 07:13:04

Fine. I used speedtest to test my wifi speed. Here is the result:

     Server: 湖南电信5G - Changsha (id = 28225)
        ISP: China Telecom
    Latency:     9.19 ms   (0.77 ms jitter)
   Download:    86.37 Mbps (data used: 87.6 MB )                               
     Upload:    34.81 Mbps (data used: 55.1 MB )                               
Packet Loss:     0.0%
 Result URL: https://www.speedtest.net/result/c/353f2937-b28a-4ad1-b5f8-036f04e05d36

seth · 2022-07-17 08:28:47

I'd rather test a gigabyte traffic and make sure to avoid sideload from browsers etc, for reliable results and while idk what you can expect from your ISP (you could alo run a local iperf test) that's considerably more than 5Mpbs and enough to stream 4k h264 @60fps.

Do you get different results when plugging an rj45 into the router?

KafCoppelia · 2022-07-17 12:15:08

Speedtest with rj45 only:

     Server: 湖南电信5G - Changsha (id = 28225)
        ISP: China Telecom
    Latency:    13.52 ms   (0.28 ms jitter)
   Download:   120.47 Mbps (data used: 124.9 MB )                               
     Upload:    34.95 Mbps (data used: 56.4 MB )                               
Packet Loss:     0.0%
 Result URL: https://www.speedtest.net/result/c/09c6d5ed-1b8d-4372-ac4c-76882011c7d0

seth · 2022-07-17 12:40:51

For a single test, the difference isn't significant (esp. the upload is rather static) and can be down to "uncontrolled environment" (other network processes) and "that's not enough data to draw a good average"
Also it's both way below the actual traffic measured on the WIFI NIC and I don't think that's the limiting factor here at all.

If you want to measure the WiFi performance by itself (w/o your ISPs bandwidth becoming a limiting factor), you'll need two LAN hosts and https://wiki.archlinux.org/title/Benchmarking#iperf

1. What do you expect from your ISP
2. Did you try the linode tests (more traffic data gets you a less variable result)
3. Does the rj45 connection fare better wrt. youtube?

Arch Linux

#1 2022-07-14 08:42:34

[SOLVED] AX210 cannot connect wifi normally

#2 2022-07-14 15:20:11

Re: [SOLVED] AX210 cannot connect wifi normally

#3 2022-07-14 16:07:09

Re: [SOLVED] AX210 cannot connect wifi normally

#4 2022-07-14 16:14:06

Re: [SOLVED] AX210 cannot connect wifi normally

#5 2022-07-14 16:55:42

Re: [SOLVED] AX210 cannot connect wifi normally

#6 2022-07-14 19:13:03

Re: [SOLVED] AX210 cannot connect wifi normally

#7 2022-07-15 03:49:22

Re: [SOLVED] AX210 cannot connect wifi normally

#8 2022-07-15 06:49:59

Re: [SOLVED] AX210 cannot connect wifi normally

#9 2022-07-16 03:35:50

Re: [SOLVED] AX210 cannot connect wifi normally

#10 2022-07-16 07:30:04

Re: [SOLVED] AX210 cannot connect wifi normally

#11 2022-07-16 11:55:35

Re: [SOLVED] AX210 cannot connect wifi normally

#12 2022-07-16 14:30:38

Re: [SOLVED] AX210 cannot connect wifi normally

#13 2022-07-16 14:51:58

Re: [SOLVED] AX210 cannot connect wifi normally

#14 2022-07-16 15:02:16

Re: [SOLVED] AX210 cannot connect wifi normally

#15 2022-07-16 16:46:12

Re: [SOLVED] AX210 cannot connect wifi normally

#16 2022-07-16 17:02:48

Re: [SOLVED] AX210 cannot connect wifi normally

#17 2022-07-16 18:22:16

Re: [SOLVED] AX210 cannot connect wifi normally

#18 2022-07-16 19:09:57

Re: [SOLVED] AX210 cannot connect wifi normally

#19 2022-07-17 06:34:21

Re: [SOLVED] AX210 cannot connect wifi normally

#20 2022-07-17 06:39:22

Re: [SOLVED] AX210 cannot connect wifi normally

#21 2022-07-17 06:52:30

Re: [SOLVED] AX210 cannot connect wifi normally

#22 2022-07-17 07:13:04

Re: [SOLVED] AX210 cannot connect wifi normally

#23 2022-07-17 08:28:47

Re: [SOLVED] AX210 cannot connect wifi normally

#24 2022-07-17 12:15:08

Re: [SOLVED] AX210 cannot connect wifi normally

#25 2022-07-17 12:40:51

Re: [SOLVED] AX210 cannot connect wifi normally

Board footer