Apparently a recent upgrade of the Linux firmware packages has caused some Intel Wi-fi 6 AX 200 cards to stop working on Linux. These devices can be found on some motherboards like the Gigabyte X570 I AORUS PRO WIFI/X570 I.
For some reason, kernel/device/etc complains that the version of the firmware cannot be loaded. When looking at the dmesg output, you can spot a lot of messages similar to these:
iwlwifi 0000:06:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2 iwlwifi 0000:06:00.0: minimum version required: iwlwifi-cc-a0-39 iwlwifi 0000:06:00.0: maximum version supported: iwlwifi-cc-a0-64
I recently spotted this one on my pre-release Fedora 35 install.
I don’t know about any fix for it yet, but there is a good work-around by rolling back to the latest package and then using the versionlock plugin to prevent the update.
If you have an alternate way to get online (i.e.: by using a different network device), you can follow the steps below to work-around this issue.
First, rollback to the latest working package:
sudo dnf install -y iwl7260-firmware-188.8.131.52-122.fc35
Also make sure to keep a local backup of that RPM, in case you want to test future updates to that firmware package. You can do that with the dnf download:
sudo dnf download iwl7260-firmware-184.108.40.206-122.fc35
Then, install the dnf versionlock plugin:
sudo dnf install 'dnf-command(versionlock)'
Lastly, prevent that package from being upgraded:
sudo dnf versionlock iwl7260-firmware-220.127.116.11-122.fc35
Reboot and check if it is working.
If you don’t have an alternate way to get online, then use another computer to download the package from one of the Fedora mirrors. This is of the direct links, but it is not guaranteed to continue to work in the future.
Once you download the rpm file, save it on a USB disk and install it manually using the following command:
sudo rpm -ivh iwl7260-firmware-18.104.22.168-122.fc35.noarch.rpm
Hopefully this will be fixed soon and we all can enjoy the amazing Fedora 35 release.
I submitted a bug report about this.
Update 2: unfortunately Bugzilla is not very friendly, so there was another issue already opened which I couldn’t find.