lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 4 Jan 2007 11:32:20 -0800
From:	Greg KH <greg@...ah.com>
To:	Stephen Hemminger <shemminger@...l.org>
Cc:	Jean Delvare <khali@...ux-fr.org>, i2c@...sensors.org,
	linux-kernel@...r.kernel.org
Subject: Re: [i2c] Why to I2c drivers not autoload like other PCI devices?

On Thu, Jan 04, 2007 at 09:54:12AM -0800, Stephen Hemminger wrote:
> On Thu, 4 Jan 2007 17:54:12 +0100
> Jean Delvare <khali@...ux-fr.org> 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 <greg@...ah.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