[Asterisk-Users] Am I stupid or is my card DOA.?
Alex Barnes
abarnes at ubiquitysoftware.com
Mon Oct 11 01:44:42 MST 2004
I had/have exactly the same problem with my X100P / TDM400P dev setup.
To fix this error all I did was swap the PCI slots that the cards were
in.
And this error came back either due to a reboot or because I update to
the latest CVS. But again after much messing around with config's and
BIOS options I gave up and swapped the cards again (well went from X on
1 - TDM on 2 to X on 0 - TDM 1).
Restarted and hey-presto the TDM was recognised.
This does have me a little concerned as I'm running out of combinations
of PCI slots.
HTH
Alex
-----Original Message-----
From: Martin Marshall [mailto:marshalm at paradoxical.co.uk]
Sent: 09 October 2004 22:28
To: 'Asterisk Users Mailing List - Non-Commercial Discussion'
Subject: RE: [Asterisk-Users] Am I stupid or is my card DOA.?
Thank you for the information.
My kernel was a stock Fedora Core 1 kernel (2.4.22). I have now tried
with the latest 2.4.27 kernel with the same results.
I will now try to rollback to an earlier release of zaptel code.
Regards
Martin
-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Dave
Cotton
Sent: 09 October 2004 16:39
To: Asterisk List
Subject: Re: [Asterisk-Users] Am I stupid or is my card DOA.?
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>
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Dear Friends of Ubiquity Software:
As you may have noticed, Ubiquity Software began using the web domain ubiquity.com earlier this year in addition to the previously established ubiquity.net for our website and email communications to you. However, since that time, a dispute has emerged with respect to actual ownership of the ubiquity.com domain.
As an international software company founded over decade ago, you can always reach Ubiquity Software under the website www.ubiquity.net <http://www.ubiquity.net/> and via email at @ubiquity.net. However, we have also chosen to expand our domain to the more specific www.ubiquitysoftware.com <http://www.ubiquitysoftware.com/> for web and @ubiquitysoftware.com for email communications.
Please use either the historical ubiquity.net or begin to use the new ubiquitysoftware.com domain for all email communications to Ubiquity employees from now on.
Thank you.
Regards,
Ubiquity Software
www.ubiquitysoftware.com <http://www.ubiquitysoftware.com/>
info at ubiquitysoftware.com
More information about the asterisk-users
mailing list