From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 1 02:08:49 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 B2BDD106564A for ; Mon, 1 Aug 2011 02:08:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6B0718FC17 for ; Mon, 1 Aug 2011 02:08:49 +0000 (UTC) Received: by vws18 with SMTP id 18so5450519vws.13 for ; Sun, 31 Jul 2011 19:08:48 -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=H/uanXnxfJS0fHgj/4m3SqgdqPe5uO/T56JVrXoVByQ=; b=hVvaO5WdvsvYXuFdYVk4TO+M5P8itzm6c1qZOgw9Xn9C3LVXNYju5/QsG/oaGUKskf ssi3uGcEFdZ5EHzZ8NuTaCHNy1+9tchP3vp5wPE/NUaaTs4xaWeGf2jHflTMB/PwA9Vi XW9nw49sC+pmYibwzFX8dVXTj+vIpgalx7xjo= MIME-Version: 1.0 Received: by 10.52.27.36 with SMTP id q4mr3886912vdg.296.1312164528317; Sun, 31 Jul 2011 19:08:48 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.52.161.165 with HTTP; Sun, 31 Jul 2011 19:08:48 -0700 (PDT) In-Reply-To: <20110801005639.GB20219@richh-desktop.boxdice.com.au> References: <20110801005639.GB20219@richh-desktop.boxdice.com.au> Date: Mon, 1 Aug 2011 10:08:48 +0800 X-Google-Sender-Auth: H1iN9CCeDX1oPF84rHBiYsYVOMk 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 02:08:49 -0000 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. Adrian