Date: Wed, 31 Oct 2012 14:17:43 -0700 From: Adrian Chadd <adrian@freebsd.org> To: husyh@hush.com Cc: freebsd-wireless@freebsd.org Subject: Re: ath0: unable to attach hardware Message-ID: <CAJ-Vmo=36iV91tE1OWHEga7ptudUgcwHKGGxSGpivGku1rn=fQ@mail.gmail.com> In-Reply-To: <20121031211443.E797010E2C8@smtp.hushmail.com> References: <20121031211443.E797010E2C8@smtp.hushmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31 October 2012 14:14, <husyh@hush.com> wrote: > ath0: <Atheros 5413> mem 0xfdee0000-0xfdeeffff irq 16 at device 4.0 on pci2 > ar5212ChipTest: address test failed addr: 0x00008000 - wr:0x00000000 != rd:0xffffffff > ar5212Attach: hardware self-test failed > ath0: unable to attach hardware; HAL status 14 > device_attach: ath0 attach returned 6 Right, I wonder if that PCI address is actually valid. Are you able to do a verbose boot and record the dmesg to a file, and attach it here? Can you try an i386 live disk, see if it is any different? Maybe try 8.0 and 7.0-REL, see if it probe/attaches? The AR5413 support should have been there in 7.0. This is very likely a PCI bus reset/enumeration issue, rather than an ath(4) device issue. Thanks, Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=36iV91tE1OWHEga7ptudUgcwHKGGxSGpivGku1rn=fQ>