Luca Coelho <luca@xxxxxxxxx> writes: >> [ 10.630285] iwlwifi 0000:04:00.0: firmware: failed to load >> iwlwifi-8265-34.ucode (-2) >> [ 10.630331] iwlwifi 0000:04:00.0: Direct firmware load for >> iwlwifi-8265-34.ucode failed with error -2 >> [ 10.630454] iwlwifi 0000:04:00.0: firmware: failed to load >> iwlwifi-8265-33.ucode (-2) >> [ 10.630479] iwlwifi 0000:04:00.0: Direct firmware load for >> iwlwifi-8265-33.ucode failed with error -2 >> [ 10.630486] iwlwifi 0000:04:00.0: firmware: failed to load >> iwlwifi-8265-32.ucode (-2) >> [ 10.630510] iwlwifi 0000:04:00.0: Direct firmware load for >> iwlwifi-8265-32.ucode failed with error -2 >> [ 10.636423] iwlwifi 0000:04:00.0: firmware: direct-loading >> firmware >> iwlwifi-8265-31.ucode >> [ 10.637463] iwlwifi 0000:04:00.0: loaded firmware version >> 31.532993.0 op_mode iwlmvm > > This is an unfortunate side-effect of the way firmwares are loaded. > There is currently no way to prevent these error messages by making > some files optional... But you can ignore them. Or, even better, > upgrade your firmware to the latest version the driver supports. :) Or even better that we improve request_firmware()&co to make it possible not to print an error message :) In ath10k we are also (again) suffering about the same problem due to: ath10k: activate user space firmware loading again https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c0cc00f250e19c717fc9cdbdb7f55aaa569c7498 -- Kalle Valo
