<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Well,</p>
<p>we are all trying to help...</p>
<p>But the first thing outside of your checks, before any real
changes should be to protect the kernel and update/upgrade.</p>
<pre>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.
from:
<a class="moz-txt-link-freetext" href="http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ASL_1.01-20180228-armhf-raspbian-stretch-image.readme">http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ASL_1.01-20180228-armhf-raspbian-stretch-image.readme</a>
As I stated some time ago when I had similar issues, they stopped when I used that proc.
Will it work for you ???
...mike/kb8jnm
</pre>
<br>
<div class="moz-cite-prefix">On 7/12/2018 9:00 PM, Jim Aspinwall
No1PC wrote:<br>
</div>
<blockquote type="cite"
cite="mid:161013464.3198175.1531443653100@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div style="font-family:Helvetica Neue, Helvetica, Arial,
sans-serif;font-size:16px;">
<div>First, apologies for what ended up coming out as a rant
that 'got' to a few people. Not my intention... I tried to be
casual/conversational and that doesn't work in-type. As a
result I did get a different perspective on the history of
AllStar developments... :O<br>
<br>
<br>
*** Steve: thanks for the specific log locations... I'll
fetch and send them soonest. <br>
<br>
If there are common known errors and clues to "yup, bad
card..." or "check x.conf and y.conf for consistency of z
parameter" - I'm more than willing to start documenting log
tidbits, clues, etc. for the 'KB' effort. (when I designed
software I did ask the developers to spit out details once in
awhile so we knew when function X crapped out... "wow, you
know we can do that? CRAP!")<br>
<br>
In a production support realm, when you see a trend of 10...
20 similar issues, you start looking to how-to, KB, or
systematic remote fixes to relieve the support team of
production issues. As the back-end person pushing apps and
updates the last thing *I* want is end-user calls/e-mails for
the easy stuff... I have my own images, patches, packages and
deployments to work on and annoy the user base on "Patch
Tuesday"... the help desk knows better than to 'dox' me out to
the users... :O<br>
<br>
<br>
</div>
<div><br>
*** Mike, you asked: "<span></span>Could you state what the
'first few' commands are on 1st boot with your <span>new image
? ...mike/kb8jnm"<br>
<br>
What am I looking for? The boot process of course dumps a
ton of initialization info... <br>
<br>
What I type in? I go for "sudo asl-menu" <br>
<br>
<br>
<br>
</span></div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
App_rpt-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a>
<a class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
To unsubscribe from this list please visit <a class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> 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. </pre>
</blockquote>
<br>
</body>
</html>