1
0
mirror of https://github.com/morrownr/8821cu-20210916.git synced 2024-12-22 14:26:30 +00:00

minor updates

This commit is contained in:
morrownr 2023-02-27 14:31:22 -06:00
parent e75a84e4c0
commit 8d3d61775c
2 changed files with 34 additions and 25 deletions

View File

@ -32,8 +32,8 @@ confirm that this is the correct driver for your adapter.
- AP mode DFS channel support - AP mode DFS channel support
- Supported interface modes - Supported interface modes
* Managed * Managed
* Monitor (see FAQ) (see [Monitor_Mode](https://github.com/morrownr/Monitor_Mode) * Monitor (see FAQ) (see [Monitor_Mode](https://github.com/morrownr/Monitor_Mode))
* AP * AP (see [Bridged Wireless Access Point](https://github.com/morrownr/USB-WiFi/blob/main/home/AP_Mode/Bridged_Wireless_Access_Point.md))
* P2P-client * P2P-client
* P2P-GO * P2P-GO
- Log level control - Log level control
@ -100,11 +100,12 @@ be provided via PR or message in Issues.
Note: Red Hat Enterprise Linux (RHEL) and distros based on RHEL are not Note: Red Hat Enterprise Linux (RHEL) and distros based on RHEL are not
supported due to the way kernel patches are handled. I will support supported due to the way kernel patches are handled. I will support
knowledgable RHEL developers if they want to merge the required knowledgable RHEL developers if they want to merge the required
support and keep it current. support and keep it current. I reserve the right to delete this support
if it causes any problems.
Note: Android is supported in the driver according to Realtek. I will support Note: Android is supported in the driver according to Realtek. I will support
knowledgable Android developers if they want to merge and keep current the knowledgable Android developers if they want to merge and keep current the
required support (most likely just instructions about how to compile and maybe required support (most likely just instructions about how to compile and make
a modification or two to the Makefile). a modification or two to the Makefile).
### Compatible Devices ### Compatible Devices
@ -133,22 +134,20 @@ driver on installation and reactivate the in-kernel driver on removal. No
special action needs to be taken by users. special action needs to be taken by users.
Warning: Installing multiple out-of-kernel drivers for the same hardware Warning: Installing multiple out-of-kernel drivers for the same hardware
usually does not end well. If a previous attempt to install this driver failed usually does not end well. The install-driver.sh script has the capability
or if you have previously installed another driver for chipsets supported by to detect and remove many conflicting drivers but not all. If this driver
this driver, you MUST remove anything that the previous attempt does not work well after installation and you have previously installed a
installed BEFORE attempting to install this driver. This driver can be driver that you did not remove, it suggested that you run the following
removed with the script called `./remove-driver.sh`. Information is command in an effort to determine if you need to take action to manually
available in the section called `Removal of the Driver`. You can get a remove conflicting drivers:
good idea as to whether you need to remove a previously installed
driver by running the following command:
``` ```
sudo dkms status sudo dkms status
``` ```
Warning: If you decide to upgrade to a new version of kernel such as Warning: If you decide to do a distro upgrade, which will likely install a
5.15 to 6.1, you need to upgrade the driver you have installed with new version of kernel such as 5.15 to 6.1, you need to upgrade this driver
the newest available before installing the new kernel. Use the with the newest available before performing the disto upgrade. Use the
following commands in the driver directory: following commands in the driver directory:
``` ```
@ -243,7 +242,7 @@ sudo reboot
Note: If your Linux distro does not fall into one of options listed Note: If your Linux distro does not fall into one of options listed
below, you will need to research how to properly setup up the development below, you will need to research how to properly setup up the development
environment for your system. General guidance is given the next paragraph. environment for your system. General guidance follows.
Development Environment Requirements: (package names may vary by distro) Development Environment Requirements: (package names may vary by distro)

View File

@ -370,7 +370,7 @@ fi
echo "Info: Upgrade this driver with the following commands as needed:" echo "Info: Upgrade this driver with the following commands as needed:"
echo "$ git pull" echo "$ git pull"
echo "$ sudo sh install-driver.sh" echo "$ sudo sh install-driver.sh"
echo "Note: Upgrades should be performed before distro upgrades." echo "Note: Upgrades to this driver should be performed before distro upgrades."
echo "Note: Upgrades can be performed as often as you like." echo "Note: Upgrades can be performed as often as you like."
echo "Note: Work on this driver is continuous." echo "Note: Work on this driver is continuous."
echo ": ---------------------------" echo ": ---------------------------"
@ -385,15 +385,25 @@ fi
# if NoPrompt is not used, ask user some questions # if NoPrompt is not used, ask user some questions
if [ $NO_PROMPT -ne 1 ]; then if [ $NO_PROMPT -ne 1 ]; then
printf "Do you want to edit the driver options file now? (y is recommended) [y/N] " printf "Do you want to edit the driver options file now? (recommended) [Y/n] "
read -r REPLY read -r yn
case "$REPLY" in case "$yn" in
[yY]*) ${TEXT_EDITOR} /etc/modprobe.d/${OPTIONS_FILE} ;; [nN])
;;
*)
${TEXT_EDITOR} /etc/modprobe.d/${OPTIONS_FILE}
;;
esac esac
printf "Do you want to apply the new options by rebooting now? ( y is recommended) [y/N] " printf "Do you want to apply the new options by rebooting now? (recommended) [Y/n] "
read -r REPLY read -r yn
case "$REPLY" in case "$yn" in
[yY]*) reboot ;; [nN])
;;
*)
reboot
;;
esac esac
fi fi