Anthony Messina wrote: > On Saturday 06 March 2010 09:18:13 pm sean darcy wrote: >> I have a TDM400. Just updated Fedora 12 to kernel 2.6.32. Rebuilt and >> installed dahdi-2.2.1. >> >> kernel modules loaded. >> lsmod | grep wctdm >> wctdm 37233 0 >> dahdi 194985 1 wctdm >> >> lsmod | grep dahdi >> dahdi 194985 1 wctdm >> crc_ccitt 1549 2 dahdi,isdnhdlc >> >> dmesg: >> >> dahdi: Telephony Interface Registered on major 196 >> dahdi: Version: 2.2.1 >> ..... >> dahdi_dummy: Trying to load High Resolution Timer >> dahdi_dummy: Initialized High Resolution Timer >> dahdi_dummy: Starting High Resolution Timer >> dahdi_dummy: High Resolution Timer started, good to go >> >> which is much less dmesg on 2.6.31: >> >> dahdi: Telephony Interface Registered on major 196 >> dahdi: Version: 2.2.1 >> ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16 >> wctdm 0000:01:05.0: PCI INT A -> Link[APC1] -> GSI 16 (level, low) -> IRQ >> 16 Freshmaker version: 73 >> Freshmaker passed register test >> Module 0: Installed -- AUTO FXS/DPO >> Module 1: Installed -- AUTO FXS/DPO >> Module 2: Not installed >> Module 3: Installed -- AUTO FXO (FCC mode) >> Found a Wildcard TDM: Wildcard TDM400P REV I (3 modules) >> >> and dahdi_cfg fails: >> >> dahdi_cfg -vvvvvv >> DAHDI Tools Version - 2.2.1 >> >> DAHDI Version: 2.2.1 >> Echo Canceller(s): >> Configuration >> ====================== >> >> >> Channel map: >> >> Channel 01: FXO Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01) >> Channel 02: FXO Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 02) >> Channel 04: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 04) >> >> 3 channels to configure. >> >> DAHDI_CHANCONFIG failed on channel 1: No such device or address (6) >> >> I tried dahdi svn r8255 from today. Same result. >> >> If I reboot with 2.6.31, all's well. >> >> Am I missing something? > > Amazing, I just finished the same thing with, unfortunately, the same result > as you on both i686 and x86_64. > > I'll keep googling :) > >
Well, I've figured it out, at least for me. Another driver was grabbing the TDM400P: netjet. added netjet to /etc/modprobe.d/blacklist.conf. I think you can do this by: cat /lib/modules/`uname -r`/modules.pcimap | grep 00e159 e159 is the vendorid for the TDM400P. You'll see all the drivers that use e159. Then lsmod | grep those drivers other than wctdm. If you see one loaded, blacklist it. sean -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
