Date: Mon, 1 Aug 2011 11:20:24 +0800 From: Adrian Chadd <adrian@freebsd.org> To: richo <richo@psych0tik.net> Cc: freebsd-wireless@freebsd.org Subject: Re: Ath works as module, not inkernel Message-ID: <CAJ-VmomBuugHriOCJZMJ5%2Bi7Vm%2BV0GqviLdgcrSL-GC8T8Rj5g@mail.gmail.com> In-Reply-To: <20110801031706.GB31782@richh-desktop.boxdice.com.au> References: <20110801005639.GB20219@richh-desktop.boxdice.com.au> <CAJ-VmonBufiTCB60PnFK2rGjy0Y=EjaVSNiQni7UVUuvm3yvVQ@mail.gmail.com> <20110801030038.GB77144@DataIX.net> <20110801031706.GB31782@richh-desktop.boxdice.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1 August 2011 11:17, richo <richo@psych0tik.net> wrote: >> Should be noted .... does this happen with a generic kernel ? The >> default ATH setup works perfectly and I can attest to it working just >> fine built in here. > > First thing I tried was with GENERIC (iirc, freeBSD doesn't support any > other > configuration?) and still no dice. > > Adrian, I saw your post and I will have a look at what that function returns > to see if I can track it down. ok. I bet you'll find that the hardware just wasn't setup correctly at the time where ath was being probed. This could be because of things like ACPI extensions not having turned on the NIC (software rfkill, for example) or something equally strange. If you can get it reproducable, we can work on it together. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomBuugHriOCJZMJ5%2Bi7Vm%2BV0GqviLdgcrSL-GC8T8Rj5g>