[Asterisk-Users] Strange Zaptel Modprobe driver failure

[Tilghman Lesher]

On Wednesday 21 January 2004 15:53, Mark Rizzo wrote:
> Hello, my first post to the list.  I have started to install and play
> with Asterisk.  I was following some basic instructions to
> 'jump-start' my system.  I have a TDM400P with one port and a X100P.
>
> I am running the latest CVS versions (from today).
>
> Following the steps I found for basic jump-start I did the following:
> Modprobe zaptel
> Modprobe wcfxo
> Modprobe wcfxs
>
> Edited /etc/zaptel.conf and added the following lines:
> fxsks=1
> fxoks=2
> loadzone=us
> defaultzone=us
>
> I then ran ztcfg -vv and receive a good response.
>
> Asterisk started and running just fine!  YES!
>
> I then rebooted my computer for other reasons.  Now the following
> happens:
> Modprobe zaptel
> (works)
>
> Modprobe wcfxo
> ZT_CHANCONFIG failed on channel 2: No such device or address (6)
> /lib/modules/2.4.20-gentoo-r9/misc/wcfxo.o: post-install wcfxo failed
> /lib/modules/2.4.20-gentoo-r9/misc/wcfxo.o: insmod wcfxo failed
>
> Modprobe wcfxs
> (works)
>
> lsmod shows that both modules are loaded.  Asterisk runs, though I
> have yet to try and use both boards.  If I remove my changes to the
> zaptel.conf file, then run modprobe, then re-add my changes to
> zaptel.conf file I am fine.

The problem is not that the modules aren't loading, but that when the
first module is loaded, the entry in modules.conf attempts to configure
the second channel, for which the driver is not yet loaded.  This is the
error that you see about the second channel.

I have found three possible solutions:

1)  Remove the post-install wcfxo line from /etc/modules.conf.  This is
the easiest solution, but it is not permanent, as everytime you
recompile and reinstall the drivers, the line will be readded.

2)  Create /etc/zaptel.conf.0 and /etc/zaptel.conf.1, the first config
file with only the configuration for your wcfxo, and the second for
all channels.  Before each modprobe, symlink (or copy) the
appropriate file into place, e.g.

modprobe zaptel
ln -sf /etc/zaptel.conf.0 /etc/zaptel.conf
modprobe wcfxo
ln -sf /etc/zaptel.conf.1 /etc/zaptel.conf
modprobe wcfxs

The benefit here is that you don't ever have to bother with this again
until you add more hardware.  The downside is that you need a script to
do this.

3)  Ignore the error.  Upside:  no action is needed.  Downside:  if you
get in the habit of ignoring errors, sometime, you're going to miss
something important.

-Tilghman