Hi all,

Noticed iwlwifi is looking for a firmware specific to the wnic I have.
The latest firmware iwlwifi is looking for is -69
Looking into /lib/firmware, I see version -71 is available.
How do I go about getting iwlfifi to load version -71?

Not that I wouldn't mind recompiling a new kernel... but knowing if loading/unloading a specific firmware for testing could be useful.

Thanks in advance

AFAIK, the firmware is loaded by the kernel module (driver) for your card. Unloading and then reloading the module with the new firmware in /lib/firmware should suffice.

You will most likely have to deactivate the wireless interface before the kernel will allow you to unload the module. Also, remember to create a backup of the old firmware file first.

1 members found this post helpful.

It should but that didn't work.
It must be hardcoded somewhere.

yvesjv --

Curious ...

How can you tell that version -71 would be better for your WiFi than version -69 ?

Thanks !

-- kjh

Good question but I'm after a different quest.
There is a request for assistance at https://www.linuxquestions.org/quest...-a-4175704711/
Appears it works with some kernels and not with others.
Would be nice if we could be a bit granular and specify which firmware to load.

I think I'm going to compile 5.18.x and install but before doing so, first edit the file '22000.c' by giving it a bogus but higher value than the default of 72.

Hmm. If I'm not mistaken it doesnt work like that. Specific firmware is only for specific version of the Kernel driver. So you can't use firmware version Y with driver version X or firmware version X with driver version Y. You can only use X on X and Y on Y. Where both firmware and driver version is a range of versions, not only a specific one.

Which basically means you don't have to worry about it unless you run a newer Kernel and it fails to load an old firmware. And well, sometimes there could be a new firmware version for an old driver, but as long as it works, you don't really need to worry about it, unless there is a specific fix to a serious issue. In which case you would probably have to update both anyways.

Yeah, in the driver.

2 members found this post helpful.

Yes, did test it and it looks like it is hardcoded.
Raising the max value inthe file 22000.c before compiling does work but if the kernel doesn't recognise the hardware, that is not going to help.
Looks like flashy new hardware = new kernel + new flashy drivers.

Thanks for the input.
I'm closing this request.

1 members found this post helpful.