<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Ok, so rebuilding the Dahdi drivers worked – but the process as shown in the wiki did not work, nor did the –reinstall command – it looks like DKMS is by default building things with -j 4, and that’s too much for a Pi – my SSH connection was getting killed during the Dahdi recompile. So I had to manually do it with this command:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>dkms build -m asl-dahdi-linux -v 2.11.1 -j 1<o:p></o:p></p><p class=MsoNormal>dkms install -m asl-dahdi-linux -v 2.11.1 -j 1 –force<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Once I’d done that, I could load up the dahdi kernel module, and asterisk would start up. It appears I am connected to the network with the new node – however I’m having the following message spew into /var/log/asterisk/messages multiple times a second:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[Apr 11 17:21:22] WARNING[1387] chan_simpleusb.c: Unable to re-open DSP device 1 (usb_45984): No such file or directory<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Anyone got any ideas?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Jeremy, NQ0M<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Jeremy Utley <jerutley@gmail.com> <br><b>Sent:</b> Wednesday, April 11, 2018 4:43 PM<br><b>To:</b> 'Users of Asterisk app_rpt' <app_rpt-users@lists.allstarlink.org><br><b>Subject:</b> Problems with setup from newest image<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So last week while I was on vacation, I had an SD card filesystem go corrupt – lots of damaged files, Asterisk segfaulting on startup, all kinds of weird stuff happening. So I decided to rebuild this node (45984) with the newest stuff – this was my last Arch-based node, and I wanted to get back to the Debian base. So, I pulled down the 20180228 raspbian stretch image, wrote it to a new SD card, booted up the Pi, ssh’d in, expanded the filesystem, updated all packages to latest, and went thru the setup process. BTW, I love the new menu-based system – but the menu should include a way to get out to shell (if it does already, I apologize, but I did not see an option for that in it).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>After I did the node setup, and the pi rebooted, I’m getting odd errors from trying to start Asterisk. Here’s an entry from journalctl:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Apr 11 16:14:33 uhf.wi0la.org systemd[1]: asterisk.service: Job asterisk.service/start failed with result 'dependency'.<o:p></o:p></p><p class=MsoNormal>Apr 11 16:14:33 uhf.wi0la.org systemd[1]: dev-dahdi-pseudo.device: Job dev-dahdi-pseudo.device/start failed with result 'timeout'.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’m suspecting that the upgrade of the kernel I did on the first boot is making Dahdi not come up properly, so I’m trying a rebuild of Dahdi via:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>apt-get install --reinstall asl-dahdi-linux-dkms<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Don’t know if this will fix the problem or not – will know as soon as the process finishes. But isn’t DKMS supposed to handle this automatically?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Jeremy, NQ0M<o:p></o:p></p></div></body></html>