Date: Wed, 28 Dec 2005 21:06:29 -0800 From: Sam Leffler <sam@errno.com> To: Beech Rintoul <akbeech@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: ath problems Message-ID: <43B36ED5.6020300@errno.com> In-Reply-To: <43B33AC7.2040107@errno.com> References: <200512281439.57713.akbeech@gmail.com> <43B33AC7.2040107@errno.com>
index | next in thread | previous in thread | raw e-mail
Sam Leffler wrote: > Beech Rintoul wrote: > >> I'm trying to get ath working with a D-Link AG530 wireless card on a >> 6-STABLE machine. It returns the following: >> >> Dec 28 12:24:12 pinnacle kernel: ath_hal: 0.9.14.9 (AR5210, AR5211, >> AR5212, RF5111, RF5112, RF2413) >> Dec 28 12:24:12 pinnacle kernel: ath0: <Atheros 5212> mem >> 0xcffe0000-0xcffeffff irq 10 at device 10.0 on pci0 >> Dec 28 12:24:12 pinnacle kernel: ath0: unable to collect channel list >> from hal; regdomain likely 18 country code 0 >> Dec 28 12:24:12 pinnacle kernel: device_attach: ath0 attach returned 22 >> >> This card / driver works perfectly on my -CURRENT box. Is this >> supported in -CURRENT only? I don't want to upgrade the box, it's in >> production and I can't risk -CURRENT. BTW, this card is not in the >> supported devices list, but does work. Is it feasible to move the >> sources from -CURRENT to this box? If so which ones? > > > 6-STABLE and CURRENT have the same hal so I don't see how it works > differently. Verify the hal versions. > > Regardless this problem is caused by a batch of cards D-Link created > with bogus regulatory domain codes programmed into the EEPROM (they > programmed 18 when they probably wanted 16 = FCC). If you search a bit > you can find postings that describe how to "fix this". I was wrong. Regdomain code 18 is a new code that enables access to frequencies in the 4.9G range. You need the new hal I've got out for testing. Samhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43B36ED5.6020300>