I’m having the exact same issue with a Dell Precision 5560, Fedora 36, and Linux kernel version 6.0.5-200. Luckily when I installed this laptop fresh the other day it installed with Linux kernel 5.17.5-300 and the wireless drivers load and work correctly. You should have more than one Linux Kernel version available at the grub boot menu and maybe you’ll get lucky and one of those still functions. I’ll update if I find a work-around and get the wireless running with kernel 6.0.
In my case i’ve tried last kernel version available at fedora (v6.0.5) but didn’t work
I’ve tried too, fedora 37 beta, fedora rawhide, rocky linux v9, and Ubuntu 22.10 with same result, and showing exactly the same error…but surprise, surprise…works flawlessly with Manjaro distro (arch based)
Wow you tried many distros. Do you know what kernel version you are running with Manjaro? I had a different issue with older kernels. At the moment 5.17 is a sweet spot on Fedora. I’ll keep an eye on that RedHat bug. Thank you for updating.
Also having the same issue as mentioned by @mutenroid (identical dmesg output) on a Dell Latitude 7750 with the Intel AX201 on newer kernels, on Ubuntu, so it isn’t Fedora-specific. 5.15 works, but I will try 5.16 and 5.17 soon. 5.18 and later all fail, whether mainline, xanmod (what I usually use) or provided by canonical.
Found a suggestion elsewhere for the AX211 or 212 that said to grab the latest firmwares from intel and add them to the /lib/firmware folder, but that seems to make no difference (yes, I got the appropriate ones for the 201).
Have you tried Linux Hardware Org? Fedora provides their hw-probe tool that creates an anonymous database for your machine and adds it their database.
The difference between Arch and Fedora could be as simple as different module parameters (maybe configured in /etc/modprobe.d).
To understand the issue you should compare details between Arch and Fedora. Intel wifi drivers have had issues with some hardware (bluetooth or IPv6 are examples). The iwlwifi module has options that can be used to disable broken functionality. For Federa 37 with 6.0.8-300.fc37.x86_64 kernel:
% modinfo iwlwifi | grep '^parm:'
parm: debug:debug output mask (uint)
parm: swcrypto:using crypto in software (default 0 [hardware]) (int)
parm: 11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)
parm: amsdu_size:amsdu size 0: 12K for multi Rx queue devices, 2K for AX210 devices, 4K for other devices 1:4K 2:8K 3:12K (16K buffers) 4: 2K (default 0) (int)
parm: fw_restart:restart firmware in case of error (default true) (bool)
parm: nvm_file:NVM file name (charp)
parm: uapsd_disable:disable U-APSD functionality bitmap 1: BSS 2: P2P Client (default: 3) (uint)
parm: enable_ini:0:disable, 1-15:FW_DBG_PRESET Values, 16:enabled without preset value defined,Debug INI TLV FW debug infrastructure (default: 16)
parm: bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
parm: led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
parm: power_save:enable WiFi power management (default: disable) (bool)
parm: power_level:default power save level (range from 1 - 5, default: 1) (int)
parm: disable_11ac:Disable VHT capabilities (default: false) (bool)
parm: remove_when_gone:Remove dev from PCIe bus if it is deemed inaccessible (default: false) (bool)
parm: disable_11ax:Disable HE capabilities (default: false) (bool)
If Arch is using a one of these the setting should be in /sys/module/ilwifi/parameters/<parameter>.
If you find you can’t get wifi whttps://linux-hardware.org/ithout disabling a functionality you need, you should consider replacing your wifi hardware. Good Intel wifi cards are readily available. The Linux Hardware Database may help you find a model that meets our needs.
Do both systems use the same wifi hardware? Have you generated linux-hardware.org probes for the systems? They have a probe for Thinkpad X1 Carbon Gen 10 with a Mediatek wireless controller (14c3:4d75:1cf8:3502), but your first system seems to have Intel wifi.
I’m wondering if you have a bad wifi card. Can you swap it with the one that works? A visual inspection/comparison could reveal some damage or even different chips on the two cards (vendors sometimes change the hardware without changing the model name).
This seems a reasonable troubleshooting test.
If you swap the cards and the problem shifts to the other machine then it seems hardware related. Possibly the chipset is giving the kernel the wrong info so it loads the wrong driver version.
If the problem does not shift then it seems driver or firmware related in the software loaded on the system.
The output of lspci would indicate those chipsets should be the same but that command is not definitive in the results. Merely a point of reference.
Additional info that may reveal deeper differences is available with lspci -nn -vv or just after a reboot with a perusal of the output of dmesg or journalctl -b 0 for relevant data in loading the firmware and driver for that card.
You also could use modinfo iwlwifi to look for differences on the 2 machines.