On Sun, 2004-10-24 at 05:10, Tzafrir Cohen wrote:
> One obvious solution is not to automatically load kudzu.
>
> chkconfig --remove kudzu
>
> Another obvious solution of the same sort is modprobing the zaptel
> module earlier in the boot process.
>
> I can't seem to figure out , though, where kudzu takes its modue names
> from. I haven't bothred reading th source yet, though (not from
> /usr/share/hwdata, it seems)
The problem is that once Kudzu runs it configures linux to always load
the incorrect module for the card. I have already erased kudzu from the
server, recompiled Zaptel and modified modules.dep by hand but if any
application runs a depmod -a the configuration for the other module
returns. If I do a "modprobe zaptel" it will always load the other
module.
--
Carlos ChÃvez
Director de TecnologÃa
Telecomunicaciones Abiertas de MÃxico
_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
