update website docs

Author: robotastic

docs/CONFIGURE.md

@@ -26,7 +26,7 @@ make
 gdb trunk-recorder core
 ```
 
-6. *gdb* is a powerful debugging platform. However, all we need is a trace of the crash. After *gdb* has finished loading, type in `bt full` to get a trace. Copy all of the output from *gdb* into a new [GitHub Issue](https://github.com/robotastic/trunk-recorder/issues/new), along with as much information as possible on what maybe casuing the crash.
+6. *gdb* is a powerful debugging platform. However, all we need is a trace of the crash. After *gdb* has finished loading, type in `bt full` to get a trace. Copy all of the output from *gdb* into a new [GitHub Issue](https://github.com/robotastic/trunk-recorder/issues/new), along with as much information as possible on what maybe causing the crash.
 
 
 # How to Capture an IQ Sample

docs/DEBUG.md

@@ -6,13 +6,12 @@ sidebar_position: 2
 # Docker
 If you are not going to be modifying the source code, **a [Docker](https://www.docker.com/) based install is the easiest way to get started.** Images are published frequently to  [Docker Hub](https://hub.docker.com/r/robotastic/trunk-recorder). The images have GNURadio 3.8 and all other required dependencies built into it, so it should be ready to go and be a much faster solution than compiling. Images have been built for amd64 (amd64 is used by all modern Intel and AMD CPUs) and most popular flavors of ARM.
 
-To get started, create a directory and place your **config.json** file there and a **talkgroup.csv** file if you are using one. Refer to [Configuring Trunk Recorder](CONFIGURE.md) for instructions on how to create these files.
+To get started, create a directory and place your **config.json** file there and a **talkgroup.csv** file if you are using one. Refer to [Configuring Trunk Recorder](../CONFIGURE.md) for instructions on how to create these files.
 
 ```bash
 docker run -it \
-  --privileged -e TZ=$(cat /etc/timezone) --user "$(id -u):$(id -g)" \
+  --device "/dev/bus/usb:/dev/bus/usb:rwm" -e TZ=$(cat /etc/timezone) --user "$(id -u):$(id -g)" \
   -v $(pwd):/app \
-  -v /dev/bus/usb:/dev/bus/usb \
   -v /var/run/dbus:/var/run/dbus \
   -v /var/run/avahi-daemon/socket:/var/run/avahi-daemon/socket \
   robotastic/trunk-recorder:latest
