[Asterisk-Users] invalid argument 22 when modprobe wcfxs and wcfxo

[Martin Pycko]

don't bother about the 1st errors

run "ztcfg -vv"
and you shouldn't have errors

Martin

On Wed, 14 May 2003, Robert Boardman wrote:

> Thanks for that now when I modprobe wcfxo first I get this
>
> root at slackware:~# modprobe wcfxo
> ZT_CHANCONFIG failed on channel 2: No such device or address (6)
> /lib/modules/2.4.20/misc/wcfxo.o: post-install wcfxo failed
> /lib/modules/2.4.20/misc/wcfxo.o: insmod wcfxo failed
>
>
> and modprobe wcfxs works fine
>
> any advise?
>
> Rob
>
>
> Quoting Martin Pycko <martinp at digium.com>:
>
> > Well according to your zaptel.conf you need to first load the FXO module
> >
> > modprobe wcfxo
> > modprobe wcfxs
> >
> > Martin
> >
> > On Wed, 14 May 2003, Robert Boardman wrote:
> >
> > > The Zaptel.conf is there see below
> > >
> > > Robb
> > >
> > > Quoting Martin Pycko <martinp at digium.com>:
> > >
> > > > We need your zaptel.conf config file
> > > >
> > > > /etc/asterisk/zapata.conf is for asterisk and zaptel.conf is for zaptel
> > > > drivers
> > > >
> > > > Martin
> > > >
> > > > On Wed, 14 May 2003, Robert Boardman wrote:
> > > >
> > > > > Thanks for your reply
> > > > >
> > > > > Here is Zapata.conf
> > > > > [channels]
> > > > > signalling=fxs_ks
> > > > > context=incoming
> > > > > channel=>1 ;X100P
> > > > > context=internal
> > > > > signalling=fxo_ks
> > > > > channel=>2 ;tdm100b
> > > > >
> > > > > here is zaptel.conf
> > > > > fxsks=1 #X100P
> > > > > fxoks=2 #tdm100
> > > > > defaultzone=uk
> > > > > loadzone=uk
> > > > >
> > > > > here is the output from ztcfg
> > > > >
> > > > > root at slackware:~# ztcfg -vv
> > > > >
> > > > > Zaptel Configuration
> > > > > ======================
> > > > >
> > > > >
> > > > > Channel map:
> > > > >
> > > > > Channel 01: FXS Kewlstart (Default) (Slaves: 01)
> > > > > Channel 02: FXO Kewlstart (Default) (Slaves: 02)
> > > > >
> > > > > 2 channels configured.
> > > > >
> > > > > Notice: Configuration file is /etc/zaptel.conf
> > > > > line 4: Unable to open master device '/dev/zap/ctl'
> > > > >
> > > > > Here is the output from modprobe of wcfxo and wxfxs
> > > > >
> > > > > root at slackware:~# modprobe wcfxs
> > > > > ZT_CHANCONFIG failed on channel 1: Invalid argument (22)
> > > > > /lib/modules/2.4.20/misc/wcfxs.o: post-install wcfxs failed
> > > > > /lib/modules/2.4.20/misc/wcfxs.o: insmod wcfxs failed
> > > > > root at slackware:~# modprobe wcfxo
> > > > > ZT_CHANCONFIG failed on channel 1: Invalid argument (22)
> > > > > /lib/modules/2.4.20/misc/wcfxo.o: post-install wcfxo failed
> > > > > /lib/modules/2.4.20/misc/wcfxo.o: insmod wcfxo failed
> > > > > root at slackware:~#
> > > > >
> > > > > Does anyone have any advice  how to get the driver loaded
> > > > >
> > > > > Ps I'm using slakeware 9.0 and it has been working before
> > > > >
> > > > > Robb
> > > > >
> > > > > Quoting Iain Stevenson <iain at iainstevenson.com>:
> > > > >
> > > > > >
> > > > > >
> > > > > > --On Wednesday, May 14, 2003 12:52 am +0100 Robert Boardman
> > > > > > <robb at 20tauntongrove.net> wrote:
> > > > > >
> > > > > > >
> > > > > > > I ahve been having problems loading the wcfss and wcfxo drivers
> > > > > > >
> > > > > >
> > > > > > The output of lsmod that you included shows that the modules are
> > loading
> > > > -
> > > > > > so it's more likely a configuration error in zaptel.conf and/or
> > > > > > zapata.conf.  You could post those files to the list to see if
> > anyone
> > > > can
> > > > > > spot a problem.
> > > > > >
> > > > > > > I get an error message invalid argument and something about post
> > > > install
> > > > > > > insmod failed
> > > > > > >
> > > > > >
> > > > > > When do you get this error message?  If you do ztcfg -vvv what is
> > the
> > > > > > result?
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > is the problem that the hisax isdn drivers have loaded?
> > > > > > > if so how do I stop them loading?
> > > > > >
> > > > > > hisax isn't the problem.  Asterisk interfaces to passive ISDN card
> > (eg
> > > > > > hisax) through a modem interface which is outside the zaptel
> > framework.
> > > > > > There is no interaction between zaptel and hisax drivers.
> > > > > >
> > > > > >   Iain
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Asterisk-Users mailing list
> > > > > > Asterisk-Users at lists.digium.com
> > > > > > http://lists.digium.com/mailman/listinfo/asterisk-users
> > > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Asterisk-Users mailing list
> > > > > Asterisk-Users at lists.digium.com
> > > > > http://lists.digium.com/mailman/listinfo/asterisk-users
> > > > >
> > > >
> > > > _______________________________________________
> > > > Asterisk-Users mailing list
> > > > Asterisk-Users at lists.digium.com
> > > > http://lists.digium.com/mailman/listinfo/asterisk-users
> > > >
> > >
> > >
> > > _______________________________________________
> > > Asterisk-Users mailing list
> > > Asterisk-Users at lists.digium.com
> > > http://lists.digium.com/mailman/listinfo/asterisk-users
> > >
> >
> > _______________________________________________
> > Asterisk-Users mailing list
> > Asterisk-Users at lists.digium.com
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> >
>
>