Hi, everyone. I’m very new to Fedora and Linux in General. I recently installed Fedora 42 (dual boot) on a new laptop and the WiFi isn’t working. In settings, there are no options for wireless internet connection, but bluetooth is working fine.
But nmcli dev doesn’t show my wifi as an option:
DEVICE TYPE STATE CONNECTION
enp0s20f0u3 ethernet connected Wired connection 1
lo loopback connected (externally) lo
I found error message:
sudo dmesg | grep iwlwifi
[ 2.815711] iwlwifi 0000:00:14.3: enabling device (0000 → 0002)
[ 2.817922] iwlwifi 0000:00:14.3: Detected crf-id 0x501, cnv-id 0x80930 wfpm id 0x80005b30
[ 2.817931] iwlwifi 0000:00:14.3: PCI dev 7740/0244, rev=0x461, rfid=0x10c000
[ 2.817936] iwlwifi: No config found for PCI dev 7740/0244, rev=0x461, rfid=0x10c000
[ 2.817967] iwlwifi 0000:00:14.3: probe with driver iwlwifi failed with error -22
What i’ve tried:
Update firmware with sudo dnf install linux-firmware
Disable secure boot
Disable fastboot
Additional information:
Windows 11 list my network device as Intel® Wi-Fi 6 AX101, but it doesn’t match with the code listed on linux (Intel Corporation Device [8086:7740])
We had a thread just a couple of days ago where it was the Microsoft fastboot option that was preventing WiFi from working. That would be my first recommendation for testing, since the device clearly works on Windows and AX101 is supported under Linux by the iwlwifi driver. You can see under the Network section of your inxi output that it hasn’t loaded the driver (returning N/A as output).
Is that the only controller seen for any form of network connectivity? Is there nothing that shows Wi-Fi or WiFi in the description?
I have never seen an intel chipset that says Ethernet and at the same time uses iwlwifi.
I also have never seen one that shows no form of Wi-Fi in the name but uses iwlwifi.
I have 3 different systems, one of which is a laptop, and all show both an Ethernet controller (wired) and a Network controller (wifi).
@tobp03: Does your laptop have an Ethernet port? Years ago Apple removed Ethernet ports from some systems but would sell Firewire Ethernet adapters, so it would not surprise me that other thin and light laptops are removing Ethernet ports. Alas, given Intel’s financial situation, it should not be a surprise that Intel’s Linux networking support is not up the standard we have seen in the past.
Years ago I sometimes extracted firmware blobs from Windows for use in Linux. I assume WiFi is working in Windows, but some research would be needed to see if it would be possible to get the right firmware. It is not unusual to have problems with network, sound, and/or video when new kernels first appear. You might consider adding a USB WiFi dongle while waiting to get the internal WiFi working and for the next time it fails after updating.
Yes, I’ve checked through the entire list, this is the only network controller on my device. @gnwiii is right on the mark about my laptop having no Ethernet port, so it’s a bit strange that Devicename says Ethernet.
I’m sharing the full copy of lspci -nnk in case you need it
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:7d20] (rev 05)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: igen6_edac
Kernel modules: igen6_edac
00:02.0 VGA compatible controller [0300]: Intel Corporation Arrow Lake-P [Intel Graphics] [8086:7dd1] (rev 03)
DeviceName: Onboard - Video
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: i915
Kernel modules: i915, xe
00:04.0 Signal processing controller [1180]: Intel Corporation Meteor Lake-P Dynamic Tuning Technology [8086:7d03] (rev 05)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: proc_thermal_pci
Kernel modules: processor_thermal_device_pci
00:06.0 PCI bridge [0604]: Intel Corporation Meteor Lake-H/U PCIe Root Port #10 [8086:7eca] (rev 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: pcieport
00:08.0 System peripheral [0880]: Intel Corporation Device [8086:774c]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
00:0a.0 Signal processing controller [1180]: Intel Corporation Meteor Lake-P Platform Monitoring Technology [8086:7d0d] (rev 01)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: intel_vsec
Kernel modules: intel_vsec
00:0b.0 Processing accelerators [1200]: Intel Corporation Meteor Lake NPU [8086:7d1d] (rev 05)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:20bf]
Kernel driver in use: intel_vpu
Kernel modules: intel_vpu
00:0d.0 USB controller [0c03]: Intel Corporation Meteor Lake-P Thunderbolt 4 USB Controller [8086:7ec0] (rev 10)
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:201f]
Kernel driver in use: xhci_hcd
00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation [8086:7d0b]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: vmd
Kernel modules: vmd
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:777d]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:201f]
Kernel driver in use: xhci_hcd
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:777f]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
00:14.3 Network controller [0280]: Intel Corporation Device [8086:7740]
DeviceName: Onboard - Ethernet
Subsystem: Intel Corporation Device [8086:0244]
Kernel modules: iwlwifi
00:15.0 Serial bus controller [0c80]: Intel Corporation Arrow Lake-H [Serial IO I2C Host Controller] [8086:7778]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: intel-lpss
00:15.2 Serial bus controller [0c80]: Intel Corporation Arrow Lake-H [Serial IO I2C Host Controller] [8086:777a]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: intel-lpss
00:15.3 Serial bus controller [0c80]: Intel Corporation Arrow Lake-H [Serial IO I2C Host Controller] [8086:777b]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: intel-lpss
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:7770]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:7702]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:7728]
DeviceName: Onboard - Sound
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: sof-audio-pci-intel-mtl
Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:7722]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:7723]
DeviceName: Onboard - Other
Subsystem: ASUSTeK Computer Inc. Device [1043:1fe3]
01:00.0 Non-Volatile memory controller [0108]: Sandisk Corp WD PC SN5000S M.2 2280 NVMe SSD (DRAM-less) [15b7:5036]
Subsystem: Sandisk Corp WD PC SN5000S M.2 2280 NVMe SSD (DRAM-less) [15b7:5036]
Kernel driver in use: nvme
Kernel modules: nvme
I understand, thanks for notifying me about this. I’m using a USB WiFi dongle right now to write this post, but it’s a bit inconvenient to carry it everywhere I go.
Yes, WiFi works fine in Windows, so would you recommend trying to extract the firmware from there? I’m still new to this, so I’m not sure how difficult that would be.
I also tried installing Ubuntu on this device, but WiFi doesn’t work there either. Do you think using an older kernel might fix the issue?
Check the LHDB using the USB vendor and model: 8086:a370 for probes where WiFi is shown as “Working”.
This issue may only be that the required firmware isn’t available on linux, or was released with some non-free license. The delay could be just a result of Intel’s “spinoff” of the networking unit and layoffs, or there may be some technical problem with differences between Windows and Linux.
I would also recommend updating your BIOS. You’re currently on 304 according to inxi output, while 308 seems to be the latest. Unfortunately Asus don’t have very enlightening change-logs for their BIOS, so no idea what was changed, but it’s worth updating. Same with firmware for your wifi card.
Having looked through the kernel bugzilla, there’s only three entries for AX101 cards, but plenty for AX*** devices which seem to get patched pretty quick. Many of the errors are about failing to probe properly and failing to find a conf file which is precisely in line with the last two lines of your dmesg output in the first post.
From what I’ve read on the Kernel bugzilla this is because of a failure to reset the device properly when switching between Windows and LInux and vice versa. Fastboot is one of the causes, AMT can be another cause if it’s on the chip/bios. And if the card has any power saving capabilities in Windows then it’s possible they’re causing issues when rebooting.
One solution is to remove currently loaded iwlmvm and iwlwifi firmware and reload just the iwlwifi firmware with modprobe and then use dracut -f to rebuild the initramfs to put iwlwifi further down the boot probing process so its less likely to be skipped over.
From the time I spent reading the kernel bugzilla last night, they’re pretty much on top of iwlwifi bugs across the majority of AX*** devices.
If you ran Fedora from a Live CD/DVD or USB stick before you installed it and WiFi was working, this isn’t a iwlwifi issue, or a probing issue, this is once again a Windows dual boot issue and will have something to do with fastboot, amt or other functionality not cleanly giving up control over an interface.
Exactly. Very good point. Always test WiFi from the USB live image.
In my own case the very first thing I had to do was to disable both “secure boot” and “fast boot” because otherwise I couldn’t even finalize the installation and, figure, the laptop came with Ubuntu preinstalled!
Which brings us to the usual major issue, “linux” supported hardware or why the PC vendors don’t provide “linux” models. All it takes to ruin the day is a WiFi card that does not work.
Vendors or vendor sub-units that target consumers with low-priced models look for cheapest components. Neither the low-end system vendor nor the component supplier invest in linux support, so whether Linux works is a lottery, and you have to rely on the Linux “hobbyist” community to solve issues.
Large vendors have a range for model “grades”: consumer, gaming, enterprise, etc.
Running Linux on “consumer” or “gaming” models often requires some searching for drivers or swapping components. Enterprise grade models often have longer model runs and are available with Linux pre-installed, or without OS Pre-installed linux often includes drivers that are not yet in Linux distros.
New systems that have Windows pre-installed may not get Linux drivers until months after release. Many Linux users find models that sold at a discount when a new model is introduced, or “reconditioned” models from large enterprises that reduced staff or upgraded work well. They will have multiple probes in the LHDB so you can see if any components are problematic as well as being much cheaper than new models.
Yes but I am not that sure about it.
For example I bought this very cheap Inspiron from Dell (celeron for about 250 euros that is about 300 US dollars I think) and like I said it came with Ubuntu preinstalled.
My guess is the issue with “linux” is more with brand new hardware but it is less problematic with hardware that has been sold for a while already.
So I think it is more about selling “new stuff” that works only with Windows or “new stuff” that is specifically selected for “linux” compatibility but the big firms could also sell “not-so-new” models that would be both cheaper and more “linux” compatible.
Less margin, then.
[ 3.404798] Intel(R) Wireless WiFi driver for Linux
[ 3.404866] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 3.433320] iwlwifi 0000:00:14.3: Detected crf-id 0x3617, cnv-id 0x20000302 wfpm id 0x80000000
[ 3.433345] iwlwifi 0000:00:14.3: PCI dev 4df0/0244, rev=0x351, rfid=0x10c000
[ 3.433469] iwlwifi 0000:00:14.3: firmware: failed to load iwlwifi-QuZ-a0-hr-b0-77.ucode (-2)
[ 3.433484] iwlwifi 0000:00:14.3: firmware: failed to load iwlwifi-QuZ-a0-hr-b0-77.ucode (-2)
[ 3.433486] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-77.ucode failed with error -2
...
[ 3.439249] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[ 3.439808] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 3.439819] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 3.439823] iwlwifi 0000:00:14.3: loaded firmware version 72.daa05125.0 QuZ-a0-hr-b0-72.ucode op_mode iwlmvm
From this the system actively tried to load multiple firmware versions, failing until it found a compatible one: QuZ-a0-hr-b0-72.ucode.
Now compare that to my dmesg output:
[ 2.817936] iwlwifi: No config found for PCI dev 7740/0244, rev=0x461, rfid=0x10c000
It seems that my system didn’t even attempt to load any firmware. Instead, it immediately reported that no configuration was found for my device. I think the system might not know which firmware it should use.
Hmm my approach is different and theory. If you dual boot with windows you need go to windows and properly shutdown make sure fast boot is disabled and after that you do boot your system press shift button that appear grub boot options select fedora kernel and boot it .Check your Wi-Fi