Wifi dropping randomly on AX210

I recently installed fedora + gnome, and coming from Manjaro KDE, I have a dual boot setup with windows, even previously i had Manjaro + windows setup.
Wifi was working perfectly fine in my earlier setup, even on this current setup with fedora, on windows WIFI has no issues.

But on Fedora sometimes wifi struggles on connect just after boot, sometime as soon as I start a download or something it randomly drops and struggles to reconnect.
Its so random even sometimes while doing a task it drops.

Please help me on this, thanks.

From lspci

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
03:00.0 Network controller: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a)

System info

OS: Fedora Linux 44 (Workstation Edition) x86_64
Kernel: Linux 7.0.12-201.fc44.x86_64
DE: GNOME 50.2
WM: Mutter (Wayland)

From dmesg

 1296.493545] wlp3s0: authenticate with 0e:36:23:81:46:ca (local address=0a:23:32:a3:86:b1)
[ 1296.494403] wlp3s0: send auth to 0e:36:23:81:46:ca (try 1/3)
[ 1296.627356] wlp3s0: send auth to 0e:36:23:81:46:ca (try 2/3)
[ 1296.730296] wlp3s0: send auth to 0e:36:23:81:46:ca (try 3/3)
[ 1296.784947] wlp3s0: authenticated
[ 1296.785349] wlp3s0: associate with 0e:36:23:81:46:ca (try 1/3)
[ 1296.788637] wlp3s0: RX AssocResp from 0e:36:23:81:46:ca (capab=0x1111 status=0 aid=5)
[ 1296.792360] wlp3s0: associated
[ 1296.832006] wlp3s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 0e:36:23:81:46:ca
[ 1296.968571] iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x0.
[ 1296.968651] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 1296.968654] iwlwifi 0000:03:00.0: Transport status: 0x0000004A, valid: 6
[ 1296.968657] iwlwifi 0000:03:00.0: Loaded firmware version: 89.123cf747.0 ty-a0-gf-a0-89.ucode
[ 1296.968660] iwlwifi 0000:03:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
[ 1296.968662] iwlwifi 0000:03:00.0: 0x00008210 | trm_hw_status0
[ 1296.968665] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[ 1296.968667] iwlwifi 0000:03:00.0: 0x004DACB0 | branchlink2
[ 1296.968669] iwlwifi 0000:03:00.0: 0x004D0902 | interruptlink1
[ 1296.968670] iwlwifi 0000:03:00.0: 0x004D0902 | interruptlink2
[ 1296.968672] iwlwifi 0000:03:00.0: 0x0000C248 | data1
[ 1296.968674] iwlwifi 0000:03:00.0: 0x00000010 | data2
[ 1296.968676] iwlwifi 0000:03:00.0: 0x00000000 | data3
[ 1296.968678] iwlwifi 0000:03:00.0: 0x00C14E10 | beacon time
[ 1296.968680] iwlwifi 0000:03:00.0: 0x068C6248 | tsf low
[ 1296.968682] iwlwifi 0000:03:00.0: 0x0000006B | tsf hi
[ 1296.968684] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 1296.968686] iwlwifi 0000:03:00.0: 0x0044B2E6 | time gp2
[ 1296.968687] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[ 1296.968689] iwlwifi 0000:03:00.0: 0x00000059 | uCode version major
[ 1296.968691] iwlwifi 0000:03:00.0: 0x123CF747 | uCode version minor
[ 1296.968693] iwlwifi 0000:03:00.0: 0x00000420 | hw version
[ 1296.968695] iwlwifi 0000:03:00.0: 0x18C80002 | board version
[ 1296.968697] iwlwifi 0000:03:00.0: 0x80C0FC18 | hcmd
[ 1296.968699] iwlwifi 0000:03:00.0: 0x24020000 | isr0
[ 1296.968701] iwlwifi 0000:03:00.0: 0x01000000 | isr1
[ 1296.968703] iwlwifi 0000:03:00.0: 0x48F0000A | isr2
[ 1296.968704] iwlwifi 0000:03:00.0: 0x00C32C0C | isr3
[ 1296.968706] iwlwifi 0000:03:00.0: 0x00200000 | isr4
[ 1296.968708] iwlwifi 0000:03:00.0: 0x0400001C | last cmd Id
[ 1296.968710] iwlwifi 0000:03:00.0: 0x0000C248 | wait_event
[ 1296.968712] iwlwifi 0000:03:00.0: 0x00000094 | l2p_control
[ 1296.968714] iwlwifi 0000:03:00.0: 0x00010034 | l2p_duration
[ 1296.968716] iwlwifi 0000:03:00.0: 0x0000000F | l2p_mhvalid
[ 1296.968718] iwlwifi 0000:03:00.0: 0x00000000 | l2p_addr_match
[ 1296.968720] iwlwifi 0000:03:00.0: 0x00000009 | lmpm_pmg_sel
[ 1296.968721] iwlwifi 0000:03:00.0: 0x00000000 | timestamp
[ 1296.968723] iwlwifi 0000:03:00.0: 0x0000B8DC | flow_handler
[ 1296.968754] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 1296.968756] iwlwifi 0000:03:00.0: Transport status: 0x0000004A, valid: 7
[ 1296.968758] iwlwifi 0000:03:00.0: 0x2010120E | ADVANCED_SYSASSERT
[ 1296.968761] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
[ 1296.968763] iwlwifi 0000:03:00.0: 0x80483AE2 | umac branchlink2
[ 1296.968764] iwlwifi 0000:03:00.0: 0xC00814E0 | umac interruptlink1
[ 1296.968766] iwlwifi 0000:03:00.0: 0x00000000 | umac interruptlink2
[ 1296.968768] iwlwifi 0000:03:00.0: 0x00000400 | umac data1
[ 1296.968770] iwlwifi 0000:03:00.0: 0x00000004 | umac data2
[ 1296.968772] iwlwifi 0000:03:00.0: 0x00000003 | umac data3
[ 1296.968774] iwlwifi 0000:03:00.0: 0x00000059 | umac major
[ 1296.968776] iwlwifi 0000:03:00.0: 0x123CF747 | umac minor
[ 1296.968778] iwlwifi 0000:03:00.0: 0x0044FD1E | frame pointer
[ 1296.968779] iwlwifi 0000:03:00.0: 0xC08875CC | stack pointer
[ 1296.968781] iwlwifi 0000:03:00.0: 0x00700517 | last host cmd
[ 1296.968783] iwlwifi 0000:03:00.0: 0x00010008 | isr status reg
[ 1296.968794] iwlwifi 0000:03:00.0: IML/ROM dump:
[ 1296.968796] iwlwifi 0000:03:00.0: 0x00000B03 | IML/ROM error/state
[ 1296.968807] iwlwifi 0000:03:00.0: 0x000082AB | IML/ROM data1
[ 1296.968818] iwlwifi 0000:03:00.0: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
[ 1296.968826] iwlwifi 0000:03:00.0: Fseq Registers:
[ 1296.968829] iwlwifi 0000:03:00.0: 0x60000000 | FSEQ_ERROR_CODE
[ 1296.968834] iwlwifi 0000:03:00.0: 0x80440007 | FSEQ_TOP_INIT_VERSION
[ 1296.968838] iwlwifi 0000:03:00.0: 0x00080009 | FSEQ_CNVIO_INIT_VERSION
[ 1296.968842] iwlwifi 0000:03:00.0: 0x0000A652 | FSEQ_OTP_VERSION
[ 1296.968846] iwlwifi 0000:03:00.0: 0x00000002 | FSEQ_TOP_CONTENT_VERSION
[ 1296.968850] iwlwifi 0000:03:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 1296.968854] iwlwifi 0000:03:00.0: 0x00400410 | FSEQ_CNVI_ID
[ 1296.968858] iwlwifi 0000:03:00.0: 0x00400410 | FSEQ_CNVR_ID
[ 1296.968862] iwlwifi 0000:03:00.0: 0x00400410 | CNVI_AUX_MISC_CHIP
[ 1296.968868] iwlwifi 0000:03:00.0: 0x00400410 | CNVR_AUX_MISC_CHIP
[ 1296.968874] iwlwifi 0000:03:00.0: 0x00009061 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 1296.968881] iwlwifi 0000:03:00.0: 0x00000061 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 1296.968885] iwlwifi 0000:03:00.0: 0x00080009 | FSEQ_PREV_CNVIO_INIT_VERSION
[ 1296.968889] iwlwifi 0000:03:00.0: 0x00440007 | FSEQ_WIFI_FSEQ_VERSION
[ 1296.968893] iwlwifi 0000:03:00.0: 0x00440007 | FSEQ_BT_FSEQ_VERSION
[ 1296.968897] iwlwifi 0000:03:00.0: 0x000000F0 | FSEQ_CLASS_TP_VERSION
[ 1296.968908] iwlwifi 0000:03:00.0: UMAC CURRENT PC: 0x804a5ab0
[ 1296.968912] iwlwifi 0000:03:00.0: LMAC1 CURRENT PC: 0xd0
[ 1296.968927] iwlwifi 0000:03:00.0: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[ 1297.438237] iwlwifi 0000:03:00.0: Too many device errors - delay next reset
[ 1297.438246] iwlwifi 0000:03:00.0: Failed to send MAC_CONFIG_CMD (action:2): -5
[ 1297.438250] iwlwifi 0000:03:00.0: failed to update MAC 0a:23:32:a3:86:b1
[ 1297.438422] iwlwifi 0000:03:00.0: mcast filter cmd error. ret=-5
[ 1297.438426] iwlwifi 0000:03:00.0: Failed to synchronize multicast groups update
[ 1298.227507] iwlwifi 0000:03:00.0: mcast filter cmd error. ret=-5
[ 1298.227518] iwlwifi 0000:03:00.0: Failed to synchronize multicast groups update

