http://www.linux-mips.org/wiki?title=Modules&feed=atom&action=history 2013-06-19T06:55:28Z Revision history for this page on the wiki MediaWiki 1.20.2 //www.linux-mips.org/wiki?title=Modules&diff=6246&oldid=prev 2004-11-11T13:03:33Z

<p></p> <p><b>New page</b></p><div>== Insmod complains about the _gp_disp symbol being undefined ==<br /> <br /> &lt;code&gt;_gp_disp&lt;/code&gt; is a magic symbol used with PIC code on MIPS. Be happy, this error message saved you from crashing your system. You should use the same compiler options to compile a kernel module as the kernel makefiles do. In particular the options &lt;code&gt;-fno-pic -mno-abicalls&lt;/code&gt; are important.<br /> <br /> == Loading a module results in relocation overflow errors ==<br /> <br /> The attempt to load a module results in relocation overflow messages for virtually every function used in the kernel:<br /> <br /> mymod.o: Relocation overflow of type 4 for printk<br /> mymod.o: Relocation overflow of type 4 for printk<br /> mymod.o: Relocation overflow of type 4 for printk<br /> mymod.o: Relocation overflow of type 4 for alloc_etherdev<br /> ...<br /> <br /> This error is caused by the limited range of relocation type 4 (R_MIPS26) which due to it's 26-bit offset only has a 28-bit reach. Modules and kernels happen to be located very far from each other and as the result this 28-bit range is insufficient. Insmod, not being stupid notices the problem and issues this error message.<br /> <br /> The solution is the same as in the previous section. When compiling a kernel you ''must'' use the same compiler flags for modules as your actual kernel source is using in this particular kernel configuration. These are different from the flags that are used during the build of the kernel itself. In this particular case the module was built without &lt;code&gt;-mlong-calls&lt;/code&gt; which is causing this kind of error.</div>

Ralf