From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 1 03:26:45 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 E9333106566B; Mon, 1 Aug 2011 03:26:44 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 677EB8FC08; Mon, 1 Aug 2011 03:26:44 +0000 (UTC) Received: by iyb11 with SMTP id 11so8484375iyb.13 for ; Sun, 31 Jul 2011 20:26:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to; bh=t5eDKOCxGpjBSf90ah+qrVhDLnrVUEagylY0udnYyyY=; b=NUz5hpiAmpKHHK+e6kpDnqzdJmwfZOPDQ/L9yxSqgSl7iagDCyUjt+bSwa+QIEPr8f zkNJ+U6FGQYK1aBVdqH/6D2OUsSUs1gnPyJlcYeQ5Ykp5XkEHunZPVM0vZnObAhRL7tZ kdUZML3J46+BdWxjvUmq9C5YDRjplMIReoD4k= Received: by 10.231.205.197 with SMTP id fr5mr2456854ibb.198.1312167644283; Sun, 31 Jul 2011 20:00:44 -0700 (PDT) Received: from DataIX.net ([99.56.120.66]) by mx.google.com with ESMTPS id k16sm6137011icc.22.2011.07.31.20.00.42 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 31 Jul 2011 20:00:43 -0700 (PDT) Sender: "J. Hellenthal" Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.5/8.14.5) with ESMTP id p7130d4p030473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 31 Jul 2011 23:00:39 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.5/8.14.5/Submit) id p7130dLh030457; Sun, 31 Jul 2011 23:00:39 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Sun, 31 Jul 2011 23:00:39 -0400 From: Jason Hellenthal To: Adrian Chadd Message-ID: <20110801030038.GB77144@DataIX.net> References: <20110801005639.GB20219@richh-desktop.boxdice.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 03:26:45 -0000 On Mon, Aug 01, 2011 at 10:08:48AM +0800, Adrian Chadd wrote: > Hi, > > On 1 August 2011 08:56, richo wrote: > > Hi -wireless, > > > > A while ago I posted with some issues with ath on 9.0-CURRENT, which were > > fixed by a patch someone posted to the list. > > > > A few weeks later, ath broke again and neither a vanilla kernel nor one with > > the patch worked, complaining of errors attaching HAL. Googling the terms > > turned up only results from 2008. > > > > I didn't have time to look into it so I ignored it, figuring that it would > > be > > fixed in due course and that I'd pull when I had time. > > Well, if noone reported the issue and noone chases the issue up, it's > not likely to get magically fixed by itself. :) > > > Over the weekend I spent some time on the problem, and it appeared that > > building ath support into the kernel was the issue, my config with > > > >> device ath > >> device ath_pci > >> device ath_hal > > > > (Apologies if that's not spelled correctly, I'm not actually in front of the > > machine) > > > > Doesn't load, however if I removed MODULES_OVERRIDE from make.conf and try > > to > > load those modules, I'm told that it's already in the kernel. > > > > I also built GENERIC from the config in SVN and no luck. > > > > Finally, I removed those device lines from my config, built with all modules > > and enabled load_ath and load_ath_pci in loader.conf and wireless now works > > flawlessly. > > > > I'm now curious about why- and what I can do to know how to chase this up > > myself next time. > > 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.