Tried disabling wifi6 and powersave already, bt still happens

From /etc/modprobe.d/iwlwifi.conf

options iwlwifi disable_11ax=Y
options iwlwifi power_save=0
options iwlmvm power_scheme=1

Windows fast startup is already OFF

@computersavvy hope u dont mind the direct mention here, bt reading ur replies on similar other wifi issue posts.
Do u also have similar problem or things working fine on ur side on AX210?

WiFi often has problems with newer kernels. When Intel had their own Linux distro their WiFi firmware was updated with in sync with new kernels, but now there are often issues. Years ago I learned to have USB dongles with in-kernel drivers to use while waiting for WiFi vendors to update firmware and drivers. In some cases the Linux community comes up with workarounds, but those can be hard to find.

When reporting an issue, you should provide enough detail to allow others with similar systems to reproduce your issue:

  1. ensure you have current Fedora and vendor firmware updates so it is easy for others to reproduce and avoid wasting time on solved problems.
  2. output from inxi -Fzxx

Yes i understand.
I have already complete a dnf upgrade for system which bumped my kernel from 6.19.10-300 → 7.0.12-201
And to clarify, same was happening on 6.19 as well on fedora.
Sadly I just dont recall my kernel version on Manjaro, where it was working just fine :grimacing:.

Output from for inxi

