[asterisk-users] Bristuffed asterisk 1.2.10 on Suse 10 - problem with module versionmagic

[Tzafrir Cohen]

On Sun, Sep 17, 2006 at 03:34:05PM +0200, Paul Hewlett wrote:
> On Saturday 16 September 2006 20:35, Tzafrir Cohen wrote:
> > On Fri, Sep 15, 2006 at 02:58:02PM +0200, Robert Rozman wrote:
> > > I'm banging my head on compiling bristuff modules for Suse 10.0 with
> > > kernel
> > >
> > >
> > > Linux laps1 2.6.13-15.11-smp #1 SMP Mon Jul 17 09:43:01 UTC 2006 x86_64
> > > x86_64 x86_64 GNU/Linux
> > >
> > >
> > > and Asterisk 1.2.10-BRIstuffed-0.3.0-PRE-1s.
> > >
> > > I get this :
> > >
> > > laps1:~/Voipy/Bristuff/bristuff-0.3.0-PRE-1s/zaptel # modprobe zaphfc
> > > FATAL: Error inserting zaphfc
> > > (/lib/modules/2.6.13-15.11-smp/misc/zaphfc.ko): Invalid module format
> > >
> > > and this in dmesg :
> > >
> > > zaphfc: version magic '2.6.13-15.11-smp gcc-4.0' should be
> > > '2.6.13-15.11-smp SMP gcc-4.0'
> >
> > This means you built zaptel with the wrong kernel headers. Is there a
> > SUSE power user in the crowd?
> 
>   From memory as I do not use SUSE anymore..
> 
>   Suse already has the zaptel modules in its kernel under the (IIRC) the extra 
> directory (instead of misc) . you end up with 2 sets of zaptel modules in the 
> linux module tree and modprobe then gets confused as to which to load.
> 
> Look for a directory /lib/modules/2.6.13-15.11-smp/extra
> 
> You must (again from memory) delete the old modules abd rerun depmod or 
> rebuild your asterisk

deleting files from a package is probably not smart and works agains
rpm. Why not just remove the package altogether (rpm -e) ?

-- 
Tzafrir Cohen         sip:tzafrir at local.xorcom.com
icq#16849755          iax:tzafrir at local.xorcom.com
+972-50-7952406          jabber:tzafrir at jabber.org
tzafrir.cohen at xorcom.com     http://www.xorcom.com