[App_rpt-users] Anyone compiling asterisk from sources onDebian.

Wed Apr 6 18:38:20 UTC 2011

This may be a pulse audio issue??? I have had a lot of issue with PulseAudio
blocking up ALSA from the usb sound devices on late distro's that have
started to use Pulse Audio. The error you get looks similar to those I have
run into on other projects...

Doug
KD8B 

-----Original Message-----
From: app_rpt-users-bounces at ohnosec.org
[mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Jann Traschewski
Sent: Wednesday, April 06, 2011 2:26 PM
To: 'Tom Russo'; 'David KE6UPI'; app_rpt-users at ohnosec.org
Subject: Re: [App_rpt-users] Anyone compiling asterisk from sources
onDebian.

 Hi,

I have trouble to get my URI board blinking with the "red" LED after
starting zaptel on a fresh Debian/Squeeze box (as far as I remember it did
on my installations with Debian/Lenny).

Alsamixer does show the CM108 but the Asterisk console does show: [Apr  6
20:23:04] WARNING[2107]: chan_usbradio.c:2236 setformat: Unable to re-open
DSP device 0 (usb): No such file or directory

The only difference I found is the missing /dev/dsp on Debian/Squeeze. Any
ideas?
Tnx!

73,
Jann

> -----Original Message-----
> From: app_rpt-users-bounces at ohnosec.org 
> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Tom Russo
> Sent: Friday, February 18, 2011 5:36 PM
> To: David KE6UPI; app_rpt-users at ohnosec.org
> Subject: Re: [App_rpt-users] Anyone compiling asterisk from sources 
> onDebian.
> 
> On Fri, Feb 18, 2011 at 07:21, David KE6UPI <dshaw at ke6upi.com> wrote:
> > http://kriskirkland.com/?p=143
> 
> Yeah, that was the one site I had found (I did google before asking 
> here), where there is a script that did an install onto a Lenny-based 
> system.  It helped me to be sure I was getting all the right 
> dependencies, but didn't address the build failure.  The missing 
> includes I pointed out appear only to impact builds on the very latest 
> system, Debian Squeeze, which uses the 2.6.32 kernel.
> 
> When I get back to it this afternoon, I plan on submitting a bug 
> report and patches to Mantis.
> 
> I note also that the upstream version of Asterisk at digium has bug 
> tracker entris because the wctc4xx kernel module fails on recent 
> kernels/  They've  fixed it in SVN.  I also saw that module fail, but 
> since I don't need support for that card I didn't bother patching it
> --- I just used menuselect to unselect that driver and built the 
> others.
> 
> > On Thu, Feb 17, 2011 at 10:54 AM, Tom Russo
> <tom.km5vy at gmail.com> wrote:
> >>
> >> On Thu, Feb 17, 2011 at 10:52, Tom Russo
> <tom.km5vy at gmail.com> wrote:
> >>
> >> > The short story is that the zaptel kernel module build
> is behaving
> >> > very much like it's not getting the kernel headers right, even 
> >> > though the correct headers for the kernel are installed.  It 
> >> > doesn't complain about not finding specific files, though, it's 
> >> > merely dying during compilation of pciradio.c with
> undefined macros
> >> > that are definitely present in kernel headers that it
> should have
> >> > found.  I don't want to burden the list with details
> unless there
> >> > is interest in the solution, though.  If someone else is using 
> >> > app_rpt on a Debian-based system, I'd love to be in
> contact to hash out details.
> >>
> >> Never mind.  Looks like the issue is just that a few files don't 
> >> include <linux/sched.h> (some do, some don't) and this is
> apparently
> >> just a difference between Lenny and Squeeze (I saw someone
> on the web
> >> providing a debian allstar install script that claimed to
> work Just
> >> Fine installing zaptel, so it must just be a change in a
> later kernel
> >> revision).
> >>
> >> The files needing #include <linux/sched.h> are kernel/pciradio.c, 
> >> kernel/wctdm.c, and kernel/zaptel-base.c   Without this
> include, they
> >> complain about set_current_state and TASK_INTERRUPTABLE not having 
> >> been declared.  Since several other modules already include 
> >> <linux/sched.h>, it's probably a safe thing to do to make
> this change
> >> in the repository for zaptel, I'd wager.
> >>
> >> Some of the other kernel modules are failing to compile, one that 
> >> complains abut netif_rx_schedule --- this appears to have
> gone away
> >> in the 2.6.32 kernel.  Fortunately, I don't need the
> module that has
> >> that problem, and don't need to spend time finding how to
> fix 'em.
> >> Fixing the three above and deselecting the modules I don't
> need seems
> >> to get me going.
> >>
> >>
> >> --
> >> Tom Russo    KM5VY   SAR502   DM64ux http://www.swcp.com/~russo/ 
> >> Tijeras, NM  QRPL#1592 K2#398  SOC#236 
> >> http://kevan.org/brain.cgi?DDTNM
> >>  "The truth will set you free, but first it will piss you off."
> >> _______________________________________________
> >> App_rpt-users mailing list
> >> App_rpt-users at ohnosec.org
> >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> >
> >
> 
> 
> 
> --
> Tom Russo    KM5VY   SAR502   DM64ux http://www.swcp.com/~russo/ 
> Tijeras, NM  QRPL#1592 K2#398
> SOC#236 http://kevan.org/brain.cgi?DDTNM
>  "The truth will set you free, but first it will piss you off."
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> 

_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users