From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 1 15:30:43 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF46A1065670 for ; Mon, 1 Aug 2011 15:30:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 74EF88FC19 for ; Mon, 1 Aug 2011 15:30:43 +0000 (UTC) Received: by vxg33 with SMTP id 33so5926808vxg.13 for ; Mon, 01 Aug 2011 08:30:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0jpsHcjAMdmR8U6SQXNc1RGrVO/cqGVaosTA+Cuw6rc=; b=EgxiWc6YDxADL8UqApfzmPLj7HdoEPiFkN7nh7Q4jQ31aMGU7vn93HsGBbO1mL8YW3 LX5AJtvB63KfQNtVANIiwu+5KxD06mWoyRpJUXQwmSRTqs721oXyAuEIE0XGyn4nl+ei cwqn2t66T5cuJAU/cVjsVNGo/XIWKSZ36yN7M= MIME-Version: 1.0 Received: by 10.52.67.8 with SMTP id j8mr4593712vdt.363.1312212642606; Mon, 01 Aug 2011 08:30:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.52.161.165 with HTTP; Mon, 1 Aug 2011 08:30:42 -0700 (PDT) In-Reply-To: <20110801152323.GA22417@vesper.psych0tik.net> References: <20110801005639.GB20219@richh-desktop.boxdice.com.au> <20110801030038.GB77144@DataIX.net> <20110801031706.GB31782@richh-desktop.boxdice.com.au> <20110801150242.GA14650@vesper.psych0tik.net> <20110801152323.GA22417@vesper.psych0tik.net> Date: Mon, 1 Aug 2011 23:30:42 +0800 X-Google-Sender-Auth: 5QyqPcA6NLreluEIfbGwnvnXWp0 Message-ID: From: Adrian Chadd To: richo Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Ath works as module, not inkernel X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2011 15:30:43 -0000 .. it should've produced output in dmesg. Also try adding: dev.ath.0.hal.debug=0x4 See if that helps? 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? Adrian On 1 August 2011 23:24, richo wrote: > On 01/08/11 23:07 +0800, Adrian Chadd wrote: >> >> Try adding >> >> hw.ath.hal.debug=0x4 >> >> to /boot/loader.conf ; just to get some boot-time reset logging going. >> I'd like to see what the exact condition is that's triggering that HAL >> attach failure (it's either "can't wakeup chip" or "can't reset >> chip".) >> >> >> Adrian >> > > I just booted with that option.. there's nothing extra in dmesg. Where does > that produce logs? > > -- > richo || Today's excuse: > Operators killed when huge stack of backup tapes fell over. >