iwlagn won't scan 5 GHz band

linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

* iwlagn won't scan 5 GHz band
@ 2009-03-06 23:01 Chuck Anderson
  2009-03-07 19:24 ` John W. Linville
  0 siblings, 1 reply; 3+ messages in thread
From: Chuck Anderson @ 2009-03-06 23:01 UTC (permalink / raw)
  To: linux-wireless

Please Cc: me on replies as I'm not subscribed.  Thanks.

I have a 4965, using kernel-2.6.29-0.197.rc7.fc11.x86_64 (Intel(R) 
Wireless WiFi Link AGN driver for Linux, 1.3.27kds).  I can connect to 
802.11n on 2.4 GHz, but it never finds the 5 GHz cell of the AP.  Is 5 
GHz 802.11n supported yet?  For that matter, shouldn't I be seeing the 
802.11a from my APs?  How do I get this thing to scan the A/N 5 GHz 
band?

Thanks.

#iwlist wlan0 channel

wlan0     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)


I turned on the debug flag and verified that the driver is seeing 5.2 
GHz band channels as allowed:

Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Initializing regulatory info from EEPROM
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Parsing data for 56 channels.
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 1 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 2 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 3 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 4 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 5 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 6 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 7 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 8 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 9 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 10 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 11 [2.4GHz] VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 12 Flags 0 [2.4GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 13 Flags 0 [2.4GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 14 Flags 0 [2.4GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 183 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 184 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 185 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 187 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 188 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 189 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 192 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 196 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 7 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 8 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 11 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 12 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 16 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 34 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 36 [5.2GHz] VALID WIDE (0x21 15dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 38 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 40 [5.2GHz] VALID WIDE (0x21 15dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 42 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 44 [5.2GHz] VALID WIDE (0x21 15dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 46 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 48 [5.2GHz] VALID WIDE (0x21 15dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 52 [5.2GHz] VALID RADAR WIDE (0x31 15dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 56 [5.2GHz] VALID RADAR WIDE (0x31 15dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 60 [5.2GHz] VALID RADAR WIDE (0x31 15dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 64 [5.2GHz] VALID RADAR WIDE (0x31 15dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 100 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 104 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 108 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 112 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 116 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 120 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 124 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 128 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 132 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 136 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 140 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 145 Flags 0 [5.2GHz] - No traffic
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 149 [5.2GHz] VALID WIDE (0x21 16dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 153 [5.2GHz] VALID WIDE (0x21 16dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 157 [5.2GHz] VALID WIDE (0x21 16dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 161 [5.2GHz] VALID WIDE (0x21 16dBm): Ad-Hoc not supported
Mar  6 17:45:08 l kernel: ieee80211 phy5: U iwl_init_channel_map Ch. 165 [5.2GHz] VALID WIDE (0x21 16dBm): Ad-Hoc not supported

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: iwlagn won't scan 5 GHz band
  2009-03-06 23:01 iwlagn won't scan 5 GHz band Chuck Anderson
@ 2009-03-07 19:24 ` John W. Linville
  2009-03-10 12:45   ` Chuck Anderson
  0 siblings, 1 reply; 3+ messages in thread
From: John W. Linville @ 2009-03-07 19:24 UTC (permalink / raw)
  To: Chuck Anderson; +Cc: linux-wireless

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

On Fri, Mar 06, 2009 at 06:01:24PM -0500, Chuck Anderson wrote:
> Please Cc: me on replies as I'm not subscribed.  Thanks.
> 
> I have a 4965, using kernel-2.6.29-0.197.rc7.fc11.x86_64 (Intel(R) 
> Wireless WiFi Link AGN driver for Linux, 1.3.27kds).  I can connect to 
> 802.11n on 2.4 GHz, but it never finds the 5 GHz cell of the AP.  Is 5 
> GHz 802.11n supported yet?  For that matter, shouldn't I be seeing the 
> 802.11a from my APs?  How do I get this thing to scan the A/N 5 GHz 
> band?

Ah, the joys of Rawhide...

Make sure you have "iw" installed.

	yum install iw

Then you need to specify your regulatory domain:

	iw reg set US # Use ISO/IEC 3166-1 alpha2 as appropriate for you

Does that change things for you?

We are still discussing ways to get this set automatically.  We are
hoping that NetworkManager grows this capability "soon"...  In the
meantime, you might try calling the attached script from /etc/rc.local.

Hth!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

[-- Attachment #2: set-regdomain --]
[-- Type: text/plain, Size: 541 bytes --]

#!/bin/sh

CLOCK=/etc/sysconfig/clock

if [ -f $CLOCK ]
then
	# This should set ZONE
	. $CLOCK
else
	echo "Timezone information not found!  Unable to set regulatory domain."
	exit
fi

if [ -z "$ZONE" ]
then
	echo "Timezone information not set!  Unable to set regulatory domain."
	exit
fi

COOKED_ZONE=$(echo $ZONE | sed -e 's/ /_/')

COUNTRY=$(grep $COOKED_ZONE /usr/share/zoneinfo/zone.tab | awk '{ print $1 }')

if [ -z "$COUNTRY" ]
then
	echo "Could not determine country!  Unable to set regulatory domain."
	exit
fi

iw reg set $COUNTRY

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: iwlagn won't scan 5 GHz band
  2009-03-07 19:24 ` John W. Linville
@ 2009-03-10 12:45   ` Chuck Anderson
  0 siblings, 0 replies; 3+ messages in thread
From: Chuck Anderson @ 2009-03-10 12:45 UTC (permalink / raw)
  To: John W. Linville; +Cc: linux-wireless

On Sat, Mar 07, 2009 at 02:24:17PM -0500, John W. Linville wrote:
> On Fri, Mar 06, 2009 at 06:01:24PM -0500, Chuck Anderson wrote:
> > Please Cc: me on replies as I'm not subscribed.  Thanks.
> > 
> > I have a 4965, using kernel-2.6.29-0.197.rc7.fc11.x86_64 (Intel(R) 
> > Wireless WiFi Link AGN driver for Linux, 1.3.27kds).  I can connect to 
> > 802.11n on 2.4 GHz, but it never finds the 5 GHz cell of the AP.  Is 5 
> > GHz 802.11n supported yet?  For that matter, shouldn't I be seeing the 
> > 802.11a from my APs?  How do I get this thing to scan the A/N 5 GHz 
> > band?
> 
> Ah, the joys of Rawhide...
> 
> Make sure you have "iw" installed.
> 
> 	yum install iw
> 
> Then you need to specify your regulatory domain:
> 
> 	iw reg set US # Use ISO/IEC 3166-1 alpha2 as appropriate for you
> 
> Does that change things for you?

Works great!

> We are still discussing ways to get this set automatically.  We are
> hoping that NetworkManager grows this capability "soon"...  In the
> meantime, you might try calling the attached script from /etc/rc.local.
> 
> Hth!

Thanks!

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-03-10 12:45 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-06 23:01 iwlagn won't scan 5 GHz band Chuck Anderson
2009-03-07 19:24 ` John W. Linville
2009-03-10 12:45   ` Chuck Anderson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).