[Asterisk-Users] Asterisk Developer's Kit (TDM) help

[Steven Critchfield]

On Tue, 2003-07-29 at 19:01, Kyle Hagan wrote:
> I'm having trouble getting the cards configured. I have followed the
> instructions but get errors.
>  
> when I modprobe zaptel 
>  
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> proc_mkdir_Re6122de7
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> skb_over_panic_R5ced0794
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> devfs_generate_path_R4c75cb0f
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> devfs_register_Rcfcce5f5
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> devfs_register_chrdev_R118aac95
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> add_wait_queue_R2ca850b2
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> create_proc_entry_Rab06bca9
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> devfs_mk_dir_Ref49dc63
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> softnet_data_R338e35b2
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> __pollwait_R73a0d137
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> devfs_unregister_R8d92d91d
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> devfs_mk_symlink_R727d9a2e
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> __kfree_skb_Rc45b82d1
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> remove_proc_entry_R63ad0716
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> remove_wait_queue_R07012fb2
> /lib/modules/2.4.21-0.13mdk/misc/zaptel.o: unresolved symbol
> alloc_skb_Rdc2b24bd
> modprobe: insmod /lib/modules/2.4.21-0.13mdk/misc/zaptel.o failed
> modprobe: insmod zaptel failed
> 
> looks pretty similar for all modprobes it says to do.

This is because you don't have the proper symbols. The line noise
looking crap on the end is a versioning string. You may want to download
and build a custom kernel instead of relying on your mandrake kernel
that shipped with the install disks. This will ensure you have all the
right settings and that your modules will load appropriately.
 
-- 
Steven Critchfield <critch at basesys.com>