[Asterisk-Users] Am I stupid or is my card DOA.?

[Dave Cotton]

On Sat, 2004-10-09 at 16:16 +0100, marshalm at paradoxical.co.uk wrote:

> I wonder if someone with a little more experience with the zaptel driver
> could give me a little help with the following driver loading issue.  
> 
> My Setup:
> One TDM400P PCI Card with 2 x FXS Modules
> One X100P PCI FXO Card
> 
> I have downloaded the latest CVS of the zaptel driver and compiled it
> against my current kernel source.  However, each time I load the driver, I
> get the following error.  I have also enclosed a copy of the zaptel.conf,
> lsmod, lspci and /proc/interrupts.  My machine is running Redhat FC1 on
> Intel(R) Xeon(TM) CPU 2.80GHz's (SMP Kernel).  I have also tried the card in
> an AMD (1xWay) with the same results (no PCI conflicts - that I can see).
> 
> # modprobe zaptel (Loads OK)
> # modprobe wcfxo  (Loads OK with the normal status information) 
> # modprobe wcfxs
> /lib/modules/2.4.22-1.2115.nptl.msm/misc/wcfxs.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.22-1.2115.nptl.msm/misc/wcfxs.o: insmod
> /lib/modules/2.4.22-1.2115.nptl.msm/misc/wcfxs.o failed
> /lib/modules/2.4.22-1.2115.nptl.msm/misc/wcfxs.o: insmod wcfxs failed
> 
> # ztcfg
> ZT_CHANCONFIG failed on channel 2: No such device or address (6)

> ----------------------- lspci -vv ---------------------------------------
> 
> [root at p1host4 zaptel]# lspci -vv
> 03:01.0 Communication controller: Tiger Jet Network Inc. Intel 537
>         Subsystem: Unknown device 8085:0003
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (250ns min, 32000ns max)
>         Interrupt: pin A routed to IRQ 24
>         Region 0: I/O ports at 3000 [size=256]
>         Region 1: Memory at fb240000 (32-bit, non-prefetchable) [size=4K]
>         Capabilities: [40] Power Management version 2
>                 Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA
> PME(D0+,D1-,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> 06:01.0 Network controller: Tiger Jet Network Inc. Intel 537
>         Subsystem: Unknown device a8fd:0001
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (250ns min, 32000ns max)
>         Interrupt: pin A routed to IRQ 72
>         Region 0: I/O ports at 5000 [size=256]
>         Region 1: Memory at fc800000 (32-bit, non-prefetchable) [size=4K]
>         Capabilities: [40] Power Management version 2
>                 Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA
> PME(D0+,D1-,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-

The answers to your questions are no and probably not.

According to lspci you seem to have 2 X100s, and I have had this with
the same setup.

My question is what version of the kernel are you using?

Because I'm experiencing the same type of problems now with a TDM card
that worked perfectly before on 2.4 kernels and older drivers.  This is
either a kernel problem or something in the newer zaptel drivers.

I have pulled the TDM and it has worked perfectly in another machine but
not when an X100 is involved.


-- 
Dave Cotton <dcotton at linuxautrement.com>