If this is a single CPU system try loading the smp kernel
yum install kernel-smp then force this to boot in grub.conf
This will force your interrupts to be handled with IO-APIC
handler instead of the old style XT-PIC interrupts handler.
Switching to APIC from XT will normally fix a lot of interrupt
issues. If you have them.
On Wed, 2005-01-05 at 17:35 -0800, Michael Swan wrote:
At 06:53 PM 1/5/2005 -0600, you wrote:
I've struggled for several days trying to get a Digium TDM04B 4-port
wxfco card working on a Dell 1U PowerEdge 750 machine running
Fedora Core 1. I finally got a call back from Digium who indicated that
there is a fundamental conflict between the card and the PowerEdge
having to do with PCI interrupts. Asterisk version is stable v1-0
12/29/04.
That sounds a little hard to believe.
I agree. Perhaps I have too much faith in Digium support. Does
anyone else disagree with Digium's assessement?
The symptoms of the problem were as follows:
1. issue modprobe zaptel which immediately returns with no feedback
2. issue modprobe wcfxo which returns
init_module: No such device
Hint: isnmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
3. issue modprobe wcfxs which immediately returns with no feedback,
however
the four lights on the card go on and then the machine locks up
completely,
requiring
a power cycle to get it running again. After the power cycle, if I look in
/var/log/messages
If you have a tdm04b, that says you have four fxo ports. Why are you
trying to load wcfxs?
Actually, I tried modprobe wctdm which was supposed to load the
correct TDM driver and this resulted in the same behavior described
above (lights on, system locks.) In an attempt to figure out why the
system locked up I subsequently issued a modprobe wcfxs to
confirm that was causing the problem.
I see a long cycle of the following messages before reboot:
kernel: Dazed and confused, but trying to continue
kernel: Do you have a strnage power saving mode enabled?
kernel: Uhhuh, NMI received for unknown reason 20 on CPU 0
4. if I cat /proc/interrupts, I don't see any entry for a wcfxo module.
In any case, I did follow the setup instructions on the Digium site (make
install in /usr/src/zaptel, edit /etc/zaptel.conf, edit
/etc/asterisk/zapata.conf, etc.)
and we currently have a X100P wcfxo card in another machine running well
so we've already had experience getting a card working.
If anyone has insight into what might be wrong, please do let me know.
Ultimately, if I trust the Digium support information, then this card will
never work, so I'd be grateful to hear about any other PCI card that
provides
four or so wcfxo interfaces that might work with the PowerEdge.
I don't use Fedora, but it seems those that do have had problems
loading the drivers. Try the modprobe wcfxo then zaptel, then check
your /proc/interrupts. If that doesn't work, try modprobe zaptel only.
I think someone mentioned a readme in the src/zaptel directory for
Fedora as well. Might look.
Thanks for the advice. However, modprobe zaptel didn't
do anything (that I could tell) and modprobe wcfxo returned
the error. And, greping for Fedora in src/zaptel didn't turn up any
matches.
Michael Swan
Neon Software, Inc.
___
Asterisk-Users mailing list
Asterisk-Users@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@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
