Date: Mon, 1 Aug 2011 11:07:23 +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-VmonNxbU%2Byhbr3MJn0E%2Bur-F1Fq=0aByCg57uMC088JeEFw@mail.gmail.com> In-Reply-To: <20110801030140.GA31782@richh-desktop.boxdice.com.au> References: <20110801005639.GB20219@richh-desktop.boxdice.com.au> <CAJ-VmonBufiTCB60PnFK2rGjy0Y=EjaVSNiQni7UVUuvm3yvVQ@mail.gmail.com> <20110801030140.GA31782@richh-desktop.boxdice.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1 August 2011 11:01, richo <richo@psych0tik.net> wrote: > This is true. I surmised that either the issue was widespread and so it'd > get > reported, or it was just me and probably self-inflicted ;) I don't have that issue on my netbooks. I thus can't fix it. :) >> 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. > > I did some more reading about FreeBSD's wireless support just now, it looks > like maybe a missing device wlan > could be the issue, however I'll build a kernel with the broken config > tonight and posts boot info. > > IIRC it's hal attach returned 6, and another error 3. I went looking for > them > in sys/dev/ath/ath_hal/ah.h but couldn't work out what I was looking for > (Very new to kernel dev, in case you'd not guessed :] ) the attach is the device attach - ar5210Attach, ar5212Attach .. ar9280Attach, etc. See what that function returns. :) Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonNxbU%2Byhbr3MJn0E%2Bur-F1Fq=0aByCg57uMC088JeEFw>