Tom Chadwin wrote:
> 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

As I said before, the cards will work better under dahdi and 0.7.

------------------------------------------------------------------------------
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].

Reply via email to