Maxim Litnitskiy
2009-Jan-26 12:08 UTC
[asterisk-users] Digium TE220 card partially detected
Hello folks. I've got a strange issue. When I modprobe TE220 I do not see mesages like Launching card: 0 <..> Setting up global serial parameters. You can see how I loaded and unloaded the card for several times - http://asteriskpbx.ru/pastebin/11 lspci can detect the card: 03:08.0 Communication controller: Digium, Inc. Device 0220 (rev 02) dahdi_hardware also: astpbx ~ # dahdi_hardware pci:0000:03:08.0 wct4xxp+ d161:0220 Wildcard TE220 (4th Gen) astpbx ~ # But dahdi_tool does not show the card and dahdi_cfg gives DAHDI_SPANCONFIG failed on span 1: Invalid argument (22) System info is provided here - http://asteriskpbx.ru/pastebin/12 Please advise. -- Maxim Litnitskiy http://asteriskpbx.ru http://asterisk-support.ru -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090126/3d898c0b/attachment-0001.htm
On Mon, Jan 26, 2009 at 03:08:13PM +0300, Maxim Litnitskiy wrote:> Hello folks. > I've got a strange issue. > When I modprobe TE220 I do not see mesages like Launching card: 0 <..> > Setting up global serial parameters. > You can see how I loaded and unloaded the card for several times - > http://asteriskpbx.ru/pastebin/11 > > lspci can detect the card: 03:08.0 Communication controller: Digium, Inc. > Device 0220 (rev 02) > dahdi_hardware also: > astpbx ~ # dahdi_hardware > pci:0000:03:08.0 wct4xxp+ d161:0220 Wildcard TE220 (4th Gen)Fine. The card is indeed handled by the module (+).> astpbx ~ # > But dahdi_tool does not show the card and dahdi_cfg gives DAHDI_SPANCONFIG > failed on span 1: Invalid argument (22)Next: are you sure that it is configured for E1 and not for T1? What is the output of: cat /proc/dahdi/1> System info is provided here - http://asteriskpbx.ru/pastebin/12-- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Maxim Litnitskiy
2009-Feb-10 22:46 UTC
[asterisk-users] Digium TE220 card partially detected
> lspci can detect the card: 03:08.0 Communication controller: Digium, Inc. > > Device 0220 (rev 02) > > dahdi_hardware also: > > astpbx ~ # dahdi_hardware > > pci:0000:03:08.0 wct4xxp+ d161:0220 Wildcard TE220 (4th Gen) > > Fine. The card is indeed handled by the module (+). > > > astpbx ~ # > > But dahdi_tool does not show the card and dahdi_cfg gives > DAHDI_SPANCONFIG > > failed on span 1: Invalid argument (22) > > Next: are you sure that it is configured for E1 and not for T1? What is > the output of: > > cat /proc/dahdi/1 >Please see what's there: NET: Registered protocol family 10 lo: Disabled Privacy Extensions eth0: no IPv6 routers present ACPI: PCI Interrupt Link [APC6] enabled at IRQ 16 ACPI: PCI Interrupt 0000:03:08.0[A] -> Link [APC6] -> GSI 16 (level, low) -> IRQ 16 Found TE2XXP at base address f5100000, remapped to f8d64000 TE2XXP version c01a016a, burst ON Octasic optimized! FALC version: 00000005, Board ID: 09 Reg 0: 0x2b817400 Reg 1: 0x2b817000 Reg 2: 0xffffffff Reg 3: 0x00000000 Reg 4: 0x00000001 Reg 5: 0x00000000 Reg 6: 0xc01a016a Reg 7: 0x90001300 Reg 8: 0x00000000 Reg 9: 0x00ff0000 Reg 10: 0x0000004a Found a Wildcard: Wildcard TE220 (4th Gen) astpbx dahdi # cat /proc/dahdi/1 Span 1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: RTC) 1" (MASTER) astpbx dahdi # astpbx dahdi # ls /proc/dahdi/1 /proc/dahdi/1 astpbx dahdi # -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090211/1c900ffa/attachment.htm
Kevin P. Fleming
2009-Feb-10 23:01 UTC
[asterisk-users] Digium TE220 card partially detected
Maxim Litnitskiy wrote:> FALC version: 00000005, Board ID: 09The board ID switch (the rotary switch on the board) is set to 9 (nine). If you are going to have the switches set to anything other than zero, there must be at least one board with it set to zero, then one set to one, then one set to two, etc. Skipping numbers causes boards to be ignored by the driver at startup time, even though they were located. -- Kevin P. Fleming Digium, Inc. | Director of Software Technologies 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA skype: kpfleming | jabber: kpfleming at digium.com Check us out at www.digium.com & www.asterisk.org