On Sat, Jun 07, 2003 at 08:53:58PM -0400, Brett I. Holcomb wrote:
> 
> I built a test kernel with i2c /proc option and that worked.  However, to run 
> sensors-detect I need the /dev option so I went back to menuconfig and 
> checked it.  I did make dep && make clean bzImage modules modules_install
> 
> and got the errors shown below (these are from bug 10629 - I have 
> 2.4.20-xfs-r3).  Bugzilla lists this and the comment from Brandon is this is 
> not a bug - we have to insure the deps we build this agains are the same we 
> build the kernel with.  Okay - how do I do that???
> 
> This kernel is the same one I've been running with for a couple of weeks, 
> same /usr/src/linux tree.  I built the kernel with the /proc i2c option with 
> no problem - booted it and it worked - so I just went back and added the /dev 
> option.  Now it's broken.  I tried running make mrproper, restoring my 
> .config and running the make dep && .... command.  I also tried make clean.  
> None of that works.  I even did depmod -a before building these.
> 
> Any ideas on how to get the modules to "insure my deps" are proper?
> 
> Thanks.
> 
> depmod:         i2c_bit_del_bus_R88f4afaf
> depmod:         i2c_bit_add_bus_R933524db
> depmod: *** Unresolved symbols in 
> /lib/modules/2.4.19-gentoo-r10/misc/i2c-i810.o
> depmod:         i2c_bit_del_bus_R88f4afaf
> depmod:         i2c_bit_add_bus_R933524db
> depmod: *** Unresolved symbols in 
> /lib/modules/2.4.19-gentoo-r10/misc/i2c-savage
>                                  4.o
> depmod:         i2c_bit_del_bus_R88f4afaf
> depmod:         i2c_bit_add_bus_R933524db
> depmod: *** Unresolved symbols in 
> /lib/modules/2.4.19-gentoo-r10/misc/i2c-via.o
> depmod:         i2c_bit_del_bus_R88f4afaf
> depmod:         i2c_bit_add_bus_R933524db
> depmod: *** Unresolved symbols in 
> /lib/modules/2.4.19-gentoo-r10/misc/i2c-voodoo
>                                  3.o
> depmod:         i2c_bit_del_bus_R88f4afaf
> depmod:         i2c_bit_add_bus_R933524db
> 

Hello Brett,

The functions i2c_bit_(add|del)_bus() are only available if you compile
your kernel with CONFIG_I2C_ALGOBIT. Check your .config file.

If you keep getting unresolved symbols you should need to run 'modprobe
i2c-algo-bit' before running sensors-detect.

Regards,

-- 
Hamilton Coutinho
[EMAIL PROTECTED]
Porto Alegre - RS - Brasil

--
[EMAIL PROTECTED] mailing list

Reply via email to