[App_rpt-users] URI-X Issues With New Raspbian build

[Mike]

Personally, I only mentioned the voltage issue for everyone/anyone to 
check as a possibility for errors they may get.

So I was only referencing from experience.

But this kernel protection before upgrade worked for me, did you try it ?

http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ASL_1.01-20180228-armhf-raspbian-stretch-image.readme

Login: repeater
Passsword: allstarlink
SSH port: 22
User repeater has sudo privileges (sudo -s)

There may have been updates to the operating system and AllStarLink since this image was built.
Run the following commands after the first time you boot.

sudo apt-mark hold raspberrypi-kernel-headers raspberrypi-kernel
sudo apt-get update
sudo apt-get upgrade -y
sudo reboot

at the # prompt run "asl-menu" to setup your node.

...mike/kb8jnm

On 7/10/2018 11:20 AM, Jim Aspinwall No1PC wrote:
> Coincidence? Serendipity?
>
> I just tried the latest builds from: 
> http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/
>
> Liking asl-menu... that helps... but as with others below... I have 
> found, on a Pi3 + RA-40 that works under the prior 'build' - I too am 
> experiencing multiple errors and ultimately failure of asterisk app to 
> identify, connect to and use the USB-connected RA-40 as either 
> USBRadio or SimpleUSB that worked under same configuration parameters. 
> It's even complaining that asterisk.ctl is not in /var/run when it 
> clearly is there.
>
> On the console I am getting low voltage errors I never saw before... 
> using the same power source. Measurement at the board is minimum 
> 4.96v.  Power source is a PowerPole USBBuddy 3A device from clean DC - 
> these run all of my field-racked nodes so far.  Even a 1.5a wall-wart 
> has been fine prior.  Doesn't make sense when the operational voltage 
> tolerance of the Pi is greater than this 0.8% difference.  If the 
> low-voltage check is getting in the way... how do we fix that?    
> Separate power sources for Pi vs interface boards?
>
> If the voltage issue is NOT "getting in the way" of Asterisk using a 
> good known USB-interfaced device? What is?
>
> Again, I can shut down the boards, swap the USB Flash drive from the 
> latest build to the prior and it runs fine.  I'm reluctant to in-place 
> update the working node/stick... until I can properly clone the stick 
> and test on an expendable build.   (What tool does one use to make an 
> image from a bootable stick?)
>
>
>  Yeah it's decidedly an issue with snd-pcm-oss missing from the system..
> > may need to compile a custom kernel.. _shrug_
>
>
> >> this may not be relevant, but worth saying at this point.
> >>
> >> I have found that if you initialize a pi node while not supplying 
> the Pi
> >> board with enough current
> >>
> >> during the initial start-up. Many things seem to go wrong.
> >>
> >> I'm building a bigger 5v power supply to handle 2 or three of these at
> >> once to verify what I'm thinking,
> >>
> >> but not tested anything yet.
> >>
> >> In my case, it is Dahdi
> >>> Not sure why but the /dev/dsp1 seems to be missing... I've installed
> >>> oss-compat and tried a number of things.. see below output...
> >>>
> >>> $ sudo uridiag
> >>> URIDiag, diagnostic program for the DMK Engineering URI
> >>> USB Radio Interface, version 0.9, 08/14/15
> >>>
> >>> Found CM119 USB Radio Interface at 001/005
> >>> Unable to re-open DSP device 1: /dev/dsp1
> >>>
>
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at lists.allstarlink.org
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20180710/92ad90dc/attachment.html>