I just ran a dmesg (see output below) and this looks much better than it did originally (originally I didn't have zaptel_enable="YES" in rc.conf, I wonder if that was all I needed, along with my security being disabled).
It appears I'm ready to configure asterisk and use this card, let me know if you think there's something more (hardware/drive/device wise I need to do). Thanks again, # dmesg Zapata Telephony Interface Registered on major 196 Echo Canceller: MG2 FXS device: vendor=e159 device=1 subvendor=b1d9 wcfxs0: <Wildcard TDM400P REV I> port 0x1000-0x10ff mem 0xf8511000-0xf8511fff irq 18 at device 9.0 on pci5 FXS Attach for wcfxs0: deviceID : 0xe159 wcfxs0: [FAST] Freshmaker version: 73 Freshmaker passed register test ProSLIC sanity check failed Module 0: Not installed ProSLIC sanity check failed Module 1: Not installed ProSLIC sanity check failed Module 2: Not installed Module 3: Installed -- AUTO FXO Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules) Registered tone zone 0 (United States / North America) Thanks again, John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chad Leigh -- Pengar Enterprises Inc Sent: Tuesday, May 29, 2007 8:34 pm To: Asterisk on BSD discussion Subject: Re: [Asterisk-bsd] Zaptel Drivers On May 29, 2007, at 8:28 PM, John S. Strock wrote: > After receiving your last response, one thing hit me, I have my server > locked down and have the following in my /etc/rc.conf file: > > kern_securelevel_enable="YES" > kern_securelevel="1" I thought that might be a problem but was checking some things before I replied as I was not sure how that affected kernel modules > > So I've now disabled these lines, and I get the following errors, now > instead of "Operation not permitted", I received "File Exists": > > > # /usr/local/etc/rc.d/zaptel.sh start > zaptelkldload: can't load /usr/local/lib/zaptel/zaptel.ko: File exists > > # kldload /usr/local/lib/zaptel/zaptel.ko > kldload: can't load /usr/local/lib/zaptel/zaptel.ko: File exists maybe it is already loaded from your startup? try # kldstat is it listed? Chad > > Again, I'm not familiar with loading modules and devices so I'm not > sure > what this means. > > To answer your install question... > > Installing Asterisk from ports appeared to have installed zaptel as > well, > because when I tried to install zaptel from ports, I received an error > stating it was already installed. Also, the zaptel.ko file exists in > /usr/local/lib/zaptel, so again, I assume it was created for me. > > Any more ideas? > > Thanks again, > > John > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Mimura,Shigeki > Sent: Tuesday, May 29, 2007 8:11 pm > To: Asterisk on BSD discussion > Subject: RE: [Asterisk-bsd] Zaptel Drivers > > John Strock wrote: >> As a side note, how do I get zaptel.ko, I assume when I installed > Asterisk >> via the ports, it would've installed the *.ko file, but apparently > not. > > When you installed asterisk from ports, also zaptel was installed > under > '/usr/local/lib/zaptel'. > How about to execute 'kldload /usr/local/lib/zaptel/zaptel.ko'? > _______________________________________________ > Asterisk-BSD mailing list > Asterisk-BSD@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-bsd > > _______________________________________________ > Asterisk-BSD mailing list > Asterisk-BSD@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-bsd _______________________________________________ Asterisk-BSD mailing list Asterisk-BSD@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-bsd _______________________________________________ Asterisk-BSD mailing list Asterisk-BSD@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-bsd
