Page 1 of 1

Wireless suddenly quit working for one of my routers.

Posted: Tue Feb 08, 2022 11:24 am
by proteusguy
My Asus laptop is fairly modern and I couldn't get wireless drivers working for it. Recently installed the latest MX-21 AHS 64 Wildflower release and my wifi started working, yea! Today, however, it stopped authenticating to one of my routers. Every other device I have works fine with this router. The laptop still authenticates with my other router at home and the ones in the office. Just decided to stop going with this one. I haven't changed the setup as far as I can tell. I blew away the config for the AP and re-created it - no luck.

Here's the syslog capture of a couple of failed attempts followed by a successful one on another router:
(My system configuration capture is at the bottom of this post.)

Code: Select all

$ lspci -nnk | grep -i net -A2
02:00.0 Network controller [0280]: MEDIATEK Corp. Device [14c3:7961]
        Subsystem: AzureWave Device [1a3b:4680]
        Kernel driver in use: mt7921e

syslog captures...
Two failed attempts to login to proteusHigh2

Feb  8 22:52:25 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb  8 22:52:42 pixies wpa_supplicant[3161]: wlan0: Reject scan trigger since one is already pending
Feb  8 22:52:49 pixies wpa_supplicant[3161]: wlan0: SME: Trying to authenticate with 2c:08:8c:e6:4f:4c (SSID='proteusHigh2' freq=2412 MHz)
Feb  8 22:52:49 pixies kernel: [ 9929.647424] wlan0: authenticate with 2c:08:8c:e6:4f:4c
Feb  8 22:52:49 pixies kernel: [ 9929.660518] wlan0: send auth to 2c:08:8c:e6:4f:4c (try 1/3)
Feb  8 22:52:49 pixies wpa_supplicant[3161]: wlan0: Trying to associate with 2c:08:8c:e6:4f:4c (SSID='proteusHigh2' freq=2412 MHz)
Feb  8 22:52:49 pixies kernel: [ 9929.663463] wlan0: authenticated
Feb  8 22:52:49 pixies kernel: [ 9929.665150] wlan0: associate with 2c:08:8c:e6:4f:4c (try 1/3)
Feb  8 22:52:49 pixies kernel: [ 9929.669996] wlan0: RX AssocResp from 2c:08:8c:e6:4f:4c (capab=0x1411 status=0 aid=7)
Feb  8 22:52:49 pixies kernel: [ 9929.691039] wlan0: associated
Feb  8 22:52:49 pixies wpa_supplicant[3161]: wlan0: Associated with 2c:08:8c:e6:4f:4c
Feb  8 22:52:49 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Feb  8 22:52:56 pixies kernel: [ 9936.809507] wlan0: deauthenticated from 2c:08:8c:e6:4f:4c (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
Feb  8 22:52:57 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:08:8c:e6:4f:4c reason=15
Feb  8 22:52:57 pixies wpa_supplicant[3161]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Feb  8 22:52:57 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="proteusHigh2" auth_failures=1 duration=10 reason=WRONG_KEY
Feb  8 22:52:57 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Feb  8 22:53:15 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb  8 22:53:15 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb  8 22:53:17 pixies wpa_supplicant[3161]: wlan0: SME: Trying to authenticate with 2c:08:8c:e6:4f:4c (SSID='proteusHigh2' freq=2412 MHz)
Feb  8 22:53:17 pixies kernel: [ 9956.884697] wlan0: authenticate with 2c:08:8c:e6:4f:4c
Feb  8 22:53:17 pixies kernel: [ 9956.897685] wlan0: send auth to 2c:08:8c:e6:4f:4c (try 1/3)
Feb  8 22:53:17 pixies wpa_supplicant[3161]: wlan0: Trying to associate with 2c:08:8c:e6:4f:4c (SSID='proteusHigh2' freq=2412 MHz)
Feb  8 22:53:17 pixies kernel: [ 9956.900598] wlan0: authenticated
Feb  8 22:53:17 pixies kernel: [ 9956.901952] wlan0: associate with 2c:08:8c:e6:4f:4c (try 1/3)
Feb  8 22:53:17 pixies kernel: [ 9956.906789] wlan0: RX AssocResp from 2c:08:8c:e6:4f:4c (capab=0x1411 status=0 aid=7)
Feb  8 22:53:17 pixies kernel: [ 9956.925777] wlan0: associated
Feb  8 22:53:17 pixies wpa_supplicant[3161]: wlan0: Associated with 2c:08:8c:e6:4f:4c
Feb  8 22:53:17 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Feb  8 22:53:24 pixies kernel: [ 9964.111380] wlan0: deauthenticated from 2c:08:8c:e6:4f:4c (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
Feb  8 22:53:24 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-DISCONNECTED bssid=2c:08:8c:e6:4f:4c reason=15
Feb  8 22:53:24 pixies wpa_supplicant[3161]: wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Feb  8 22:53:24 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="proteusHigh2" auth_failures=1 duration=10 reason=WRONG_KEY
Feb  8 22:53:24 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Feb  8 22:53:30 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb  8 22:53:30 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb  8 22:53:31 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN


Now successfully logging into Biggest Fan Gang_5GHz

Feb  8 22:55:58 pixies wpa_supplicant[3161]: wlan0: SME: Trying to authenticate with f8:2e:3f:0c:de:bc (SSID='Biggest Fan Gang_5GHz' freq=5180 MHz)
Feb  8 22:55:58 pixies kernel: [10118.225843] wlan0: authenticate with f8:2e:3f:0c:de:bc
Feb  8 22:55:58 pixies kernel: [10118.240842] wlan0: send auth to f8:2e:3f:0c:de:bc (try 1/3)
Feb  8 22:55:58 pixies wpa_supplicant[3161]: wlan0: Trying to associate with f8:2e:3f:0c:de:bc (SSID='Biggest Fan Gang_5GHz' freq=5180 MHz)
Feb  8 22:55:58 pixies kernel: [10118.243732] wlan0: authenticated
Feb  8 22:55:58 pixies kernel: [10118.244635] wlan0: associate with f8:2e:3f:0c:de:bc (try 1/3)
Feb  8 22:55:58 pixies kernel: [10118.248324] wlan0: RX AssocResp from f8:2e:3f:0c:de:bc (capab=0x1531 status=0 aid=2)
Feb  8 22:55:58 pixies kernel: [10118.269359] wlan0: associated
Feb  8 22:55:58 pixies wpa_supplicant[3161]: wlan0: Associated with f8:2e:3f:0c:de:bc
Feb  8 22:55:58 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Feb  8 22:55:58 pixies wpa_supplicant[3161]: wlan0: WPA: Key negotiation completed with f8:2e:3f:0c:de:bc [PTK=CCMP GTK=CCMP]
Feb  8 22:55:58 pixies wpa_supplicant[3161]: wlan0: CTRL-EVENT-CONNECTED - Connection to f8:2e:3f:0c:de:bc completed [id=0 id_str=]
Feb  8 22:55:58 pixies wpa_supplicant[3161]: bgscan simple: Failed to enable signal strength monitoring
Feb  8 22:55:58 pixies kernel: [10118.310245] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb  8 22:55:58 pixies avahi-daemon[3003]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::4b2:2595:3a56:613d.
Feb  8 22:55:58 pixies avahi-daemon[3003]: New relevant interface wlan0.IPv6 for mDNS.
Feb  8 22:55:58 pixies avahi-daemon[3003]: Registering new address record for fe80::4b2:2595:3a56:613d on wlan0.*.
Feb  8 22:55:58 pixies kernel: [10118.346646] wlan0: Limiting TX power to 24 (24 - 0) dBm as advertised by f8:2e:3f:0c:de:bc
Feb  8 22:56:00 pixies ntpd[126470]: IO: Listen normally on 7 wlan0 [fe80::4b2:2595:3a56:613d%2]:123
Feb  8 22:56:00 pixies ntpd[126470]: IO: new interface(s) found: waking up resolver
Feb  8 22:56:04 pixies avahi-daemon[3003]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::4b2:2595:3a56:613d.
Feb  8 22:56:04 pixies avahi-daemon[3003]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2001:fb1:45:a5bc:737c:597a:c7b2:ca9f.
Feb  8 22:56:04 pixies avahi-daemon[3003]: Registering new address record for 2001:fb1:45:a5bc:737c:597a:c7b2:ca9f on wlan0.*.
Feb  8 22:56:04 pixies avahi-daemon[3003]: Withdrawing address record for fe80::4b2:2595:3a56:613d on wlan0.
Feb  8 22:56:04 pixies dbus-daemon[2936]: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.3' (uid=0 pid=3034 comm="/usr/sbin/NetworkManager ") (using servicehelper)
Feb  8 22:56:04 pixies dbus-daemon[2936]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb  8 22:56:05 pixies avahi-daemon[3003]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.55.
Feb  8 22:56:05 pixies avahi-daemon[3003]: New relevant interface wlan0.IPv4 for mDNS.
Feb  8 22:56:05 pixies avahi-daemon[3003]: Registering new address record for 192.168.1.55 on wlan0.IPv4.
Feb  8 22:56:05 pixies ntpd[126470]: ERR: ntpd exiting on signal 15 (Terminated)
Feb  8 22:56:05 pixies ntpd[131109]: INIT: ntpd ntpsec-1.2.0 2021-06-17T05:15:04Z: Starting
Feb  8 22:56:05 pixies ntpd[131109]: INIT: Command line: /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec
Feb  8 22:56:05 pixies ntpd[131115]: INIT: precision = 0.060 usec (-24)
Feb  8 22:56:05 pixies ntpd[131115]: INIT: successfully locked into RAM
Feb  8 22:56:05 pixies ntpd[131115]: CONFIG: readconfig: parsing file: /etc/ntpsec/ntp.conf
Feb  8 22:56:05 pixies ntpd[131115]: CONFIG: restrict nopeer ignored
Feb  8 22:56:05 pixies ntpd[131115]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
Feb  8 22:56:05 pixies ntpd[131115]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2022-06-28T00:00Z last=2017-01-01T00:00Z ofs=37
Feb  8 22:56:05 pixies ntpd[131115]: INIT: Using SO_TIMESTAMPNS
Feb  8 22:56:05 pixies ntpd[131115]: IO: Listen and drop on 0 v6wildcard [::]:123
Feb  8 22:56:05 pixies ntpd[131115]: IO: Listen and drop on 1 v4wildcard 0.0.0.0:123
Feb  8 22:56:05 pixies ntpd[131113]: INIT: ntpd ntpsec-1.2.0 2021-06-17T05:15:04Z: Starting
Feb  8 22:56:05 pixies ntpd[131115]: IO: Listen normally on 2 lo 127.0.0.1:123
Feb  8 22:56:05 pixies ntpd[131113]: INIT: Command line: /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec
Feb  8 22:56:05 pixies ntpd[131115]: IO: Listen normally on 3 wlan0 192.168.1.55:123
Feb  8 22:56:05 pixies ntpd[131115]: IO: Listen normally on 4 lo [::1]:123
Feb  8 22:56:05 pixies ntpd[131115]: IO: bind(21) AF_INET6 2001:fb1:45:a5bc:737c:597a:c7b2:ca9f#123 flags 0x1 failed: Cannot assign requested address
Feb  8 22:56:05 pixies ntpd[131115]: IO: unable to create socket on wlan0 (5) for 2001:fb1:45:a5bc:737c:597a:c7b2:ca9f#123
Feb  8 22:56:05 pixies ntpd[131115]: IO: failed to init interface for address 2001:fb1:45:a5bc:737c:597a:c7b2:ca9f
Feb  8 22:56:05 pixies ntpd[131115]: IO: Listen normally on 6 wlan0 [fe80::4b2:2595:3a56:613d%2]:123
Feb  8 22:56:05 pixies ntpd[131115]: IO: Listening on routing socket on fd #22 for interface updates
Feb  8 22:56:05 pixies ntpd[131119]: INIT: precision = 0.060 usec (-24)
Feb  8 22:56:05 pixies ntpd[131119]: INIT: successfully locked into RAM
Feb  8 22:56:05 pixies ntpd[131119]: CONFIG: readconfig: parsing file: /etc/ntpsec/ntp.conf
Feb  8 22:56:05 pixies ntpd[131119]: CONFIG: restrict nopeer ignored
Feb  8 22:56:05 pixies ntpd[131119]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
Feb  8 22:56:05 pixies ntpd[131119]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2022-06-28T00:00Z last=2017-01-01T00:00Z ofs=37
Feb  8 22:56:05 pixies ntpd[131119]: IO: unable to bind to wildcard address :: - another process may be running: Address already in use; EXITING
Feb  8 22:56:05 pixies ntpd[131115]: INIT: MRU 10922 entries, 13 hash bits, 65536 bytes
Feb  8 22:56:05 pixies ntpd[131115]: INIT: OpenSSL 1.1.1k  25 Mar 2021, 101010bf
Feb  8 22:56:05 pixies ntpd[131115]: NTSc: Using system default root certificates.
Feb  8 22:56:05 pixies ntpd[131115]: statistics directory /var/log/ntpsec/ does not exist or is unwriteable, error No such file or directory
Feb  8 22:56:06 pixies PackageKit: get-updates transaction /70_daecdeee from uid 1000 finished with success after 546ms
Feb  8 22:56:06 pixies ntpd[131115]: DNS: dns_probe: 0.debian.pool.ntp.org, cast_flags:8, flags:101
Feb  8 22:56:06 pixies ntpd[131115]: DNS: dns_check: processing 0.debian.pool.ntp.org, 8, 101
Feb  8 22:56:06 pixies ntpd[131115]: DNS: Pool taking: 124.109.2.169
Feb  8 22:56:06 pixies ntpd[131115]: DNS: Pool taking: 61.91.205.20
Feb  8 22:56:06 pixies ntpd[131115]: DNS: Pool taking: 202.29.58.130
Feb  8 22:56:06 pixies ntpd[131115]: DNS: Pool taking: 202.28.116.236
Feb  8 22:56:06 pixies ntpd[131115]: DNS: dns_take_status: 0.debian.pool.ntp.org=>good, 8
Feb  8 22:56:07 pixies ntpd[131115]: DNS: dns_probe: 1.debian.pool.ntp.org, cast_flags:8, flags:101
Feb  8 22:56:07 pixies ntpd[131115]: IO: Listen normally on 7 wlan0 [2001:fb1:45:a5bc:737c:597a:c7b2:ca9f]:123
Feb  8 22:56:07 pixies ntpd[131115]: IO: new interface(s) found: waking up resolver
Feb  8 22:56:07 pixies ntpd[131115]: DNS: dns_check: processing 1.debian.pool.ntp.org, 8, 101
Feb  8 22:56:07 pixies ntpd[131115]: DNS: Pool taking: 202.28.93.5
Feb  8 22:56:07 pixies ntpd[131115]: DNS: Pool taking: 110.170.126.104
Feb  8 22:56:07 pixies ntpd[131115]: DNS: Pool taking: 162.159.200.1
Feb  8 22:56:07 pixies ntpd[131115]: DNS: Pool taking: 203.159.70.33
Feb  8 22:56:07 pixies ntpd[131115]: DNS: dns_take_status: 1.debian.pool.ntp.org=>good, 8
Feb  8 22:56:08 pixies ntpd[131115]: DNS: dns_probe: 3.debian.pool.ntp.org, cast_flags:8, flags:101
Feb  8 22:56:08 pixies ntpd[131115]: DNS: dns_check: processing 3.debian.pool.ntp.org, 8, 101
Feb  8 22:56:08 pixies ntpd[131115]: DNS: Pool skipping: 203.159.70.33
Feb  8 22:56:08 pixies ntpd[131115]: DNS: Pool taking: 110.170.126.105
Feb  8 22:56:08 pixies ntpd[131115]: DNS: Pool skipping: 61.91.205.20
Feb  8 22:56:08 pixies ntpd[131115]: DNS: Pool taking: 161.200.192.4
Feb  8 22:56:08 pixies ntpd[131115]: DNS: dns_take_status: 3.debian.pool.ntp.org=>good, 8
Feb  8 22:56:09 pixies ntpd[131115]: DNS: dns_probe: 2.debian.pool.ntp.org, cast_flags:8, flags:101
Feb  8 22:56:09 pixies ntpd[131115]: DNS: dns_check: processing 2.debian.pool.ntp.org, 8, 101
Feb  8 22:56:09 pixies ntpd[131115]: DNS: Pool taking: 2001:3c8:1501:65::1501:11
Feb  8 22:56:09 pixies ntpd[131115]: DNS: Pool taking: 2406:3100:1010:c03::148
Feb  8 22:56:09 pixies ntpd[131115]: DNS: Pool taking: 2606:4700:f1::123
Feb  8 22:56:09 pixies ntpd[131115]: DNS: Pool taking: 2606:4700:f1::1
Feb  8 22:56:09 pixies ntpd[131115]: DNS: Pool taking: 202.12.97.45
Feb  8 22:56:09 pixies ntpd[131115]: DNS: Pool taking: 185.78.166.99
Feb  8 22:56:09 pixies ntpd[131115]: DNS: Pool taking: 110.170.126.103
Feb  8 22:56:09 pixies ntpd[131115]: DNS: Pool taking: 119.110.245.51
Feb  8 22:56:09 pixies ntpd[131115]: DNS: dns_take_status: 2.debian.pool.ntp.org=>good, 8
Feb  8 22:56:10 pixies ntpd[131115]: DNS: dns_probe: 0.debian.pool.ntp.org, cast_flags:8, flags:101
Feb  8 22:56:10 pixies ntpd[131115]: DNS: dns_check: processing 0.debian.pool.ntp.org, 8, 101
Feb  8 22:56:10 pixies ntpd[131115]: DNS: Pool skipping: 202.28.116.236
Feb  8 22:56:10 pixies ntpd[131115]: DNS: Pool skipping: 202.29.58.130
Feb  8 22:56:10 pixies ntpd[131115]: DNS: Pool skipping: 61.91.205.20
Feb  8 22:56:10 pixies ntpd[131115]: DNS: Pool skipping: 124.109.2.169
Feb  8 22:56:10 pixies ntpd[131115]: DNS: dns_take_status: 0.debian.pool.ntp.org=>good, 8


Code: Select all

System:    Kernel: 5.14.0-4mx-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/vmlinuz-5.14.0-4mx-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 7 dm: LightDM 1.26.0 
           Distro: MX-21_ahs_x64 Wildflower November 22  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: ASUSTeK product: ROG Zephyrus G14 GA401QM_GA401QM v: 1.0 
           serial: <filter> 
           Mobo: ASUSTeK model: GA401QM v: 1.0 serial: <filter> UEFI: American Megatrends LLC. 
           v: GA401QM.408 date: 05/13/2021 
Battery:   ID-1: BAT0 charge: 72.6 Wh (100.0%) condition: 72.6/76.0 Wh (95.5%) volts: 15.8 
           min: 15.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Not charging 
CPU:       Info: 8-Core model: AMD Ryzen 9 5900HS with Radeon Graphics bits: 64 type: MT MCP 
           arch: Zen 3 family: 19 (25) model-id: 50 (80) stepping: 0 microcode: A50000C cache: 
           L2: 4 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 105400 
           Speed: 2886 MHz min/max: 1200/3300 MHz boost: enabled Core speeds (MHz): 1: 2886 
           2: 2936 3: 3322 4: 2860 5: 2884 6: 2861 7: 2737 8: 3586 9: 3381 10: 3689 11: 2812 
           12: 3551 13: 2761 14: 3178 15: 3272 16: 3284 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP: 
           always-on, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: ASUSTeK driver: N/A 
           alternate: nouveau bus-ID: 01:00.0 chip-ID: 10de:2520 class-ID: 0300 
           Device-2: AMD Cezanne vendor: ASUSTeK driver: amdgpu v: kernel bus-ID: 04:00.0 
           chip-ID: 1002:1638 class-ID: 0300 
           Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") 
           s-diag: 777mm (30.6") 
           Monitor-1: eDP res: 2560x1440 hz: 120 dpi: 210 size: 310x174mm (12.2x6.9") 
           diag: 355mm (14") 
           OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.14.0-4mx-amd64 LLVM 12.0.1) 
           v: 4.6 Mesa 21.2.5 direct render: Yes 
Audio:     Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
           chip-ID: 10de:228e class-ID: 0403 
           Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel 
           bus-ID: 04:00.1 chip-ID: 1002:1637 class-ID: 0403 
           Device-3: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: ASUSTeK 
           driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x bus-ID: 04:00.5 
           chip-ID: 1022:15e2 class-ID: 0480 
           Device-4: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403 
           Sound Server-1: ALSA v: k5.14.0-4mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: MEDIATEK vendor: AzureWave driver: mt7921e v: kernel modules: wl port: e000 
           bus-ID: 02:00.0 chip-ID: 14c3:7961 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 3-4:4 
           chip-ID: 13d3:3563 class-ID: e001 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: N/A rfk-block: 
           hardware: no software: no address: <filter> 
           Info: acl-mtu: 0:0 sco-mtu: 0:0 link-mode: slave accept 
Drives:    Local Storage: total: 953.87 GiB used: 402.49 GiB (42.2%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVLQ1T0HBLB-00B00 
           size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           type: SSD serial: <filter> rev: FXM7201Q temp: 39.9 C scheme: GPT 
Partition: ID-1: / raw-size: 107.41 GiB size: 105.16 GiB (97.91%) used: 9.16 GiB (8.7%) fs: ext4 
           dev: /dev/dm-0 maj-min: 253:0 mapped: root.fsm 
           ID-2: /boot raw-size: 512 MiB size: 487.2 MiB (95.16%) used: 184.4 MiB (37.8%) 
           fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2 
           ID-3: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) 
           fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 
           ID-4: /home raw-size: 822.24 GiB size: 822.24 GiB (100.00%) used: 393.14 GiB (47.8%) 
           fs: btrfs dev: /dev/dm-1 maj-min: 253:1 mapped: 1.home.fsm 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 23.42 GiB used: 3.2 MiB (0.0%) priority: -2 
           dev: /dev/dm-2 maj-min: 253:2 mapped: swap 
Sensors:   System Temperatures: cpu: 67.0 C mobo: N/A gpu: amdgpu temp: 61.0 C 
           Fan Speeds (RPM): cpu: 2600 
Repos:     Packages: 2637 note: see --pkg apt: 2633 lib: 1379 flatpak: 4 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bullseye main non-free
           2: deb https://mirror.kku.ac.th/mx-packages/mx/repo/ bullseye ahs
Info:      Processes: 394 Uptime: 3h 10m wakeups: 2 Memory: 15.05 GiB used: 6.34 GiB (42.1%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Shell: quick-system-in default: Bash v: 5.1.4 running-in: quick-system-in 
           inxi: 3.3.06 

Re: Wireless suddenly quit working for one of my routers.

Posted: Tue Feb 08, 2022 11:53 am
by j2mcgreg
You should check to see if the problem router has a limit on the number devices that can connect to it at any one time. Usually routers that employ a scheme like this will give priority to older connections over the newer ones by ranking their MAC addresses. If this newish laptop is a replacement, try to obtain the older units mac address and remove it from the router's connection list.

Re: Wireless suddenly quit working for one of my routers.

Posted: Tue Feb 08, 2022 11:53 am
by Huckleberry Finn
Just btw: Even Nouveau wasn't loaded for some reason:

Graphics: Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: ASUSTeK driver: N/A
alternate: nouveau bus-ID: 01:00.0 chip-ID: 10de:2520 class-ID: 0300

...

You can install a more recent & LTS kernel: 5.15 with 2 clicks from Popular Apps tab in "MX Package Installer".

Driver etc. look ok:

Network: Device-1: MEDIATEK vendor: AzureWave driver: mt7921e v: kernel modules: wl port: e000
bus-ID: 02:00.0 chip-ID: 14c3:7961 class-ID: 0280
IF: wlan0 state: up

Edit your connection and check : All users may connect ...

While you're at it: IPv4 tab .. "Additional DNS Servers"

add there:

Code: Select all

8.8.8.8, 8.8.4.4
or

Code: Select all

1.1.1.1, 1.0.0.1
whichever you like.. Apply...

Re: Wireless suddenly quit working for one of my routers.

Posted: Tue Feb 08, 2022 1:48 pm
by razor2021
For temp workarounds, try instead of restarting to reboot your laptop, try shutting down completely first. Then boot up your laptop, and see if Wifi is working.
Or, also try to put the laptop to sleep and opening it again to see if the Wifi works again.

It might be something to do with your new Mediatek wifi module mt7921e and the linux kernels. Not sure when it will get fixed - hopefully soon-ish on newer linux kernels .. as reported here --> https://patchwork.kernel.org/project/li ... ter=169671

Re: Wireless suddenly quit working for one of my routers.

Posted: Tue Feb 08, 2022 1:58 pm
by razor2021
Also are you able to update your motherboard BIOS from 408 (05/13/2021) to the latest? --> Version 410 -- 2022/01/07

Re: Wireless suddenly quit working for one of my routers.

Posted: Tue Feb 08, 2022 11:25 pm
by proteusguy
I upgraded the kernel as Huckleberry Finn recommended and then my wifi wouldn't connect to ANY router... ;-) haha damn

But - I did find the new BIOS v410 on the ASUS site and upgraded as razor2021 recommended then suddenly wifi connected to everything.

So...all's well that ends. Thanks guys!

Re: Wireless suddenly quit working for one of my routers.

Posted: Wed Feb 09, 2022 4:43 am
by Huckleberry Finn
Glad to hear that and thank you for the feedback. You can try even more recent kernels later (for it's a new machine) when they appear.

You can (and please) mark the thread as solved by clicking the check-mark icon on the post that was the solution :)