I have a new laptop with a Intel Raptor Lake PCH CNVi Wifi module (as reported by inxi).
The wifi worked during the Anaconda install, downloading a custom system via the F44 Everything installer.
On booting the system properly post install, the wifi does not work, and inxi reports the driver as n/a.
I have linux-firmware and iwlwifi drivers installed.
Why would Anaconda be able to the the module, but a custom install not?
The installer makes setup easy, but the everything installer does not enable wifi on the installed system unless the user selects to install NetworkManager and the appropriate other packages such as wpasupplicant. I think it does enable wired ethernet but not wifi.
Good suggestion, but
I have Network_Manager and wpa_supplicant installed.
Any other packages you can think of?
USB tethering from my phone is also working, and I will assume ethernet is as the driver is showing up properly.
I installed
iwlwifi-dvm-firmware - DVM Firmware for Intel(R) Wireless WiFi adapters
iwlwifi-mvm-firmware - MVM Firmware for Intel(R) Wireless WiFi adapters
and then rebooted
and it worked!
Thanks Jeff you inspired me in the right direction.
And thanks to CoreOS docs for providing the info
I have not tried a new bare bones install recently and definitely not with new hardware. The closest I could come for testing would be to do a new install into a VM with the everything installer but that would not be of benefit since it by default configures virtual networking to the host and not wifil
Looking at the outout of sudo dmesg to find where it tries to load a driver may provide some pointers. Similarly journalctl for the boot where the wifi failure occurred should provide some info.
You posted the solution while I was composing the above.
Glad to know you found the correct firmware packages (actually drivers?) for that adapter..
My guess is the firmware exposes the drivers to the OS, allowing the drivers to load.
Thanks again.
how would that work in real world?
check output of journalctl -b -k -g iwlwifi and modinfo -F firmware iwlwifi
user@fedora:~$ journalctl -b -k -g iwlwifi
Mar 29 19:09:26 fedora kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
Mar 29 19:09:26 fedora kernel: iwlwifi 0000:00:14.3: Detected crf-id 0x1300504, cnv-id 0x80400 wfpm id 0x80000030
Mar 29 19:09:26 fedora kernel: iwlwifi 0000:00:14.3: PCI dev 51f1/6074, rev=0x370, rfid=0x10a100
Mar 29 19:09:26 fedora kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz
Mar 29 19:09:27 fedora kernel: iwlwifi 0000:00:14.3: loaded firmware version 89.123cf747.0 so-a0-hr-b0-89.ucode op_mode iwlmvm
Mar 29 19:09:27 fedora kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
Mar 29 19:09:27 fedora kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Mar 29 19:09:27 fedora kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
Mar 29 19:09:27 fedora kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
Mar 29 19:09:27 fedora kernel: iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
Mar 29 19:09:27 fedora kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
Mar 29 19:09:27 fedora kernel: iwlwifi 0000:00:14.3: base HW address: e8:bf:e1:d2:6f:ea
Mar 29 19:09:27 fedora kernel: iwlwifi 0000:00:14.3 wlo1: renamed from wlan0
Mar 29 19:09:29 fedora kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
Mar 29 19:09:29 fedora kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Mar 29 19:09:29 fedora kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
Mar 29 19:09:29 fedora kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
Mar 29 19:09:29 fedora kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
Mar 29 19:09:29 fedora kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
Mar 29 19:09:29 fedora kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Mar 29 19:09:29 fedora kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
Mar 29 19:09:29 fedora kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
Mar 29 19:09:29 fedora kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
user@fedora:~$ modinfo -F firmware iwlwifi
iwlwifi-100-5.ucode
iwlwifi-1000-5.ucode
iwlwifi-135-6.ucode
iwlwifi-105-6.ucode
iwlwifi-2030-6.ucode
iwlwifi-2000-6.ucode
iwlwifi-5150-2.ucode
iwlwifi-5000-5.ucode
iwlwifi-6000g2b-6.ucode
iwlwifi-6000g2a-6.ucode
iwlwifi-6050-5.ucode
iwlwifi-6000-6.ucode
iwlwifi-7265D-29.ucode
iwlwifi-7265-17.ucode
iwlwifi-3168-29.ucode
iwlwifi-3160-17.ucode
iwlwifi-7260-17.ucode
iwlwifi-8265-36.ucode
iwlwifi-8000C-36.ucode
iwlwifi-9260-th-b0-jf-b0-46.ucode
iwlwifi-9000-pu-b0-jf-b0-46.ucode
iwlwifi-cc-a0-77.ucode
iwlwifi-gl-c0-fm-c0-c101.ucode
iwlwifi-gl-b0-fm-b0-c101.ucode
iwlwifi-bz-a0-fm4-b0-c101.ucode
iwlwifi-bz-a0-fm-c0-c101.ucode
iwlwifi-bz-a0-fm-b0-c101.ucode
iwlwifi-sc2-a0-wh-a0-c101.ucode
iwlwifi-sc2-a0-fm-c0-c101.ucode
iwlwifi-sc-a0-wh-a0-c101.ucode
iwlwifi-sc-a0-fm-c0-c101.ucode
iwlwifi-sc-a0-fm-b0-c101.ucode
iwlwifi-dr-a0-pe-a0-c101.ucode
iwlwifi-so-a0-jf-b0-77.ucode
iwlwifi-QuZ-a0-jf-b0-77.ucode
iwlwifi-Qu-c0-jf-b0-77.ucode
iwlwifi-Qu-b0-jf-b0-77.ucode
iwlwifi-sc-a0-hr-b0-100.ucode
iwlwifi-sc-a0-hr-b0-100.ucode
iwlwifi-bz-a0-hr-b0-100.ucode
iwlwifi-ma-b0-hr-b0-100.ucode
iwlwifi-ma-a0-hr-b0-100.ucode
iwlwifi-so-a0-hr-b0-100.ucode
iwlwifi-QuZ-a0-hr-b0-100.ucode
iwlwifi-Qu-c0-hr-b0-100.ucode
iwlwifi-Qu-b0-hr-b0-100.ucode
iwlwifi-sc-a0-gf4-a0-100.ucode
iwlwifi-sc-a0-gf-a0-100.ucode
iwlwifi-bz-a0-gf4-a0-100.ucode
iwlwifi-bz-a0-gf-a0-100.ucode
iwlwifi-ma-b0-gf4-a0.pnvm
iwlwifi-ma-b0-gf4-a0-100.ucode
iwlwifi-ma-a0-gf4-a0.pnvm
iwlwifi-ma-a0-gf4-a0-100.ucode
iwlwifi-ma-b0-gf-a0.pnvm
iwlwifi-ma-b0-gf-a0-100.ucode
iwlwifi-ma-a0-gf-a0.pnvm
iwlwifi-ma-a0-gf-a0-100.ucode
iwlwifi-ty-a0-gf-a0.pnvm
iwlwifi-ty-a0-gf-a0-100.ucode
iwlwifi-so-a0-gf-a0.pnvm
iwlwifi-so-a0-gf-a0-100.ucode
That is after the firmware was installed.
yes, but the driver requests the kernel to load a specific fw, The driver is already loaded and active, not the other way around – unless I misunderstood you.
Now compare with a journal log w/o the required firmware available.