From owner-freebsd-current@FreeBSD.ORG Fri Nov 9 16:45:24 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 27248447 for ; Fri, 9 Nov 2012 16:45:24 +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 E8CB78FC0C for ; Fri, 9 Nov 2012 16:45:23 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so1840222dad.13 for ; Fri, 09 Nov 2012 08:45:22 -0800 (PST) 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 :content-transfer-encoding; bh=Jh4t48eVOtQml300XRfc5JGc+pLc4yuKPXMZFdSMmi8=; b=IzoV3QpWHezMxyX7s8vKCa4KNbMYe8bZ2CRFHvYY+fPsq7k6GrIHh/J/0XPPIHTZGN QeWab0Ozdpn94ufM/7xDujeDx+JzkWdDRSp34aeIaqYzLK5L1Zno5mkcgB24+f3h+NSE HYNHHcw3DKDcmOUrzwxdIHEmn9t5mgfcFQ/w+8udAGKv6eO0jIdalfEpjma11p79kUT1 PXbI1Ouf1MUUIDgpR7PfAqpJivfwUfuyDDS9gvo+kofqQxcem+dhGhZPkb2dbqcfnzyA H907sOMutl9uJ7lN3cB4A7n0t+akimh++BFzKKutyyZ6NGiTDYNdHFyzMrFTCvj8PF1Z DzjQ== MIME-Version: 1.0 Received: by 10.68.137.198 with SMTP id qk6mr35171394pbb.60.1352479522527; Fri, 09 Nov 2012 08:45:22 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Fri, 9 Nov 2012 08:45:22 -0800 (PST) In-Reply-To: <20121109095702.A36C0E6726@smtp.hushmail.com> References: <20121109095702.A36C0E6726@smtp.hushmail.com> Date: Fri, 9 Nov 2012 08:45:22 -0800 X-Google-Sender-Auth: _htOcRgMg8nnCi7kvdCESNKDD3c Message-ID: Subject: Re: ath0: unable to attach hardware From: Adrian Chadd To: husyh@hush.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 16:45:24 -0000 Can you use pciconf to dump the config space? I think its pciconf -r 0:255 thanks! adrian On 9 November 2012 01:57, wrote: > Hello again, > > the mail I'm replying to (and which is cited below) hasn't caused a react= ion yet. Seeing that this mailing list has quite a lot of traffic, I'm worr= ied that the mail, and the issue it tries to point out, will be forgotten. > Should I file a bug report in hopes that the issue will somewhen be inves= tigated/resolved? > > Again, I'm offering any kind of help I'm able to provide, i.e. delivering= more information upon (hopefully detailed enough for me to understand) req= uest, testing proposed fixes and doing some progamming on my own; for the l= atter, please keep in mind that I have no experience with the FreeBSD codeb= ase or hardware programming. > > Thanks! > > On Samstag, 3. November 2012 at 11:43 AM, husyh@hush.com wrote: >> >>Hello everyone, >> >>I'm new to FreeBSD and wanted to install 9.0-RELEASE amd64 on a PC >>I was given. At first glance, it seems like everything is working, >>except the wireless LAN PCI card. >> >>I started a thread on freebsd-wireless on the 31st of October (see >>here: http://lists.freebsd.org/pipermail/freebsd-wireless/2012- >>October/002511.html or a repost of my original message with proper >>formatting: http://lists.freebsd.org/pipermail/freebsd- >>wireless/2012-October/002513.html ) >> >>Short summary: >>The card has the strings "Anatel", "WN5301A-H1-V02" and >>"KN160562*7" printed on it, although I'm not sure which, if any, >>of those is a proper product number. >>After setting >> >>hw.ath.debug=3D1 >>hw.ath.hal.debug=3D1 >> >>I receive >> >>ath0: mem 0xfdee0000-0xfdeeffff irq 16 at device >>4.0 on pci2 >>ar5212ChipTest: address test failed addr: 0x00008000 - >>wr:0x00000000 !=3D rd:0xffffffff >>ar5212Attach: hardware self-test failed >>ath0: unable to attach hardware; HAL status 14 >>device_attach: ath0 attach returned 6 >> >>and am left unable to use the device. >>I tried 8.3-RELEASE i386 as well as 10.0-CURRENT amd64 and i386 >>snapshots from https://snapshots.glenbarber.us/Latest/ (seemlingly >>built a few days ago) and received the same messages, although I >>did not get the debug messages since I booted off of the >>installation media and therefore had a stock kernel, which >>seemingly doesn't enable ATH_DEBUG and AH_DEBUG. Booting the >>Ubuntu 12.04 amd64 installation media, I can use the NIC without >>having any problems. >> >>Adrian Chadd tried to help me via freebsd-wireless (thank you >>again,) but ultimately asked me this: >>"Please try a recent -HEAD i386 and amd64 snapshot and if that >>doesn't >>work, you could try posting for help on freebsd-current. But please >>stress that I think it's a bus enumeration and PCI bridge >>programming >>problem, _not_ a driver problem." >> >>And so I did. >> >>I'd be very glad if you could try to help me. Of course, I'm >>willing to provide any kind of information you might need, but >>please keep in mind that I'm new to FreeBSD and therefore would be >>thankful if you stated your instructions/requests in a newbie- >>friendly way. >> >>Thank you. >> >>_______________________________________________ >>freebsd-current@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-current >>To unsubscribe, send any mail to "freebsd-current- >>unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "