From owner-freebsd-current@FreeBSD.ORG Thu Dec 27 21:30:34 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 5CC28B11; Thu, 27 Dec 2012 21:30:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by mx1.freebsd.org (Postfix) with ESMTP id AFD8E8FC0A; Thu, 27 Dec 2012 21:30:33 +0000 (UTC) Received: by mail-we0-f174.google.com with SMTP id x10so4617190wey.5 for ; Thu, 27 Dec 2012 13:30:27 -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=e8I2mf2FlI/pz5cXtsYrKFg1F/kxLbSP+cjgxTDbK8o=; b=f5Hq6qgIGl66XZbsFxbUXTgRU0Xc4/HvDvn3417Qa4Owi7uhk35/YDwGA1uuBKQn0T vfIKmNMtEblrhBfgs9imeYm+enF6Vch9RbHxRtl3mhNVGQvq/vE0UF67JJRbgAEtdw2t dGy0vzsNP0sHk0xMvzusA5Z2qM9rjbRusbCkfF1yLJsoGpywW1Xj139qhS9nY6YSmxLA X1sFHXkAi93QmdIb2Sv7QVE5ujMMj1PYReHX9kA7zgtrARFt83jlvNOlfBrDNE/xG4Z+ kEu53YOCAabckLuJuUJHtRZVAmR5OHDPle+gFYEsryj0G9S3i3QvaxQ5qOYvTXvRvR20 +Sqw== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr50956989wjc.1.1356643827639; Thu, 27 Dec 2012 13:30:27 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Thu, 27 Dec 2012 13:30:27 -0800 (PST) In-Reply-To: <20121227200643.9F13DE6726@smtp.hushmail.com> References: <20121123213551.C2CB9E6739@smtp.hushmail.com> <201212101437.54825.jhb@freebsd.org> <201212111549.49942.jhb@freebsd.org> <20121213211100.5395F10E2C8@smtp.hushmail.com> <20121214085607.3938D10E2C8@smtp.hushmail.com> <20121227200643.9F13DE6726@smtp.hushmail.com> Date: Thu, 27 Dec 2012 13:30:27 -0800 X-Google-Sender-Auth: MjO9IO-VAxm0ViZm7mhRHW4mR-0 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: Thu, 27 Dec 2012 21:30:34 -0000 Hi, Just leave all of the ath/ah options in the kernel. Then comment out device ath device ath_hal device ath_rate_sample .. but yes, leave all the options in there. Adrian On 27 December 2012 12:06, wrote: > Hello, > > I hope you had a pleasant trip. Sorry for not replying for a while. > > Anyway, I tried to do what you asked me to. However, it seems like I misu= nderstood the handbook and/or your request, as I failed to compile the kern= el. > > I copied my previous, working kernel config to a new file, and commented = the devices ath, ath_pci, ath_hal and ath_rate_sample, as well as the optio= ns AH_SUPPORT_AR5416, AH_DEBUG and ATH_DEBUG. I did this because I could no= t find instructions in the handbook that explained how to build a module as= a kld, and commenting the modules out was my best guess. Please point me t= o the relevant section in the handbook in the case that the information was= actually there and I just was unable to find it. > The full kernel config can be seen here: http://nopaste.info/d7475552bd.h= tml > Finally, I went to /usr/src and entered > make buildkernel KERNCONF=3DPAVILIONNOATH > > This is what I suspect is the relevant output: > > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdin= c -I. -I/usr/src/sys/modules/ath/../../dev/ath -I/usr/src/sys/modules/ath/= ../../dev/ath/ath_hal -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/sr= c/sys/PAVILIONNOATH/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=3D= 8000 --param inline-unit-growth=3D100 --param large-function-growth=3D1000 = -fno-common -g -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/PAVILIONNOATH= -mno-sse -mcmodel=3Dkernel -mno-red-zone -mno-mmx -msoft-float -fno-asyn= chronous-unwind-tables -ffreestanding -fstack-protector -std=3Diso9899:1999= -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-protot= ypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -W= no-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-s= how-option -c /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ah.c > In file included from /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ah.c= :55: > @/net/if_var.h:125: error: 'IFNAMSIZ' undeclared here (not in a function) > @/net/if_var.h:151: error: field 'if_data' has incomplete type > cc1: warnings being treated as errors > @/net/if_var.h:157: warning: 'struct sockaddr' declared inside parameter = list > @/net/if_var.h:157: warning: its scope is only this definition or declara= tion, which is probably not what you want > @/net/if_var.h:167: warning: 'struct sockaddr' declared inside parameter = list > @/net/if_var.h:187: error: 'AF_MAX' undeclared here (not in a function) > @/net/if_var.h:718: error: field 'if_data' has incomplete type > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ah.c: In function 'ath_hal= _attach': > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ah.c:65: warning: derefere= ncing 'void *' pointer > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ah.c:65: error: request fo= r member 'sc_ifp' in something not a structure or union > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ah.c:70: warning: derefere= ncing 'void *' pointer > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ah.c:70: error: request fo= r member 'sc_ifp' in something not a structure or union > *** Error code 1 > > The full output has been posted to http://nopaste.info/408e62ac0f.html > > I'm willing and hoping to help troubleshoot this issue, but please keep i= n mind that I'm new to FreeBSD, so please give detailed instructions whenev= er you can. > > Thank you very much! > >> >>Hi, >> >>Ok. I'm travelling for a little bit; if I don't reply in a few >>days, >>please poke me again. >> >>It may be that the device is asleep for a bit longer (failing this >>test) and has completed resetting at this point. >> >>It may be that the power on sequence is not quite right for some >>reason. >> >>Would you mind recompiling your kernel and making if_ath a kld, >>rather >>than statically in the kernel? >> >>Thanks, >> >> >>Adrian >> >>> >>> attached to this e-mail you find the output of dmesg. What I >>guess the most relevant lines could be is: >>> >>> 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 >>> >>> I read the registers 4004 and 4010 again to make sure the values >>still are the same, which indeed they are. >>> >>> I hope this helps. >>> >>> Thanks! >>> >>> On Donnerstag, 13. Dezember 2012 at 10:18 PM, "Adrian Chadd" >> wrote: >>>> >>>>On 13 December 2012 13:11, wrote: >>>>> Hello everyone, >>>>> >>>>> I'm afraid I still don't know what exactly BAR is, or how I get >>>>its value that I'm supposed to plug into the line John provided: >>>>> dd if=3D/dev/mem bs=3D4 iseek=3D((start of bar + reg offset)/4) >>>>count=3D1 | hd >>>>> >>>>> I assumed that "start of bar" is 0xfdee0000 in my case, since >>>>dmesg reports >>>>> ath0: mem 0xfdee0000-0xfdeeffff irq 16 at device >>>>4.0 on pci2 >>>> >>>>Yup. >>>> >>>>> This is what I get: >>>>> # dd if=3D/dev/mem bs=3D4 iseek=3D`echo "ibase=3D16; (FDEE0000+4004)/= 4" >>>>| bc` count=3D1 | hd >>>>> 00 00 01 00 >>>>> # dd if=3D/dev/mem bs=3D4 iseek=3D`echo "ibase=3D16; (FDEE0000+4010)/= 4" >>>>| bc` count=3D1 | hd >>>>> 14 00 01 00 >>>>> >>>>> Please correct me if my assumption about "start of bar" was >>>>wrong and/or I made some other mistake. >>>>> Also, please don't hesitate to ask me to do anything else that >>>>might help you during debugging. >>>>> >>>>> Thank you very much for the effort. >>>> >>>>Hm. Wait, what's the rest of the ath0: output? >>>> >>>> >>>> >>>>Adrian >