Date: Tue, 25 Apr 2006 16:51:13 -0700 From: Sam Leffler <sam@errno.com> To: Douglas Berry <bitnix@bitnix.ca> Cc: freebsd-stable@freebsd.org Subject: Re: ath0: ath_chan_set: unable to reset channel 5 (2432 Mhz, flags 0x3e0 hal flags 0x140) Message-ID: <444EB5F1.7030004@errno.com> In-Reply-To: <200604252258.k3PMwJ74026969@monk.cnd.dundas.on.ca> References: <200604252258.k3PMwJ74026969@monk.cnd.dundas.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Douglas Berry wrote: > On Tue, 25 Apr 2006 13:36:56 PDT, Sam Leffler wrote: >> flags 0x3e0 = Passive+5Ghz+2Ghz+OFDM+CCK >> hal flags 0x140 = 5Ghz+OFDM >> Both of these make no sense for a frequency of 2432 Mhz, hence the hal >> got upset. > > Thanks for the interpretation. > >> What are the regulatory domain settings for the card; sysctl dev.ath.0 >> will show them? Please also show the output of ifconfig ath0 list channel. > > Below is the output of of both commands. I couldn't find what 18 > meant as a regulatory domain. The card is currently in use in > Canada. 18 is a recent addition; it's a variant of FCC that enables use in the 4.9G range (as you can see below). > > dev.ath.0.%desc: Atheros 5212 > dev.ath.0.%driver: ath > dev.ath.0.%location: slot=9 function=0 > dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1186 subdevice=0x3a14 class=0x020000 > dev.ath.0.%parent: pci3 > dev.ath.0.smoothing_rate: 95 > dev.ath.0.sample_rate: 10 > dev.ath.0.countrycode: 0 > dev.ath.0.regdomain: 18 > dev.ath.0.slottime: 20 > dev.ath.0.acktimeout: 48 > dev.ath.0.ctstimeout: 48 > dev.ath.0.softled: 0 > dev.ath.0.ledpin: 0 > dev.ath.0.ledon: 0 > dev.ath.0.ledidle: 2700 > dev.ath.0.txantenna: 0 > dev.ath.0.rxantenna: 1 > dev.ath.0.diversity: 0 > dev.ath.0.txintrperiod: 5 > dev.ath.0.diag: 0 > dev.ath.0.tpscale: 0 > dev.ath.0.tpc: 0 > dev.ath.0.tpack: 63 > dev.ath.0.tpcts: 63 > dev.ath.0.monpass: 24 > > > Channel 1 : 2412 Mhz 11g Channel 137 : 4955* Mhz 11a > Channel 2 : 2417 Mhz 11g Channel 137 : 4957* Mhz 11a > Channel 3 : 2422 Mhz 11g Channel 137 : 4960* Mhz 11a > Channel 4 : 2427 Mhz 11g Channel 137 : 4962* Mhz 11a > Channel 5 : 2432* Mhz 11a 11g Channel 137 : 4965* Mhz 11a > Channel 6 : 2437 Mhz 11g Channel 137 : 4967* Mhz 11a > Channel 7 : 2442 Mhz 11g Channel 137 : 4970* Mhz 11a > Channel 8 : 2447 Mhz 11g Channel 138 : 4972* Mhz 11a > Channel 9 : 2452 Mhz 11g Channel 138 : 4975* Mhz 11a > Channel 10 : 2457* Mhz 11a 11g Channel 138 : 4977* Mhz 11a > Channel 11 : 2462 Mhz 11g Channel 138 : 4980* Mhz 11a > Channel 136 : 4947* Mhz 11a Channel 138 : 4982* Mhz 11a > Channel 136 : 4950* Mhz 11a Channel 138 : 4985* Mhz 11a > Channel 137 : 4952* Mhz 11a Channel 138 : 4987* Mhz 11a Ok, something is b0rked; the 2432 and 2457 frequencies are obviously not capable of 11a. As a workaround you can eliminate them from the channel list using the chanlist directive; e.g. ifconfig ath0 chanlist 1-4,6-9,11-255 should do it. That obviously won't work if you've got ap's on those channels. I will look into the problem. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?444EB5F1.7030004>