When booting, this is what journalctl -b | grep "kernel: iwlwifi" says:
kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
kernel: iwlwifi: No config found for PCI dev 7af0/1692, rev=0x430, rfid=0x3010d000
kernel: iwlwifi: probe of 0000:00:14.3 failed with error -22
Running sudo modprobe iwlwifi yields no outputā¦
From searching this is supposedly the AX411 Linux driver? This should have been merged into 5.14 but it does not work in 5.19 for meā¦ I tried numerous attempts into copying the entire firmware binaries into /lib/firmware from linux-firmware repoābut nothing has worked yetā¦
I did make sure that fastboot was disabled in my BIOS. Also, I did happen to try the Manjaro 22 6.0 kernel stable release-review as well but got the same result with my WIFI card not being detected and iwlwifi not loading. Other searches indicated that 5.17 kernel worked for some, but if that was the case, it should work for me with 5.19. It might be a BIOS setting or a combination of settings, but I do not know which one(s). This is not a dual-boot machine eitherāstrictly Manjaro all the way.
Gonna add more command line candy if it helps anyā¦ inxi -N yields the following:
I looked for iwlwifi-next but I could not locate the package, e.g. pacman -Ss iwlwifi-next yields nothing. I checked in the AUR, and it still does not build. Last comment was 02/2022 stating it still does not build 2.5 years later after general availability in the AUR.
Just an update for those experiencing the same or similar issue.
I have tried the following kernels: linux519 (EOL) do not use linux515 linux60
and none of them to worked for me.
I also tried to adjust BIOS settings but did not get anywhere with that either. Fastboot is not enabled for me but that did not make a difference unfortunatelyā¦
this should be line 673. I added AX1690s just for gigglesā¦
I am using linux60 to build a custom kernel and modules.
From the boot logs my WIFI card dev and subdev are 0x7AF0 and 0x1692 and that seems to be the main issue.
Installed custom kernelāand all works fine now. I am guessing this hardware is too new? Some Intel driver maintainer needs to make sure this makes it into upstreamā¦