The I2C mainboard interfaces option has been added to the 2.4.22 series (-r5, -r7 and -r9). This option allows for the proper usage of the bttv driver. Without this option (patch?) I cannot run both lm-sensors and bttv at the same time on the same system as I had before. Reproducible: Always Steps to Reproduce: 1. build new kernel using gentoo-sources-2.4.25 (or -r1 or -r2) including I2C module support 2. emerge i2c 3. emerge lm-sensors 4. /sbin/modprobe bttv; returns error "Segmentation Fault" Actual Results: The system will do one of two things depending on the order of loading the modules: 1) If bttv loads first, the kernel boot will hang 100% of the time (documented in the I2C group's dialog during the emerge i2c). 2) If i2c and lm-sensors-based modules load first, bttv will 100% of the time will Segmentation Fault Expected Results: When using the I2C mainboard interfaces option, the system would allow for all three sets of modules to run at the same time with no conflict: I2C, lm-sensors, and bttv. Currently if you have the bttv driver in use and would like to use i2c and lm-sensors or vice versa, the gentoo-sources 2.4.25 line will not correctly build the modules necessary to accomplish this.
You don't need to compile I2C modules in your kernel - the kernel merely has to support I2C and the I2C versions between the kernel and the i2c ebuild should match...
Please retest using in-kernel support for i2c only, and using the external "i2c" ebuild for the drivers as requested. Reopen this bug if any issues remain. Thanks.
