Edwin Groothuis
2005-Aug-01 21:48 UTC
[Asterisk-Users] TDM400P REV I issues - ProSLIC vs TDM400P
The REV I card shows up in the PCI table as: 02:05.0 Network controller: Tiger Jet Network Inc. Intel 537 (or 02:05.0 Class 0280: e159:0001) Subsystem: Unknown device b119:0001 But the REV E/F shows up as: 02:0d.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface (or 02:0d.0 Class 0780: e159:0001) Subsystem: Unknown device b100:0003 One is class 0780, one is class 0280. I don't know if this normal, but it might be an indication of the problem. I managed to probe it with zaptel 1.0.8 correctly once after which the box paniced. $ sudo /sbin/modprobe wcfxs zaptel kernel: Zapata Telephony Interface Registered on major 196 kernel: Freshmaker version: 73 kernel: Freshmaker passed register test kernel: Module 0: Installed -- AUTO FXS/DPO kernel: Module 1: Installed -- AUTO FXO (FCC mode) kernel: Module 2: Installed -- AUTO FXO (FCC mode) kernel: Module 3: Installed -- AUTO FXO (FCC mode) kernel: Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules) kernel: Registered tone zone 0 (United States / North America) One restart later, it fails: kernel: Zapata Telephony Interface Registered on major 196 /lib/modules/2.4.21-4.EL/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.21-4.EL/misc/wcfxs.o: insmod /lib/modules/2.4.21-4.EL/misc/wcfxs.o failed /lib/modules/2.4.21-4.EL/misc/wcfxs.o: insmod wcfxs failed Very confusing. Adding some printk()s to wcfxs.c, for example in wcfxs_init() just before the call to pci_module_init() and as the first command in wcfxs_init_one(), shows that pci_module_init() gets called but wcfxs_init_one() never gets called. In the PCI table of wcfxs_pci_tbl, if I add { 0xe159, 0x0001, 0xb119, PCI_ANY_ID, 0, 0, (unsigned long) &wcfxsi }, (as done revision 1.116 of wctdm.c) to it, the modprobe works (at least wcfxs_init_one() gets called): kernel: Freshmaker version: 73 kernel: Freshmaker passed register test But then, the full story is: kernel: Zapata Telephony Interface Registered on major 196 kernel: Freshmaker version: 73 kernel: Freshmaker passed register test kernel: Module 0: Installed -- AUTO FXS/DPO kernel: Module 1: Installed -- AUTO FXO (FCC mode) kernel: Module 2: Installed -- AUTO FXO (FCC mode) kernel: Module 3: Installed -- AUTO FXO (FCC mode) kernel: Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules) and the next attempt gives me: kernel: Freshmaker version: 73 kernel: Freshmaker passed register test kernel: ProSLIC on module 0, product 0, version 2 kernel: ProSLIC on module 0 seems sane. kernel: ProSLIC on module 0 powered up to -74 volts (c6) in 10 ms kernel: Loop current set to 20mA! kernel: Post-leakage voltage: 48 volts kernel: ProSLIC on module 0 powered up to -75 volts (ca) in 0 ms kernel: Loop current set to 20mA! kernel: Calibration Vector Regs 98 - 107: kernel: 98: 11 kernel: 99: 10 kernel: 100: 00 kernel: 101: 00 kernel: 102: 06 kernel: 103: 34 Does this still make sense to anybody? Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/
Tzafrir Cohen
2005-Aug-01 21:56 UTC
[Asterisk-Users] TDM400P REV I issues - ProSLIC vs TDM400P
On Tue, Aug 02, 2005 at 02:48:00PM +1000, Edwin Groothuis wrote:> The REV I card shows up in the PCI table as: > > 02:05.0 Network controller: Tiger Jet Network Inc. Intel 537 (or > 02:05.0 Class 0280: e159:0001) > Subsystem: Unknown device b119:0001 > > But the REV E/F shows up as: > > 02:0d.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface (or > 02:0d.0 Class 0780: e159:0001) > Subsystem: Unknown device b100:0003 > > One is class 0780, one is class 0280. I don't know if this normal, > but it might be an indication of the problem. > > I managed to probe it with zaptel 1.0.8 correctly once after which > the box paniced.What is "it" exactly? IIRC zaptel 1.0.9 is basically 1.0.8 with the added support for TDM REV I. -- Tzafrir Cohen | tzafrir@jbr.cohens.org.il | VIM is http://tzafrir.org.il | | a Mutt's tzafrir@cohens.org.il | | best ICQ# 16849755 | | friend
Edwin Groothuis
2005-Aug-01 22:23 UTC
[Asterisk-Users] Re: TDM400P REV I issues - ProSLIC vs TDM400P
On Mon, Aug 01, 2005 at 11:56:26PM -0500, asterisk-users-request@lists.digium.com wrote:> On Tue, Aug 02, 2005 at 02:48:00PM +1000, Edwin Groothuis wrote: > > The REV I card shows up in the PCI table as: > > > > 02:05.0 Network controller: Tiger Jet Network Inc. Intel 537 (or > > 02:05.0 Class 0280: e159:0001) > > Subsystem: Unknown device b119:0001 > > > > But the REV E/F shows up as: > > > > 02:0d.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface (or > > 02:0d.0 Class 0780: e159:0001) > > Subsystem: Unknown device b100:0003 > > > > One is class 0780, one is class 0280. I don't know if this normal, > > but it might be an indication of the problem. > > > > I managed to probe it with zaptel 1.0.8 correctly once after which > > the box paniced. > > What is "it" exactly? IIRC zaptel 1.0.9 is basically 1.0.8 with the > added support for TDM REV I.The TDM400P REV I card. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/