[Fwd: Re: [Asterisk-Users] udev or not?]

[Howard Lowndes]

On Fri, 2004-12-10 at 16:15, Steven Critchfield wrote:
> Forwarded back to the list so others might get the benefit of the
> answers, and I get fact checked by others.

In FC3 the file /etc/modules.conf becomes /etc/modprobe.conf

> 
> -------- Forwarded Message --------
> > From: Lee <leeb00 at gmail.com>
> > Reply-To: Lee <leeb00 at gmail.com>
> > To: Steven Critchfield <critch at basesys.com>
> > Subject: Re: [Asterisk-Users] udev or not?
> > Date: Fri, 10 Dec 2004 13:00:29 -0800
> > On Fri, 10 Dec 2004 06:36:02 -0600, Steven Critchfield
> > <critch at basesys.com> wrote:
> > > On Thu, 2004-12-09 at 23:39 -0800, Lee wrote:
> > > 
> > > 
> > > > I'm just getting started with asterisk on White Box Linux 3.0
> > > > I have a x100p card in the PC.
> > > >
> > > > If I reboot and immediately do a "ztcfg -vv" I get the well known
> > > > "Unable to open master device '/dev/zap/ctl'. If I then do a "modprobe
> > > > wcfxo" this error disappears and Asterisk runs fine.
> > > 
> > > > Asterisk runs fine as long as I do a modprobe wcfxo after each reboot,
> > > > prior to running Asterisk. I can make and receive calls through the
> > > > x100p. I would just like to solve the error issue. Thanks.
> > > 
> > > Check in /etc and look for a file with module in the name. On my debian
> > > machine it is /etc/modules. In there you can place your wcfxo driver
> > > name and it will auto load everytime.
> 
> > Thanks for the help. There is indeed a file called /etc/modules.conf 
> > but it appears to already have wcfxo in it, unless in misunderstood
> > what you are recommending. Are you saying that I should add "modprobe
> > wcfxo" to this file?
> > 
> > /etc/modules.conf:
> > ---------------------------------------------
> > alias eth0 e100
> > alias sound-slot-0 via82cxxx_audio
> 
> This is why I was somewhat vague. Check again for a file that is
> just /etc/modules. It should have a comment about loading modules one at
> a time at boot time. Make sure you also get the zapata module listed as
> well. The modules.conf file you mentioned is a config file about what to
> do when a module is loading or unloading. 
-- 
Howard.
LANNet Computing Associates;
Your Linux people <http://www.lannetlinux.com>
------------------------------------------
"When you just want a system that works, you choose Linux;
when you want a system that just works, you choose Microsoft."
------------------------------------------
"Flatter government, not fatter government;
Get rid of the Australian states."