Wifi card failed to connect and memorize password for 5GHz

Ask Fedora
, , , ,
1

I recently installed an ASUS PCE-BE6500 (mt7925e). Previously I had a Gigabyte GC-WBAX200 (intel). Since I installed it, when I boot up my pc, I can’t connect directly to my 5 GHz wifi hotspot. The regular 2.4GHz seems to work though.

The only way I have to make it work is to remove the network from the known list in networkmanager and reconnect to it. And even then it takes several attempts to connect. Each time it fails as if the password is incorrect.

Here is an extract from dmesg after boot:

[    8.587287] mt7925e 0000:07:00.0: enabling device (0000 -> 0002) 
[    8.591068] intel_rapl_common: Found RAPL domain package `
[    8.591071] intel_rapl_common: Found RAPL domain core `
[    8.594862] snd_hda_codec_alc882 hdaudioC3D0: autoconfig for ALC1220: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line `
[    8.594866] snd_hda_codec_alc882 hdaudioC3D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) `
[    8.594869] snd_hda_codec_alc882 hdaudioC3D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) `
[    8.594871] snd_hda_codec_alc882 hdaudioC3D0:    mono: mono_out=0x0 `
[    8.594872] snd_hda_codec_alc882 hdaudioC3D0:    inputs: `
[    8.594874] snd_hda_codec_alc882 hdaudioC3D0:      Rear Mic=0x18 `
[    8.594875] snd_hda_codec_alc882 hdaudioC3D0:      Front Mic=0x19 `
[    8.594876] snd_hda_codec_alc882 hdaudioC3D0:      Line=0x1a `
[    8.600371] mt7925e 0000:07:00.0: ASIC revision: 79250000 `
[    8.600905] amd_atl: AMD Address Translation Library initialized `
[    8.607617] input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:08.1/0000:0d:00.6/sound/card3/input36 `
[    8.608130] input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:0d:00.6/sound/card3/input37 `
[    8.608187] input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:08.1/0000:0d:00.6/sound/card3/input38 `
[    8.608235] input: HD-Audio Generic Line Out Front as /devices/pci0000:00/0000:00:08.1/0000:0d:00.6/sound/card3/input39 `
[    8.608292] input: HD-Audio Generic Line Out Surround as /devices/pci0000:00/0000:00:08.1/0000:0d:00.6/sound/card3/input40 `
[    8.608336] input: HD-Audio Generic Line Out CLFE as /devices/pci0000:00/0000:00:08.1/0000:0d:00.6/sound/card3/input41 `
[    8.608385] input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:08.1/0000:0d:00.6/sound/card3/input42 `
[    8.651480] usbcore: registered new interface driver snd-usb-audio `
[    8.676907] mt7925e 0000:07:00.0: HW/SW Version: 0x8a108a10, Build Time: 20260605184651a `
[    8.804009] EXT4-fs (sda5): mounted filesystem eb6dff8e-6a11-447e-858d-7740ae9a4a08 r/w with ordered data mode. Quota mode: none. `
[    8.818139] ntfs3: Enabled Linux POSIX ACLs support `
[    8.818141] ntfs3: Read-only LZX/Xpress compression included `
[    8.819748] EXT4-fs (dm-1): mounted filesystem 34ef9771-f8c4-408f-b9e1-de2cd4d037f6 r/w with ordered data mode. Quota mode: none. `
[    8.847892] RPC: Registered named UNIX socket transport module. `
[    8.847894] RPC: Registered udp transport module. `
[    8.847895] RPC: Registered tcp transport module. `
[    8.847896] RPC: Registered tcp-with-tls transport module. `
[    8.847897] RPC: Registered tcp NFSv4.1 backchannel transport module. `
[    9.020619] mt7925e 0000:07:00.0: WM Firmware Version: ____000000, Build Time: 20260605184805 `
[   10.287118] mt7925e 0000:07:00.0 wlp7s0: renamed from wlan0 `
[   10.335048] Bluetooth: hci0: Device setup in 1816124 usecs `
[   10.335052] Bluetooth: `**`hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.`**` `
[   10.501569] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 `
[   10.501574] Bluetooth: BNEP filters: protocol multicast `
[   10.501578] Bluetooth: BNEP socket layer initialized `
[   10.505171] Bluetooth: hci0: AOSP extensions version v1.00 `
[   10.505175] Bluetooth: hci0: AOSP quality report is supported `
[   10.505246] Bluetooth: MGMT ver 1.23 `
[   10.687879] NET: Registered PF_QIPCRTR protocol family `
[   11.694376] Realtek Internal NBASE-T PHY r8169-0-900:00: attached PHY driver (mii_bus:phy_addr=r8169-0-900:00, irq=MAC) `
[   11.800157] r8169 0000:09:00.0 eno1: Link is Down `
[   20.202876] RPC: Registered rdma transport module. `
[   20.202880] RPC: Registered rdma backchannel transport module. `
[   20.341546] NFSD: Using nfsdcld client tracking operations. `
[   20.341550] NFSD: no clients to reclaim, skipping NFSv4 grace period (net effffff9) `
[   24.398453] Bluetooth: RFCOMM TTY layer initialized `
[   24.398465] Bluetooth: RFCOMM socket layer initialized `
[   24.398469] Bluetooth: RFCOMM ver 1.11 `
[   24.929378] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[   24.947932] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[   24.948117] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[   24.948419] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[   24.948434] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[   40.056855] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) `
[   40.061728] ata3.00: configured for UDMA/100 `
[   98.608650] HDR SB:01 1a 02 00 e5 85 52 3b ec 2e 0c 8b 0a 1c 41 0b `
[   98.608655] HDR SB:3a 3d 47 40 fe 00 00 00 fe 00 fe 00 00 00 00 00 `
[   98.609229] HDR SB:01 1a 02 00 e5 85 52 3b ec 2e 0c 8b 0a 1c 41 0b `
[   98.609231] HDR SB:3a 3d 47 40 fe 00 00 00 fe 00 fe 00 00 00 00 00 `
[   98.609330] HDR SB:01 1a 02 00 e5 85 52 3b ec 2e 0c 8b 0a 1c 41 0b `
[   98.609331] HDR SB:3a 3d 47 40 fe 00 00 00 fe 00 fe 00 00 00 00 00 `
[   98.609842] HDR SB:01 1a 02 00 e5 85 52 3b ec 2e 0c 8b 0a 1c 41 0b `
[   98.609844] HDR SB:3a 3d 47 40 fe 00 00 00 fe 00 fe 00 00 00 00 00 `
[   98.738076] HDR SB:01 1a 02 00 e5 85 52 3b ec 2e 0c 8b 0a 1c 41 0b `
[   98.738080] HDR SB:3a 3d 47 40 fe 00 00 00 fe 00 fe 00 00 00 00 00 `
[   98.738731] HDR SB:01 1a 02 00 e5 85 52 3b ec 2e 0c 8b 0a 1c 41 0b `
[   98.738732] HDR SB:3a 3d 47 40 fe 00 00 00 fe 00 fe 00 00 00 00 00 `
[   99.716737] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[   99.729664] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[   99.729805] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[   99.729943] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[   99.729953] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[  100.032929] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[  100.043605] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[  100.043746] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[  100.043883] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[  100.043893] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 `
[  103.577512] wlp7s0: authenticate with 22:66:cf:a2:e3:70 (local address=7a:e7:cd:c0:fd:8f) `
[  103.938081] wlp7s0: send auth to 22:66:cf:a2:e3:70 (try 1/3) `
[  103.948305] wlp7s0: authenticated `
[  103.952331] wlp7s0: associate with 22:66:cf:a2:e3:70 (try 1/3) `
[  103.972063] wlp7s0: RX AssocResp from 22:66:cf:a2:e3:70 (capab=0x1111 status=0 aid=2) `
[  104.006312] wlp7s0: associated `
[  104.291417] wlp7s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 22:66:cf:a2:e3:70 `
[  107.117438] wlp7s0: deauthenticated from 22:66:cf:a2:e3:70 (Reason: 15=4WAY_HANDSHAKE_TIMEOUT) `
[  121.231456] evm: overlay not supported`
3

