[plug] i2c???
Craig Ringer
craig at postnewspapers.com.au
Thu Jan 1 20:07:10 WST 2004
Mungo TheB wrote:
> playing with tv inputs and outputs
> XFree log says i2c loaded
... but it may be talking about XFree86 support for the kernel i2c
interfaces.
> anyone want to point me in the right direction of how to solve this?
>
> saa7108e.o: unresolved symbol i2c_probe
> saa7108e.o: unresolved symbol i2c_detach_client
> saa7108e.o: unresolved symbol i2c_check_functionality
> saa7108e.o: unresolved symbol i2c_del_driver
> saa7108e.o: unresolved symbol i2c_smbus_read_byte_data
> saa7108e.o: unresolved symbol schedule_timeout_Rsmp_17d59d01
> saa7108e.o: unresolved symbol kfree_Rsmp_037a0cba
> saa7108e.o: unresolved symbol printk_Rsmp_1b7d4074
> saa7108e.o: unresolved symbol kmalloc_Rsmp_93d4cfe6
> saa7108e.o: unresolved symbol i2c_smbus_write_byte_data
> saa7108e.o: unresolved symbol i2c_attach_client
> saa7108e.o: unresolved symbol i2c_add_driver
Looks like i2c-core hasn't been loaded, and may not be built for your
kernel. Make sure it exists
find /lib/modules/`uname -r` -name i2c-core.o
and is loadable
modprobe i2c-core
then try loading the module again.
If you can't find i2c-core, check that it isn't built into your kernel:
grep 'i2c_probe' /boot/System.map-`uname -r`
(if it finds something, then basic i2c support is probably built in to
your kernel image).
The fact that modprobe didn't try to load i2c-core for you, but instead
complained about unresolved symbols, suggested that your kernel may
entirely lack i2c support. Sould this be the case, just build a new
kernel with i2c enabled and you should be fine.
Craig Ringer
More information about the plug
mailing list