FS#46197 - [linux] iwlwifi firmware loading fails with 4.2-1

Attached to Project: Arch Linux
Opened by Gaetan Bisson (vesath) - Friday, 04 September 2015, 05:16 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 04 September 2015, 12:47 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

With linux-4.1.6-1 once the kernel module iwldvm is loaded my wireless card (an Intel Centrino Ultimate-N 6300) is properly detected and configured. This is not the case with linux-4.2-1. See the attached kernel ring bugger output, dmesg.bad (with linux-4.2-1) versus dmesg.good (with linux-4.1.6-1).

It appears that microcode loading fails with linux-4.1.6-1:

iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000-6.ucode failed with error -2
iwlwifi 0000:03:00.0: Falling back to user helper

While it succeeds on the third attempt with linux-4.2-1:

iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000-6.ucode failed with error -2
iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000-5.ucode failed with error -2
iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 04 September 2015, 12:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.2-2
Comment by Gaetan Bisson (vesath) - Friday, 04 September 2015, 05:17 GMT
Please let me know if there is anything else I could do to help diagnose this.
Comment by Tobias Powalowski (tpowa) - Friday, 04 September 2015, 05:22 GMT
Firmware files are missing, will look at it.
Comment by Jan Alexander Steffens (heftig) - Friday, 04 September 2015, 08:24 GMT
Reopening; while the firmware I added is needed (in my case, iwlwifi-7260-15), this particular firmware (iwlwifi-6000-5 or -6) is still missing.
Comment by Jan Alexander Steffens (heftig) - Friday, 04 September 2015, 12:32 GMT
I believe the actual cause here is CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y, which should not be set since our udev has no firmware helper. The kernel waits forever for it to connect instead of failing the firmware load and letting the driver try the next one.

Loading...