@@ -21,15 +20,14 @@ docker run -it \
 To use it as part of a [Docker Compose](https://docs.docker.com/compose/) file:
 
 ```yaml
-version: '3'
 services:
   recorder:
     image: robotastic/trunk-recorder:latest
     container_name: trunk-recorder
     restart: always
-    privileged: true
+    devices:
+      - "/dev/bus/usb:/dev/bus/usb:rwm"
     volumes:
-      - /dev/bus/usb:/dev/bus/usb
       - /var/run/dbus:/var/run/dbus 
       - /var/run/avahi-daemon/socket:/var/run/avahi-daemon/socket
       - ./:/app

docs/Install/INSTALL-DOCKER.md

@@ -7,7 +7,7 @@ sidebar_position: 1
 
 This page covers installing Trunk Recorder on a Linux box. I test everything on Ubuntu, but other flavors of Linux are supported. Instructions are also included for Arch Linux.
 
-## Install Prerequistes
+## Install Prerequisites
 To get started, install all of the required packages. Instructions for different versions are below:
 
 
@@ -63,7 +63,7 @@ If you are using a HackRF:
 sudo apt install -y hackrf libhackrf-dev libhackrf0
 ```
 
-### Older Ubuntu Verions...
+### Older Ubuntu Versions...
 
 These instructions should work on Ubuntu 16.x to 17.x, including Debian 9 and 10. 
 
@@ -213,7 +213,7 @@ Now restart to make sure these drivers are not loaded.
 
 ## Configuring Trunk Recorder
 
-The next step is to [configure Trunk Recorder](CONFIGURE.md) for the system you are trying to capture.
+The next step is to [configure Trunk Recorder](../CONFIGURE.md) for the system you are trying to capture.
 
 ## Running trunk recorder. 
 

docs/Install/INSTALL-LINUX.md

@@ -5,7 +5,7 @@ sidebar_position: 3
 
 # Raspberry Pi / Debian
 
-Smaller radio systems can be covered using a Raspberry Pi. If you are interested in doing this, you should really get a Pi 4. It maybe possible to get things running on an older Pi, but you often get unexpect behavior and errors. A Pi 4 can handle 3-4 simulatanious recordings. Make sure you have a good power supply. Also pay attention to heat. If the Pi gets too hot, it will slow down. A good case or fan can help keep it going full tilt. You can also just run debian on a NUC or Miniform PC. These commands will work with a vaneilla debian install as well.
+Smaller radio systems can be covered using a Raspberry Pi. If you are interested in doing this, you should really get a Pi 4 or better yet, a Pi 5. It maybe possible to get things running on an older Pi, but you often get unexpect behavior and errors. A Pi 4 can handle 3-4 simultaneous recordings. Make sure you have a good power supply. Also pay attention to heat. If the Pi gets too hot, it will slow down. A good case or fan can help keep it going full tilt. 
 
 ## RaspberryOS (aka Raspbian)
 
@@ -84,7 +84,13 @@ sudo apt upgrade
 sudo apt -y install libssl-dev openssl curl git fdkaac sox libcurl3-gnutls libcurl4 libcurl4-openssl-dev gnuradio gnuradio-dev gr-osmosdr libhackrf-dev libuhd-dev cmake make build-essential libboost-all-dev libusb-1.0-0-dev libsndfile1-dev
 ```
 
-Configure RTL-SDRs to load correctly:
+- Remove xtra-dkms.
+DKMS is not needed on the Raspberry Pi platform, and just causes issues. The above command actually returns an error on Raspberry Pi OS. So we remove that module from our build so we do not get errors from subsaquent `apt` calls.
+```bash
+sudo apt remove xtrx-dkms
+```
+
+## Configure RTL-SDRs to load correctly:
 
 ```bash
 sudo wget https://raw.githubusercontent.com/osmocom/rtl-sdr/master/rtl-sdr.rules ~/rtl-sdr.rules
@@ -97,7 +103,55 @@ You will need to restart for the rules to take effect. Logging out and logging b
 sudo shutdown -r now
 ```
 
-Now go [Build](#build-trunk-recorder) Trunk Recorder!
+## Configuring the UHD for Ettus SDRs
+
+If you haven't setup UHD yet there are a few extra steps you need to take:
+
+Install the UHD drivers:
+
+```bash
+sudo apt-get install libuhd-dev uhd-host
+```
+
+Download the firmware images. The location of the downloader is different than the error message:
+
+```bash
+dpkg -L uhd-host | grep "downloader"
+```
+The run the downloader at the location identified, it should be something like this:
+
+```bash
+sudo python3 /usr/libexec/uhd/utils/uhd_images_downloader.py
+```
+
+Setup the udev rules so any user can access the USB, as documented [here](https://files.ettus.com/manual/page_transport.html#transport_usb_udev):
+
+```bash
+cd /usr/libexec/uhd/utils/
+sudo cp uhd-usrp.rules /etc/udev/rules.d/
+sudo udevadm control --reload-rules
+sudo udevadm trigger
+```
+
+## Building Trunk Recorder
+
+In order to keep your copy of the Trunk Recorder source code free of build artifacts created by the build process, it is suggested to create a separate "out-of-tree" build directory. We will use `trunk-build` as our build directory. We by default do this in our home directory (`~` - Is a shortcut back to home.).
+
+**Note:** Depending on the amount of RAM in your Raspberry Pi, it may be best to run `make -j1` (2GB), `make -j3` (4GB), and `make -j4` (8GB) in order to ensure that you do not run out of RAM, at the cost of making the compile process take longer. If you ran out of RAM the compile process will fail completely, so it can be an acceptable tradeoff.
+
+```bash
+cd ~
+mkdir trunk-build
+git clone https://github.com/robotastic/trunk-recorder.git
+cd trunk-build
+cmake ../trunk-recorder
+make -j1
+sudo make install
+```
+
+## Configuring Trunk Recorder
+
+The next step is to [configure Trunk Recorder](../CONFIGURE.md) for the system you are trying to capture.
 
 ***
 # Ubuntu 22.04 Server (64-bit support!)