{"id":18566827,"url":"https://github.com/morrownr/8821au-20210708","last_synced_at":"2025-05-15T00:08:13.882Z","repository":{"id":39618278,"uuid":"408464031","full_name":"morrownr/8821au-20210708","owner":"morrownr","description":"Linux Driver for USB WiFi Adapters that are based on the RTL8811AU and RTL8821AU Chipsets - v5.12.5.2","archived":false,"fork":false,"pushed_at":"2025-04-08T17:11:24.000Z","size":3549,"stargazers_count":882,"open_issues_count":49,"forks_count":137,"subscribers_count":21,"default_branch":"main","last_synced_at":"2025-04-13T22:39:18.489Z","etag":null,"topics":["aircrack-ng","debian","hostapd","kali-linux","linux-driver","linux-mint","raspberry-pi","realtek","rtl8811au","rtl8821au","ubuntu","usb","wifi","wireshark"],"latest_commit_sha":null,"homepage":"","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/morrownr.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":"supported-device-IDs","governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2021-09-20T13:56:25.000Z","updated_at":"2025-04-10T11:02:56.000Z","dependencies_parsed_at":"2023-02-06T05:31:22.147Z","dependency_job_id":"7c1ace3b-d090-4cc0-91b5-be914f33c86c","html_url":"https://github.com/morrownr/8821au-20210708","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/morrownr%2F8821au-20210708","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/morrownr%2F8821au-20210708/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/morrownr%2F8821au-20210708/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/morrownr%2F8821au-20210708/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/morrownr","download_url":"https://codeload.github.com/morrownr/8821au-20210708/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254249200,"owners_count":22039029,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["aircrack-ng","debian","hostapd","kali-linux","linux-driver","linux-mint","raspberry-pi","realtek","rtl8811au","rtl8821au","ubuntu","usb","wifi","wireshark"],"created_at":"2024-11-06T22:24:30.486Z","updated_at":"2025-05-15T00:08:08.859Z","avatar_url":"https://github.com/morrownr.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"## 8821au ( 8821au.ko ) :rocket:\n\nHot: An in-kernel driver for the rtl8821/11au chipsets has been merged\ninto kernels 6.13 and 6.14. Installing this driver will automatically\nblacklist the new in-kernel driver, which is part of the rtw88 series of\ndrivers. The new in-kernel driver is Linux Standards compliant\n(mac80211) and is a much better driver than this one. This driver will\nno longer get API related updates beyond kernel 6.14. Pull Requests are\nstill welcome. If you use a kernel prior to 6.14, it is possible use the\nnew standards compliant driver. See: https://github.com/lwfinger/rtw88\n\n## Linux Driver for USB WiFi Adapters that are based on the RTL8811AU and RTL8821AU Chipsets\n\n- v5.12.5.2 (Realtek) plus updates from the Linux community\n\nNote: Please read the file \"supported-device-IDs\" for information about\nhow to confirm that this is the correct driver for your adapter.\n\nNote: Posting this driver is not a recommendation for Linux users to buy\nUSB WiFi adapters based on the Realtek chipsets supported by this driver.\nRealtek out-of-kernel WiFi drivers, such as this one, are not Linux Wireless\nStandards compliant and appear to be designed to be used by skilled\nprogrammers producing products such as embedded systems. Users of desktop\nand server distros such as Ubuntu, Debian, Manjaro, Fedora, Raspberry Pi OS\nand other mainline desktop and server distros will likely find adapters that\nuse in-kernel drivers (Linux Wireless Standards compliant) to be more stable\nand much more trouble-free. The following links will provide more\ninformation:\n\n[USB WiFi adapters that are supported with Linux in-kernel drivers](https://github.com/morrownr/USB-WiFi/blob/main/home/USB_WiFi_Adapters_that_are_supported_with_Linux_in-kernel_drivers.md)\n\n[USB WiFi adapter information for Linux](https://github.com/morrownr/USB-WiFi/blob/main/home/USB_WiFi_Adapter_Information_for_Linux.md)\n\n### Supported Features\n\n- IEEE 802.11 b/g/n/ac WiFi compliant\n- 802.1x, WPA2 AES for PSK and TLS (Radius)\n- WPA3-SAE (Personal)\n- IEEE 802.11b/g/n/ac Client mode\n  * Supports wireless security for WPA2 AES PSK and WPA3-SAE\n  * Supports site survey scan and manual connect\n  * Supports TLS client\n- TDLS support\n- Power saving modes\n- hostapd compatible\n- AP mode DFS channel support\n- Supported interface modes\n  * Managed\n  * Monitor (see FAQ) (see [Monitor_Mode](https://github.com/morrownr/Monitor_Mode))\n  * AP (see [Bridged Wireless Access Point](https://github.com/morrownr/USB-WiFi/blob/main/home/AP_Mode/Bridged_Wireless_Access_Point.md))\n  * P2P-client\n  * P2P-GO\n- Log level control\n- LED control\n- Power saving control\n- VHT control (allows 80 MHz channel width in AP mode)\n- AP mode DFS channel control\n\n### A FAQ is available in this repo with the name `FAQ.md`\n\n- Please read the FAQ and this document before posting issues.\n\n### Additional documentation is in the file `8821au.conf`\n\n### Compatible CPU Architectures\n\n- x86, i386, i686\n- x86-64, amd64\n- armv6l, armv7l (arm)\n- aarch64 (arm64)\n\nNote: Additional CPU architectures may work but I currently only have\nthe hardware to test the above.\n\n### Compatible Kernels\n\n- Kernels: 5.4  - 5.11  (Realtek)\n- Kernels: 5.12 - 6.14  (community support)\n\nNote: Kernels earlier than 5.4 may work but are not tested or\nsupported.\n\n### Tested Compilers\n\n- gcc 12, 13 and 14\n\n### Tested Linux Distributions\n\nNote: The information in this section depends largely on user reports\nwhich can be provided via PR or message in Issues.\n\n- [Arch Linux](https://www.archlinux.org) (kernels 5.4, 5.11 and 6.6)\n\n- [Debian](https://www.debian.org/) (kernels 5.10, 5.15, 6.1 and 6.6)\n\n- [Fedora](https://getfedora.org) Fedora 38, 41 (kernel 6.11)\n\n- [Manjaro](https://manjaro.org) (kernel 5.15)\n\n- [openSUSE](https://www.opensuse.org/) Tumbleweed (rolling) (kernel 5.15)\n\n- [Raspberry Pi OS](https://www.raspberrypi.org) (2023-12-05)(ARM 32 bit and 64 bit)\n\n- [Raspberry Pi Desktop](https://www.raspberrypi.org) (2022-07-01) (x86 32 bit) (kernel 5.10)\n\n- [Ubuntu](https://www.ubuntu.com) 22.04 (kernel 5.15), 22.10 (kernel 5.19) (kernel 6.5) and 24.10 (kernel 6.11)\n\nNote: Red Hat Enterprise Linux (RHEL) and distros based on RHEL are\nsupported by Red Hat devs due to the way kernel patches are handled in\nRed Hat. I support knowledgable RHEL developers if they want to merge\nthe required support and keep it current. I reserve the right to delete\nthis support without notice if it causes any problems.\n\nCurrent RHEL maintainer: none\n\nNote: Android is supported in the driver according to Realtek. I will\nsupport knowledgable Android developers if they want to merge and keep\ncurrent the required support (most likely just instructions about how to\ncompile and maybe a modification or two to the Makefile).\n\nCurrent Android maintainer: none\n\nNote: OpenWRT is not supported. OpenWRT provides drivers for USB WiFi\nadapters. OpenWRT provided drivers include support for the MT7921au\n(AXE3000), MT7612u (AC1200), MT7610u (AC600) chipsets. It is a challenge\nto use Realtek based adapters that use out-of-kernel drivers with\nOpenWRT so it is strongly advised to use the already supported chipsets.\n\n### Compatible Devices\n\n* ALFA AWUS036ACS\n* Buffalo WI-U2-433DHP\n* Edimax EW-7811UTC\n* Edimax EW-7811UAC\n* Edimax EW-7811UCB\n* ELECOM WDC-433DU2H\n* GMYLE - AC450\n* Netgear A6100\n* Netis WF2180\n* Planex GW-450S\n* EDUP EP-1607\n* TP-Link Archer T2U nano\n* Numerous adapters that are based on the supported chipsets.\n\n### Installation Information\n\nWarning: It is recommended that you follow the installation instructions\nin the Installation Steps section. Avoid installation by downloading the\nzip file if at all possible. Support can only be provided, on a best\neffort basis, if the instructions in the Installation Steps section are\nfollowed.\n\nWarning: Installing multiple out-of-kernel drivers for the same hardware\nusually does not end well. The `install-driver.sh` script has the\ncapability to detect and remove most conflicting drivers but not all. If\nthis driver does not work well after installation and you have\npreviously installed a driver that you did not remove, it is suggested\nthat you run the following command in an effort to determine if you need\nto take action to manually remove conflicting drivers:\n\n```\nsudo dkms status\n```\n\nWarning: If you decide to do a distro upgrade, which will likely install\na new version of kernel such as 5.15 to 6.1, you need to update this\ndriver with the newest available code and then reinstall it before\nperforming the disto upgrade. Use the following commands in the driver\ndirectory:\n\n```\ngit pull\n```\n\n```\nsudo sh install-driver.sh\n```\n\nInternet access is required for initial installation. There are\nnumerous ways to enable temporary internet access depending on your\nhardware and situation. [One method is to use tethering from a phone.](https://www.makeuseof.com/tag/how-to-tether-your-smartphone-in-linux).\nAnother method is to keep a [WiFi adapter that uses an in-kernel driver](https://github.com/morrownr/USB-WiFi/blob/main/home/USB_WiFi_Adapters_that_are_supported_with_Linux_in-kernel_drivers.md) in your toolkit.\n\nYou will need to use the terminal interface. The quick way to open a\nterminal: Ctrl+Alt+T (hold down on the Ctrl and Alt keys then press the\nT key).\n\nAn alternative terminal is to use SSH (Secure Shell) from the same or from\nanother computer, in which case you will be in a suitable terminal after logging\nin, but this step requires that an SSH daemon/server has already been\nconfigured. (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/).)\n\nYou will need to have sufficient access rights to use `sudo` so that commands\ncan be executed as the `root` user. (If the command `sudo echo Yes` returns\n\"Yes\", with or without having to enter your password, you do have sufficient\naccess rights.)\n\nDKMS is used for the installation, if available. DKMS is a system utility\nwhich will automatically recompile and reinstall this driver when a new\nkernel is installed. DKMS is provided by and maintained by Dell.\n\nIt is recommended that you do not delete the driver directory after\ninstallation as the directory contains information and scripts that you\nmay need in the future.\n\nSecure Boot: see FAQ.\n\n### Installation Steps\n\nNote: The installation instructions are for the novice user. Experienced\nusers are welcome to alter the installation to meet their needs. Support\nwill be provided, on a best effort basis, based on the steps below.\nAnother way to word this paragraph is that if you do not follow the\nbelow steps for installation, you are your own tech support.\n\n#### Step 1: Open a terminal (e.g. Ctrl+Alt+T)\n\n#### Step 2: Update and upgrade system packages (select the option for the distro you are using)\n\nNote: If your Linux distro does not fall into one of options listed\nbelow, you will need to research how to `update` and `upgrade` your\nsystem packages.\n\n- Option for Debian based distributions such as Ubuntu, Kali, Armbian\nand Raspberry Pi OS\n\n```\nsudo apt update \u0026\u0026 sudo apt upgrade\n```\n\n- Option for Arch based distributions such as Manjaro\n\n```\nsudo pacman -Syu\n```\n\n- Option for Fedora based distributions\n\n```\nsudo dnf upgrade\n```\n\n- Option for openSUSE based distributions\n\n```\nsudo zypper update\n```\n\n- Option for Void Linux\n\n```\nsudo xbps-install -Syu\n```\n\nNote: It is recommended that you reboot your system at this point. The\nrest of the installation will appreciate having a fully up-to-date\nsystem to work with. The installation can then be continued with Step 3.\n\n```\nsudo reboot\n```\n\n#### Step 3: Install the required packages (select the option for the distro you are using)\n\nNote: If your Linux distro does not fall into one of options listed\nbelow, you will need to research how to properly setup up the development\nenvironment for your system. General guidance follows.\n\nDevelopment Environment Requirements: (package names may vary by distro)\n\n- Mandatory packages: `gcc` `make` `bc` `kernel-headers` `build-essential` `git`\n- Highly recommended packages: `dkms` `rfkill` `iw` `ip`\n- Mandatory packages if Secure Boot is active: `openssl` `sign-file` `mokutil`\n\nNote: The below options should take care of the mandatory and highly recommended\nrequirements. If Secure Boot is active on your system, please also install the\nmandatory packages for Secure Boot as shown above.\n\n- Option for Armbian (arm64)\n\n```\nsudo apt install -y build-essential\n```\n\n- Option for Raspberry Pi OS (arm/arm64)\n\n```\nsudo apt install -y raspberrypi-kernel-headers build-essential bc dkms git\n```\n\n- Option for Debian, Kali, and Raspberry Pi Desktop (x86)\n\n```\nsudo apt install -y linux-headers-$(uname -r) build-essential bc dkms git libelf-dev rfkill iw\n```\n\n- Option for Ubuntu (all official flavors) and the numerous Ubuntu based distros\n\n```\nsudo apt install -y build-essential dkms git iw\n```\n\n- Option for Fedora\n\nNote: Fedora users should also install `openssl` if secure boot is\nactive.\n\n```\nsudo dnf -y install git dkms kernel-devel\n```\n\n- Option for openSUSE\n\n```\nsudo zypper install -t pattern devel_kernel dkms\n```\n\n- Option for Alpine\n\n```\nsudo apk add linux-lts-dev make gcc\n```\n\n- Option for Void Linux\n\n```\nsudo xbps-install linux-headers dkms git make\n```\n\n- Options for Arch and Manjaro (if using Manjaro for RasPi4B, see note)\n\nIf using pacman\n\n```\nsudo pacman -S --noconfirm linux-headers dkms git bc iw\n```\n\nNote: The following is needed if using Manjaro for RasPi4B.\n\n```\nsudo pacman -S --noconfirm linux-rpi4-headers dkms git bc\n```\n\nNote: If you are asked to choose a provider, make sure to choose the one\nthat corresponds to your version of the linux kernel (for example,\n\"linux510-headers\" for Linux kernel version 5.10). If you install the\nincorrect version, you'll have to uninstall it and install the correct\nversion.\n\nIf using other methods, please follow the instructions provided by those\nmethods.\n\n#### Step 4: Create a directory to hold the downloaded driver\n\n```\nmkdir -p ~/src\n```\n\n#### Step 5: Move to the newly created directory\n\n```\ncd ~/src\n```\n\n#### Step 6: Download the driver\n\n```\ngit clone https://github.com/morrownr/8821au-20210708.git\n```\n\n#### Step 7: Move to the newly created driver directory\n\n```\ncd ~/src/8821au-20210708\n```\n\n#### Step 8: Run the installation script (`install-driver.sh`)\n\nImportant: The compilation may fail if the major version of gcc that is\nin use is not the same as the major version of gcc that was used to\ncompile the kernel that is in use:\n\nExample of bad situation:\n\n```\ngcc 12.1 (used to compile the kernel)\ngcc 10.3 (version of gcc in use)\n```\n\nExample of good situation:\n\n```\ngcc 12.2 (used to compile the kernel)\ngcc 12.1 (version of gcc in use)\n```\n\nTo determine the values:\n\n```\ncat /proc/version\n```\n\n```\ngcc --version\n```\n\nIf you find your system in a bad situation, it is recommended that you\ninstall a version of gcc that matches the major version of gcc that was\nused to compile your kernel. Here is an example for Ubuntu:\n\n```\nsudo apt install gcc-12\n```\n\nNote: If your system is a low memory system, it is recommended that you\nterminate running apps so as to provide the maximum amount of RAM to the\ncompilation process.\n\nNote: For automated builds (non-interactive), use `NoPrompt` as an\noption.\n\n```\nsudo ./install-driver.sh\n```\n\nor\n\n```\nsudo sh install-driver.sh\n```\n\nNote: If you elect to skip the reboot at the end of the installation\nscript, the driver may not load immediately and the driver options will\nnot be applied. Rebooting is strongly recommended.\n\nNote: Fedora users that have secure boot turned on may need to run the\nfollowing to enroll the key:\n\n```\nsudo mokutil --import /var/lib/dkms/mok.pub\n```\n\n### Manual Installation Instructions\n\nNote: The installation script, `install-driver.sh` , automates the\ninstallation process, however, if you want to or need to do a basic\ncommand line installation, use the following:\n\n```\nmake clean\n```\n\n```\nmake -j$(nproc)\n```\n\nIf secure boot is off:\n\n```\nsudo make install\n```\n\n```\nsudo reboot\n```\n\nIf secure boot is on:\n\nNote: Please read to the end of this section before coming back here to\nenter commands.\n\n```\nsudo make sign-install\n```\n\nNote: You will be prompted for a password, please remember the password\nas it will be used in some of the following steps.\n\n```\nsudo reboot\n```\n\nThe MOK managerment screen will appear during boot:\n\n`Shim UEFI Key Management`\n\n`Press any key...`\n\nSelect \"Enroll key\"\n\nSelect \"Continue\"\n\nSelect \"Yes\"\n\nWhen promted, enter the password you entered earlier.\n\nWarning: If you enter the wrong password, your computer will not be\nbootable. In this case, use the BOOT menu from your BIOS to boot then as\nfollows:\n\n```\nsudo mokutil --reset\n```\n\nRestart your computer. Use the BOOT menu from BIOS to boot. In the MOK\nmanagerment screen, select `reset MOK list`, then reboot and retry from\nthe above step `sudo make sign-install`.\n\nNote: If you use the Manual Installation Instructions, you will need to\nrepeat the installation process each time a new kernel is installed in\nyour distro.\n\n-----\n\n### Manual Removal Instructions\n\nTo remove the driver if installed by the Manual Installation\nInstructions:\n\n```\nsudo make uninstall\n```\n\n```\nsudo reboot\n```\n\nNote: If you use the manual installation instructions, or if dkms is not\ninstalled, you will need to repeat the process each time a new kernel is\ninstalled in your distro.\n\n-----\n\n### Driver Options (`edit-options.sh`)\n\nNote: In Linux, driver options are also called `module parameters` .\n\nA file called `8821au.conf` will be installed in `/etc/modprobe.d` by\ndefault if you use the installation script, `install-driver.sh`. If you\nare following the Manual Installation Instructions, you can use the\n`edit-options.sh` script to install and/or edit the file.\n\nNote: The installation script, `install-driver.sh`. will prompt you to\nedit the options.\n\n`8821au.conf` will be read and applied to the driver on each system boot.\n\nTo edit the driver options file, run the `edit-options.sh` script\n\n```\nsudo ./edit-options.sh\n```\n\nNote: Documentation for Driver Options is included in the file\n `8821au.conf`.\n\n-----\n\n### Upgrading the Driver\n\nNote: Linux development is continuous therefore work on this driver is\ncontinuous.\n\nNote: Upgrading the driver is advised in the following situations:\n\n- every 2-3 months\n- if a new or updated version of the driver needs to be installed\n- if a distro version upgrade is going to be installed (i.e. going from\nkernel 5.10 to kernel 5.15)\n\n#### Step 1: Open a terminal (e.g. Ctrl+Alt+T)\n\n#### Step 2: Move to the driver directory\n\n```\ncd ~/src/8821au-20210708\n```\n\n#### Step 3: Pull updated code from this repo\n\n```\ngit pull\n```\n\n#### Step 4: Reinstall the driver\n\nNote: The `install-driver.sh` script will automatically remove the\npreviously installed driver.\n\n```\nsudo ./install-driver.sh\n```\n\n-----\n### Removal of the Driver (`remove-driver.sh`)\n\nNote: Removing the driver is advised in the following situations:\n\n- if the driver is no longer needed\n\nNote: The following removes everything that has been installed, with the\nexception of the packages installed in Step 3 and the driver directory.\nThe driver directory can be deleted after running this script.\n\n#### Step 1: Open a terminal (e.g. Ctrl+Alt+T)\n\n#### Step 2: Move to the driver directory\n\n```\ncd ~/src/8821au-20210708\n```\n\n#### Step 3: Run the removal script\n\nNote: For automated builds (non-interactive), use `NoPrompt` as an\noption.\n\n```\nsudo ./remove-driver.sh\n```\n\n-----\n\n### Recommended WiFi Router/ Access Point Settings\n\nNote: These recommendations apply when using your adapter in managed\n(client) mode, not AP mode.\n\nNote: These are general recommendations, some of which may not apply to\nyour specific situation.\n\n- Security: Set WPA2-AES or WPA2/WPA3 mixed or WPA3. Do not set WPA2\nmixed mode or WPA or TKIP.\n\n- Channel width for 2.4 GHz: Set 20 MHz fixed width. Do not use 40 MHz\nor 20/40 automatic.\n\n- Channels for 2.4 GHz: Set channel 1 or 6 or 11 depending on the\ncongestion at your location. Do not set automatic channel selection. As\ntime passes, if you notice poor performance, recheck congestion and set\nchannel appropriately. The environment around you can and does change\nover time.\n\n- Mode for 2.4 GHz: For best performance, set \"N only\" if you no longer\nuse B or G capable devices.\n\n- Network names: Do not set the 2.4 GHz Network and the 5 GHz Network\nto the same name. Note: Unfortunately many routers come with both\nnetworks set to the same name. You need to be able to control which\nnetwork that is in use so changing the name of one of the networks is\nrecommended. Since many IoT devices use the 2.4 GHz network, it may be\nbetter to change the name of the 5 GHz network.\n\n- Channels for 5 GHz: Not all devices are capable of using DFS channels\n(I'm looking at you Roku.) It may be necessary to set a fixed channel in\nthe range of 36 to 48 or 149 to 165 in order for all of your devices to\nwork on 5 GHz. (For US, other countries may vary.)\n\n- Best location for the WiFi router/access point: Near center of\napartment or house, at least a couple of feet away from walls, in an\nelevated location. You may have to test to find the best location is\nin your environment.\n\n- Check congestion: There are apps available for smart phones that allow\nyou to get an idea of the congestion levels on WiFi channels. The apps\ngenerally go by the name of `WiFi Analyzer` or something similar.\n\nAfter making and saving changes, reboot the router.\n\n-----\n\n### Recommendations regarding USB\n\n- Moving your USB WiFi adapter to a different USB port has been known to\nfix a variety of problems.\n\n- If connecting your USB WiFi adapter to a desktop computer, use the USB\nports on the rear of the computer if you encounter any problems. Why?\nThe ports on the rear are directly connected to the motherboard which\nwill reduce problems with interference and disconnection. An extension\ncable can be helpful to position the adapter for best reception.\n\n- If your USB WiFi adapter is USB 3 capable and you want it to operate\nin USB3 mode, plug it into a USB 3 port.\n\n- Avoid USB 3.1 Gen 2 ports if possible as most currently available\nadapters have been tested with USB 3.1 Gen 1 (aka USB 3) and not with\nUSB 3.1 Gen 2.\n\n- If you use an extension cable and your adapter is USB 3 capable, the\ncable needs to be USB 3 capable (if not, you will be limited to USB 2\nspeeds).\n\n- Extention cables can be problematic. A way to check if the extension\ncable is the problem is to plug the adapter temporarily into a USB port\non the computer.\n\n- Some USB WiFi adapters require considerable electrical current and\npush the capabilities of the power available via USB port. One example\nis adapters that use the Realtek 8814au chipset. Using a powered\nmultiport USB extension can be a good idea in cases like this.\n\n-----\n\nTo Contribute:\n\n- Fork this repository.\n- Make your edits.\n- TEST THEM!\n- Create a pull request.\n\n-----\n\n#### [Go to Main Menu](https://github.com/morrownr/USB-WiFi)\n\n-----\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmorrownr%2F8821au-20210708","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmorrownr%2F8821au-20210708","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmorrownr%2F8821au-20210708/lists"}