secure boot docs and minor updates

README.md

@@ -38,12 +38,12 @@ confirm that this is the correct driver for your adapter.
 
 ### A FAQ is available at the end of this document.
 
-### Compatible CPUs
+### Compatible CPU Architectures
 
-- x86
+- x86, i686
-- x86-64 (amd64)
+- x86-64, amd64
-- arm    (armv7l)
+- armv7l (arm)
-- arm64  (aarch64)
+- aarch64 (arm64)
 
 ### Compatible Kernels
 
@@ -59,7 +59,7 @@ If you see information that needs to be updated, please report the
 updated information and if you do not see adequate support for
 items such as Installation Steps 2 and 3, and you know what updates 
 need to added or you can get that information, please provide it so that
-the Installation Steps can be improved.
+the installation steps can be improved.
 
 - Arch Linux (kernels 5.4 and 5.11)
 
@@ -81,6 +81,12 @@ the Installation Steps can be improved.
 
 - Void Linux (kernel 5.18)
 
+Note: Red Hat Enterprise Linux (RHEL) and distros based on RHEL are not
+supported due to the way kernel patches are handled.
+
+Note: Android is not supported due to the tremendous amount of changes
+that Google has made to the mainline Linux kernel.
+
 ### Download Locations for Tested Linux Distributions
 
 - [Arch Linux](https://www.archlinux.org)
@@ -165,17 +171,29 @@ DKMS is used for the installation. DKMS is a system utility which will
 automatically recompile and reinstall this driver when a new kernel is
 installed. DKMS is provided by and maintained by Dell.
 
-It is recommended that you do not delete the driver directory after installation
+It is recommended that you do not delete the driver directory after
-as the directory contains information and scripts that you may need in the future.
+installation as the directory contains information and scripts that you
+may need in the future.
 
-Secure mode: The primary installation script, `install-driver.sh`, will support
+Secure Boot: The primary installation script, `install-driver.sh`, will
-secure mode... if your distro supports the method dkms uses. I regularly test the
+automatically support secure boot... if your distro supports the method
-installation script on systems with secure mode on. It works very well on Ubuntu based
+dkms uses. I regularly test the installation script on systems with
-distros. Some distros, such as Raspberry Pi OS, do not support secure mode because the
+secure boot on. It works seemlessly on modern Ubuntu based distros as
-hardware they support does not support secure mode making it unnecessary. There are
+long as secure boot was set up properly during the installation of the
-distros that do not work with the support currently in use. If you install this driver
+operating system. Some distros, such as the Raspberry Pi OS, do not
-and, after a reboot, the driver is not working, you can go into the BIOS and temporarily
+support secure boot because the hardware they support does not support
-turn secure mode off to see if secure mode is the problem.
+secure boot making it unnecessary to attempt to support it. There are
+distros that may require additional steps to sign the driver for secure
+boot operation. Fedora is an example. In installation Step 3, note that
+`openssl` must be installed as Fedora does not install it by default.
+There will also be another step for Fedora after the main
+`install-driver.sh` script is completed. This will be explained in the
+instructions at the appropriate time. Overall, secure boot requires that
+`openssl` and `mokutil` be installed and that additional steps be
+performed if necessary. To test is secure boot is the problem:  If you
+install this driver and, after a reboot, the driver is not working, you
+can go into the BIOS and temporarily turn secure boot off to see if
+secure boot is the problem.
 
 ### Installation Steps
 
@@ -251,6 +269,8 @@ sudo apt install -y build-essential dkms git
 
 - Option for Fedora
 
+Note: Installing `openssl` is only necessary for secure boot support.
+
 ```
 sudo dnf -y install git dkms kernel-devel openssl
 ```
@@ -320,6 +340,11 @@ Note: If you elect to skip the reboot at the end of the installation
 script, the driver may not load immediately and the driver options will
 not be applied. Rebooting is strongly recommended.
 
+Fedora users that have secure boot turned on should run the following to
+enroll the key:
+
+$ sudo mokutil --import /var/lib/dkms/mok.pub
+
 Manual build instructions: The above script automates the installation
 process, however, if you want to or need to do a command line
 installation, use the following:

install-driver.sh

@@ -62,9 +62,9 @@ fi
 
 # information that helps with bug reports
 # kernel
-echo "Kernel=${KVER}"
+echo "Linux Kernel=${KVER}"
 # architecture - for ARM: aarch64 = 64 bit, armv7l = 32 bit
-echo "Architecture=${KARCH}"
+echo "CPU Architecture=${KARCH}"
 #getconf LONG_BIT (may be handy in the future)
 
 # blacklist the in-kernel module (driver) so that there is no conflict