[arm-allstar] dmesg output

[Roger Coudé]

Don,
That seems a good trick.
I still had a few errors with the turbo mode enabled, but with the wifi and blue tooth turned down, as you suggested, I have no error reported yet on dmesg after 30 minutes, with a qso going on.
I am testing on 8 nodes at 3 locations that where reporting errors, and there are all quiet as never before, with yours and Doug suggestions both implemented.
There is only one place I use the wifi and it is a test radio in a private house, so no issue there.
Sometimes I resist asking too much questions, being myself quite busy with Radio Mobile, but today I am happy having asked Hi
73 to allRoger


      De : Don Backstrom - AA7AU via ARM-allstar <arm-allstar at hamvoip.org>
 À : Roger Coudé via ARM-allstar <arm-allstar at hamvoip.org> 
Cc : Don Backstrom - AA7AU <z-armallstar at deliberate.net>
 Envoyé le : vendredi 30 novembre 2018 13h31
 Objet : Re: [arm-allstar] dmesg output
   
On Fri 30-Nov-18 08:36, "Roger Coudé via ARM-allstar" wrote:
> If I use more than one PI at one location, I need an ethernet  hub, a new fan, and a second power supply in the box.
> We have many sites and using a single PI would be cost effective, we are talking about thousands of dollars.
> I have heatsink and fan everywhere, so the turbo mode is something I can try.
> The site that gives the more error messages is a running with a 3B+
> I will try with turbo mode.

    Roger:

    If you're going to push that PI3B/3B+ for max performance, I'd suggest 
that you might want to turn off the built-in Bluetooth:  Use menu #9 
(bash shell) and then edit the basic Pi start-up file with:
    nano /boot/config.txt
to insert the following additional line:
    dtoverlay=pi3-disable-bt

    This hopefully eliminates the power use for, and the stray RF from, 
that built-in (and on-by-default) BT radio. If one is not using their 
WiFi for connectivity in a PI3, you can add this line as well:
    dtoverlay=pi3-disable-wifi

    BTW: If you do so, make good note of this as I don't think that Doug's 
terrific little file-backup.sh routine addresses this boot startup 
control file.

    I do this for every PI3 I work on unless we are specifically using 
WiFi. There's enough stray RF around, why add to it? When we do want a 
second NIC connection on a PI3, we generally use a USB-ethernet adapter 
instead of WiFi - but that takes some editing down in the bowls of 
ArchLinux to run properly.

    Good luck with those UW cables (those backhoes get everywhere),

    - Don - AA7AU
_______________________________________________

ARM-allstar mailing list
ARM-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2/3 web page - http://hamvoip.org