[Asterisk-Users] Problems with TDM400P card

[John Novack]

Anton Krall wrote:
> Zttool shows nothing inside thebox.
I have had similar problems with a TDM400 and CERTAIN Motherboards which are PCI 2.2 but the TDM400 is not seen, in my case, AT ALL
The one I have reports it as an E/F but the silk-screen clearly says H, Digium contends there is no problem with the card, the reporting of different version numbers is a "known bug" but doesn't
prevent the card from working, and because I can place it in another machine and get it working, they refuse to acknowledge there is any defect in the board.

Perhaps a different motherboard? That is Digium's answer.
Just keep going through hardware that otherwise meets published specs
until you find one that works.

I have to conclude that, due to Digiums refusal to acknowledge there are problems with the design, ( and there are more I won't bore you with ) and no willingness to address the issues that have been raised on this list time and time again, that the TDM400
should be considered a "card of last resort" when absolutely nothing else will work.
Seems their IAXy falls into that same classification.
Can't say about their T1/E1 cards

JMO

John Novack


> 
> I tried removing the x100 cards, moving the tdm card around, disabled all
> usb and unnecessary stuff still, kudzu when booting up shows the card and
> the card shows up on /etc/sysconfig/hwconf but I wonder why it shows 2 of
> these and I only have 1 tdm400p card with 1 module 
> 
> class: MODEM
> bus: PCI
> detached: 1
> driver: hisax
> desc: "Tiger Jet Network Inc.|Intel 537"
> vendorId: e159
> deviceId: 0001
> subVendorId: 8086
> subDeviceId: 0003
> pciType: 1
> -
> class: MODEM
> bus: PCI
> detached: 1
> driver: hisax
> desc: "Tiger Jet Network Inc.|Intel 537"
> vendorId: e159
> deviceId: 0001
> subVendorId: 8086
> subDeviceId: 0003
> pciType: 1
> 
> Still, interrupts doesn't show the card
> 
> [root at conmutador root]# cat /proc/interrupts
>            CPU0
>   0:    3994353          XT-PIC  timer
>   1:          2          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   8:          1          XT-PIC  rtc
>  10:      95510          XT-PIC  eth0
>  14:     129871          XT-PIC  ide0
> NMI:          0
> ERR:          0
> 
> And when trying to load the drvier
> 
> [root at conmutador root]# modprobe zaptel
> [root at conmutador root]# modprobe wctdm
> /lib/modules/2.4.20-8/misc/wctdm.o: init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.20-8/misc/wctdm.o: insmod
> /lib/modules/2.4.20-8/misc/wctdm.o failed
> /lib/modules/2.4.20-8/misc/wctdm.o: insmod wctdm failed
> You have new mail in /var/spool/mail/root
> 
> I tried using diff. modules with no luck.,..... Could be the mobo itself?
> 
>  
> 
> |-----Original Message-----
> |From: asterisk-users-bounces at lists.digium.com 
> |[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of 
> |Rich Adamson
> |Sent: Viernes, 29 de Abril de 2005 08:59 a.m.
> |To: Asterisk Users Mailing List - Non-Commercial Discussion
> |Subject: Re: [Asterisk-Users] Problems with TDM400P card
> |
> |> I have a problem getting a TDM400P card to go.
> |> 
> |> It has 4 FXS ports (green modules) and I get this error:
> |> 
> |> [root at conmutador root]# ztcfg -vvvvv
> |> 
> |> Zaptel Configuration
> |> ======================
> |> 
> |> 
> |> Channel map:
> |> 
> |> Channel 01: FXS Kewlstart (Default) (Slaves: 01) Channel 02: FXS 
> |> Kewlstart (Default) (Slaves: 02) Channel 03: FXO Kewlstart (Default) 
> |> (Slaves: 03) Channel 04: FXO Kewlstart (Default) (Slaves: 
> |04) Channel 
> |> 05: FXO Kewlstart (Default) (Slaves: 05) Channel 06: FXO Kewlstart 
> |> (Default) (Slaves: 06)
> |> 
> |> 6 channels configured.
> |> 
> |> ZT_CHANCONFIG failed on channel 3: Invalid argument (22) Did you 
> |> forget that FXS interfaces are configured with FXO 
> |signalling and that 
> |> FXO interfaces use FXS signalling?
> |> 
> |> My zaptel.conf reads:
> |> 
> |> [root at conmutador root]# more /etc/zaptel.conf
> |> fxsks=1
> |> fxsks=2
> |> fxoks=3-6
> |> loadzone=us
> |> defaultzone=us
> |> 
> |> And my rc.local loads:
> |> 
> |> /sbin/modprobe zaptel
> |> /sbin/modprobe wcfxo
> |> /sbin/modprobe wctdm
> |> 
> |> The 2 100p cards load perfectly but the TDM is not. 
> |> 
> |> Any ideas?
> |
> |What does zttool indicate?
> |
> |Have you tried moving the cards around in different slots?
> |
> |Any shared interrupt issues?
> |
> |Try loading wctdm before wcfxo.
> |
> |Try removing the x100p's and loading the TDM card only. Any issues?