similar to: New CentOS 5 repo: dahdi, asterisk, freepbx RPMs

Hi, We installed the latest 1.4.24 on a test machine and can't get zaptel nor dahdi compile. It's a Linux Debian Etch. Errors we have: keewi:/usr/src/dahdi-linux-2.1.0.4# make make -C /lib/modules/2.6.18-custom.2/build ARCH=i386 SUBDIRS=/usr/src/dahdi-linux-2.1.0.4/drivers/dahdi DAHDI_INCLUDE=/usr/src/dahdi-linux-2.1.0.4/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes

On attempting to make Zaptel 1.2.16 on FC5, I get the following messages: /usr/src/zaptel-1.2.16/xpp/xbus-core.c: In function 'debugfs_open': /usr/src/zaptel-1.2.16/xpp/xbus-core.c:171: error: 'struct inode' has no member named 'u' make[3]: *** [/usr/src/zaptel-1.2.16/xpp/xbus-core.o] Error 1 make[2]: *** [/usr/src/zaptel-1.2.16/xpp] Error 2 make[1]: ***

I get the following error when trying to compile zaptel on CentOS 5 kernel 2.6.18-8.1.3.el5 CC [M] /root/asterisk-src/zaptel-1.2.17.1/xpp/xbus-core.o /root/asterisk-src/zaptel-1.2.17.1/xpp/xbus-core.c: In function ? /root/asterisk-src/zaptel-1.2.17.1/xpp/xbus-core.c:171: error: ? has no member named ? make[3]: *** [/root/asterisk-src/zaptel-1.2.17.1/xpp/xbus-core.o] Error 1 make[2]: ***

I'm trying to compile latest zaptel-1.2.13 and I'm getting following errors: /usr/src/Asterisk-1.2.14/zaptel-1.2.13/xpp/xbus-core.c: In function ?debugfs_open?: /usr/src/Asterisk-1.2.14/zaptel-1.2.13/xpp/xbus-core.c:171: error: ?struct inode? has no member named ?i_private? make[5]: *** [/usr/src/Asterisk-1.2.14/zaptel-1.2.13/xpp/xbus-core.o] Error 1 make[4]: ***

I just purchased an Amfeltec USB-FXO adapter and am trying to compile DAHDI 2.10 on a Raspberry PI running Pidora 2014 R3. I have all the dependencies but I get an error and cannot finish. Is it even possible to compile DAHDI for the ARM plataform? Here is the error I am getting: root at astpi dahdi-linux-complete-2.10.2+2.10.2]# make make -C linux all make[1]: Entering directory

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.8.0-rc5 DAHDI-Tools-v2.8.0-rc5 dahdi-linux-complete-2.8.0-rc5+2.8.0-rc5 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete *** THIS RC FIXES

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.8.0-rc5 DAHDI-Tools-v2.8.0-rc5 dahdi-linux-complete-2.8.0-rc5+2.8.0-rc5 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete *** THIS RC FIXES

Hi, I''m having problems with this configuration: iptables 1.3.7 (vanilla or repackaged for fc5) kernel 2.6.19 (vanilla) ROUTE 1.11 (last pom-ng) layer7-filter 2.6 (last in sf.net) connlimit (last pom-ng) When I try to use -j ROUTE in any chain in mangle table I have this error: [root@myhost ~]# iptables -v -t mangle -A POSTROUTING -p tcp --dport msnp -j ROUTE --gw

All, I have been trying to get CAPI4Linux working on my machine and being frank am failing miserably! I am looking for any help available, I am real newbie (so please be gentle) and choose to run Mandrake 9.2 as it appears quite friendly (or so I thought!). I have been following the guidance found at http://www.voip-info.org/wiki-Asterisk+How+to+connect+with+CAPI for the AVM card (actually I

I am enclosing the patch I have been working on. I have tested this on sles9 (2.6.5) and RHEL 4 (2.6.9). The patch applies cleanly on ChangeSet 11635. This patch was cleaned up based on Ian''s and DOI''s work. Signed-off-by: K. Y. Srinivasan (ksrinivasan@novell.com) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

It's both in 2.6 and recent 2.6 (for RH ASS2.1 you'll probably need to copy the latest 2.4 defintion, but I don't care for obsolete junk). Index: src/super.c =================================================================== --- src/super.c (revision 1014) +++ src/super.c (working copy) @@ -799,7 +799,7 @@ /* get first two blocks */ for (i=0; i<2; i++) { - bhs[i] = getblk

when i compile zaptel make linux26 make install i got these errors: make[1]: Leaving directory `/usr/src/zaptel-1.4/wct4xxp' make -C datamods clean make[1]: Entering directory `/usr/src/zaptel-1.4/datamods' make -C /lib/modules/2.4.27-3-386/build SUBDIRS=/usr/src/zaptel-1.4/datamods clean make[2]: Entering directory `/usr/src/kernel-headers-2.4.27-3-386' make: *** arch/i386/boot: No

Hello: Have a TE110P laying around and decided to see if I could build a router around it. I've tried compiling several versions of zaptel .1.4.x with the same results. I checked the zaptel changelog and can't find anything about it no longer being supported (or that it ever was for that matter). ztcfg: Zaptel Configuration SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)

hello, all of users: there are header files missed when you compile dahdi with kernel-2.6.29 or 2.6.33. i believe that few files are affected: wctdm.c dahdi-base.c wcb4xxp/base.c, opvxa1200.c... the errors look like these: ================================================ from?/usr/src/dahdi-linux-complete-2.2.0.2+2.2.0/linux/drivers/dahdi/dahdi-base.c:61:

Hi list, Enabling plugins returns fatal errors like the following: Jan 16 00:28:11 norman dovecot: deliver(jman at zultron.com): Fatal: Plugin sieve_plugin not found from directory /usr/lib64/dovecot/lda Same errors for loading plugins in the "protocol imap" section of dovecot.conf (tested trash_plugin), same errors for loading other plugins (tested virtual_plugin), same

always use the 2.6 variants and fix up for 2.4 under the hood Index: src/journal.c =================================================================== --- src/journal.c (revision 1156) +++ src/journal.c (working copy) @@ -105,9 +105,17 @@ return status; } -#else -#define ocfs_journal_start journal_start -#define ocfs_journal_stop journal_stop + +#define journal_start(journal, nblocks) \ +

Several nvidia-based systems don't support backlight control via the standard ACPI control mechanisms. Instead, it's necessary for the driver to modify the backlight control registers directly. This patch adds support for determining whether the registers appear to be in use, and if so registers a kernel backlight device to control them. The backlight can then be controlled via

Hi, Is there a reason that the allocate_empty_lowmem_region() function in hypervisor.c is only available in Domain 0. It is only included if CONFIG_XEN_PHYSDEV_ACCESS is defined, however, when I remove this it seems to work fine in DomUs. Thanks, Ross _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello Since TDM cards are known for being particular when it comes to motherboards (PCI 2.2, etc.), I was wondering if there is a utility that can check that the Zaptel driver works OK and can tell if the TDM card is compatible? That way, if an FXO module is not reporting an incoming call, we'd know it's because of the Zaptel driver, and not something elsewhere. Are "dmesg",

I am about to setup a new machine and based on a thread in the freetel-oslec list, I came across the idea of compiling Intel optimizations in when using oslec w/ dahdi. So I edit dahdi-linux-complete-2.1.0.4+2.1.0.2/linux/drivers/dahdi/dahdi_config.h to #define CONFIG_DAHDI_MMX which on its own wont compile. It was suggested to edit dahdi-linux-complete-2.1.0.4+2.1.0.2/linux/drivers/dahdi/Kbuild