Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030198AbXADTcz (ORCPT ); Thu, 4 Jan 2007 14:32:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030201AbXADTcz (ORCPT ); Thu, 4 Jan 2007 14:32:55 -0500 Received: from ns1.suse.de ([195.135.220.2]:42377 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030198AbXADTcy (ORCPT ); Thu, 4 Jan 2007 14:32:54 -0500 Date: Thu, 4 Jan 2007 11:32:20 -0800 From: Greg KH To: Stephen Hemminger Cc: Jean Delvare , i2c@lm-sensors.org, linux-kernel@vger.kernel.org Subject: Re: [i2c] Why to I2c drivers not autoload like other PCI devices? Message-ID: <20070104193220.GA29541@kroah.com> References: <20070103165020.4b277ebc@freekitty> <20070104005600.GA25712@kroah.com> <20070103172916.7f9ca11a@freekitty> <20070104055128.GA8115@kroah.com> <20070104175412.76ebce25.khali@linux-fr.org> <20070104095412.16ac9f53@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070104095412.16ac9f53@localhost> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2825 Lines: 70 On Thu, Jan 04, 2007 at 09:54:12AM -0800, Stephen Hemminger wrote: > On Thu, 4 Jan 2007 17:54:12 +0100 > Jean Delvare wrote: > > > On Wed, 3 Jan 2007 21:51:28 -0800, Greg KH wrote: > > > On Wed, Jan 03, 2007 at 05:29:16PM -0800, Stephen Hemminger wrote: > > > > On Wed, 3 Jan 2007 16:56:00 -0800 > > > > Greg KH wrote: > > > > > > > > > On Wed, Jan 03, 2007 at 04:50:20PM -0800, Stephen Hemminger wrote: > > > > > > Is there some missing magic (udev rule?) that keeps i2c device modules > > > > > > from loading? For example: the Intel i2c-i801 module ought to get loaded > > > > > > automatically on boot up since it has a set of PCI id's that generate > > > > > > the necessary module aliases. It would be better if I2C device's autoloaded > > > > > > like other PCI devices. > > > > > > > > > > No, it should autoload, if it has a MODULE_DEVICE_TABLE() in it. In > > > > > fact, the i2c-i801 autoloads on one of my machines just fine. Are you > > > > > sure your pci ids match properly? > > > > > > > > > > thanks, > > > > > > > > > > greg k-h > > > > > > > > This laptop is running Ubuntu Edgy (6.10) and it doesn't autoload. > > > > Everything works fine if I manually load the module with modprobe. > > > > > > > > This device should match: > > > > > > > > 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02) > > > > 00: 86 80 da 27 01 00 80 02 02 00 05 0c 00 00 00 00 > > > > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > > > 20: a1 18 00 00 00 00 00 00 00 00 00 00 cf 10 88 13 > > > > 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 02 00 00 > > > > > > > > This driver modinfo: > > > > > > > > filename: /lib/modules/2.6.20-rc3/kernel/drivers/i2c/busses/i2c-i801.ko > > > > > > What does: > > > modprobe --show-depends `cat /sys/bus/pci/0000:00:1f.3/modalias` > > > show? > > > > Greg really means: > > modprobe --show-depends `cat /sys/bus/pci/devices/0000:00:1f.3/modalias` > > and same for the other commands below. > > > Ahak > $ modprobe --show-depends `cat /sys/bus/pci/devices/0000:00:1f.3/modalias` > WARNING: Not loading blacklisted module i2c_i801 > FATAL: Module pci:v00008086d000027DAsv000010CFsd00001388bc0Csc05i00 not found. > > And the blacklist entry is: > > # causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306) > blacklist i2c_i801 > > Looks like Ubuntu decided to wallpaper over a problem rather than fixing it I figured it was something like that, not a kernel issue at all :) good luck convincing ubuntu to remove the blacklist. greg k-h - 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/