Nice.
I think that's iwlwifi-Qu-b0-hr-b0-50.ucode
Could you please post the greppings of dmsg and modinfo?

Edit:
I think I may have found where it is set.
Depending on your kernel version, the firmware version min and max values are set in the file linux-5.x.z/drivers/net/wireless/intel/cfg/22000.c

I looked into a few kernels I've downloaded and the values within the file are different:
Kernel series 5.17.12 shows the max as 69
kernel series 5.18.1 shows the max as 72
And kernel series linux-5.4.196 shows the max as 50
bash-5.1$ grep IWL_22000_UCODE_API_MAX linux-5.4.196/drivers/net/wireless/intel/iwlwifi/cfg/22000.c
#define IWL_22000_UCODE_API_MAX 50

I got my new desktop system running with intel ax200 built into motherboard. The default kernel for debian 11.3 and slackware 15 both work.

why my laptop wont work with intel ax200 using intel ngw or m.2 key E wont use anything newer 5.4.196 kernel beats me.

Has OP won the lotterry and left us hanging?

Just for fun, I compiled and installed the latest 5.18.x kernel
Before compiling I modified the file 22000.c and raised the max value to 92
Rebooted into the new kernel and it looks for the firmware starting at 92!
# dmesg | grep iwlwifi
[ 5.522858] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 5.530807] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-92.ucode failed with error -2
[ 5.530821] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-91.ucode failed with error -2
[ 5.530906] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-90.ucode failed with error -2
[ 5.530918] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-89.ucode failed with error -2
[ 5.530931] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-88.ucode failed with error -2
[ 5.530945] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-87.ucode failed with error -2
[ 5.530961] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-86.ucode failed with error -2
[ 5.530974] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-85.ucode failed with error -2
[ 5.530987] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-84.ucode failed with error -2
[ 5.531003] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-83.ucode failed with error -2
[ 5.531019] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-82.ucode failed with error -2
[ 5.531034] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-81.ucode failed with error -2
[ 5.531049] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-80.ucode failed with error -2
[ 5.531064] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-79.ucode failed with error -2
[ 5.531079] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-78.ucode failed with error -2
[ 5.531094] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-77.ucode failed with error -2
[ 5.531110] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-76.ucode failed with error -2
[ 5.531126] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-75.ucode failed with error -2
[ 5.531140] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-74.ucode failed with error -2
[ 5.531159] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-73.ucode failed with error -2
[ 5.531185] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-jf-b0-72.ucode failed with error -2
[ 5.533099] iwlwifi 0000:00:14.3: loaded firmware version 71.058653f6.0 QuZ-a0-jf-b0-71.ucode op_mode iwlmvm

The newest found in /lib/firmware/ is v71

Not that it will help with loading the firmware for a new WNIC if an entry for it doesn't exist in the drv.c file.

I dont know about QuZ firmware its not AX200's.

comparing the intel iwlwifi source particularly pcie drv.c

AX200 firmware is CC-A0 or 0A
though I do see a
under Qu firmware which means either someone put something in wrong place or Qu firmware is now for AX200. dont think so.

Havent code or scripted for years.
More worried about the kernel programmers. though I did sorta hijack the OP's thread.

Yeah, you should apologise to OP.
OP might come back.

OP please accept my apology for hijacking thread.

Mine too.
OP... please come back.

Hey yvesjv. Unfortunately, not. I haven't forgotten about this thread. I'm just too busy and find getting wireless to work to be so tedious. I'll be back as soon as I can. \o

using iwl instead of iwlwifi in dmesg and lsmod is better. iwlmvm loads too and messages a little info.

Hey OP whats going on?

try sending iwlmvm
option iwlmvm power_scheme=1
in file /etc/modprobe.d/iwlmvm.conf
youll have to create the file.

for people on laptop not the OP who has desktop
look for wmi files in lsmod if you see asus,hp,acer,lenovo laptop manufacture blacklist it as it will interfere with wireless and bluetooth hardware. specially if you want to use a add on m.2 key E device or similar on a laptop that with unoriginal hardware.

check bios and desktop manager settings for power saving features make sure you are not shutting stuff down part of some conservative power management.

I've recently purchased the ThinkPenguin 802.11N USB Wifi Adapter. At least now, I've a backup to my current WiFi USB adapter (Technoethical N300). both work fine in GNU/Linux.

I'm now on kernel 5.18.2-1~bpo11+1. The AX200 still doesn't work.

Try kernel 5.4.x
My laptop doesnt like anything past 5.4.x cause of code change afterwards.

Doubt my desktop would work with 5.18.x kernel supposed to have broken support. firmware crashing.

do a
sudo dmesg | grep iwl
sudo dmesg | grep firmware

My PC has 3 drives. I installed Fedora 36 on another drive. The AX200 WiFi card worked OOTB right after booting in.

I'll still use Debian 11 as my main OS but at least now, I know the AX200 WiFi works fine on Fedora and likely will work in Debian 12 without having to jump through hoops.

As mentioned before, I've 2 WiFi dongles that work OOTB in Debian 11 so that area is well covered.

so check which kernel and driver are in use on fedora