>>>>> "jorg" == jorg <[EMAIL PROTECTED]> writes:
jorg> [root@vulcan /lib/modules/2.4.13-11mdk/kernel/drivers/i2c]# insmod i2c-via jorg> Using /lib/modules/2.4.13-11mdk/kernel/drivers/i2c/i2c-via.o.gz jorg> /lib/modules/2.4.13-11mdk/kernel/drivers/i2c/i2c-via.o.gz: unresolved symbol jorg> i2c_bit_add_bus_R8c3bc60e jorg> /lib/modules/2.4.13-11mdk/kernel/drivers/i2c/i2c-via.o.gz: unresolved symbol jorg> i2c_bit_del_bus_R92b18f49 jorg> thus, can not get lm_sensors to work because of it.. jorg> [root@vulcan /lib/modules/2.4.13-11mdk/kernel/drivers/i2c]# sensors jorg> No sensors found! jorg> VIA KT133 chipset weird, recheck with 2.4.13-12mdk, it works for me (TM). Otherwise, I am not sure if you need i2c-via or i2c-viapro for kt133. Check with sensors detect. (I need i2c-viapro) root$ modprobe i2c-via /lib/modules/2.4.13-12mdkenterprise/kernel/drivers/i2c/i2c-via.o.gz: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.13-12mdkenterprise/kernel/drivers/i2c/i2c-via.o.gz: insmod /lib/modules/2.4.13-12mdkenterprise/kernel/drivers/i2c/i2c-via.o.gz failed /lib/modules/2.4.13-12mdkenterprise/kernel/drivers/i2c/i2c-via.o.gz: insmod i2c-via failed (I don't have that device), what is stranger is that I don't remind having unresolved symbols in 2.4.13-11mdk (I checked). Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
