On Thu, Jun 14, 2007 at 08:10:33AM +0200, Sebastian Reitenbach wrote:
> Hi,
>
> > >
> > Two things come to mind,
> >
> > (1) being that you don't have the TE110P card jumped for an E1.
> > (2) UDEV isn't creating the devices fast enough for the driver load.
> >
> > My guess is it's UDEV. You can test this theory by creating a startup
> > script that loads the modules, put a sleep statement in that script that
> > waits for a second or so.
>
> I have the asterisks running as a cluster managed via linux-ha. First the
> driver loads when booting, then I log in, and start linux-ha, which then
> starts asterisk. I think that is time enough for udev to create the devices,
> but it is not doing it in the first place.
> I added a rmmod wcte11xp && modprobe wcte11xp to /etc/init.d/zaptel into the
> start section, and when I then login I have no problem to start asterisk.
This seems like unneeded voodoo.
You have already demonstrated that ztcfg ran perfectly well after system
boot with no startup.
Conisder the following startup sequence:
TMOUT=10 # timeout for udev to populate /dev/zap
# maybe it does nothing, as the module is already loaded by
# hotplug/udev ?
modprobe wcte11xp
# wait for /dev/zap/ctl:
while [ ! -c /dev/zap/ctl ] ; do
sleep 1
TMOUT=`expr $TMOUT - 1`
if [ $TMOUT -eq 0 ] ; then
echo "Error: missing /dev/zap/ctl. udev problem?"
exit 1
fi
done
/sbin/ztcfg
Basically the same as in in the zaptel init.d script but with lots of
junk removed.
Also, be sure to remove the lines in the modprobe configuration that run
ztcfg on module startup. Otherwise you defeat the purpose of the above
loop.
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406 mailto:[EMAIL PROTECTED]
http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir
_______________________________________________
--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
