<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div style="font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;"><div style="font-size: 16px;"></div>
<div style=""><span style="color: rgb(38, 40, 42);"><font size="2">Coincidence? Serendipity?</font></span></div><div style=""><font size="2"><span style="color: rgb(38, 40, 42);"><br>I just tried the latest builds from: </span></font><a href="http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/" rel="nofollow" target="_blank">http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/</a> <font size="2"><br><br>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.<br><br>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?<br><br>If the voltage issue is NOT "getting in the way" of Asterisk using a good known USB-interfaced device? What is? <br><br>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?)<br><br></font></div><div style="font-size: 16px;"><span style="color: rgb(38, 40, 42); font-size: 13px;"><br></span></div><div style="font-size: 16px;"><span style="color: rgb(38, 40, 42); font-size: 13px;"> Yeah it's decidedly an issue with snd-pcm-oss missing from the system..</span><br></div></div><div id="ydp56ee7b69yahoo_quoted_1833693460" class="ydp56ee7b69yahoo_quoted"><div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;"><div><div dir="ltr">> may need to compile a custom kernel.. _shrug_<br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">>> this may not be relevant, but worth saying at this point.<br></div><div dir="ltr">>><br></div><div dir="ltr">>> I have found that if you initialize a pi node while not supplying the Pi<br></div><div dir="ltr">>> board with enough current<br></div><div dir="ltr">>><br></div><div dir="ltr">>> during the initial start-up. Many things seem to go wrong.<br></div><div dir="ltr">>><br></div><div dir="ltr">>> I'm building a bigger 5v power supply to handle 2 or three of these at<br></div><div dir="ltr">>> once to verify what I'm thinking,<br></div><div dir="ltr">>><br></div><div dir="ltr">>> but not tested anything yet.<br></div><div dir="ltr">>><br></div><div dir="ltr">>> In my case, it is Dahdi<br></div><div dir="ltr">>>> Not sure why but the /dev/dsp1 seems to be missing... I've installed<br></div><div dir="ltr">>>> oss-compat and tried a number of things.. see below output...<br></div><div dir="ltr">>>><br></div><div dir="ltr">>>> $ sudo uridiag<br></div><div dir="ltr">>>> URIDiag, diagnostic program for the DMK Engineering URI<br></div><div dir="ltr">>>> USB Radio Interface, version 0.9, 08/14/15<br></div><div dir="ltr">>>><br></div><div dir="ltr">>>> Found CM119 USB Radio Interface at 001/005<br></div><div dir="ltr">>>> Unable to re-open DSP device 1: /dev/dsp1<br></div><div dir="ltr">>>><br></div><div dir="ltr"><br></div></div>
</div>
</div></div></body></html>