Summary: | ASTERISK-00421: ztdummy device won't load - unresolved symbol zt_.... | ||
Reporter: | chris_de (chris_de) | Labels: | |
Date Opened: | 2003-10-23 13:22:30 | Date Closed: | 2011-06-07 14:00:43 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | If I compile zaptel (enabling ztdummy in Makefile) I can insmod zaptel but cannot insmod ztdummy. Using /lib/modules/2.4.18-14/misc/ztdummy.o /lib/modules/2.4.18-14/misc/ztdummy.o: unresolved symbol zt_unregister /lib/modules/2.4.18-14/misc/ztdummy.o: unresolved symbol zt_transmit /lib/modules/2.4.18-14/misc/ztdummy.o: unresolved symbol zt_receive /lib/modules/2.4.18-14/misc/ztdummy.o: unresolved symbol zt_register There are some other people also having this problem. In addition to that I only can compile zaptel if I change KINCLUDES from /usr/src/linux/include to /usr/src/linux. I use redhat 8 ****** ADDITIONAL INFORMATION ****** # lsmod | grep "usb" usb-uhci 26188 0 (unused) usbcore 77024 1 [hid usb-uhci] | ||
Comments: | By: Brian West (bkw918) 2003-10-24 13:35:28 use modprobe ztdummy By: chris_de (chris_de) 2003-10-25 12:11:59 # modprobe ztdummy /lib/modules/2.4.18-14/misc/ztdummy.o: unresolved symbol zt_unregister /lib/modules/2.4.18-14/misc/ztdummy.o: unresolved symbol zt_transmit /lib/modules/2.4.18-14/misc/ztdummy.o: unresolved symbol zt_receive /lib/modules/2.4.18-14/misc/ztdummy.o: unresolved symbol zt_register /lib/modules/2.4.18-14/misc/ztdummy.o: insmod /lib/modules/2.4.18-14/misc/ztdumm y.o failed /lib/modules/2.4.18-14/misc/ztdummy.o: insmod ztdummy failed By: Thorsten Lockert (tholo) 2003-10-25 16:23:49 Did you do "modprobe zaptel" first? By: Brian West (bkw918) 2003-10-25 18:21:45 modprobe ztdummy will pickup the module dependancies. So you shouldn't have to modprobe or insmod zaptel first. It sounds like kernel and kernel header version skew. By: Mark Spencer (markster) 2003-10-25 21:21:33 This is not a bug just a compile issue localized to this build environment. |