Benno Schulenberg <benno.schulenberg <at> gmail.com> writes: > > modprobe i2c-dev > modprobe i2c-dev -v <reveals> insmod /lib/modules/2.6.15-gentoo-r5/kernel/drivers/i2c/i2c-dev.ko
> What modules did this actually load? (Use -v. Or do lsmod now.) lsmod Module Size Used by i2c_dev 9344 0 eeprom 6672 0 uhci_hcd 29452 0 radeonfb 20884 0 fb 41000 1 radeonfb cfbcopyarea 4608 1 radeonfb cfbimgblt 3840 1 radeonfb cfbfillrect 4608 1 radeonfb ehci_hcd 39048 0 ohci_hcd 30340 0 i2c_sis96x 6532 0 i2c_core 19072 3 i2c_dev,eeprom,i2c_sis96x usbcore 115972 4 uhci_hcd,ehci_hcd,ohci_hcd > > 'i2cdetect -l' returns: > > i2c-0 unknown SiS96x SMBus adapter at 0x8100 Algorithm unavailable > > but building a 2.6.15-gentoo-r5 kernel, in the menu I see: > > <M> SiS 96x > > <M> I2C/SMBus Test Stub > Doesn't "Test Stub" mean that it doesn't really do anything? Read > the help, and probably say No. OK I eliminated that from the 2.6.15-gentoo-r5 kernel, but, it makes no difference: sensors -s No sensors found! /etc/conf.d/lm_sensors reveals: # Load modules at startup LOADMODULES=yes # Initialize sensors at startup INITSENSORS=yes MODULE_0=i2c-sis96x MODULE_1=eeprom I just don't get it.....? James -- gentoo-user@gentoo.org mailing list
