Bug 709803 - Cannot connect to 5GHz wifi
Summary: Cannot connect to 5GHz wifi
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stanislaw Gruszka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-01 16:56 UTC by a.m.suharev
Modified: 2011-08-22 14:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-22 14:23:17 UTC
Type: ---


Attachments (Terms of Use)
lspci -mm (3.19 KB, text/plain)
2011-06-06 15:49 UTC, a.m.suharev
no flags Details
/var/log/messages (99.19 KB, application/octet-stream)
2011-06-16 11:48 UTC, a.m.suharev
no flags Details
iw list (4.15 KB, application/octet-stream)
2011-06-16 16:12 UTC, a.m.suharev
no flags Details

Description a.m.suharev 2011-06-01 16:56:32 UTC
Description of problem:
New-installed F15 doesn't see 5GHz 802.11n wireless network. Very strange, but I've installed it using that network. Installer connected without any problem.

How reproducible:
Always. (Tried several installations both with i686 and x86_64.)


Steps to Reproduce:
1. Install F15 using netinst iso image via 5GHz 802.11n wireless network.
2. Boot it normally.
3. iwlist scan
  
Actual results:
A lot of wireless networks listed, all in 2.4GHz band. 

Expected results:
At least one 5GHz wireless network listed too.

Additional info:
Hardware: HP EliteBook 8440p, Intel Corporation Centrino Advanced-N 6200 (rev 35) wireless device, NetGear WNDR3700 dualband wireless router

F14 works fine in the same setup. (However I didn't try to reinstall it.) dmesg outputs in F14 and F15 seems to have no significant differences to me.

Comment 1 wey-yi.w.guy 2011-06-06 14:18:36 UTC
what firmware version you are using?

Wey

Comment 2 a.m.suharev 2011-06-06 15:19:37 UTC
According to dmesg it is firmware version 9.221.4.1 build 25532 both in F14 and F15.

Comment 3 wey-yi.w.guy 2011-06-06 15:27:22 UTC
ok, then my next question will be what the PCI subsystem id is?
COuld you do the following:
#lscpi -mm


Thanks
Wey

Comment 4 a.m.suharev 2011-06-06 15:49:51 UTC
Created attachment 503261 [details]
lspci -mm

Comment 5 wey-yi.w.guy 2011-06-06 16:07:34 UTC
hmm, it is strange, work on F14 but not F15 with the same firmware.

If you load the module with debug=0x40, then check the dmesg log. it should give you all the information on what the device belive is "A" capable or not.

Wey

Comment 6 a.m.suharev 2011-06-06 16:19:51 UTC
(In reply to comment #5)
> hmm, it is strange, work on F14 but not F15 with the same firmware.

The most strange think that it works in F15 installer but not in F15 itself.
 
> If you load the module with debug=0x40, then check the dmesg log. it should
> give you all the information on what the device belive is "A" capable or not.

Cannot test it until next week, please wait.

Comment 7 a.m.suharev 2011-06-16 11:48:42 UTC
Created attachment 505028 [details]
/var/log/messages

Comment 8 wey-yi.w.guy 2011-06-16 14:36:09 UTC
don't see anything wrong in the dmesg, both 2.4 and 5.2 GHz are supported.
what version of wpa_supplicant you are using?
what result you get if you using "iw" or "iwlist" to scan?

Thanks
Wey

Comment 9 a.m.suharev 2011-06-16 16:12:40 UTC
Created attachment 505091 [details]
iw list

wpa_supplicant-0.7.3-6.fc15.x86_64

iwlist scan shows no 5GHz as I said in the initial post.

iw scan gives
... 5220 MHz [44] (disabled) ...
(the access point operates channel 44)

Comment 10 a.m.suharev 2011-06-16 16:16:57 UTC
by the way
iw-0.9.22-1.fc15.x86_64
wireless-tools-29-5.1.fc12.i686

Comment 11 a.m.suharev 2011-06-16 16:19:20 UTC
(In reply to comment #10)
> wireless-tools-29-5.1.fc12.i686
sorry, it's
wireless-tools-29-6.1.fc15.x86_64
actually

Comment 12 a.m.suharev 2011-06-16 16:40:29 UTC
Got it work after
iw reg set US
so it is definitely not a kernel bug.

The question now is why it works in F14 and in F15 installer with RU Regulatory domain?

Comment 13 Stanislaw Gruszka 2011-08-22 14:23:17 UTC
Regdomain is setup by /sbin/setregdomain script. It read files /etc/sysconfig/regdomain file or if it is empty, use time zone information from /etc/sysconfig/clock.

To solve this problem you can add "COUNTRY=US" line to /etc/sysconfig/regdomain
or configure time zone corresponding to your geographical location (preferred),
you can do it using system-config-date command (as root).

I'm closing bug as seems issue here is bad time zone setting. Reopen bug if
correcting zone setting do not help.


Note You need to log in before you can comment on or make changes to this bug.