Mirrors
/
ARDEN-documentation
mirror of https://github.com/aredn/documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Move wifi down to How-To 

Move wifi down tip to How-To guide.
This commit is contained in:
Steve Lewis KC0EUW 2020-02-23 08:01:34 -07:00 committed by Joe AE6XE
parent 249e0da301
commit 2336aef636
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
arednGettingStarted/downloading_firmware.rst
View File

@ -17,7 +17,7 @@ Once you have selected the correct firmware image for your device, click the lin
**Features Inherited from OpenWRT for New Architectures**
The latest AREDN |trade| firmware contains features which are inherited from the newest OpenWRT upstream release (19.07). The OpenWRT *Release Notes* describe these new features and can be found here: `OpenWRT 19.07 Release Notes <http://openwrt.org/releases/19.07/start>`_
One important change is the inclusion of a new *target* for the firmware, labelled "ath79", which is the successor to the existing "ar71xx" target. The OpenWRT team explains the new target here: `ath79 <http://openwrt.org/docs/techref/targets/ath79>`_. Their main goal is to bring the code into a form that will allow all devices to run a standard unpatched Linux kernel. This will greatly reduce the amount of customization required and will streamline the firmware build process.
One important change is the inclusion of a new *target* for the firmware, labelled "ath79", which is the successor to the existing "ar71xx" target. The OpenWRT team explains the new target here: `ath79 <http://openwrt.org/docs/techref/targets/ath79>`_. Their main goal is to bring the code into a form that will allow all devices to run a standard unpatched Linux kernel. This will greatly reduce the amount of customization required and will streamline the firmware development process.
You may notice that the AREDN |trade| firmware download page has one or both of these firmware versions for specific devices. Refer to the latest `firmware notes <http://downloads.arednmesh.org/snapshots/trunk/readme.md>`_ in order to ensure you have the correct firmware image for your specific device.

2
arednGettingStarted/installing_firmware.rst
View File

@ -229,8 +229,6 @@ my-computer:$ ssh -p 2222 root@192.168.1.1
~~~~~~~ after logging into the node as root (hsmm) ~~~~~~~
node:# sysupgrade -n /tmp/aredn-firmware-filename.bin
The steps above will usually work for operators struggling to install AREDN |trade| firmware on a *Mikrotik hAP ac lite* device. Recently another issue was described in the upstream OpenWRT code. The 5GHz 802.11ac wireless driver used only in the *hap ac lite* has a memory issue which can leave the device without sufficient memory to complete the firmware install. The AREDN |trade| development team advises that, if you can telnet or ssh to the node and type the command ``wifi down`` you can free the memory used by this driver. Then the firmware install from the command line or web interface should work as designed.
Additional questions and troubleshooting assistance can usually be obtained by creating a post on the AREDN |trade| `online forum <https://www.arednmesh.org/forum>`_, which has an active community of helpful and experienced operators.
Post-Install Steps

6
arednHow-toGuides/firmware_upgrade.rst
View File

@ -6,11 +6,13 @@ Upgrading an AREDN |trade| node is a straightforward process accomplished using
Here are some "best practice" tips to assist with the firmware upgrade process. These ensure that memory utilization is at its minimum on the node. The upgrade process can fail due to lack of memory, but such a failure will leave the node unchanged on its previous firmware version.
Before starting the firmware upgrade, it may be necessary to stop, disable, or uninstall Meshchat, hamchat, snmp, and any active tunnels. The goal of this step is to keep those processes from using RAM memory and to free as much RAM as possible before the upgrade. Rebooting the node will ensure that its RAM utilization is at a minimum.
Before starting the firmware upgrade, it may be necessary to stop, disable, or uninstall extra packages such as Meshchat, snmp, and tunneling. The goal of this step is to keep those processes from using RAM memory and to free as much RAM as possible before the upgrade. Rebooting the node will ensure that its RAM utilization is at a minimum.
You may also want to stop node programs or services that are not needed during the upgrade. For example, if you can telnet or ssh to the node and type the command ``wifi down`` you can free the memory used by this driver.
When using a web browser to perform an upgrade, be sure to clear the browser's cache to remove any cached pages remaining from your node's previous firmware version. A clear cache will help to eliminate confusion when displaying node data in the browser.
Use a stepped approach to firmware upgrades. For example, if your node is running version 3.16.1.0 you should probably upgrade to version 3.18.9.0 before attempting to apply a newer version.
Use a stepped approach to firmware upgrades. For example, if your node is running version 3.18.9.0 you should probably upgrade to version 3.19.3.0 before attempting to apply a newer version.
.. |trade| unicode:: U+00AE .. Registered Trademark SIGN