Date: Mon, 1 Aug 2011 18:45:22 -0400 From: Jason Hellenthal <jhell@DataIX.net> To: richo <richo@psych0tik.net> Cc: freebsd-wireless@freebsd.org Subject: Re: Ath works as module, not inkernel Message-ID: <20110801224522.GC77144@DataIX.net> 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 Mon, Aug 01, 2011 at 01:17:06PM +1000, richo wrote: > On 31/07/11 23:00 -0400, Jason Hellenthal wrote: > > > > > >On Mon, Aug 01, 2011 at 10:08:48AM +0800, Adrian Chadd wrote: > >> Well, can you please post boot messages, including the HAL load > >> failure information? > >> > >> This isn't the first time I've heard about strange issues like this; > >> it almost always boils down to something strange in PCI/ACPI handling. > >> > > > >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. > I read your other posts... Can you please boot a GENERIC kernel and post the output of ( pciconf -lvb ) and a dmesg output from /var/run/dmesg.boot after booting with ( boot -v ) or the verbose option from the menu please. Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110801224522.GC77144>