System:
  Kernel: 7.0.12-201.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
  Desktop: GNOME v: 50.2 tk: GTK v: 3.24.52 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 44 (Workstation Edition)
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A15 FA506QM_FA506QM
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: FA506QM v: 1.0 serial: <superuser required>
    Firmware: UEFI vendor: American Megatrends LLC. v: FA506QM.314
    date: 01/07/2023
Battery:
  ID-1: BAT1 charge: 64.5 Wh (100%) condition: 64.5/90 Wh (71.7%) volts: 16.46
    min: 15.86 model: ASUS A32-K55 serial: N/A charging: status: full
    cycles: N/A
CPU:
  Info: 8-core model: AMD Ryzen 7 5800H with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 1103 min/max: 403/4465 boost: enabled cores: 1: 1103
    2: 1103 3: 1103 4: 1103 5: 1103 6: 1103 7: 1103 8: 1103 9: 1103 10: 1103
    11: 1103 12: 1103 13: 1103 14: 1103 15: 1103 16: 1103 bogomips: 102212
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: ASUSTeK
    driver: nouveau v: kernel arch: Ampere pcie: speed: 8 GT/s lanes: 8 ports:
    active: none empty: DP-1 bus-ID: 01:00.0 chip-ID: 10de:2520
  Device-2: Advanced Micro Devices [AMD/ATI] Cezanne [Radeon Vega Series /
    Radeon Mobile Series] vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5
    pcie: speed: 8 GT/s lanes: 16 ports: active: HDMI-A-1,eDP-1 empty: none
    bus-ID: 06:00.0 chip-ID: 1002:1638 temp: 51.0 C
  Display: wayland server: Xwayland v: 24.1.12 compositor: gnome-shell
    driver: gpu: amdgpu display-ID: 0
  Monitor-1: HDMI-A-1 model: LG (GoldStar) ULTRAGEAR res: 1920x1080 dpi: 93
    diag: 604mm (23.8")
  Monitor-2: eDP-1 model: Najing CEC Panda 0x004d res: 1920x1080 dpi: 142
    diag: 395mm (15.5")
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.0.8 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir ACO DRM
    3.64 7.0.12-201.fc44.x86_64) device-ID: 1002:1638 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GA106 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 8 bus-ID: 01:00.1
    chip-ID: 10de:228e
  Device-2: Advanced Micro Devices [AMD/ATI] Renoir/Cezanne HDMI/DP Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
    lanes: 16 bus-ID: 06:00.1 chip-ID: 1002:1637
  Device-3: Advanced Micro Devices [AMD] Audio Coprocessor driver: N/A pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 06:00.5 chip-ID: 1022:15e2
  Device-4: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 06:00.6 chip-ID: 1022:15e3
  API: ALSA v: k7.0.12-201.fc44.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.6.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168
  IF: enp2s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2725
  IF: wlp3s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-3:3 chip-ID: 8087:0032
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.4
    lmp-v: 13
Drives:
  Local Storage: total: 1.38 TiB used: 54.56 GiB (3.9%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
    size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 48.9 C
  ID-2: /dev/nvme1n1 vendor: Samsung model: MZVLQ512HBLU-00B00
    size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 43.9 C
Partition:
  ID-1: / size: 380.9 GiB used: 41 GiB (10.8%) fs: btrfs dev: /dev/dm-0
    mapped: luks-f1764ad9-d568-4a88-a7c1-e04471f05827
  ID-2: /boot size: 1.8 GiB used: 697.7 MiB (37.9%) fs: ext4
    dev: /dev/nvme1n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 51.7 MiB (8.6%) fs: vfat
    dev: /dev/nvme1n1p1
  ID-4: /home size: 380.9 GiB used: 41 GiB (10.8%) fs: btrfs dev: /dev/dm-0
    mapped: luks-f1764ad9-d568-4a88-a7c1-e04471f05827
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 1.32 GiB (16.5%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 53.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 15.01 GiB
    used: 10.26 GiB (68.3%)
  Processes: 540 Power: uptime: 6h 53m wakeups: 2 Init: systemd v: 259
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 12
    Compilers: N/A Shell: pk-command-not running-in: ptyxis-agent inxi: 3.3.40

A bit of topic.
I have a Framework16 Laptop. It comes with a RZ717 wifi card that lots of people have/had the exact same issue as described above. The go to solution for resolving the problem in Linux was to replace it with the AX210 card.
I have got one sitting here that I purchased in case of. Never did have to install it.

My laptop actually came with mt7921e WIFI card, which i replaced myself for a similar issue with AX210 (bought it seeing its good reputation, since everyone was recommending to switch with it), now i am seeing issue with AX210 :rofl: (although the 1st time).

This line from your dmesg output seems to point at the root issue:

iwlwifi 0000:03:00.0: Microcode SW error detected. Restarting 0x0.
...
0x00000071 | NMI_INTERRUPT_UMAC_FATAL
0x2010120E | ADVANCED_SYSASSERT

There seems to be a firmware crash in the AX210’s UMAC. Is your firmware up-to-date? Running sudo dnf update linux-firmware should guarantee it is.

Did you alter your iwlwifi.conf yourself or did it come like that?

Yes Bryan its up to date.

iwlwifi conf is altered, as i mentioned in post I was trying to see if disabling powersave or wifi6 can help. But nothing helped so far.

You’re absolutely right about the file; sorry I missed that…

Before playing the whack-a-mole game of BIOS/UEFI settings and checking on kernel regressions, since you already altered that file perhaps try adding disable_11ax for the mvm module, too, and disabling 11ac as a further fallback while also enabling the swcrypto flag which is known to stabilize some AX210 instability.

sudo tee /etc/modprobe.d/iwlwifi.conf <<'EOF'
options iwlwifi disable_11ax=Y disable_11ac=Y swcrypto=1
options iwlwifi power_save=0
options iwlmvm power_scheme=1
EOF

sudo dracut --force

Then reboot and share the results…

It may also be the device firmware. Try running sudo fwupdmgr update and see if it might update any device firmware for you.

My system shows the same as yours for the AX210

Mine

  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725
  IF: wlp5s0 state: up mac: <filter>

The only difference I see is the pcie bus the device is attached to.

Please remove the file you created /etc/modprobe.d/iwlwifi.conf and reboot to see if there may be a difference. I do not have that modprobe.d file and have never seen an issue with my wifi.

Note also that this type issue may be affected by the AP as well. Routers/APs sometimes may fail and trigger intermittent network issues during the early stages.

Try showing the output from sudo dmesg | grep iwlwifi (and remember to mask out the MAC address) that will be shown with the line reading
base HW address:
Displaying the MAC address for any interface on a public forum increases the risk of malicious attack.

$ sudo dmesg | grep iwlwifi
[    6.546037] iwlwifi 0000:05:00.0: enabling device (0000 -> 0002)
[    6.548761] iwlwifi 0000:05:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000
[    6.548770] iwlwifi 0000:05:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000
[    6.548774] iwlwifi 0000:05:00.0: Detected Intel(R) Wi-Fi 6E AX210 160MHz
[    6.587506] iwlwifi 0000:05:00.0: loaded firmware version 89.735b75a4.0 ty-a0-gf-a0-89.ucode op_mode iwlmvm
[    6.923668] iwlwifi 0000:05:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[    6.923688] iwlwifi 0000:05:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    6.923701] iwlwifi 0000:05:00.0: WFPM_AUTH_KEY_0: 0x90
[    6.923719] iwlwifi 0000:05:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[    6.923734] iwlwifi 0000:05:00.0: Detected RF GF, rfid=0x10d000
[    7.013755] iwlwifi 0000:05:00.0: base HW address: XX:XX:XX:XX:XX:XX
[    7.065934] iwlwifi 0000:05:00.0 wlp5s0: renamed from wlan0
[   11.199599] iwlwifi 0000:05:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[   11.199617] iwlwifi 0000:05:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[   11.199636] iwlwifi 0000:05:00.0: WFPM_AUTH_KEY_0: 0x90
[   11.199651] iwlwifi 0000:05:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[   11.497822] iwlwifi 0000:05:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[   11.497845] iwlwifi 0000:05:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[   11.497860] iwlwifi 0000:05:00.0: WFPM_AUTH_KEY_0: 0x90
[   11.497874] iwlwifi 0000:05:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0

I see that the firmware version you are loading is different than mine

[ 1296.968657] iwlwifi 0000:03:00.0: Loaded firmware version: 89.123cf747.0 ty-a0-gf-a0-89.ucode

This means the suggestion above to ensure the firmware is fully up to date is valid.
sudo dnf upgrade linux-firmware should ensure you have the latest available versions.

I have to ask if your system is allowed to auto-suspend? By default fedora performs an auto-suspend at the 15 minute mark when idle (defined as no keyboard or mouse input). The auto suspend will disable the wifi and can mean it must be manually reconnected.

The original post is for Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a). There are a few other AX210 “rev 1a” mentions, so it appears to a “unicorn”.

You tell us that wifi sometimes have problem between lines I find that you using dual boot with windows and could cause interference with linux kernel .To test go to windows and properly shutdown yours windows .Don’t reset do shutdown ,Boot system and in grub menu chose fedora .Test your wifi like that .

My windows is always properly shutdown and fast startup is disabled as well.

Also another thing worth mentioning i guess is:
This seems to be more of a AccessPoint + firmware issue, because I tried with my Mobile’s wifi 6 hotspot and the WIFI works stable on Fedora.

So for now, what i have done is from this Wifi 6E router that is causing trouble with this current fedora’s linux fw, i have created another AP using a spare router (which is dual band). And both bands from this another AP works fine.

But we can’t just pin it on the Wifi6 AP, because it used to work fine on Manjaro and is also working fine on Windows 10, 11.

Some AP’s advertise features that don’t actually work. Some distros may not support those features. What AP are you using?
See https://wiki.archlinux.org/title/Network_configuration/Wireless section 6.6.4.

Looks like a driver or firmware problem. But confirm that this is the error you get when you get the connection drop. You’ll have to report it upstream. See relevant info here: Bugs and support — Linux Wireless documentation

What driver version?