Philip Prindeville wrote: > For modules and settings, look at $MODOPTS and $ZAPMODS and $AUTOMODS in > you /mnt/kd/rc.conf file. > > What does your /etc/modprobe.conf file look like? > > First focus on getting your hardware properly configured. You can't > really do anything before that. > > Doing a modinfo on wctdm24xxp, I see: > > filename: /lib/modules/2.6.25.19-astlinux/misc/wctdm24xxp/wctdm24xxp.ko > license: GPL > alias: wctdm8xxp > author: Mark Spencer <marks...@digium.com> > description: Wildcard TDM2400P/TDM800P Zaptel Driver > alias: pci:v0000D161d00008006sv*sd*bc*sc*i* > alias: pci:v0000D161d00008005sv*sd*bc*sc*i* > alias: pci:v0000D161d00008003sv*sd*bc*sc*i* > alias: pci:v0000D161d00008002sv*sd*bc*sc*i* > alias: pci:v0000D161d00000800sv*sd*bc*sc*i* > alias: pci:v0000D161d00002400sv*sd*bc*sc*i* > depends: zaptel,firmware_class > vermagic: 2.6.25.19-astlinux preempt mod_unload GEODE > parm: debug:int > parm: fxovoltage:int > parm: loopcurrent:int > parm: robust:int > parm: opermode:charp > parm: lowpower:int > parm: boostringer:int > parm: fastringer:int > parm: fxshonormode:int > parm: battdebounce:uint > parm: battalarm:uint > parm: battthresh:uint > parm: alawoverride:int > parm: nativebridge:int > parm: fxotxgain:int > parm: fxorxgain:int > parm: fxstxgain:int > parm: fxsrxgain:int > parm: ringdebounce:int > parm: fwringdetect:int > parm: latency:int > parm: neonmwi_monitor:int > parm: neonmwi_level:int > parm: neonmwi_envelope:int > parm: neonmwi_offlimit:int > parm: vpmsupport:int > parm: vpmdtmfsupport:int > parm: dtmfthreshold:int > parm: vpmnlptype:int > parm: vpmnlpthresh:int > parm: vpmnlpmaxsupp:int > > > > (Ignore the different Linux version #... I'm running trunk, not 0.6.2...) > > I don't have this hardware, and rarely work with analog stuff, but I'd > suggest looking at "robust", "opermode", "latency", and "nativebridge"... > > Oh, maybe "lowpower" and "debug" too. :-) > > Anyone know why he can't find firmware? > > -Philip > > > > Justin Phelps wrote: > >> I'm replacing an aging server in a remote office, and this is my first >> time working with Asterisk. The server I'm replacing is an aster...@home >> server that is obviously outdated. The reason for this replacement is a >> lot of phone static, and the outdated system. >> >> I'm looking to get started with Asterisk. I have a Soekris net5501 and a >> TDM404E card from Digium with four FXO ports. I have Astlinux 0.6.2 >> installed on an 8 GB CF card. There are 3 POT lines at this office that >> the current system uses. Please know that I'm very new to all the >> terminology associated with Asterisk as well. >> >> I need to know where to start! I have the O'Reilly book on Asterisk, but >> that pertains to a standard install. Astlinux does a lot of custom stuff >> due to the hardware it is installed on, and I just don't know where to >> start! >> >> I imagine my first goal is to get the module loaded for my specific >> card. I have loaded the wctdm24xxp module from the command line, but I >> noticed several errors in dmesg that I believe relate to IRQ conflicts. >> >> From there, I would configure zaptel.conf, and then extensions.conf with >> my dial plan. >> >> I'd also like to explore what settings are important for my system, >> including firewall config, DHCP for both my phones and the Windows >> workstations. I'll also need to serve up config files for my phones as >> well, over tftp I believe. >> >> So, let me kick things off by showing you the errors I'm getting when I >> modprobe the module. >> >> # modprobe wctdm24xxp >> WARNING: /etc/modprobe.conf line 1: ignoring bad line starting with >> 'options' >> >> And: >> >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 4 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 5 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 6 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 7 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 8 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 9 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 10 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 11 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 12 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 13 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 14 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 15 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 16 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 17 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 18 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 19 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 20 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 21 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 22 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 23 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> wctdm24xxp0: Missed interrupt. Increasing latency to 24 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 25 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> Port 2: Installed -- AUTO FXO (FCC mode) >> Port 3: Installed -- AUTO FXO (FCC mode) >> Port 4: Installed -- AUTO FXO (FCC mode) >> VPM100: Not Present >> VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace >> wctdm24xxp0: Missed interrupt. Increasing latency to 26 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 27 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> Port 2: Installed -- AUTO FXO (FCC mode) >> Port 3: Installed -- AUTO FXO (FCC mode) >> Port 4: Installed -- AUTO FXO (FCC mode) >> VPM100: Not Present >> VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace >> wctdm24xxp0: Missed interrupt. Increasing latency to 28 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 29 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> Port 2: Installed -- AUTO FXO (FCC mode) >> Port 3: Installed -- AUTO FXO (FCC mode) >> Port 4: Installed -- AUTO FXO (FCC mode) >> VPM100: Not Present >> VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace >> wctdm24xxp0: Missed interrupt. Increasing latency to 30 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: Missed interrupt. Increasing latency to 31 ms in order to >> compensate. >> Port 1: Installed -- AUTO FXO (FCC mode) >> Port 2: Installed -- AUTO FXO (FCC mode) >> Port 3: Installed -- AUTO FXO (FCC mode) >> Port 4: Installed -- AUTO FXO (FCC mode) >> VPM100: Not Present >> VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace >> wctdm24xxp0: Missed interrupt. Increasing latency to 32 ms in order to >> compensate. >> wctdm24xxp0: Restarting board initialization after increasing latency. >> wctdm24xxp0: ERROR: Unable to service card within 30 ms and unable to >> further increase latency. >> Port 1: Installed -- AUTO FXO (FCC mode) >> Port 2: Installed -- AUTO FXO (FCC mode) >> Port 3: Installed -- AUTO FXO (FCC mode) >> Port 4: Installed -- AUTO FXO (FCC mode) >> VPM100: Not Present >> VPMADT032: firmware zaptel-fw-vpmadt032.bin not available from userspace >> Found a Wildcard TDM: Wildcard TDM410P (4 modules) >> >> Thank you for your attention! >> >> >> > > > ------------------------------------------------------------------------------ > SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. > The future of the web can't happen without you. Join us at MIX09 to help > pave the way to the Next Web now. Learn more and register at > http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. >
thanks for the reply Phillip. I'm not sure what all those values do . . . Can anyone give me some insight into those options? I've added the module to the automods variable, as well as the zapmods. I uncommented the default modops and changed it from UK to US. Here's the values I have changed: MODOPTS="wctdm:opermode=US" AUTOMODS="rtc 3c59x typhoon tulip eepro100 natsemi forcedeth 8139cp 8139too via-rhine pcnet32 acenic e1000 ns83820 r8169 tg3 wctdm24xxp" ZAPMODS="wctdm24xxp" The device is not loading at startup. Here are the contents of modprobe.conf options wctdm24xxp Thanks again for your help. -- Linuturk www.onitato.com ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
