Since the newer kernels (2.6.22+) are marked stable and pci_module_init has been deprecated, you need a newer zaptel package or patch the old one so that it can use register_drivers. This ebuild proposal emerges zaptel 1.2.22.1 and has been successfully compiled on gentoo-sources 2.6.22 (with astribank, mmx, rtc and ecoslec use flags). Reproducible: Always Steps to Reproduce: 1. copy /usr/portage/net-misc/zaptel to your custom overlay 2. copy the oslec gzipped diff to /usr/portage/distfiles/ 3. add the gentoo.diff file to the custom overlay 4. ebuild <new-zaptel-ebuild> digest 5. emerge zaptel
Created attachment 139867 [details] net-misc/zaptel 1.2.22.1 ebuild
Created attachment 139869 [details, diff] a gentoo diff file
Created attachment 139870 [details] the diff distfile for oslec
Created attachment 139871 [details, diff] the diff distfile for oslec (same as above but ungzipped for the devs)
Created attachment 144079 [details] net-misc/zaptel-1.2.24 ebuild
Created attachment 144081 [details, diff] net-misc/zaptel-1.2.24 ebuild diff with resp. 1.2.23
Created attachment 144082 [details] oslec distfile
also copy files/zaptel-1.2.23-gentoo.diff to files/zaptel-1.2.24-gentoo.diff.
Created attachment 146464 [details, diff] zaptel-1.2.24.ebuild patch to add support for OSLEC Apply diff to zaptel-1.2.24.ebuild in offciial portage tree and place the OSLEC distfile in /usr/portage/distfiles/.
Created attachment 146707 [details, diff] zaptel-1.2.24-linux-mod.diff in FILESDIR diff for linux-mod
Created attachment 146709 [details] net-misc/zaptel-1.2.24.ebuild diff for linux-mod net-misc/zaptel-1.2.24 with linux-mod
Created attachment 146711 [details] net-misc/zaptel-1.2.24.ebuild for linux-mod for non-devs: duplicate /usr/portage/net-misc/zaptel to your custom overlay (eg. /usr/local/portage), place this ebuild there, rename it to *-r1.ebuild, make sure you manually copied th3e oslec distfile to /usr/portage/distfiles/ and digest the custom zaptel ebuild. Please report any build problms. I tested it on x86.
ebuild+patch for zaptel-1.2.25 in bug #216974.
Doesn't build for me. I copied zaptel-1.2.24.ebuild to /usr/local/portage/net-misc/zaptel/zaptel-1.2.24-r1.ebuild and `ebuild zaptel-1.2.24-r1.ebuild digest` But when I emerge: pbx zaptel # emerge zaptel WARNING: repository at /usr/local/portage is missing a repo_name entry Calculating dependencies... done! >>> Emerging (1 of 1) net-misc/zaptel-1.2.24-r1 * oslec-0.1-zaptel-1.2.24.diff.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * oslec-0.1.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * zaptel-1.2.24.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 2.6.25-gentoo-r7 * Running pre-flight checks... * Zaptel is happy and continues... :) >>> Unpacking source... >>> Unpacking zaptel-1.2.24.tar.gz to /var/tmp/portage/net-misc/zaptel-1.2.24-r1/work >>> Unpacking oslec-0.1.tar.gz to /var/tmp/portage/net-misc/zaptel-1.2.24-r1/work >>> Unpacking oslec-0.1-zaptel-1.2.24.diff.gz to /var/tmp/portage/net-misc/zaptel-1.2.24-r1/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/local/portage/net-misc/zaptel/files/zaptel-1.2.24-gentoo.diff * ( zaptel-1.2.24-gentoo.diff ) * * ERROR: net-misc/zaptel-1.2.24-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 3597: Called epatch '/usr/local/portage/net-misc/zaptel/files/zaptel-1.2.24-gentoo.diff' * environment, line 1483: Called die * The specific snippet of code: * die "Cannot find \$EPATCH_SOURCE!"; * The die message: * Cannot find $EPATCH_SOURCE! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-misc/zaptel-1.2.24-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-misc/zaptel-1.2.24-r1/temp/environment'. * This ebuild is from an overlay: '/usr/local/portage/' * * Messages for package net-misc/zaptel-1.2.24-r1: * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/local/portage/net-misc/zaptel/files/zaptel-1.2.24-gentoo.diff * ( zaptel-1.2.24-gentoo.diff ) * * ERROR: net-misc/zaptel-1.2.24-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 3597: Called epatch '/usr/local/portage/net-misc/zaptel/files/zaptel-1.2.24-gentoo.diff' * environment, line 1483: Called die * The specific snippet of code: * die "Cannot find \$EPATCH_SOURCE!"; * The die message: * Cannot find $EPATCH_SOURCE! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-misc/zaptel-1.2.24-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-misc/zaptel-1.2.24-r1/temp/environment'. * This ebuild is from an overlay: '/usr/local/portage/' Where is zaptel-1.2.24-gentoo.diff ? PS. I'm currently running 2.6.18-gentoo-r4 with zaptel-1.2.16 (with oslec) and would like to upgrade to a newer kernel that's still in portage, but zaptel-1.2.16 broke with upgraded kernel. Anyhow I'm trying to upgrade to latest stable x86 kernel 2.6.25-r7 without breaking zaptel+oslec and asterisk/freepbx.
(In reply to comment #14) > Where is zaptel-1.2.24-gentoo.diff ? Did you try Comment #8 ?
OK, I missed Comment #8. I've refollowed the instructions and now in /usr/portage/local/net-misc/zaptel/ I have: ~/zaptel-1.2.24-r1.ebuild ~/files/zaptel-1.2.24-linux-mod.diff ~/files/zaptel-1.2.24.ebuild.diff ~/files/zaptel-1.2.24-gentoo.diff but emerge fails looking for ARCH=x86 folder instead of i386: LD [M] /var/tmp/portage/net-misc/zaptel-1.2.24-r1/work/zaptel-1.2.24/zttranscode.ko LD [M] /var/tmp/portage/net-misc/zaptel-1.2.24-r1/work/zaptel-1.2.24/ztdynamic.ko make[1]: Leaving directory `/usr/src/linux-2.6.25-gentoo-r7' * Preparing oslec module make -C /lib/modules/2.6.18-gentoo-r4/build EXTRA_CFLAGS='-I/var/tmp/portage/net-misc/zaptel-1.2.24-r1/work/oslec-0.1/kernel/../spandsp-0.0.3/src/spandsp -DEXPORT_SYMTAB -O6' SUBDIRS=/var/tmp/portage/net-misc/zaptel-1.2.24-r1/work/oslec-0.1/kernel modules make[1]: Entering directory `/usr/src/linux-2.6.18-gentoo-r4' Makefile:486: /usr/src/linux-2.6.18-gentoo-r4/arch/x86/Makefile: No such file or directory make[1]: *** No rule to make target `/usr/src/linux-2.6.18-gentoo-r4/arch/x86/Makefile'. Stop. make[1]: Leaving directory `/usr/src/linux-2.6.18-gentoo-r4' make: *** [all] Error 2 * * ERROR: net-misc/zaptel-1.2.24-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3541: Called linux-mod_src_compile * environment, line 2623: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CC=\"$(get-KERNEL_CC)\" LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CC="$(get-KERNEL_CC)" LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * The die message: * Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CC=i686-pc-linux-gnu-gcc LDFLAGS= KVERS=2.6.25-gentoo-r7 SRC=/usr/src/linux ARCH=x86 all I have /usr/src/linux -> /usr/src/linux-2.6.25-gentoo-r7 but have not booted into the 2.6.25-gentoo-r7 kernel. I'm still running 2.6.18-gentoo-r4 I see the 2.6.25-r7 kernel introduces the "x86" arch in addition to the "i386": pbx zaptel # ls /usr/src/linux-2.6.18-gentoo-r4/arch alpha arm26 frv i386 m32r m68knommu parisc ppc sh sparc um x86_64 arm cris h8300 ia64 m68k mips powerpc s390 sh64 sparc64 v850 xtensa pbx zaptel # ls /usr/src/linux-2.6.25-gentoo-r7/arch Kconfig arm blackfin frv i386 m32r m68knommu mn10300 powerpc s390 sparc um x86 alpha avr32 cris h8300 ia64 m68k mips parisc ppc sh sparc64 v850 xtensa I'll try booting to 2.6.25-r7 and emerging zaptel when my pbx isn't very busy.
(In reply to comment #14) > I see the 2.6.25-r7 kernel introduces the "x86" arch in addition to the "i386" Side note: you may want to rename the custom ebuilds to zaptel-1.2.26 while you're at it. Anyway, it seems that your report is related to $(tc-arch-kernel). In fact, the toolchain eclass has a note about 2.6.24+ kernels: "the x86_64 and i38 trees have been unified into x86". Personally, I got stuck with 2.6.23 for mISDN-related issues. So I haven't tried yet a more recent kernel. But I'm guessing that if you try zaptel-1.2.26 it should emerge fine (you will needto rename some files in the custom overlay).
I copied oslec zaptel-1.2.24.ebuild to zaptel-1.2.26.r1 and added the xpputils patch from the official portage zaptel-1.2.26.ebuild epatch "${FILESDIR}"/zaptel-1.2.25-xpputils.diff and copied /usr/portage/distfiles/oslec-0.1-zaptel-1.2.24.diff.gz to oslec-0.1-zaptel-1.2.26.diff.gz and copied /usr/portage/local/net-misc/zaptel/files/zaptel-1.2.23-gentoo.diff to zaptel-1.2.26-gentoo.diff and then booted into linux-2.6.25-r7 and was able to emerge my zaptel Unfortunately, while outgoing calls on my PSTN trunk worked, incoming calls were not answered. I turned on verbosity and set debug level 256 in asterisk, but got not a peep as to why asterisk wasn't picking up incoming calls. So I've rolled back to linux-2.6.18-gentoo-r4 with oslec zaptel-1.2.16
(In reply to comment #18) > was able to emerge my zaptel good. > Unfortunately, while outgoing calls on my PSTN trunk worked, incoming calls > were not answered. I turned on verbosity and set debug level 256 in asterisk, > but got not a peep as to why asterisk wasn't picking up incoming calls. That's very odd and I can't reproduce the problem since I'm not upgrading from 2.6.23 for now. However, you can try to ask for help on the asterisk mailing list. (If you have a test server and an extra card you can try to upgrade without oslec but I doubt that your problem is related to this)
net-misc/zaptel was removed from the portage tree on 2011-02-27. please upgrade to net-misc/dahdi.
