Description of problem: iwlwifi firmware (iwlwifi-7260-10.ucode) version 23.10.10.0 is available (requires kernel 3.17+). Version-Release number of selected component (if applicable): iwl7260-firmware-25.222.9.0-41.fc20.noarch linux-firmware-20141013-41.git0e5f6377.fc20.src.rpm How reproducible: Always. Steps to Reproduce: 1. modprobe iwlwifi Actual results: iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7260-10.ucode failed with error -2 iwlwifi 0000:01:00.0: loaded firmware version 25.228.9.0 op_mode iwlmvm Expected results: iwlwifi 0000:01:00.0: loaded firmware version 23.10.10.0 op_mode iwlmvm Additional info: http://wireless.kernel.org/en/users/Drivers/iwlwifi [...] http://wireless.kernel.org/en/users/Drivers/iwlwifi?action=AttachFile&do=get&target=iwlwifi-7260-ucode-23.10.10.0.tgz
We only take firmware from the linux-firmware git tree upstream. When it gets in that tree, we'll update. Also, it's kind of terrible that the version number for newer firmware is actually smaller than the previous release. This is going to cause a headache because of RPM version comparison.
Maybe we could just stop doing separate iwl*-firmware rpms and just provide those images in linux-firmware.rpm like other blobs.
Yeah... that was the original intention when we merged them into the linux-firmware package. However, someone complained that they didn't need any of them installed before, and adding it all into linux-firmware would be a 'regression'. I'm getting tired of the headache of dealing with them split out though.
I think we should stop splitting them as well.
(In reply to Josh Boyer from comment #1) > We only take firmware from the linux-firmware git tree upstream. When it > gets in that tree, we'll update. FWIW it seems to be working well. I haven't noticed any regressions. > Also, it's kind of terrible that the version number for newer firmware is > actually smaller than the previous release. This is going to cause a > headache because of RPM version comparison. You could add Epoch: equal to ucode version. The latest in Fedora contains ucode level 9 while latest from Intel seems to be ucode level 10 and is loadable only with kernels 3.17+. It seems half-hearted to split only some of the firmwares into separate packages. It might be more work to maintain, but I'd split all firmwares into separate subpackages and keep linux-firmware as a meta-package requiring all it used to contain.
I'm aware of how Epoch works, but thank you for the suggestion. We won't be splitting any more firmware out. If anything, we'll consolidate it into the main package.
I've fixed this in Fedora git. Rawhide should have a build of it show up whenever it composes again. F21 will get an update submitted shortly and F20 a bit after that.
linux-firmware-20150115-42.git78535e88.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/linux-firmware-20150115-42.git78535e88.fc21
Package linux-firmware-20150115-42.git78535e88.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing linux-firmware-20150115-42.git78535e88.fc21' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-0793/linux-firmware-20150115-42.git78535e88.fc21 then log in and leave karma (feedback).
linux-firmware-20150115-42.git78535e88.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.