Problems with tdm11b card

Hello, I am running asterisk 1.2.6 with zaptel 1.2.5 on a SuSE 10 server. The instalation worked fine but the zaptel module don’t want to load. I checked the dmesg and i got the following message:

zaptel: module not supported by Novell, setting U taint flag.
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.2.5 Echo Canceller: KB1
wcfxs: module not supported by Novell, setting U taint flag.
wcfxs: disagrees about version of symbol zt_receive
wcfxs: Unknown symbol zt_receive
wcfxs: disagrees about version of symbol zt_qevent_lock
wcfxs: Unknown symbol zt_qevent_lock
wcfxs: disagrees about version of symbol zt_ec_chunk
wcfxs: Unknown symbol zt_ec_chunk
wcfxs: disagrees about version of symbol zt_transmit
wcfxs: Unknown symbol zt_transmit
wcfxs: disagrees about version of symbol zt_unregister
wcfxs: Unknown symbol zt_unregister
wcfxs: disagrees about version of symbol zt_hooksig
wcfxs: Unknown symbol zt_hooksig
wcfxs: disagrees about version of symbol zt_register
wcfxs: Unknown symbol zt_register
wctdm: module not supported by Novell, setting U taint flag.
ACPI: PCI Interrupt 0000:03:0c.0[A] -> GSI 53 (level, low) -> IRQ 217
Freshmaker version: 73
Freshmaker passed register test
Module 0: Installed – AUTO FXS/DPO
Module 1: Installed – AUTO FXO (FCC mode)
Module 2: Not installed
Module 3: Not installed
Found a Wildcard TDM: Wildcard TDM400P REV I (2 modules)

Please tell me what can I do?

There is a mismatch of your zaptel drivers. Make sure to remove any Suse Zaptel/asterisk packages from the system and recompile the zaptel/asterisk source. Make sure to unload any zaptel drivers currently loaded and then load the drivers from the source you just compiled.

[quote=“zozo6015”]Hello, I am running asterisk 1.2.6 with zaptel 1.2.5 on a SuSE 10 server. The instalation worked fine but the zaptel module don’t want to load. I checked the dmesg and i got the following message:

zaptel: module not supported by Novell, setting U taint flag.
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.2.5 Echo Canceller: KB1
wcfxs: module not supported by Novell, setting U taint flag.
wcfxs: disagrees about version of symbol zt_receive
wcfxs: Unknown symbol zt_receive
wcfxs: disagrees about version of symbol zt_qevent_lock
wcfxs: Unknown symbol zt_qevent_lock
wcfxs: disagrees about version of symbol zt_ec_chunk
wcfxs: Unknown symbol zt_ec_chunk
wcfxs: disagrees about version of symbol zt_transmit
wcfxs: Unknown symbol zt_transmit
wcfxs: disagrees about version of symbol zt_unregister
wcfxs: Unknown symbol zt_unregister
wcfxs: disagrees about version of symbol zt_hooksig
wcfxs: Unknown symbol zt_hooksig
wcfxs: disagrees about version of symbol zt_register
wcfxs: Unknown symbol zt_register
wctdm: module not supported by Novell, setting U taint flag.
ACPI: PCI Interrupt 0000:03:0c.0[A] -> GSI 53 (level, low) -> IRQ 217
Freshmaker version: 73
Freshmaker passed register test
Module 0: Installed – AUTO FXS/DPO
Module 1: Installed – AUTO FXO (FCC mode)
Module 2: Not installed
Module 3: Not installed
Found a Wildcard TDM: Wildcard TDM400P REV I (2 modules)

Please tell me what can I do?[/quote]

I use exactly the same configuration. (since today)
When you install Asterisk1.2.6 you will find that during Suse installation there are already modules installed in /usr/lib/asterisk/modules.
You have to remove ALL modules there and do a “make install” in /usr/src/asterisk

After that my system started working (including TDM11B) :laughing:

Gr.
Henk

I am also running Asterisk (1.2.12.1) on a SuSE 10 server, and got this message, I followed the suggestion of removing everything from the modules directory and doing a new make install but I still get the same error:

any suggestions?

modprobe wctdm
FATAL: Error inserting wctdm (/lib/modules/2.6.13-15-default/misc/wctdm.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error running install command for wctdm

dmesg
wctdm: module not supported by Novell, setting U taint flag.
wctdm: disagrees about version of symbol zt_receive
wctdm: Unknown symbol zt_receive
wctdm: disagrees about version of symbol zt_qevent_lock
wctdm: Unknown symbol zt_qevent_lock
wctdm: disagrees about version of symbol zt_ec_chunk
wctdm: Unknown symbol zt_ec_chunk
wctdm: disagrees about version of symbol zt_transmit
wctdm: Unknown symbol zt_transmit
wctdm: disagrees about version of symbol zt_unregister
wctdm: Unknown symbol zt_unregister
wctdm: disagrees about version of symbol zt_hooksig
wctdm: Unknown symbol zt_hooksig
wctdm: disagrees about version of symbol zt_register
wctdm: Unknown symbol zt_register

Ok, a reboot seems to have fixed that particular problem. I guess it wasn’t unloading the module from memory inspight of a rmmod command.

In any case, the error I now get is on trying to start asterisk

asterisk (start) -v
/usr/lib/asterisk/modules/chan_zap.so: undefined symbol: pri_restart
and then it fails to load asterisk.

This is discussed in another discussion
forums.digium.com/viewtopic.php? … prirestart

but the solution seems to be the same - remove all modules and recompile.
Since I did that for the earlier solution, this seems unlikely to, and if fact did not seem to solve my problem.

Any other thoughts? Thanks in advance …

are you compiling libpri as well as zaptel ? i don’t recall why exactly, but i’ve always compiled libpri on my systems, regardless of whether they are connecting to a PRI.

yes. I recompiled libpri as well, and per something else that I read, although I can’t find the reference to it, I compiled the libpri before zaptel and asterisk.

Once compiled, modprobe, zttools, and ztcfg work fine, it’s only asterisk that fails.

I have a similar problem regarding tdm001

ERROR
ZT_CHANCONFIG failed on channel 1: No such device or address (6)

zaptel Version: 1.2.10 … is OK but when

wctdm: module not supported by Novell, setting U taint flag.
or

wcfxo: module not supported by Novell, setting U taint flag.

lsmod wctdm 33856 0 wcfxo 13088 0 zaptel 187396 2 wctdm,wcfxo crc_ccitt 2176 1 zaptel

I had run into this problem before getting to my current one.

A search of the forum indicated that there were three primary reasons for this error. (1) that the 12 volt power source (pc power plug) was not plugged into the digium card, (2) That your motherboard didn’t support the right version of the PCI standard (2.1?), or (3) that you used the default installtion of SuSE that installed an (incompatible) version of asterisk and did not completely remove that earlier version before installing the most reacent version that you downloaded. In particular, it was suggested to delete the entire modules directory and re make (clean/make/install) all the packages.

following this advice got me past your problem and into my current (still unsoved) predicament.

I’ve checked for all modules and I found no compatibility issues.

modprobe zaptel reports the following error message:

zaptel: module not supported by Novell, setting U taint flag. Zapata Telephony Interface Registered on major 196 Zapata Version:1.2.10 Echo Canceller: KB1
sould I recompile a new kernel? My kernel=2.6.13-15.12-default, just upgrade source & rpm.
SuSE 11.x supports asterisk(I thing with pre-build rpms) should I upgrade
or I just need a new asterisk patch?.