asterisk users - Aug 2006 - modprobe wctdm fails in /etc/rc.local on FC5

If I boot my server and manually type "modprobe wctdm", it correctly  
loads both wctdm and zaptel.  If I put the modprobe in /etc/rc.local  
and reboot, it fails.  Why?  I am running the latest svn source of  
zaptel on Fedora Core 5 (w/latest updates as of 8/15)

Here are the error messages from modprobe:

Aug 15 15:55:39 WARNING[1860] chan_zap.c: Unable to specify channel  
1: No such device or address
Aug 15 15:55:39 ERROR[1860] chan_zap.c: Unable to open channel 1: No  
such device or address
here = 0, tmp->channel = 1, channel = 1
Aug 15 15:55:39 ERROR[1860] chan_zap.c: Unable to register channel '1'
Aug 15 15:55:39 WARNING[1860] loader.c: chan_zap.so: load_module  
failed, returning -1
Aug 15 15:55:39 WARNING[1860] loader.c: Loading module chan_zap.so  
failed!

Can someone send me their modprobe.conf file?  I think that may be  
the problem.  A zaptel file is created during install in /etc/ 
modprobe.d but modprobe.conf must need to reference it...

Hi Robert

Why don't you select the modules in /etc/sysconfig/zaptel and allow the 
system to boot via /etc/init.d/zaptel by placing a link S99zaptel in 
your appropriate run level directory. I found that S09zaptel, the 
default, didn't work for me in my setup because it was too early in the 
boot process. You have to install zaptel for these files to exist. Hope 
this helps.

Robert La Ferla wrote:
> If I boot my server and manually type "modprobe wctdm", it
correctly
> loads both wctdm and zaptel.  If I put the modprobe in /etc/rc.local and 
> reboot, it fails.  Why?  I am running the latest svn source of zaptel on 
> Fedora Core 5 (w/latest updates as of 8/15)
> 
> Here are the error messages from modprobe:
> 
> Aug 15 15:55:39 WARNING[1860] chan_zap.c: Unable to specify channel 1: 
> No such device or address
> Aug 15 15:55:39 ERROR[1860] chan_zap.c: Unable to open channel 1: No 
> such device or address
> here = 0, tmp->channel = 1, channel = 1
> Aug 15 15:55:39 ERROR[1860] chan_zap.c: Unable to register channel
'1'
> Aug 15 15:55:39 WARNING[1860] loader.c: chan_zap.so: load_module failed, 
> returning -1
> Aug 15 15:55:39 WARNING[1860] loader.c: Loading module chan_zap.so failed!
> 
> 
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
> 
-- 
Martti Tienhaara (martti@dash.ca)
DASH Software Ltd.

On Tue, Aug 15, 2006 at 09:32:00PM -0400, Robert La Ferla
wrote:
> If I boot my server and manually type "modprobe wctdm", it
correctly
> loads both wctdm and zaptel.  If I put the modprobe in /etc/rc.local  
> and reboot, it fails.  Why?  
Maybe /sbin is not in the path?

Anyway, rc.local is normally a rather late place to load modules.
Asterisk should be started in an init.d script that is run before
rc.local .

-- 
Tzafrir Cohen         sip:tzafrir@local.xorcom.com
icq#16849755          iax:tzafrir@local.xorcom.com
+972-50-7952406          jabber:tzafrir@jabber.org
tzafrir.cohen@xorcom.com     http://www.xorcom.com

rc.local:

touch /var/lock/subsys/local

setpci -v -s 00:1f.1 LATENCY_TIMER=4
setpci -v -s 02:0e.0 LATENCY_TIMER=4
setpci -v -s 0b:07.0 LATENCY_TIMER=4
setpci -v -s 0c:08.0 LATENCY_TIMER=4
setpci -v -s 10:0d.0 LATENCY_TIMER=0
setpci -v -s 06:02.0 LATENCY_TIMER=ff
sleep 5

echo UnLoading wct4xxp
rmmod -v wct4xxp
rmmod -v zaptel
sleep 3

echo Loading wct4xxp
/sbin/modprobe -v zaptel
sleep 5
/sbin/modprobe -v wct4xxp
sleep 5
# ztcfg -vvvv
#sleep 5

echo 1 > /proc/irq/201/smp_affinity
echo 1 > /proc/irq/217/smp_affinity
echo 0 > /proc/irq/209/smp_affinity
echo 1 > /proc/irq/14/smp_affinity

/usr/sbin/amportal start



-- 
-- 
Steven

http://www.glimasoutheast.org



"Robert La Ferla" <robertlaferla@comcast.net> wrote in message
news:275EBEF2-D328-44F1-A3FE-16B44762765B@comcast.net...
> Can someone send me their modprobe.conf file?  I think that may be  the
problem.  A zaptel file is created during install in /etc/
> modprobe.d but modprobe.conf must need to reference it...
>
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>

Hi Tzafrir

I'm still testing so I start asterisk manually after boot. You are right 
that 99 would normally be too late but as long as zaptel + modules are 
loaded first with a lesser boot sequence number and is running when 
asterisk starts on boot up it shouldn't matter where it is done in the 
boot process.
-----
Martti Tienhaara wrote:
 > > Hi Robert
 > >
 > > Why don't you select the modules in /etc/sysconfig/zaptel and
allow
the
 > > system to boot via /etc/init.d/zaptel by placing a link S99zaptel in
 > > your appropriate run level directory. I found that S09zaptel, the
 > > default, didn't work for me in my setup because it was too early
in
the
 > > boot process. You have to install zaptel for these files to exist. 
Hope
 > > this helps.
-----
 > Tzafrir Cohen wrote
 >
 > Why is 09 too early? And isn't 99 too late? How do you start asterisk?

-- 
Martti Tienhaara (martti@dash.ca)
DASH Software Ltd.

I found an init.d script for asterisk BUT not for asterisk/zaptel  
modules.  I'm still looking for a good solution.  It seems to me that  
the correct solution would involve /etc/modprobe.d/modpobe.conf.