Red Hat Bugzilla – Bug 504626
Wireless 4965AGN: only 802.11b appears to be working (no 802.11a or 802.11n; 5.8ghz)
Last modified: 2009-06-08 11:37:41 EDT
Created attachment 346887 [details]
Dmesg output from a boot with the new kernel.
Description of problem:
Prior to upgrading Fedora I usually try the future kernel to verify basic hardware compatibility. I upgraded my F10 Thinkpad x61t to 18.104.22.168-168.fc11.x86_64 from Koji and discovered that I could no longer connect or even see to my 802.11a wireless access point using the internal 4965AGN wireless card. 802.11b networks appeared in the list as normal.
I didn't notice any obvious warnings or errors in the logs or dmesg.
Version-Release number of selected component (if applicable):
Linux version 22.214.171.124-168.fc11.x86_64 (firstname.lastname@example.org) (gcc version 4.4
.0 20090506 (Red Hat 4.4.0-4) (GCC) ) #1 SMP Tue Jun 2 17:21:41 EDT 2009
(this firmware works fine with my F10 kernel)
Upgrade to kernel-126.96.36.199-168.fc11.x86_64 and observe that only 802.11b is working
Steps to Reproduce:
0. Obtain x61t with intel 4965 wireless card and an 802.11a network.
1. Upgrade to kernel-188.8.131.52-168.fc11.x86_64.
2. Discover that you can't see your 802.11a AP but you can see 802.11b APs.
3. Be grateful that you tried the new kernel before upgrading Fedora.
It doesn't work.
iwlist freq output:
wlan1 11 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
Current Frequency:2.437 GHz (Channel 6)
wlan1 IEEE 802.11abgn ESSID:"NETGEAR"
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
("NETGEAR" is one of the neighbours APs, I guess)
full dmesg of the boot is attached.
"cfg80211: Calling CRDA to update world regulatory domain"
You should install the crda package:
yum install crda
Also, ensure that you have set your timezone correctly with system-config-date -- the timezone is used to select the appropriate regulatory domain.
Once crda is installed, "iw reg set US" (or other 2-letter country code as appropriate) should get things working OK for you.
Thank you so much for the prompt and helpful response. Your suggestion resolved my problem.