Bug 903668
Summary: | Firmware fails to load on new kernels. Intel Wireless adaptor is not working. | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | cbindahouse | ||||||||
Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> | ||||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | urgent | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 19 | CC: | gansalmon, itamar, jonathan, kernel-maint, linville, madhu.chinakonda, sgruszka | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | |||||||||||
: | 980055 (view as bug list) | Environment: | |||||||||
Last Closed: | 2014-01-24 18:44:00 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
cbindahouse
2013-01-24 14:39:55 UTC
The driver name changed from iwlagn to iwlwifi. I'm not sure what workaround you mean, but maybe that helps? Anyway, I would need to see the output of dmesg to have any idea what the problem is with the firmware loading. Please run 'dmesg' and attach the output from that to this bug...thanks! Created attachment 686825 [details]
dmesg output on Fedora 18
Ok so the workaround of reverting to the old v3 code does still work, by doing something like sudo mv /lib/firmware/iwlwifi-1000-5.ucode /lib/firmware/iwlwifi-1000-5.ucode.backup However, this has been a temporary fix for the past nearly year and a half (see http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2314 which I reported on the Intel bugzilla). Firmware errors on load with iwlwifi-1000-5...Johannes, should we consider changing the driver to only ask for version 3? Is this a fix? V3 is not included by default any more, it has to be manually downloaded from the Intel website. Either firmware should be fixed or driver should be fixed to work with the new firmware. Does the problem still ocures on lates kernel i.e. 3.9 ? Yep, still broken on 3.10. Then, please load module with verbose debugging enabled, i.e. modprobe -r iwldvm modprobe iwlwifi debug=47ffffff and attach dmesg output. (In reply to Stanislaw Gruszka from comment #8) > modprobe iwlwifi debug=47ffffff It should be: modprobe iwlwifi debug=0x47ffffff Please also attach output of "lspci -vnn" Created attachment 783393 [details]
dmesg output with verbose debugging enabled
Created attachment 783394 [details]
output of "lspci -vnn"
Unfortunately dmesg buffer wrapped out so reason of microcode error at start is not visible. Please do the following to grab debug messages: Add this line in /etc/rsyslog.conf: kern.* /var/log/kernel Restart rsyslog: # systemctl restart rsyslog.service Unload module: # modprobe -r iwldvm Grab messages: # echo > /var/log/kernel # modprobe iwlwifi debug=0x0x47ffffff Again unload module: # modprobe -r iwldvm And attach /var/log/kernel file here. Could you please provide information requested in comment 13 ? *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those. We need logs requested in comment 13 ? closing due to lack of response |