thanks for the info I am working with an image of my own and has the kernel 4.14.79 with the image ASL_1.01-20180228-armhf-raspbian-stretch-image.img, it works perfectly for me. but with my own image

thanks for the info I am working with an image of my own and has the kernel 4.14.79 with the image ASL_1.01-20180228-armhf-raspbian-stretch-image.img, it works perfectly for me. but with my own image

That’s what I’m talking about when I reference “unless you are using a URI” in terms of sound “modules” which is just OSS that was deprecated long ago (over 10 years), was marked broken

The known good instructions from N4IRS state to hold the Raspbian kernel, and from a previous post in this thread it has to do with sound modules that may or may not be present in newer Raspbian

I disagree with rebuilding and with holding the kernel unless there is a good reason to do so. The only reason to hold the kernel back is if you need to use a URI to interface with a radio.. other

Oh boy, yeah I think the version that's on there was at least 4.14, I think I may have seen 4.17 in there too. Manuel, The root cause of asl-menu option 5 not working is that the asterisk service on

You are right, he is pulling a specific design. The center part of his design is ASL, and it is the most complicated part to run, when ASL run in a stable way. then he should build on that.. fixing

uname -r 4.9.80-v7+ Is what I have What happens with newer kernel is you loose sound support which dahdi needs to compile right. Not sure what for him to do but the fastest

It looks like Manuel is making a system of his own design, including all the digital and analog networking systems into one device. While his implementation is a custom one, a lot of the ideas are

Did you used the raspberry pi image from the wiki??? http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ Cause with this image and the readme I was able to do a node in half an hour using

It probably was installed/updated without the hold on kernel headers. ...mike/kb8jnm

After taking an initial look at the Pi in question, I've noticed that the dahdi pseudo device is not loading, preventing asterisk from starting. lsmod shows no dahdi module installed. The /etc/modules

Agreed, the initial diagnosis is to run the asterisk cli from the shell outside the script, and see what the error is. There's a log file that is called when running asl-menu in /tmp/asl-menu.log

And I just realized we're talking capitalization... in Manuel's situation his screenshot shows the variable is uppercase, and should remain that way in the do_asterisk_cli function.

Very good Stephen, I should have taken my time and looked at it all and not looked for the short answer. As I said, I don't use the asl-menu, but I guess I should find

Mike, The $ASTERISK is a variable set earlier in the script, on line 68. The do_asterisk_cli takes that variable and makes it into a full line that the shell expects. The variable in this case allows

Funny, I went looking at my install. I don't use the asl-menu, but it is not installed on my Pi. So, I went to the PC and took a look at the asl-menu shell script. 5 is the

I am using a raspberry pi B + with the raspbian Stretch installed. if I throw the command like: asl-menu (error5) sudo asl.menu (error5)

I assume that with the graphical interface being used, you installed ASL on top of an existing Linux install? If I recall correctly, the ASL image is based on ALArm, not Debian/Raspbian. When running

so I have it and it gives me the error 5