Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423063AbXBUUWF (ORCPT ); Wed, 21 Feb 2007 15:22:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423085AbXBUUWF (ORCPT ); Wed, 21 Feb 2007 15:22:05 -0500 Received: from mx1.redhat.com ([66.187.233.31]:40393 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423063AbXBUUWB (ORCPT ); Wed, 21 Feb 2007 15:22:01 -0500 Date: Wed, 21 Feb 2007 15:19:44 -0500 From: Dave Jones To: Jean Delvare , Chuck Ebbert , linux-acpi@vger.kernel.org, linux-kernel , lm-sensors@lm-sensors.org, notting@redhat.com Subject: Re: [lm-sensors] Could the k8temp driver be interfering with ACPI? Message-ID: <20070221201944.GD13794@redhat.com> Mail-Followup-To: Dave Jones , Jean Delvare , Chuck Ebbert , linux-acpi@vger.kernel.org, linux-kernel , lm-sensors@lm-sensors.org, notting@redhat.com References: <45D5EA88.7090300@redhat.com> <45D6DDCE.5050803@assembler.cz> <45D7461A.2040808@redhat.com> <45D8D6AE.3000204@assembler.cz> <45DB0EEA.2010205@redhat.com> <20070220191142.GE16614@redhat.com> <20070221171737.b6592104.khali@linux-fr.org> <20070221173740.GD19851@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070221173740.GD19851@redhat.com> User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1669 Lines: 47 On Wed, Feb 21, 2007 at 12:37:40PM -0500, Dave Jones wrote: > On Wed, Feb 21, 2007 at 05:17:37PM +0100, Jean Delvare wrote: > > On Tue, 20 Feb 2007 14:11:42 -0500, Dave Jones wrote: > > > On Tue, Feb 20, 2007 at 10:08:26AM -0500, Chuck Ebbert wrote: > > > > > > > i2c_core > > > > i2c_ec > > > > i2c_piix4 > > > > asus_acpi (on a Compaq???) > > > > sbs > > > > > > Something is pulling in asus_acpi as a dependancy. I've never > > > figured out what the cause is. For a long time I was thinking > > > that we had an explicit modprobe for it in an initscript, but > > > grepping for it in /etc turns up zip. > > > > How could it be, given that asus_acpi doesn't export any symbol? > > If I knew I'd have fixed it by now. Ah, Fedora has this horror in its initscripts (which explains why I missed it in my grep).. # Initialize ACPI bits if [ -d /proc/acpi ]; then for module in /lib/modules/$unamer/kernel/drivers/acpi/* ; do module=${module##*/} module=${module%.ko} modprobe $module >/dev/null 2>&1 done fi This is there because there's no clean way for userspace to know whether to load the system specific stuff right now. Bill Nottingham pointed out that we could add a /sys/class/dmi/modalias and appropriate MODULE_DMI tags to the various modules like asus_acpi to make udev autoload them. Dave -- http://www.codemonkey.org.uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/