Re: Insmod messages and modules space

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ralf Baechle wrote:
> 
> On Mon, Apr 09, 2001 at 08:10:16PM +0200, Shay Deloya wrote:
> 
> > 1.Should text segment of module after insmod be in KSEG2 or KUSEG ?
> > I've notices that the module address after insmod are c0... instead of 80...
> > Is it insmod Bug  ?
> 
> It's a sign of insmod working properly :)
> 
> > 2. I keep getting in insmod of busybox pkg , "relocation overflow" message
> > especially on printk symbols , when I debug the code, changing some function
> > declaration from static int func () to int func()  , makes the module to
> > insert correctly , anyone ?
> 
> Two possibilities, either you're using a too old and broken version of
> modutils or you used inapropriate options to compile your module.
> 

Compiling with -mlong-calls worked for me when I had the same problem
(modutils 2.4.5). Relinking the module with 'ld -r -o new_mod.o
orig_mod.o' was useful too ...it worked around some 'exceeds
local_symtab_size' messages.

Ian


[Index of Archives]     [Linux MIPS Home]     [LKML Archive]     [Linux ARM Kernel]     [Linux ARM]     [Linux]     [Git]     [Yosemite News]     [Linux SCSI]     [Linux Hams]

  Powered by Linux