Hi Darrick Thanks for the quick reply. I think I'm making some progress. There is a Zaptel firmware at:
http://downloads.digium.com/pub/telephony/firmware/releases/ I've tried dropping that in, and it's booting now, with some signs of success. However, as has been mentioned before, the boot time is now getting absolutely huge - 10 minutes and counting. This is because the wctdm24xxp board keeps starting up, and then saying: wctdm24xxp0: Missed interrupt. Increasing latency to NN ms to compensate It then reinitializes, and cycles like this for minutes on end, until NN climbs from 4 to 25, 1ms at a time. It then becomes more successful from NN=25 onwards, installing the modules, but still gives up with the above message, until NN=32, when it gives up totally: wctdm24xxp0: ERROR: Unable to service card within 30 ms and unable to further increase latency. However, it then seems to load absolutely fine. This delayed boot time a great deal when the ec firmware was not present, but now, it boots the ec each and every time it tries to do this, which takes a huge amount of time. I'll append the relevant bits of dmesg here, for reference. Update: it's finally booted up, and I am without echo, with a working echo-cancellation module. Thanks Tom dmesg without vpmadt032 fw: Zapata Telephony Interface Registered on major 196 Zaptel Version: 1.4.12.1 Zaptel Echo Canceller: MG2 Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 4 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 5 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 6 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 7 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 8 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 9 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 10 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 11 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 12 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 13 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 14 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 15 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 16 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 17 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 18 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 19 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 20 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 21 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 22 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 23 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 24 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 25 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Installed -- AUTO FXO (FCC mode) Port 3: Installed -- AUTO FXO (FCC mode) Port 4: Installed -- AUTO FXS/DPO VPM100: Not Present VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace wctdm24xxp0: Missed interrupt. Increasing latency to 26 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 27 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Installed -- AUTO FXO (FCC mode) Port 3: Installed -- AUTO FXO (FCC mode) Port 4: Installed -- AUTO FXS/DPO VPM100: Not Present VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace wctdm24xxp0: Missed interrupt. Increasing latency to 28 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 29 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Installed -- AUTO FXO (FCC mode) Port 3: Installed -- AUTO FXO (FCC mode) Port 4: Installed -- AUTO FXS/DPO VPM100: Not Present VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace wctdm24xxp0: Missed interrupt. Increasing latency to 30 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 31 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Installed -- AUTO FXO (FCC mode) Port 3: Installed -- AUTO FXO (FCC mode) Port 4: Installed -- AUTO FXS/DPO VPM100: Not Present VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace wctdm24xxp0: Missed interrupt. Increasing latency to 32 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: ERROR: Unable to service card within 30 ms and unable to further increase latency. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Installed -- AUTO FXO (FCC mode) Port 3: Installed -- AUTO FXO (FCC mode) Port 4: Installed -- AUTO FXS/DPO VPM100: Not Present VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace Found a Wildcard TDM: Wildcard TDM410P (4 modules) Registered tone zone 4 (United Kingdom) dmesg with vpmadt032: Zapata Telephony Interface Registered on major 196 Zaptel Version: 1.4.12.1 Zaptel Echo Canceller: MG2 Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 4 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 5 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 6 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 7 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 8 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 9 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 10 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 11 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 12 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 13 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 14 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 15 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 16 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 17 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 18 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 19 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 20 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 21 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 22 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 23 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 24 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 25 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Installed -- AUTO FXO (FCC mode) Port 3: Not installed Port 4: Not installed VPM100: Not Present VPMADT032 Loading firwmare... Success Booting VPMADT032 VPMADT032: Present and operational (Firmware version 107) wctdm24xxp0: Missed interrupt. Increasing latency to 26 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 27 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Installed -- AUTO FXO (FCC mode) Port 3: Not installed Port 4: Not installed VPM100: Not Present VPMADT032 Loading firwmare... Success Booting VPMADT032 VPMADT032: Present and operational (Firmware version 107) wctdm24xxp0: Missed interrupt. Increasing latency to 28 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 29 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Installed -- AUTO FXO (FCC mode) Port 3: Not installed Port 4: Not installed VPM100: Not Present VPMADT032 Loading firwmare... Success Booting VPMADT032 VPMADT032: Present and operational (Firmware version 107) wctdm24xxp0: Missed interrupt. Increasing latency to 30 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 31 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Installed -- AUTO FXO (FCC mode) Port 3: Not installed Port 4: Not installed VPM100: Not Present VPMADT032 Loading firwmare... Success Booting VPMADT032 VPMADT032: Present and operational (Firmware version 107) wctdm24xxp0: Missed interrupt. Increasing latency to 32 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: ERROR: Unable to service card within 30 ms and unable to further increase latency. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Installed -- AUTO FXO (FCC mode) Port 3: Not installed Port 4: Not installed VPM100: Not Present VPMADT032 Loading firwmare... Success Booting VPMADT032 VPMADT032: Present and operational (Firmware version 107) Found a Wildcard TDM: Wildcard TDM410P (4 modules) Registered tone zone 4 (United Kingdom) On Wed, Oct 28, 2009 at 2:03 PM, Darrick Hartman <[email protected]> wrote: > Tom Chadwin wrote: >> Hello all >> >> I'm on-site, with a net5501 running 0.6.7, with a TDM404E (TDM410 + hw >> e/c). I don't think the firmware for the Digium hardware echo >> cancellation module is present - dmesg has: >> >> VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace >> >> /lib/firmware is empty. I also have severe echo. Can anyone point me >> towards a copy of the file, and, will dropping it into /lib/firmware >> do the trick? >> >> Thanks >> >> Tom > > Tom, > > I apologize this is taking so long, but I believe the TDM410 cards will > work much better under dahdi (which 0.7 will use by default) I don't > have my 0.6 build machine fired up right now so I don't know if these > firmware files exist with Zaptel (they might only be in Dahdi). > > Darrick > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Astlinux-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > [email protected]. > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
