[Home]

Summary:DAHLIN-00267: TDM400P fails to start
Reporter:Richard Miller (ulogic)Labels:
Date Opened:2011-11-22 13:41:57.000-0600Date Closed:2011-11-23 06:08:25.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:wctdm
Versions:2.3.0.1 2.6.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:CentOS 6.0, Fedora 15Attachments:
Description:A TDM400P is not usable in these distributions.  It appears the the card is not being correctly recognized.

lspci shows
05:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface

The dahdi_tool utility does not display any devices.

[root@testivr ~]# cat /etc/system-release
CentOS Linux release 6.0 (Final)

[root@testivr ~]# uname -a
Linux testivr.local 2.6.32-71.el6.x86_64 #1 SMP Fri May 20 03:51:51 BST 2011 x86_64 x86_64 x86_64 GNU/Linux

[root@testivr ~]# dahdi_hardware
driver should be 'wctdm' but is actually 'netjet'
pci:0000:05:00.0     wctdm+       e159:0001 Wildcard TDM400P REV I

[root@testivr dahdi-linux-2.6.0-rc1~]# service dahdi start
Loading DAHDI hardware modules:
 wctdm:                                                   [  OK  ]

driver should be 'wctdm' but is actually 'netjet'
Running dahdi_cfg:  DAHDI_CHANCONFIG failed on channel 1: Invalid argument (22)
Selected signaling not supported
Possible causes:
       FXS signaling is being used on a FXS interface (use a FXO signaling variant)
       RBS signaling is being used on a E1 CCS span
       Signaling is being assigned to channel 16 of an E1 CAS span
                                                          [FAILED]

Rolling back to an earlier version, the display is

[root@testivr dahdi-linux-2.3.0.1]# service dahdi start
Loading DAHDI hardware modules:
 wctdm:                                                   [  OK  ]

driver should be 'wctdm' but is actually 'netjet'
Running dahdi_cfg:  DAHDI_CHANCONFIG failed on channel 1: No such device or address (6)
                                                          [FAILED]

[root@testivr ~]# lsmod|grep -e dahdi -e netjet
dahdi                 209867  1 wctdm
netjet                 16516  0
isdnhdlc                5339  1 netjet
crc_ccitt               1643  2 dahdi,isdnhdlc
mISDNipac              38183  1 netjet
mISDN_core             90247  3 netjet,mISDNipac

Comments:By: Shaun Ruffell (sruffell) 2011-11-22 14:03:07.980-0600

Try adding netjet to the blacklist in /etc/modprobe.d/blacklist.conf.  
By: Richard Miller (ulogic) 2011-11-22 14:52:49.302-0600

Thank you for your quick reply.  That took care of the problem on one machine but not on the other.  I am trying to troubleshoot what appears to be a possible motherboard hardware problem on that other machine.
By: Richard Miller (ulogic) 2011-11-23 06:08:25.573-0600

The workaround of adding netjet to the blacklist in /etc/modprobe.d/blacklist.conf addresses the problem.