Hello!<br><br><div class="gmail_quote">On Tue, Dec 1, 2009 at 4:18 PM, Ian FREISLICH <span dir="ltr"><<a href="mailto:ianf@clue.co.za">ianf@clue.co.za</a>></span> wrote:<br><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> > >> On Monday 30 November 2009 15:37:59 Jerry B. Altzman wrote:<br>
> > >>> Anyone out there running Asterisk on FBSD 8.0? I'm about to bite the<br>
> > >>> bullet and rebuild my asterisk machine (running 6.1, I'm tired of<br>
> > seeing<br>
> > >>> portversion complain incessantly to me), and want to know who's managed<br>
> > >>> a successful test/deployment (if anyone) yet.<br>
> > >> Yes, works fine.<br>
> > >> Haven't tested ZapTel though.<br>
> > > And I haven't been able to make Zaptel work yet.<br>
> ><br>
> > Oh, that's bad: I depend on zaptel for my TDM400...thanks for the heads-up.<br>
> ><br>
><br>
> Which zaptel version do you mean? Zaptel should work fine. As well as dahdi<br>
> port (although there's much less dahdi hw drivers ported so far).<br>
<br>
</div>I have zaptel-1.4.11.2 installed. I get a kernel panic if I unload<br>
the driver. I've just rebuilt to test and zaptel loads and asterisk<br>
can now open the zap devices. I still get a hard-lock when I try<br>
to unload the driver and OSLEC doesn't work because it uses floating<br>
point arithmetic which is forbidden in the kernel.<br></blockquote><div><br></div><div>Problems with unloading look like driver-specific issue because I do not have problems with qozap.</div><div>OSLEC problems are driver-specific.</div>
<div><br></div><div>I can take a look if you can provide me with remote access and serial console.</div><div><br></div><div>Max</div><div><br></div></div>