>have Intel Wi-Fi
>the driver loads a firmware file /lib/firmware/intel/iwlwifi/iwlwifi-9260-th-b0-jf-b0-46.ucode
>the device is integrated to the motherboard and therefore always there
>decide to compile the driver into the kernel image (say "yes" instead of "module") and embed the said firmware file
CONFIG_IWLWIFI=y
CONFIG_EXTRA_FIRMWARE="intel/iwlwifi/iwlwifi-9260-th-b0-jf-b0-46.ucode"
>reboot
>fails to find the firmware file ("error -2" on "iwlwifi-9260-th-b0-jf-b0-46.ucode" (note that it didn't say any directory names))
>move the firmware file from /lib/firmware/intel/iwlwifi to /lib/firmware and recompile with
CONFIG_EXTRA_FIRMWARE="iwlwifi-9260-th-b0-jf-b0-46.ucode"
>works
So. Having Intel Wi-Fi support as a module file (like normal people usually do) makes it look for firmware from /lib/firmware/intel/iwlwifi. But when you bake it into the image it suddenly looks for the firmware from the root of the firmware directory.
Feature or a bug?
>>108521374
Aren't guinea pigs getting all the new stuff?
Comment too long. Click here to view the full text.