Date: Mon, 1 Aug 2011 23:42:13 +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-VmomszdbjCO9YSkLpriKLPFz5MHHiFv2HoGbOE6Lz%2Ba%2B5VA@mail.gmail.com> In-Reply-To: <20110801153920.GA17336@vesper.psych0tik.net> 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> <CAJ-VmomBuugHriOCJZMJ5%2Bi7Vm%2BV0GqviLdgcrSL-GC8T8Rj5g@mail.gmail.com> <20110801150242.GA14650@vesper.psych0tik.net> <CAJ-VmomT%2BASOjuE7xJFy_MyMTE7zazf6J0CXVH6-cVGbic-VZQ@mail.gmail.com> <20110801152323.GA22417@vesper.psych0tik.net> <CAJ-Vmonfj2oDncvxePAjmAf%2BMp4FwVCbmdO=wbL_PbOAtz7_aw@mail.gmail.com> <20110801153920.GA17336@vesper.psych0tik.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I've not tried loading the module(s) from loader. Just try loading if_ath_pci (not if_ath) and see if that pulls in if_ath as a dependency? adrian On 1 August 2011 23:39, richo <richo@psych0tik.net> wrote: > On 01/08/11 23:30 +0800, Adrian Chadd wrote: >> >> .. it should've produced output in dmesg. >> >> Also try adding: >> >> dev.ath.0.hal.debug=0x4 >> >> See if that helps? > > I'll try that in a moment > >> >> Also, how the hell are you able to load a module for ath/hal if it's >> compiled into your kernel? or is it failing to load it early on in the >> single user boot, but then fine to load it in later? >> > > I'm 99% sure that this kernel was built without ath support built in and > it's > the load_if_ath and load_if_ath_pci lines in loader.conf that is causing it > to load at some point later? > > We might be at cross purposes, I'm guessing from your question that dmesg is > suggesting that support is built in? > > When I've tried to load a module that's already in the kernel in the past it > gives a xxxxx is already in kernel.kld (or something along those lines, the > exact message escapes me). > > The behavior from the user standpoint is that it attempts to load the > correct > modules at boot time and fails in some way, once the system has come up > multiuser, I am able to unload the modules and then load them manually, at > which point the nic comes up and functions normally. > > I hope this clears things up, I'll post the new dmesg shortly (I just > started > a stack of ports updating so I'll wait till that finishes) > > Thanks for your help, really appreciate it > > rich > >> >> Adrian >> > > -- > richo || Today's excuse: > User was distributing pornography on server; system seized by FBI. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomszdbjCO9YSkLpriKLPFz5MHHiFv2HoGbOE6Lz%2Ba%2B5VA>