Summary:ASTERISK-10228: Zaptel unknown symbol
Reporter:tootai (tootai)Labels:
Date Opened:2007-09-04 09:21:52Date Closed:2007-09-04 10:49:37
Versions:Frequency of
Description:Asterisk doesn't recognize any Zaptel channel but there is a wcfxo one. In dmesg we found

zaptel: Unknown symbol _GLOBAL_OFFSET_TABLE_

By installing zaptel stuff fron SVN 1.4 it's working like a charm. Debian Etch 2.6.18-5 kernel.
Comments:By: Brandon Kruse (bkruse) 2007-09-04 09:38:23

Try to make, and make install.

rmmod zaptel; insmod ./zaptel.ko ; insmod ./driver_name.ko

then check dmesg for errors.

You could be trying to insert the modules from a newer driver, older zaptel version. Common mistake.


By: tootai (tootai) 2007-09-04 10:22:39

If I didn't made it 5 times I didn't made it one ;-) I even reload the whole zaptel stuff from SVN

after make clean && make && make install

keewi:/usr/src/asterisk-trunk/zaptel-trunk# modprobe zaptel
FATAL: Error inserting zaptel (/lib/modules/2.6.18-5-vserver-1-686/misc/zaptel.ko): Unknown symbol in module, or unknown parameter (see dmesg)

From dmesg:

zaptel: Unknown symbol _GLOBAL_OFFSET_TABLE_

And on another terminal I also found

Message from syslogd@keewi at Tue Sep  4 16:18:21 2007 ...

keewi kernel: Oops: 0000 [#1]
keewi kernel: CPU:    0
keewi kernel: EIP is at 0xf88dc063
keewi kernel: eax: f88dc063   ebx: 00000001   ecx: 00000000   edx: dba9f128
keewi kernel: esi: c51c9200   edi: f6ec071c   ebp: f4eb2914   esp: e6581e30
keewi kernel: ds: 007b   es: 007b   ss: 0068
keewi kernel: Process asterisk (pid: 31112[#0], ti=e6580000 task=cb6cd000 task.ti=e6580000)
keewi kernel: Stack: f8bd892e dba9f128 00000008 c01506c9 f6ec071c c51c9200 dfff4140 c51c9200
keewi kernel:        00000000 dfebc740 dadad500 c014dff8 c51c9200 dfebc740 c51c9200 dfebc740
keewi kernel:        dfebc740 000003b3 00000054 c011487e c51c9200 dfebc740 00000000 00000000
keewi kernel: Call Trace:
keewi kernel: Code:  Bad EIP value.
keewi kernel: EIP: [<f88dc063>] 0xf88dc063 SS:ESP 0068:e6581e30

Rebuilding the zaptel SVN 1.4 against the *same* Asterisk trunk version and installing it does work.


By: Tilghman Lesher (tilghman) 2007-09-04 10:39:24

That is correct.  Zaptel trunk right now IS broken.  However, it a development version and is not intended to be used in production.  If you are using the trunk code, it is expected that you are a developer and that you know what you're doing.

By: Jason Parker (jparker) 2007-09-04 10:49:36

Zaptel trunk is currently in an unknown state.  For reasons that are out of the scope of this bug tracker, people have purposely not been updating trunk with fixes/updates.

Closing - this is not something that we'll fix in trunk.  Please use zaptel 1.4.