[Asterisk-Dev] Odd problem with asterisk in boot time (Second part and answer)
pop at cofradia.org
Thu Jul 29 13:47:17 MST 2004
I fund the solution of the problem, ist no to easy to identifacte but
what happen is this:
I modify the /etc/init.d/zaptel file, replacing the "insmod" and "rmmod"
with the "modprobe" equivalentes commands, The old form to load an
unload modules in FC2 with Kernel 2.6.7 don't work well.
And if you have "Kudzu" (The hardware discovery service), in the test of
the TDM400P, left the PCI Channel of the TDM card bloqued and the Zaptel
scritps don't load correctly the modules for the hardware, then the
asterisk send the following message and few seconds later die:
chan_zap.c:765 zt_open: Unable to specify channel 2: No such device or
Jul 28 20:28:07 ERROR: chan_zap.c:5879 mkintf: Unable to
open channel 2: No such device or address
here = 0, tmp->channel = 2, channel = 2
Jul 28 20:28:07 ERROR: chan_zap.c:8721 setup_zap: Unable to
register channel '2'
Jul 28 20:28:07 WARNING: loader.c:328 ast_load_resource:
chan_zap.so: load_module failed, returning -1
Jul 28 20:28:07 WARNING: loader.c:423 load_modules: Loading
module chan_zap.so failed!
I reboot the hardware 20 times and when deactivate the kudzu service
(for fast boot), everything go ok.
I think is necesary check how the Zaptel modules as load.
A easy workaround is deactivate de Kudzu service and modify the zaptel
initialization script with modprobe.
And i think (in personal form), we need more efforts in Kernel 2.6
development and forget Kernel 2.4
Best Regards.... Fernando Romo
pop at cofradia.org
Fernando Romo wrote:
> Dear Developers:
> Well, i run asterisk in many machines with kernel 2.4 without
> problems, but recently we star to buy new Intel Motherboards and
> SATA-HD. This force to me to use a new Kernel version (2.6.7),
> beacouse the old Kernel don't support the new HD and the new chipset
> of my Motherboard (Intel D875-PBZ).
> I use FC2 with Kernel 2.6.7 and compile the zaptel drivers and modules
> without problem. I define the udev devices and zaptel recognize my
> TDM400P and the FXO/FXS channels.
> i make a symbolic links to the following devices:
> /dev/zap/channel -> /udev/zap/channel
> /dev/zap/ctl -> /udev/zap/ctl
> /dev/zap/pseudo -> /udev/zap/pseudo
> /dev/zap/timer -> /udev/zap/timer
> This is to force the devices without modify the chan_zap.c and don't
> brake any dependence in asterisk.
> Everything works fine, but the real problem comes when y put the
> /etc/init.d/asterisk scripts to initialize like deamond. In the boot
> process, Zaptel load without problems and asterisk report sucesfully
> load but when a check the log messages, asterisk die few seconds later.
> I login with a root acount and start asterisk wit "-c" and asterisk
> work fine. I notice if i try to start asterisk in the shell few
> seconds later of the boot process, this fail and report problems with
> the channel_zap creation.
> If i wait a few moments, and start asterisc in console mode or
> deamond, works fine. But obviusly i need the PBX load in boot time in
> case of a power lose.
> I think the problem maybe is caused for the UDEV identification
> process and the time taked for the kernel to activate this UDEV devices.
> Any Ideas?
> Thanks in advanced..... Fernando Romo
> pop at cofradia.org
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> To UNSUBSCRIBE or update options visit:
More information about the asterisk-dev