From d59ee49a352453696d05e81a9d7d46bc81e4362f Mon Sep 17 00:00:00 2001 From: morrownr Date: Sun, 19 Dec 2021 12:21:56 -0600 Subject: [PATCH] minor updates --- README.md | 61 +++++++++++++++++++++++++++---------------------- edit-options.sh | 1 - 2 files changed, 34 insertions(+), 28 deletions(-) diff --git a/README.md b/README.md index 3872831..4fc407b 100644 --- a/README.md +++ b/README.md @@ -8,12 +8,10 @@ ----- -#### Problem reports go in `Issues`. - -#### Problem reports should include the information obtained with the following command: +#### Problem reports go in `Issues`. Include the information obtained with: ``` -$ sudo uname -a; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev +sudo uname -a; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev ``` ----- @@ -22,8 +20,8 @@ $ sudo uname -a; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev ### Linux Driver for USB WiFi Adapters that are based on the RTL8812BU and RTL8822BU Chipsets -- v5.13.1 (Realtek) (20210702) -- Plus updates from the Linux community +- v5.13.1 (Realtek) (20210702) plus updates from the Linux community +- 1,132 clones over the 2 weeks ending on 20211218 ### Features @@ -44,8 +42,8 @@ $ sudo uname -a; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev - Supported interface modes * IBSS * Managed - * Monitor - * AP (see `Bridged_Wireless_Access_Point.md` in the `docs` folder.) + * Monitor (see `Monitor_Mode.md` in the `docs` folder.) + * AP (see `Bridged_Wireless_Access_Point.md` in the `docs` folder.) * P2P-client * P2P-GO * Concurrent (see `Concurrent_Mode.md` in the `docs` folder.) @@ -151,9 +149,9 @@ you have previously installed another driver for chipsets supported by this driver, you MUST remove anything that the previous attempt installed BEFORE attempting to install this driver. This driver can be removed with the script called `./remove-driver.sh`. Information is -available below the section called `Removal of the Driver.` You can get -a good idea as to whether you need to remove a previously installed -driver by running the following: +available in the section called `Removal of the Driver.` You can get a +good idea as to whether you need to remove a previously installed +driver by running the following command: ``` dkms status @@ -161,13 +159,13 @@ dkms status The installation instructions are for the novice user. Experienced users are welcome to alter the installation to meet their needs. -Temporary internet access is required for installation. There are numerous ways to enable temporary internet access depending on your hardware and situation. [One method is to use tethering from a phone.](https://www.makeuseof.com/tag/how-to-tether-your-smartphone-in-linux) Another method to enable temporary internet access is to keep a [WiFi adapter that uses an in-kernel driver](https://github.com/morrownr/USB-WiFi) in your toolkit. +Temporary internet access is required for installation. There are numerous ways to enable temporary internet access depending on your hardware and situation. [One method is to use tethering from a phone.](https://www.makeuseof.com/tag/how-to-tether-your-smartphone-in-linux) Another method is to keep a [WiFi adapter that uses an in-kernel driver](https://github.com/morrownr/USB-WiFi) in your toolkit. You will need to use the terminal interface. The quick way to open a terminal: Ctrl+Alt+T (hold down on the Ctrl and Alt keys then press the T key). An alternative terminal is to use SSH (Secure Shell) from the same or from another computer, in which case you will be in a suitable terminal after logging in, but this step requires that an SSH daemon/server has already been configured. (There are lots of SSH guides available, e.g., for the [Raspberry Pi](https://www.raspberrypi.com/documentation/computers/remote-access.html#setting-up-an-ssh-server) and for [Ubuntu](https://linuxconfig.org/ubuntu-20-04-ssh-server). Do not forget [to secure the SSH server](https://www.howtogeek.com/443156/the-best-ways-to-secure-your-ssh-server/).) -You will need to have sufficient access rights to use `sudo`, so that arbitrary commands can be executed as the `root` user. (If the command `sudo echo Yes` returns "Yes", with or without having to enter your password, you do have sufficient access rights.) +You will need to have sufficient access rights to use `sudo` so that commands can be executed as the `root` user. (If the command `sudo echo Yes` returns "Yes", with or without having to enter your password, you do have sufficient access rights.) 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. @@ -205,7 +203,10 @@ sudo dnf -y update sudo zypper update ``` -Note: If you do not regularly maintain your system by installing updated packages, it is a good idea to not only update system package information but also to install the updated packages followed by a system reboot. The installation can then be continued with step 3. +Note: If you do not regularly maintain your system by installing updated +packages, please do so now and then reboot. The rest of the installation +will appreciate having a fully up to date system to work with. The +installation can then be continued with Step 3. #### Step 3: Install the required packages (select the option for the OS you are using) @@ -241,18 +242,20 @@ sudo zypper install -t pattern devel_kernel dkms - Options for Arch and Manjaro -if using pacman +If using pacman ``` sudo pacman -S --noconfirm linux-headers dkms git ``` -Note: If you are asked to choose a provider, make sure to choose the one that -corresponds to your version of the linux kernel (for example, "linux510-headers" -for Linux kernel version 5.10). If you install the incorrect version, you'll have -to uninstall it and reinstall the correct version. +Note: If you are asked to choose a provider, make sure to choose the one +that corresponds to your version of the linux kernel (for example, +"linux510-headers" for Linux kernel version 5.10). If you install the +incorrect version, you'll have to uninstall it and install the correct +version. -If using other methods, please follow the instructions provided by those methods. +If using other methods, please follow the instructions provided by those +methods. #### Step 4: Create a directory to hold the downloaded driver @@ -278,19 +281,22 @@ git clone https://github.com/morrownr/88x2bu-20210702.git cd ~/src/88x2bu-20210702 ``` -#### Step 8: Enable Concurrent Mode ( cmode-on.sh ) (optional) +#### Step 8: (optional) Enable Concurrent Mode ( cmode-on.sh ) -Note: see `Concurrent_Mode.md` in the `docs` folder. +Note: see `Concurrent_Mode.md` in the `docs` folder to help determine +whether you want to enable Concurrent Mode. ``` ./cmode-on.sh ``` -#### Step 9: Run a script to reconfigure the driver for Raspberry Pi hardware +#### Step 9: Run a script to reconfigure for Raspberry Pi hardware -Warning: This step only applies if you are installing to Raspberry Pi *hardware*. +Warning: This step only applies if you are installing to Raspberry Pi +*hardware*. -Warning: You should skip this step if installing to x86 or amd64 based systems. +Warning: You should skip this step if installing to x86 or amd64 based +systems. - Option for the 32 bit Raspberry Pi OS to be installed to Raspberry Pi hardware @@ -331,7 +337,8 @@ not be applied. Rebooting is strongly recommended. ### Driver Options ( edit-options.sh ) -A file called `88x2bu.conf` will be installed in `/etc/modprobe.d` by default. +A file called `88x2bu.conf` will be installed in `/etc/modprobe.d` by +default. Note: The installation script will prompt you to edit the options. @@ -491,7 +498,7 @@ Answer: You can't without considerable technical skills. Realtek drivers do not Question: Why do you recommend Mediatek based adapters when you maintain this repo for a Realtek driver? -Answer: Many new Linux users already have adapters based on Realtek chipsets. This repo is for Linux users to support their existing adapters but my STRONG recommendation is for Linux users to seek out WiFi solutions based on Mediatek, Intel or Atheros chipsets and drivers. If users are looking at a USB solution, Mediatek and Atheros based adapters are the best solution. Realtek based USB adapters are not a good solution because Realtek does not follow Linux Wireless standards (mac80211) for USB WiFi adapters and the drivers are not maintained in the Linux kernel. These issues make Realtek drivers problematic in many ways. You have been WARNED. For more information about USB WiFi adapters: +Answer: Many new and existing Linux users already have adapters based on Realtek chipsets. This repo is for Linux users to support their existing adapters but my STRONG recommendation is for Linux users to seek out WiFi solutions based on Mediatek, Intel or Atheros chipsets and in-kernel drivers. If users are looking at a USB solution, Mediatek and Atheros based adapters are the best solution. Realtek based USB adapters are not a good solution because Realtek does not follow Linux Wireless standards (mac80211) for USB WiFi adapters and the drivers are not maintained in the Linux kernel. These issues make Realtek drivers problematic in many ways. You have been WARNED. For more information about USB WiFi adapters: https://github.com/morrownr/USB-WiFi diff --git a/edit-options.sh b/edit-options.sh index 295797d..0fd6f18 100755 --- a/edit-options.sh +++ b/edit-options.sh @@ -1,7 +1,6 @@ #!/bin/bash # OPTIONS_FILE="88x2bu.conf" - SCRIPT_NAME="edit-options.sh" # # Purpose: Make it easier to edit the driver options file.