From owner-freebsd-acpi@FreeBSD.ORG Wed Aug 11 00:00:49 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 350A816A4CF for ; Wed, 11 Aug 2004 00:00:49 +0000 (GMT) Received: from web41112.mail.yahoo.com (web41112.mail.yahoo.com [66.218.93.28]) by mx1.FreeBSD.org (Postfix) with SMTP id 8F91343D41 for ; Wed, 11 Aug 2004 00:00:44 +0000 (GMT) (envelope-from jmkatcher@yahoo.com) Message-ID: <20040811000044.32661.qmail@web41112.mail.yahoo.com> Received: from [24.18.54.216] by web41112.mail.yahoo.com via HTTP; Tue, 10 Aug 2004 17:00:44 PDT Date: Tue, 10 Aug 2004 17:00:44 -0700 (PDT) From: Jeffrey Katcher To: freebsd-acpi@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Atheros driver doesn't actually work X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 00:00:49 -0000 I thought that recent PCI routing changes made the ath driver work, but in fact it was a combination of other bugs that made this possible. Specifically, there's a recent screwup that makes the default kernel module load path "/boot/modules" instead of "/boot/kernel". On startup, ACPI doesn't load. For quite a long time now, the T40 would panic when booting without ACPI, but apparently that's fixed. Now successfully booted without ACPI, if_ath loads and works perfectly (in fact I'm posting this via WiFi). Apologies to Nate, for saying I tested his most recent patch, when it was quietly skipped on loading. When I force a valid kernel module load path from the loader, ACPI loads OK, but ath refuses to work after loading with the same hardware errors reported. Jeff Katcher