From owner-freebsd-wireless@FreeBSD.ORG Wed Oct 31 21:17:43 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF3EFAD5 for ; Wed, 31 Oct 2012 21:17:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id BF8F38FC08 for ; Wed, 31 Oct 2012 21:17:43 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so888612dad.13 for ; Wed, 31 Oct 2012 14:17:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=uDEKYx3Q4AZJ9s52ITgA6bSGp5Uzi4RdeJgL+nFaLNI=; b=AuNqXr7ZeI8Jt78jb9woid+1RsusqOS/CwH7vnmO17s86tNs6y4rqgHBi8Is7hD7JG UwHQjYyFQTThY7otXD0LAJpEvCVfKhQM9NaGo02khAb221G/FAlIKbUnmJMz7yv05M0Q FcD2WMhP+4UvasH2oGsmmEkjWUEELI3n1qd5kzSjCNozKeAeiHya7vzD3uCHtJ/rOuwf N5OcSYRDhW7StVKLQvMFNQZB3JMn/N7rmqnI/dOwFA7oH8ktgXNV1pWxq2YcMfR9Z47R jT2Phjcc92M+9JA0qyZwCM8HuyZN75sSzviEiNNfQKCtRnhjVWbLT5THJt8Snb/kc8cv Su4A== MIME-Version: 1.0 Received: by 10.66.79.168 with SMTP id k8mr105168350pax.12.1351718263265; Wed, 31 Oct 2012 14:17:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Wed, 31 Oct 2012 14:17:43 -0700 (PDT) In-Reply-To: <20121031211443.E797010E2C8@smtp.hushmail.com> References: <20121031211443.E797010E2C8@smtp.hushmail.com> Date: Wed, 31 Oct 2012 14:17:43 -0700 X-Google-Sender-Auth: Qh2wP7EGjO1c5xedyY-YuJV4_bA Message-ID: Subject: Re: ath0: unable to attach hardware From: Adrian Chadd To: husyh@hush.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2012 21:17:44 -0000 On 31 October 2012 14:14, wrote: > ath0: 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