Try to disable power saving on the Wi-Fi hardware temporarily to see results. The auth handshake fails directly after TX power gets nerfed.

Start here to check the power saving status:
iw dev wlp7s0 get power_save

Make the change:
sudo iw dev wlp7s0 set power_save off

Verify it applied:
iw dev wlp7s0 get power_save

Connect to your network after that, and see if that produces any improvements.

If that gives good results, create a .conf file here:
/etc/NetworkManager/conf.d/disable-wifi-powersave.conf

The contents of the .conf file should be:

[connection]
wifi.powersave = 2

*If the temporary Wi-Fi power saving disablement does not produce any improvement then do not create the .conf file at all.

Edit: It could be some type of router setting or channel interference, but most people have routers and APs with minimal setting options and automatic channel optimization.

Or it could be firmware related for the wireless hardware, but I will have to defer that to someone that knows more on that subject.

4

It tried this. But looking at dmesg it doesn’t look like power saving is effective. I still have some output related to limiting tx power instantly followed by a deauthenticate

5

Based on that feedback and looking at the original outputs again, that looks like the router’s AP advertising and enforcing the TX limits for the endpoint. That would be expected and normal.

Since the new wireless hardware is what started this, it would make more sense to point there. I would guess you need some firmware installed to accommodate that new wireless hardware.

This does not seem as though it is normal because I assume this is saying “null”:

mt7925e 0000:07:00.0: WM Firmware Version: ____000000

It is probably a good idea to make sure drivers are fully updated for that wireless hardware as well.

6

How would I do that ? I installed the mediatek-firmware package but it seems related to mediatek SoC.

7

Try running sudo fwupdmgr get-updates and see what it tells you about updates. If there are any then run sudo fwupdmgr update to apply those updates.

The mt7925e driver is supported by the kernel but if it does not read the info from the card properly then it cannot function.

8

So I did this but the card isn’t even listed in my devices

9

Is the card a pcie card or an m.2 card?
The info I see with a quick search seems to indicate PCI.

In either case I would suggest that you remove it, clean the mounting slot, clean the contacts with a soft eraser, then reinsert the card. It is possible that a tiny bit of dust or corrosion may have interfered with proper contact on one or more of the traces and could cause such an issue.

10

I did this, it didn’t change anything. What seems to work, is to disable NetworkManager for a few seconds, re-enable it, wait a few seconds and then try to connect to the network.