<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
well, thats just all well and wonderful except that DAHDI DOESNT WORK!<br>Yes, it *STILL* has the *SAME* *STUPID* bugs in it that I had to fix<br>in Zaptel. It isnt going to work for a radio project stock.<br><br>JIM WB6NIL<br><br><div>> Date: Tue, 15 Nov 2011 11:31:26 +1000<br>> From: vk4akp@yahoo.com.au<br>> To: app_rpt-users@ohnosec.org<br>> Subject: [App_rpt-users] How2 get radio stuff working with Dahdi???<br>> <br>> Hi Jeremy,<br>> <br>> Yep, love Gentoo. It's the best! hihi!<br>> <br>> Thanks for all the good info. It can take ages to Google and muddle your <br>> way through all this stuff sometimes and there's no point in trying to <br>> re-invent the wheel when others have already traveled these roads and <br>> know the answers.<br>> <br>> So, we've commented out a few things and emerged the dahdi stuff and the <br>> "make install_usbradio" now works and Asterisk is up again.<br>> <br>> In terms of Asterisk, we basically did this...<br>> 1. install dahdi, dahdi-tools and libpri using Portage<br>> 2. stop your Asterisk package from building libpri and zaptel<br>> 3. prevent building some Asterisk modules that needed extra deps or <br>> didn't like the new gcc<br>> 4. remove the ztcfg line from the init.d script because it's not needed<br>> 5. set the dahdi init.d scripts to start on boot<br>> <br>> However our next problem is that the TDM card is not working even though <br>> it's detected and started correctly. And none of the DMK URI radio <br>> dongles are flashing or working.<br>> <br>> So I need a shove in the right direction again sorry.<br>> Are there some lines in some of the configs that need changing to point <br>> stuff at Dahdi instead of Zaptel perhaps?<br>> <br>> Regards,<br>> Ken - vk4akp<br>> .-.-.<br>> <br>> On 11/15/2011 3:00 AM, app_rpt-users-request@ohnosec.org wrote:<br>> ><br>> > ------------------------------<br>> ><br>> > Message: 2<br>> > Date: Mon, 14 Nov 2011 06:51:59 -0600<br>> > From: "Jeremy R. Geeo [KD?EAV]"<kd0eav@gmail.com><br>> > To: app_rpt-users@ohnosec.org<br>> > Subject: Re: [App_rpt-users] Install fails at zaptel on Gentoo system<br>> > Message-ID:<4EC10EEF.2060102@gmail.com><br>> > Content-Type: text/plain; charset=UTF-8; format=flowed<br>> ><br>> > Hey Ken,<br>> ><br>> > Glad to see a fellow Gentoo(er) on the list.<br>> ><br>> > I don't know if you require such a new kernel; but 3.1.0 is very new<br>> > (especially for Zaptel).<br>> ><br>> > Last I knew, (but this may have since been patched) the zaptel modules<br>> > won't compile as-is on any kernel before 2.6.28 (ish - I may be off a<br>> > version or two, don't remember). I've only succeeded in making it work<br>> > up to 2.6.35 (becuase I DID need a newer kernel for hardware support).<br>> > In 2.6.36 they drop support for the ioctl call<br>> > (http://lwn.net/Articles/119652/).<br>> ><br>> > I haven't followed (or caught up) on changes since about 2.6.36, so I<br>> > don't know what has changed going into 3.0 and beyond.<br>> ><br>> > While trying to refresh my memory, I did find this zaptel patch (which<br>> > is actually for openWRT) which may be a step in the right direction for<br>> > the 2.6.36 barrier...<br>> > https://dev.openwrt.org/browser/packages/libs/zaptel-1.4.x/patches/370-2.6.36.patch<br>> ><br>> > I've also found it handy to go into the config on zaptel and disable<br>> > many/most of the modules - I specifically only need ztdummy (and it's<br>> > dependencies). In your case, I assume you don't need support for<br>> > pciradio. Probably no sense troubleshooting that module if you're not<br>> > going to use it.<br>> ><br>> ><br>> ><br>> > 73<br>> ><br>> > - Jeremy, KD0EAV<br>> ><br>> ><br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@ohnosec.org<br>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br></div> </div></body>
</html>