summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--12.-Appendix.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/12.-Appendix.md b/12.-Appendix.md
index 6905f5e..d6fb932 100644
--- a/12.-Appendix.md
+++ b/12.-Appendix.md
@@ -2,7 +2,7 @@
![image](https://user-images.githubusercontent.com/78108016/170426967-eb46003d-9138-4961-9c8f-ea6085997632.png)
## Connecting to an Established WiFi Network
-If you are using either the Kraken DF or Kraken PR pre-made images on a fixed WiFi network, instead of using hotspots, then you will need to add your WiFi network details. To do so you will need to temporarily connect your Pi 4 to a monitor and keyboard or connect your Pi 4 using Ethernet and SSH into it.
+If you are using either the Kraken DF pre-made image on a fixed WiFi network, instead of using hotspots, then you will need to add your WiFi network details. To do so you will need to temporarily connect your Pi 4 to a monitor and keyboard or connect your Pi 4 using Ethernet and SSH into it.
The default login credentials for the terminal and SSH are krakenrf/krakensdr, port 22.
@@ -77,7 +77,7 @@ It is up to you the programmer to ensure that the inputs are valid. Entering inc
* Docker with ClearLinux
## Working but with major quirks
-* Odroid N2/+ - Note: You must use the **BOTTOM USB port that is closest to the DC power barrel jack**. All other USB ports do not work for high data rate devices on this machine. Also requires a high quality USB cable. On this device every ~12 hours there is some USB glitch resulting in sample mis-alignment. This results in the DOA/PR results going bad. If you have periodic recalibration turned ON (the default), it's not a huge deal, but you could be about 5 minutes with bad results.
+* Odroid N2/+ - Note: You must use the **BOTTOM USB port that is closest to the DC power barrel jack**. All other USB ports do not work for high data rate devices on this machine. Also requires a high quality USB cable. On this device every ~12 hours there is some USB glitch resulting in sample mis-alignment. This results in the DOA results going bad. If you have periodic recalibration turned ON (the default), it's not a huge deal, but you could be about 5 minutes with bad results.
## Not Working
* Tinkerboard - Unfortunately pure 32-bit ARM CPUs are not supported by Miniforge Conda.