Description of problem:
Yesterday (2012-02-05), there was an update to the crda package, from version 1.1.2 to 1.1.3_2013.01.11-1.fc17 on my Fedora 17 box. After the update and a reboot, the wireless stopped working. More specifically, no wireless networks were visible.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Update crda from 1.1.2 to 1.1.3
Wireless not working.
Even though iwconfig did list wlan0, I was not able to do a iwlist wlan0 scanning, it exited out with a "Interface doesn't support scanning." message.
I finally did a yum history undo <ID> to revert the update to the 1.1.2 package.
Sorry for the scarce information at the moment, but I will provide as much as information about the system before and after the update, as long as someone tells me what information should I provide.
This sounds rather strange -- more like a kernel problem than a crda issue.
Please post the output of running dmesg after a reboot, with both versions of the crda package. Also include the output of running ifconfig and iwconfig in both cases.
Do you have any special configuration being applied to your wireless device? If so, what would that be?
Please tell me about the configuration for the AP you normally use -- what channel is it on? What type of security does it use?
Also, what country are you in?
Created attachment 694061 [details]
dmesg with crda 112
Created attachment 694063 [details]
dmesg with crda 113
Created attachment 694064 [details]
ifconfig crda 112
Created attachment 694065 [details]
ifconfig crda 113
Created attachment 694066 [details]
iwconfig crda 112b
Created attachment 694067 [details]
iwconfig crda 113
Created attachment 694068 [details]
iwlist scanning crda 112
Created attachment 694069 [details]
iwlist scanning crda 113
Created attachment 694070 [details]
lsmod crda 112
Created attachment 694071 [details]
lsmod crda 113
Created attachment 694072 [details]
lspci crda 112
Created attachment 694073 [details]
lspci crda 113
Created attachment 694074 [details]
yum details about update
Attached everything you asked (and a bit more). Let me know if you need some other logs as well.
No special configuration. Just a regular "turn on computer, pick a wifi, let it connect, and surf" process. Everything is default as it came with Fedora 17.
This wireless network uses no security (neighbours wifi, heh). As for the channel, not sure if this is what you asked for, but iwlist wlan0 channel says channel 6, 2.437 GHz.
Country is Serbia.
Kernel is 3.7.3-101.fc17.x86_64.
Created attachment 694078 [details]
lspci -vv -s output for wireless
Just found how I can provide more details about the wireless driver, so I attached that one as well, with crda 1.1.2 only. Let me know if you need the same for crda 1.1.3, too.
Serbia is the issue. The regulatory rules database recently added a rule for Serbia, but it only defined the rules for the new 60GHz band. Previously I think you were living with the default "world" rules, and apparently your AP is later telling you that you are in the US. That causes your machine to use the US rules instead.
Actually, you are probably using the rules that the iwlwifi drivers determines are a match for your hardware, except that now the more restrictive rules for Serbia in the new database are restricting you to essentially nothing.
I'll try to straighten this out upstream. For now, stick with the crda 1.1.2 package.
Thanks. I will.
If you need help with testing stuff later on, let me know, I am more than happy to.
If you happen to have any way to determine the correct wireless regulatory rules for Serbia, that might be helpful too. :-)
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.