[App_rpt-users] How2 get radio stuff working with Dahdi???

[Jim Duuuude]

well, thats just all well and wonderful except that DAHDI DOESNT WORK!
Yes, it *STILL* has the *SAME* *STUPID* bugs in it that I had to fix
in Zaptel. It isnt going to work for a radio project stock.

JIM WB6NIL

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