linux-mips
[Top] [All Lists]

Re: Insmod messages and modules space

To: Ralf Baechle <ralf@oss.sgi.com>
Subject: Re: Insmod messages and modules space
From: Ian Soanes <ians@lineo.com>
Date: Tue, 10 Apr 2001 09:55:16 +0100
Cc: Shay Deloya <shay@jungo.com>, "'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Organization: Lineo UK
References: <01040921101605.01025@athena.home.krftech.com> <20010409211447.A18894@bacchus.dhis.org>
Sender: owner-linux-mips@oss.sgi.com
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

<Prev in Thread] Current Thread [Next in Thread>