Struggling with Digium T1 Card

Hello,
I am trying to use an old Digium TE420 in a new Supermicro build.
When I boot up, the card has power and is recognized by Dahdi and shows up in the Dahdi config module but does not work. In the Dahdi Config module I get BLU/YEL/RED/LFA
The LEDs sequence indicating that it’s not ready to be used.
In another system with the same FreePBX distro install it works. When idle on this system I only get RED/LFA and the LEDs are solid indicating they are waiting for a T1 to be connected.
I am pounding my head against the wall as to why it’s not working. Any recommendations as to where to start other than use an old motherboard?

I’m coming to the conclusion that this card just isn’t going to work in an i5 based motherboard, I think it needs to be Core Duo.

Is it any help or indicator that now I get the error in my terminal wc4xxp Interupts not detected?

Core i5 vs duo has less to do with it than BIOS version and card firmware version. Sound like something else is misconfigured between the card and motherboard. Have you contacted digium support at all?

lspci

and

watch -d /cat/proc/interrupts

should identify the hardware and the interrupts it is using

make sure your hardware is not sharing interrupts at the bios level and is step-wise incrementing the interrupts

add to that

lsmod

to make sure the module is loaded ( and dahdi)

Thank you,
Looking at /proc/interrupts I see:
16: 109 82 58 50 IR-IO-APIC-fasteoi ehci_hcd:usb1, firewire_ohci, wct4xxp

To me that seems bad that it would be trying to use the same interrupt as usb1? no?
This is beyond my linux knowledge. Is there a way that you can manually assign a different?

I will call Digium support again and see if there is any firmware update but I believe they said there is not. They kind of said “wow, that thing is older than dirt itself”

Full /proc/interrupts

       CPU0       CPU1	 CPU2       CPU3

0: 131 0 0 0 IR-IO-APIC-edge timer
1: 5 3 8 0 IR-IO-APIC-edge i8042
3: 1 1 0 1 IR-IO-APIC-edge
4: 0 0 0 2 IR-IO-APIC-edge
8: 0 1 1 0 IR-IO-APIC-edge rtc0
9: 0 0 0 0 IR-IO-APIC-fasteoi acpi
16: 113 82 60 50 IR-IO-APIC-fasteoi ehci_hcd:usb1, firewire_ohci, wct4xxp
23: 15 15 11 5 IR-IO-APIC-fasteoi ehci_hcd:usb2
24: 0 0 0 0 DMAR_MSI-edge dmar0
25: 0 0 0 0 DMAR_MSI-edge dmar1
26: 28 0 0 0 IR-HPET_MSI-edge hpet2
27: 0 0 0 0 IR-HPET_MSI-edge hpet3
28: 0 0 0 0 IR-HPET_MSI-edge hpet4
29: 0 0 0 0 IR-HPET_MSI-edge hpet5
31: 39 31 31 19 IR-PCI-MSI-edge i915
32: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
33: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
34: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
35: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
36: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
37: 0 0 0 0 IR-PCI-MSI-edge xhci_hcd
38: 10208901 10533115 7975532 3422409 IR-PCI-MSI-edge ahci
39: 0 0 0 0 IR-PCI-MSI-edge ahci
40: 2 23 52 11 IR-PCI-MSI-edge snd_hda_intel
41: 4164 3242 2312 1786 IR-PCI-MSI-edge eth0
NMI: 346 337 287 170 Non-maskable interrupts
LOC: 641865 605650 2469466 177295 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 346 337 287 170 Performance monitoring interrupts
IWI: 0 0 0 0 IRQ work interrupts
RES: 563 1106 992 1753 Rescheduling interrupts
CAL: 71 202 200 190 Function call interrupts
TLB: 2096 4901 3904 3000 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 30 30 30 30 Machine check polls
ERR: 0
MIS: 0

Yes you really need it not to share it’s interrupt, maybe in the bios somewhere . . . .

To check that there are 1K per second:-

watch -n 1 -d “cat /proc/interrupts |grep wct”

also make sure the module is loaded

lsmod|grep dah

The hardware might be old, but I still have many in use though.

Modules are loaded, you’re saying I should be seeing 1000 interrupts per second?
It doesn’t climb at all, hovers between 20 and 37, possibly because I don’t currently have a T1 connected?

Would changing the PCIe slot effect the interrupts that it uses?

[[email protected] ~]# lsmod|grep dah
dahdi_transcode 6697 1 wctc4xxp
dahdi_voicebus 54834 2 wctdm24xxp,wcte12xp
dahdi 224730 18 xpp,dahdi_transcode,wcb4xxp,rcbfx,wctdm,wcfxo,wcaxx,wctdm24xxp,rxt1,r1t1,wcte11xp,wct1xxp,wcte13xp,wcte12xp,dahdi_voicebus,wcte43x,wct4xxp,oct612x
crc_ccitt 1717 2 wctdm24xxp,dahdi

Actually 1024 :slight_smile: but the “watch” line I posted is not that accurate, I assume the 20 or 37 are from the other devices sharing that interrupt, maybe changing the slot would do that , but have you looked page by page through your BIOS yet for any interrupt/PNP related settings ?

(It’s not to do with whether the T1 is connected, just to do with your MB/BIOS hardware passing the interrupts through to the dahdi driver. You could disable USB and Firewire I’m sure in your bios though, you might also look for a newer BIOS for your hardware also)

Thank you, I haven’t been through the BIOS yet because I won’t have physical access to it until I’m in the office tomorrow.
This is the current BIOS for this SuperMicro Z87 chipset motherboard.

Thank you for your help. I ended up just crying into my keyboard as I bought a $1000 new card. Hopefully I won’t run into the same problems with a current gen Sangoma as I did the old model Digium. Fingers crossed

hehe, It might have been cheaper to replace the computer, but if all is good . . . .

Oh it definitely would have been but I’m trying to build a production machine with a modern motherboard and i5 and a Digium card that was made in like 2006. It didn’t make sense to try and go backwards with the PC when I need it to last for 10 years.

I’m sure I can use the card in another, less critical project with a Core Duo and old motherboard.