[Asterisk-Users] Problem with ztdummy

[Steven Critchfield]

On Tue, 2003-03-18 at 08:21, Rattana BIV wrote:
> Hi,
> 
> I have some problem with ztdummy in order to use Conference in asterisk.
> 
> When I do modprobe ztdummy I have this :
> 
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> proc_mkdir_Rsmp_220b03b4
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> create_proc_entry_Rsmp_3a9bfbd2
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> ppp_output_wakeup_Rsmp_fc4c9ef0
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol __write_lock_failed
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> request_module_Rsmp_27e4dc04
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> register_chrdev_Rsmp_65405f1d
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> remove_proc_entry_Rsmp_cfd23da1
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> __tasklet_schedule_Rsmp_ed5c73bf
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> tasklet_kill_Rsmp_79ad224b
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> ppp_input_error_Rsmp_14a5ddc7
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> __generic_copy_to_user_Rsmp_d523fdd3
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> ppp_unregister_channel_Rsmp_d0b1c903
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> unregister_chrdev_Rsmp_c192d491
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> remove_wait_queue_Rsmp_2d22232f
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> alloc_skb_Rsmp_3702adc3
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol __read_lock_failed
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> __wake_up_Rsmp_127fda83
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> skb_over_panic_Rsmp_7acbf56a
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> ppp_register_channel_Rsmp_bd63214e
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol printk_Rsmp_1b7d4074
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol kfree_Rsmp_037a0cba
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> tasklet_init_Rsmp_a5808bbf
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> __kfree_skb_Rsmp_980007b5
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> cpu_raise_softirq_Rsmp_d01f3ee8
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> ppp_unit_number_Rsmp_960fd73e
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol sprintf_Rsmp_3c2c5af5
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> ppp_channel_index_Rsmp_dc85af48
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol kmalloc_Rsmp_93d4cfe6
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> ppp_input_Rsmp_65b5d6aa
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> __pollwait_Rsmp_57ac46fa
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> schedule_Rsmp_4292364c
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> __generic_copy_from_user_Rsmp_116166aa
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> softnet_data_Rsmp_20eece54
> /lib/modules/2.4.7-10/misc/zaptel.o: unresolved symbol
> add_wait_queue_Rsmp_0987e9bc
> /lib/modules/2.4.7-10/misc/zaptel.o: insmod
> /lib/modules/2.4.7-10/misc/zaptel.o failed
> /lib/modules/2.4.7-10/misc/zaptel.o: insmod ztdummy failed
> 
> 
> Notice that I don't use Zaptel device. So I think strange that I need
> ztdummy in order to use conference.
> 
> Does anyone have a tip ?

Yes, I have a couple of tips for you.

First. Please do not reply to a message from a thread unrelated to what
you are asking, and just change the subject line. Those of us who are
reading through a threaded mail reader like to read a thread at a time,
and your message pops up in the middle of that thread. It is just as
easy to click on the mailing list address and get your mail reader to
create a new message with its own unique message ID that won't be
threaded wrong.

Secondly, You need the ztdummy module as a timing source for you
conferences. The conference app needs to mix and redistribute audio to
all member channels and is tightly bound to a consistent interupt to do
it's job. It was implemented to work with zapata hardware which gives a
consistent interupt. ztdummy is needed then to give you your interface
when you don't have zapata hardware.

Third, the unresolved symbols are because your kernel was compiled with
module version, and your modules where not. Please look in the Makefile
in the zaptel directory. Line 23 should have picked up your
modversions.h file if it was available. You may be best off recompliling
your kernel anyways if you can. You are many revisions behind. Current
2.4 kernel is 2.4.20.

-- 
Steven Critchfield  <critch at basesys.com>