insmod module.ko

[Jim]

Thanks Mike and all responses. The loading module works now after adding 
a full path to the insmod. Now there is another issue. My module.ko 
contains an i2c function i2c_add_driver() and other i2c functions. The 
i2c has been built in kernel, but loading module.ko was crashed at 
i2c_add_driver() in an exception of null address. The i2c functions were 
not linked in module.ko. I am not clear whether the unresolved symbols 
should be resolved in kernel module building process or in insmod 
loading process. Could you clarify please? Does the insmod loading 
process search unresolved symbols in kernel binary

As I mentioned that the module.o was running fine in kernel 2.4. In 
kernel 2.4, I did not even specify the full path to the insmod, it was 
called just "insmod module.o". In kernel 2.6, I have to call "insmod 
/usr/lib/2.6.8/kernel/module.ko" to make it works. I am not sure if I 
was still missing something in kernel 2.6 loading process?

Thank you.

Jim




Mike Frysinger wrote:

> On Thursday 06 July 2006 19:06, yh at bizmail.com.au wrote:
> 
>>Thanks Bernhard. I enabled kernel 2.6, but could not build it, please see
>>following errors from applets.a. Will a "make clean" fix it?
> 
> 
> yes, after changing .config you always need to run `make clean` first
> -mike