Date: Thu, 15 Apr 2004 16:26:56 -0700 From: greg chesson <greg@atheros.com> To: Sam Leffler <sam@errno.com> Cc: freebsd-mobile@freebsd.org Subject: Re: Atheros 5212 on a Fujitsu S6120 laptop Message-ID: <407F1A40.3000003@atheros.com> In-Reply-To: <200404151441.34208.sam@errno.com> References: <20040415210524.84611.qmail@web41701.mail.yahoo.com> <200404151441.34208.sam@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chances are that the mac portion of the chip did not come out of reset properly. The symptom of this when the mac revision numbers are ok but the phy and radio numbers are bogus. g Sam Leffler wrote: > On Thursday 15 April 2004 02:05 pm, Steve G wrote: > >>Hi all, >> >> I've been trying to install FreeBSD 5.2.1 on my laptop. Everything seems >>to work pretty well, but I can't get the wireless card to work (it's an >>internal mini-PCI card). Looking through the forum posts, I found I had to >>set the loader.conf options to >> >> hw.pci.allow_unsupported_io_range=1 >> >>This statement was to allow the computer to even boot in order to install >>5.2.1. >> >>I've scoured the web and this list trying to find possible solutions, but I >>can't seem to find any answers. The specific error I get by using 'dmesg' >>is >> >> ath0: <Atheros 5212> mem 0xd0200000-0xd020ffff irq 11 at device 13.0 >>on pci1 ath0: mac 5.6 phy 4.1 5ghz radio 4.6 >> ath0: unable to collect channel list from hal >> device_probe_and_attach: ath0 attach returned 22 >> >>I checked my kernel to make certain that it was compiled with support for >>the atheros card. I'm at a total impasse at the moment. Can anyone give >>me some suggestions on what to do? Can anyone tell me what the returned 22 >>means? I can't seem to find any documentation on that particular error >>either. I'd love to get the wireless working properly! Stephen G > > > I'm not sure you're actually talking to the h/w. The 5ghz radio h/w revision > (4.6) is unknown to me and likely bogus. As a result the HAL is unable to do > it's thing and the driver bails. Not sure what to suggest other than to look > "upstream" (e.g. to your pci config hack). > > Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?407F1A40.3000003>