On Fri, 2003-03-21 at 10:28, Frank Hoonhout wrote: > Steven: > > Here is the output from depmod -ae > I do see errors. > > [EMAIL PROTECTED] /sbin/depmod -ae > depmod: *** Unresolved symbols in /lib/modules/2.4.18-27.8.0/misc/wcusb.o > depmod: usb_control_msg_Re80c4f9a > depmod: usb_submit_urb_R77d0e891 > depmod: usb_set_configuration_R38118f0c > depmod: usb_set_interface_Rfe0b0cf8 > depmod: usb_deregister_Rb5c0939b > depmod: usb_register_Ra6fe0a72 > depmod: *** Unresolved symbols in /lib/modules/2.4.18-27.8.0/misc/zaptel.o > depmod: __kfree_skb_R3810042c > depmod: create_proc_entry_Ra3afa0f7 > depmod: register_chrdev_Ref89ab9e > depmod: add_wait_queue_R0cbf8a39 > depmod: remove_wait_queue_Rb65338b9 > depmod: remove_proc_entry_Rec1fb130 > depmod: __pollwait_Ra26a5ce8 > depmod: softnet_data_Rd1ee1ba1 > depmod: skb_over_panic_R7ac7865f > depmod: proc_mkdir_R939a6693 > depmod: alloc_skb_Rd2becd82 > depmod: *** Unresolved symbols in /lib/modules/2.4.18-27.8.0/misc/ztd-eth.o > depmod: __kfree_skb_R3810042c > depmod: dev_remove_pack_Rbe8a66d1 > depmod: dev_queue_xmit_R8ac0fc82 > depmod: dev_add_pack_R09ed4520 > depmod: dev_get_by_name_R76e16b06 > depmod: skb_under_panic_R432fccad > depmod: skb_over_panic_R7ac7865f > depmod: alloc_skb_Rd2becd82 > > But the the files are in /lib/modules/2.4.18-27.8.0/misc. > > [EMAIL PROTECTED] misc]# ls -l > total 280 > -rw-r--r-- 1 root root 89788 Mar 20 18:32 tor2.o > -rw-r--r-- 1 root root 19048 Mar 20 18:32 torisa.o > -rw-r--r-- 1 root root 10828 Mar 20 18:32 wcfxo.o > -rw-r--r-- 1 root root 19252 Mar 20 18:32 wcfxs.o > -rw-r--r-- 1 root root 15620 Mar 20 18:32 wct1xxp.o > -rw-r--r-- 1 root root 24752 Mar 20 18:32 wcusb.o > -rw-r--r-- 1 root root 69324 Mar 20 18:32 zaptel.o > -rw-r--r-- 1 root root 5808 Mar 20 18:32 ztd-eth.o > -rw-r--r-- 1 root root 10920 Mar 20 18:32 ztdynamic.o > > They match the files in /usr/src/zaptel. > > I am not sure where to go from here.
Okay, time for a little kernel demystification. The unresolved symbols do not mean it didn't find a file, it means it didn't find the function that it needs. My next few comments are not RH bashing, just ignorance of where they put files. If your kernel was installed properly, somewhere on your system you will have a System.map-(kernel version) file. In this file is a list of the symbols in the associated kernel. Take the part of the unresolved symbol from above that doesn't look like line noise, and search for it in the System.map file. If you find it and just the line noise looking sections are different then you need to make sure you had the same modversions.h file that your kernel was compiled with. This will make sure the line noise section of your modules will match the with what is in the kernel. Just a note to those compiling your own kernel, this is why module versions can suck royally once you move the kernel off of the machine it was compiled on. If you are compiling on the machine the kernel will run on, then most problems go away. -- Steven Critchfield <[EMAIL PROTECTED]> _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
