Linux Driver for USB WiFi Adapters that are based on the RTL8811AU and RTL8821AU Chipsets

Overview
Click for USB WiFi Adapter Information for Linux

8821au ( 8821au.ko ) 🚀

Linux Driver for USB WiFi Adapters that are based on the RTL8811AU and RTL8821AU Chipsets

  • v5.12.5.2 (Realtek) (20210708)
  • Plus updates from the Linux community

Features

  • IEEE 802.11 b/g/n/ac WiFi compliant
  • 802.1x, WEP, WPA TKIP and WPA2 AES/Mixed mode for PSK and TLS (Radius)
  • IEEE 802.11b/g/n/ac Client mode
    • Supports wireless security for WEP, WPA TKIP and WPA2 AES PSK
    • Supports site survey scan and manual connect
  • Power saving modes
  • Packet injection
  • Supported interface modes
    • IBSS
    • Managed
    • AP
    • Monitor (see Monitor_Mode.md)
    • P2P-client
    • P2P-GO
  • Log level control
  • LED control
  • Power saving control
  • VHT control (allows 80 MHz channel width in AP mode)
  • SU Beamformee and MU Beamformee control
  • SU Beamformer control
  • DFS Channel support and control for AP mode

Note: WPA3-SAE support is in this driver, however, for it to work with current Linux distros, you will need to download, compile and install the current master of wpa_supplicant at the following site:

https://w1.fi/cgit/

If there is interest, I will consider making and posting a guide. I am very busy so if anyone is interested in making a guide/checklist, I will add it to the README.

Note: A FAQ is available at the end of this document.

Problem Reporting

Problem reports go in Issues.

Problem reports should include the information obtained with the following command:

$ sudo uname -a && mokutil --sb-state && lsusb && rfkill list all && dkms status && iw dev

Compatible CPUs

  • x86, amd64
  • ARM, ARM64

Compatible Kernels

  • Kernels: 4.15 - 5.11 (Realtek)
  • Kernels: 5.12 - 5.15 (community support)

Tested Linux Distributions

  • Arch Linux (kernels 5.4 and 5.11)

  • Fedora (kernel 5.11)

  • Debian 11 (kernels 5.10 and 5.15)

  • Kali Linux (kernel 5.10)

  • Linux Mint 20.2 (Linux Mint based on Ubuntu) (kernels 5.4 and 5.11)

  • LMDE 4 (Linux Mint based on Debian) (kernel 4.19)

  • Manjaro 20.1 (kernel 5.9) and 21.1 (kernel 5.13)

  • Raspberry Pi OS (2021-05-07) (ARM 32 bit) (kernel 5.10)

  • Raspberry Pi Desktop (x86 32 bit) (kernel 4.19)

  • Ubuntu 20.xx (kernels 5.4 and 5.8) and 21.xx (kernels 5.11 and 5.14)

Download Locations for Tested Linux Distributions

Tested Hardware

Compatible Devices

  • Alfa AWUS036ACS
  • Buffalo WI-U2-433DHP
  • Edimax EW-7811UTC
  • Edimax EW-7811UAC
  • Edimax EW-7811UCB
  • ELECOM WDC-433DU2H
  • GMYLE - AC450
  • Netgear A6100
  • Netis WF2180
  • Planex GW-450S
  • EDUP EP-1607
  • Numerous adapters that are based on the supported chipsets.

Note: Please read "supported-device-IDs" for information about how to confirm the correct driver for your adapter.

Installation Information

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. Another method to enable temporary internet access is to keep a WiFi adapter that uses an in-kernel driver 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 and for Ubuntu. Do not forget to secure the 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.)

DKMS is used for the installation. DKMS is a system utility which will automatically recompile and install 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 as the directory contains information and scripts that you may need in the future.

There is no need to disable Secure Mode to install this driver. If Secure Mode is properly setup on your system, this installation will support it.

Installation Steps

Step 1: Open a terminal (e.g.: Ctrl+Alt+T)

Step 2: Update system package information (select the option for the OS you are using)

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.

    Option for Debian based distributions such as Ubuntu, Linux Mint, Kali and Raspberry Pi OS

    $ sudo apt update
    Option for Arch based distributions such as Manjaro

    $ sudo pacman -Syu
    Option for Fedora based distributions

    # sudo dnf -y update

Step 3: Install the required packages (select the option for the OS you are using)

    Option for Raspberry Pi OS

    $ sudo apt install -y raspberrypi-kernel-headers bc build-essential dkms git
    Option for Debian, Kali or Linux Mint Debian Edition (LMDE)

    $ sudo apt install -y linux-headers-$(uname -r) build-essential dkms git libelf-dev
    Option for Ubuntu (all flavors) or Linux Mint

    $ sudo apt install -y dkms git build-essential
    Options for Arch or Manjaro

    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.

    If using other methods, please follow the instructions provided by those methods.
    Option for Fedora

    # sudo dnf -y install git dkms kernel-devel kernel-debug-devel

Step 4: Create a directory to hold the downloaded driver

$ mkdir -p ~/src

Step 5: Move to the newly created directory

$ cd ~/src

Step 6: Download the driver

$ git clone https://github.com/morrownr/8821au-20210708.git

Step 7: Move to the newly created driver directory

$ cd ~/src/8821au-20210708

Step 8: Only for Raspberry Pi systems

Warning: This step only applies if you are installing to Raspberry Pi hardware. You should skip this step if installing to x86 or amd64 based systems.

Run a preparation script

    Option for 32 bit operating systems to be installed to Raspberry Pi hardware

    $ ./raspi32.sh
    Option for 64 bit operating systems to be installed to Raspberry Pi hardware

    $ ./raspi64.sh

Step 9: Run the installation script (For automated builds, use NoPrompt as an option)

    $ sudo ./install-driver.sh

    Note: If you elect to skip the reboot at the end of the installation script,
    the driver may not be loaded immediately and the driver options will not be
    applied. Rebooting is strongly recommended.

Driver Options

A file called 8821au.conf will be installed in /etc/modprobe.d by default.

Note: Step 9 of the installation script will prompt you to edit the options before rebooting.

Location: /etc/modprobe.d/8821au.conf

This file will be read and applied to the driver on each system boot.

To edit the driver options file, run the edit-options.sh script.

$ sudo ./edit-options.sh

Note: Documentation for Driver Options is included in the file 8821au.conf.

Removal of the Driver

Note: This script should be used in the following situations:

  • the driver is no longer needed
  • a fresh start with default settings is needed
  • a new version of the driver needs to be installed
  • a major operating system upgrade is going to be applied

Note: This script removes everything that has been installed, with the exception of the packages installed in Step 3 and the driver directory. The driver directory can and probably should be deleted in most cases after running the script.

Step 1: Open a terminal (e.g.: Ctrl+Alt+T)

Step 2: Move to the driver directory

$ cd ~/src/8821au-20210708

Step 3: Run the removal script

$ sudo ./remove-driver.sh

Recommended WiFi Router/ Access Point Settings

Note: These are general recommendations, some of which may not apply to your specific situation.

Security: Set WPA2-AES. Do not set WPA2 mixed mode or WPA or TKIP.

Channel width for 2.4 GHz: Set 20 MHz fixed width. Do not use 40 MHz or 20/40 automatic.

Channels for 2.4 GHz: Set channel 1 or 6 or 11 depending on the congestion at your location. Do not set automatic channel selection. As time passes, if you notice poor performance, recheck congestion and set channel appropriately. The environment around you can and does change over time.

Mode for 2.4 GHz: For best performance, set "N only" if you no longer use B or G capable devices.

Network names: Do not set the 2.4 GHz Network and the 5 GHz Network to the same name. Note: Unfortunately many routers come with both networks set to the same name. You need to be able to control which network that is in use.

Channels for 5 GHz: Not all devices are capable of using DFS channels (I'm looking at you Roku.) It may be necessary to set a fixed channel in the range of 36 to 48 or 149 to 161 in order for all of your devices to work on 5 GHz. (For US, other countries may vary.)

Best location for the WiFi router/access point: Near center of apartment or house, at least a couple of feet away from walls, in an elevated location. You may have to test to see what the best location is in your environment.

Check congestion: There are apps available for smart phones that allow you to check the congestion levels on WiFi channels. The apps generally go by the name of WiFi Analyzer or something similar.

After making and saving changes, reboot the router.

Set regulatory domain to correct setting in OS

Check the current setting

$ sudo iw reg get

If you get 00, that is the default and may not provide optimal performance.

Find the correct setting here: http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2

Set it temporarily

$ sudo iw reg set US

Note: Substitute your country code if you are not in the United States.

Set it permanently

$ sudo nano /etc/default/crda

Change the last line to read:

REGDOMAIN=US

Recommendations regarding USB

  • Moving your USB WiFi adapter to a different USB port has been known to fix a variety of problems. Problems include WiFi going on and off as well as connections coming and going.

  • If connecting your USB WiFi adapter to a desktop computer, use the USB ports on the rear of the computer. Why? The ports on the rear are directly connected to the motherboard which will reduce problems with interference and disconnection that can happen with front ports that use cables.

  • If your USB WiFi adapter is USB 3 capable then plug it into a USB 3 port.

  • Avoid USB 3.1 Gen 2 ports if possible as almost all currently available adapters have been tested with USB 3.1 Gen 1 (aka USB 3) and not with USB 3.1 Gen 2.

  • If you use an extension cable and your adapter is USB 3 capable, the cable needs to be USB 3 capable (if not, you will at best be limited to USB 2 speeds).

  • Some USB WiFi adapters require considerable electrical current and push the capabilities of the power available via USB port. One example is devices that use the Realtek 8814au chipset. Using a powered multiport USB extension can be a good idea in cases like this.

How to disable onboard WiFi on Raspberry Pi 3B, 3B+, 3A+, 4B and Zero W

Add the following line to /boot/config.txt

dtoverlay=disable-wifi

How to disable WiFi on most systems

The rfkill utility can disable WiFi and Bluetooth (internal or external) on several systems, including but not limited to the Raspberry Pi.

How to forget a saved WiFi network on a Raspberry Pi

  1. Edit wpa_supplicant.conf
$ sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
  1. Delete the relevant WiFi network block (including the 'network=' and opening/closing braces.

  2. Press ctrl-x followed by 'y' and enter to save the file.

  3. Reboot


FAQ:

Question: What interface combinations does this driver support?

Answer: None. Realtek out-of-kernel drivers, including this driver, do not support interface combinations. If you need support for interface combinations, I suggest adapters based on the Mediatek chipsets.

Question: What extended features does this driver support?

Answer: None. For extended features, you need an adapter that uses Mediatek or Atheros drivers.

Question: I bought two rtl8811au based adapters and am planning to run one of them as an AP and another as a WiFi client. How do I set that up?

Answer: You can't. Realtek drivers do not support more than one adapter with the same chipset in the same computer. However, testing has shown that the Mediatek drivers do support more than one adapter with the same chipset in the same computer.

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 for USB WiFi adapters. Realtek drivers are problematic in many ways. You have been WARNED. For information about USB WiFi adapters:

https://github.com/morrownr/USB-WiFi


Issues
  • (in-progress) Some differences between this driver and the older repo

    (in-progress) Some differences between this driver and the older repo

    This issue is related to the following issue in the older repo: https://github.com/morrownr/8821au/issues/19

    I installed the newer driver and tried again: dkms status reported rtl8821au, 5.12.5.2, 5.11.0-36-generic, x86_64: installed

    The good:

    • This driver is functional for both wpa_supplicant and hostapd, on the system described in the above link.
    • When using this driver in the client mode (wpa_supplicant) to connect to an external AP, connection can be established (and according to tcpdump -i RTL8811AU_DONGLE_INTERFACE while issuing ping -c 20 -f -I RTL8811AU_DONGLE_INTERFACE AP_ADDRESS, ping traffic works. (Still an ethernet cable connected, so not performance-tested, but this is a step I could not get to work with the older driver at all.)
    • When using this driver in the AP mode (hostapd), it still works more or less as before.

    The bad:

    Some minor problems were detected:

    • For some reason, wpa_supplicant seems to be not quite compatible with this driver, since I never got wpa_cli -i RTL8811AU_DONGLE_INTERFACE to work. The error was "Could not connect to wpa_supplicant: RTL8811AU_DONGLE_INTERFACE - re-trying". (I do not think the older driver worked here either, but am not 100% sure I tested it.)
    • When starting wpa_supplicant, there is still the same error in dmesg, or according to journalctl: "wpa_supplicant[851254]: nl80211: kernel reports: Authentication algorithm number required". But it seems to work (see above), so this must be minor.
    • Incorrect, see below: Despite rtw_drv_log_level=0 in /etc/modprobe.d/8821au.conf, The dmesg log is severely spammed (2-3 seconds between each) by messages such as "[191259.082604] RTW: rtl8812_sreset_xmit_status_check REG_TXDMA_STATUS:0x00000401" during normal operation. Note that it says 8812, not 8811 (which matches my chipset) or 8821 (which is the name of this driver).
    • Incorrect, see below: Despite rtw_drv_log_level=0 in /etc/modprobe.d/8821au.conf, during start of either wpa_supplicant or hostapd, it seems every step of the setup process is logged there too, with "RTW" as a prefix in dmesg.
    • The default output power in the AP mode, as reported by e.g. iw phy#2 channels, was not higher than +13 dBm in any of the 5 GHz channels, which is lower than the older driver reported. The older driver supported up to +31 dBm for some (not all) of the 5 GHz channels.

    The last issue above is annoying, but not really a stopper, since a command such as this can be used to increase the output power if needed: iw phy#2 set txpower fixed 2000 Note that higher output power is not always better, but that is a completely separate discussion

    opened by Pajkastare 27
  • I have error, please, help me

    I have error, please, help me

    [email protected]:~/src> sudo zypper install git dkms kernel-headers
    Загрузка данных о репозиториях...
    Чтение установленных пакетов...
    "git" уже установлен.
    Нет кандидатов на обновление "git-2.34.1-1.1.x86_64". Самая последняя версия уже установлена.
    "dkms" уже установлен.
    Нет кандидатов на обновление "dkms-2.6.1-2.8.noarch". Самая последняя версия уже установлена.
    Строка "kernel-headers" не найдена в именах пакетов. Пробуем возможности.
    "linux-glibc-devel", предоставляющий "kernel-headers", уже установлен.
    Разрешение зависимостей пакетов...
    Нечего выполнять.
    [email protected]:~/src> mkdir -p ~/src
    [email protected]:~/src> cd ~/src
    [email protected]:~/src> git clone https://github.com/morrownr/8821au-20210708.git
    Клонирование в «8821au-20210708»…
    remote: Enumerating objects: 1046, done.
    remote: Counting objects: 100% (1046/1046), done.
    remote: Compressing objects: 100% (713/713), done.
    remote: Total 1046 (delta 475), reused 887 (delta 329), pack-reused 0
    Получение объектов: 100% (1046/1046), 3.07 МиБ | 135.00 КиБ/с, готово.
    Определение изменений: 100% (475/475), готово.
    [email protected]:~/src> cd ~/src/8821au-20210708
    [email protected]:~/src/8821au-20210708> sudo ./install-driver.sh
    
    
    
    Running install-driver.sh version 20211002
    Starting installation...
    Copying source files to: /usr/src/rtl8821au-5.12.5.2
    Copying 8821au.conf to: /etc/modprobe.d
    
    Creating symlink /var/lib/dkms/rtl8821au/5.12.5.2/source ->
                     /usr/src/rtl8821au-5.12.5.2
    
    DKMS: add completed.
    Error! echo
    Your kernel headers for kernel 5.15.3-1-default cannot be found at
    /lib/modules/5.15.3-1-default/build or /lib/modules/5.15.3-1-default/source.
    An error occurred. dkms build error = 1
    Please report this error.
    [email protected]:~/src/8821au-20210708> 
    
    
    opened by KirMozor 12
  • Hostapd: Invalid/unknown driver '8821au'

    Hostapd: Invalid/unknown driver '8821au'

    After installing the driver on my Raspberry Pi 4, attempting to get an AP working I run into this error in journalctl -xe

    Nov 10 05:53:44 raspberrypi hostapd[943]: Line 2: invalid/unknown driver '8821au'
    Nov 10 05:53:44 raspberrypi hostapd[943]: 1 errors found in configuration file '/etc/hostapd/hosta>
    Nov 10 05:53:44 raspberrypi hostapd[943]: Failed to set up interface with /etc/hostapd/hostapd.conf
    Nov 10 05:53:44 raspberrypi hostapd[943]: Failed to initialize interface
    Nov 10 05:53:44 raspberrypi systemd[1]: hostapd.service: Control process exited, code=exited, stat>
    Subject: Unit process exited
    Defined-By: systemd
    Support: https://www.debian.org/support
    
    An ExecStart= process belonging to unit hostapd.service has exited.
     
    The process' exit code is 'exited' and its exit status is 1.
    Nov 10 05:53:44 raspberrypi systemd[1]: hostapd.service: Failed with result 'exit-code'.
    Subject: Unit failed
    Defined-By: systemd
    Support: https://www.debian.org/support
    
    The unit hostapd.service has entered the 'failed' state with result 'exit-code'.
    Nov 10 05:53:44 raspberrypi systemd[1]: Failed to start Access point and authentication server for>
    ░░ Subject: A start job for unit hostapd.service has failed
    Defined-By: systemd
    Support: https://www.debian.org/support
    
    A start job for unit hostapd.service has finished with a failure.
    
    The job identifier is 6231 and the job result is failed.
    
    opened by GreenglassT 12
  • Driver doesn't pick up usb wifi adapter

    Driver doesn't pick up usb wifi adapter

    I bought this USB wifi adapter to use with my Raspberry Pi 3 and installed your driver and rebooted, but the adapter is still showing up as unclaimed in lshw:

            *-usb:1 UNCLAIMED
                 description: Generic USB device
                 product: 802.11ac NIC
                 vendor: Realtek
                 physical id: 5
                 bus info: [email protected]:1.5
                 version: 2.00
                 serial: 123456
                 capabilities: usb-2.00
                 configuration: maxpower=500mA speed=480Mbit/s
    

    Any ideas?

    opened by UntouchedWagons 11
  • How to install your driver in Solus Linux?

    How to install your driver in Solus Linux?

    Hello, I wanted to install your driver on Solus Linux, but there is a problem: DKMS was cut by the creators of the distribution: Quick How then to install the driver?

    [email protected] ~/tools/8821au-20210708 $ sudo uname -a; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev
    Пароль: 
    Попробуйте ещё раз.
    Пароль: 
    Linux kirmozor 5.13.1-187.current #1 SMP PREEMPT Wed Jul 7 19:52:26 UTC 2021 x86_64 GNU/Linux
    bash: mokutil: команда не найдена
    Bus 001 Device 002: ID 2357:011e TP-Link AC600 wireless Realtek RTL8811AU [Archer T2U Nano]
    Bus 001 Device 007: ID 0e8d:2005 MediaTek Inc. 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 005 Device 002: ID 0458:0186 KYE Systems Corp. (Mouse Systems) Genius DX-120 Mouse
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 003: ID 046d:c21d Logitech, Inc. F310 Gamepad [XInput Mode]
    Bus 004 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    bash: dkms: команда не найдена
    bash: iw: команда не найдена
    
    opened by KirMozor 11
  • (conversation) Tune Raspberry Pi AP to Top Performance

    (conversation) Tune Raspberry Pi AP to Top Performance

    Alright! I'm ready to get this AP as efficient as possible if you're up for it still.

    IP: Spectrum (sadly) Devices Connected: iPhone X, M1 MacBook Air, Motorola Z4

    What is everything else you need to know?

    opened by GreenglassT 11
  • (solved) Problems with A6100 on RPI4 64 bit

    (solved) Problems with A6100 on RPI4 64 bit

    Hi, I am tinkering with a RPI4 and a A6100, but as soon as I plug in the A6100 things go downhill :-| - Basically any iw and uname command as requested for the issue report cause cause some lockup as seen in the syslog dump below. Anyone have experience with this kind of behavior? Is it my kernel version that is unsupported - Any tips for debugging?

    I am using wlan0 for connecting to wlan - So I would like to keep that enabled and then use the A6100 for testing.

    Info before plugging in:

    Linux pi4hyper 5.15.32-v8+ #1538 SMP PREEMPT Thu Mar 31 19:40:39 BST 2022 aarch64 GNU/Linux
    EFI variables are not supported on this system
    Bus 002 Device 002: ID 152d:0562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 3151:3000 YICHIP Wireless Device
    Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    0: phy0: Wireless LAN
    	Soft blocked: no
    	Hard blocked: no
    1: hci0: Bluetooth
    	Soft blocked: no
    	Hard blocked: no
    rtl8821au, 5.12.5.2, 5.15.32-v8+, aarch64: installed
    phy#0
    	Unnamed/non-netdev interface
    		wdev 0x2
    		addr de:a6:32:18:5d:4e
    		type P2P-device
    		txpower 31.00 dBm
    	Interface wlan0
    		ifindex 3
    		wdev 0x1
    		addr dc:a6:32:18:5d:4e
    		ssid billebib
    		type managed
    		channel 100 (5500 MHz), width: 80 MHz, center1: 5530 MHz
    		txpower 31.00 dBm
    

    Log when plugging in the A6100:

    Bus 002 Device 002: ID 152d:0562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 3151:3000 YICHIP Wireless Device
    Bus 001 Device 004: ID 0846:9052 NetGear, Inc. A6100 AC600 DB Wireless Adapter [Realtek RTL8811AU]
    Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    0: phy0: Wireless LAN
    	Soft blocked: no
    	Hard blocked: no
    1: hci0: Bluetooth
    	Soft blocked: no
    	Hard blocked: no
    2: phy1: Wireless LAN
    	Soft blocked: no
    	Hard blocked: no
    rtl8821au, 5.12.5.2, 5.15.32-v8+, aarch64: installed
    

    syslog:

    
    Apr 10 21:11:12 pi4hyper PackageKit: daemon start
    Apr 10 21:11:12 pi4hyper dbus-daemon[373]: [system] Successfully activated service 'org.freedesktop.PackageKit'
    Apr 10 21:11:12 pi4hyper systemd[1]: Started PackageKit Daemon.
    Apr 10 21:11:16 pi4hyper PackageKit: refresh-cache transaction /133_bccaabac from uid 1000 finished with success after 3573ms
    Apr 10 21:11:17 pi4hyper dhcpcd[484]: wlan0: no IPv6 Routers available
    Apr 10 21:11:20 pi4hyper kernel: [   31.710836] cam-dummy-reg: disabling
    Apr 10 21:11:22 pi4hyper PackageKit: get-updates transaction /134_dccbaabc from uid 1000 finished with success after 5761ms
    Apr 10 21:11:26 pi4hyper systemd[1]: systemd-fsckd.service: Succeeded.
    Apr 10 21:11:36 pi4hyper systemd[1]: systemd-hostnamed.service: Succeeded.
    Apr 10 21:17:01 pi4hyper CRON[1641]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Apr 10 21:22:39 pi4hyper kernel: [  711.185171] usb 1-1.3: new high-speed USB device number 4 using xhci_hcd
    Apr 10 21:22:39 pi4hyper kernel: [  711.289837] usb 1-1.3: New USB device found, idVendor=0846, idProduct=9052, bcdDevice= 2.00
    Apr 10 21:22:39 pi4hyper kernel: [  711.289869] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    Apr 10 21:22:39 pi4hyper kernel: [  711.289882] usb 1-1.3: Product: 802.11ac WLAN Adapter 
    Apr 10 21:22:39 pi4hyper kernel: [  711.289894] usb 1-1.3: Manufacturer: Realtek 
    Apr 10 21:22:39 pi4hyper kernel: [  711.289904] usb 1-1.3: SerialNumber: 00e04c000001
    Apr 10 21:22:39 pi4hyper mtp-probe: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3"
    Apr 10 21:22:39 pi4hyper mtp-probe: bus: 1, device: 4 was not an MTP device
    Apr 10 21:22:39 pi4hyper kernel: [  711.358293] 8821au: loading out-of-tree module taints kernel.
    Apr 10 21:22:39 pi4hyper kernel: [  711.390273] RTW: module init start
    Apr 10 21:22:39 pi4hyper kernel: [  711.390299] RTW: rtl8821au v5.12.5.2-0-g70054197b.20210708_COEX20190509-6d6f
    Apr 10 21:22:39 pi4hyper kernel: [  711.390307] RTW: rtl8821au BT-Coex version = COEX20190509-6d6f
    Apr 10 21:22:39 pi4hyper kernel: [  711.475969] RTW: HW EFUSE
    Apr 10 21:22:39 pi4hyper kernel: [  711.475998] RTW: 0x000: 29 81 00 7C  01 00 01 00  4C 00 04 00  10 00 00 00  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476081] RTW: 0x010: 31 31 31 31  31 35 35 35  35 35 35 02  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476146] RTW: 0x020: FF FF 23 22  21 20 20 1E  1B 1A 1A 1B  1A 19 18 17  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476212] RTW: 0x030: 02 FF FF FF  FF FF 02 FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476276] RTW: 0x040: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476341] RTW: 0x050: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476406] RTW: 0x060: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476470] RTW: 0x070: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476535] RTW: 0x080: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476599] RTW: 0x090: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476664] RTW: 0x0A0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476729] RTW: 0x0B0: FF FF FF FF  FF FF FF FF  7F 23 20 00  01 00 FF 08  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476793] RTW: 0x0C0: FF 08 00 FF  00 00 00 55  00 FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476858] RTW: 0x0D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476923] RTW: 0x0E0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.476987] RTW: 0x0F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477052] RTW: 0x100: 46 08 52 90  FF FF 03 44  A5 6E 53 0F  4C 0A 03 52  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477116] RTW: 0x110: 65 61 6C 74  65 6B 20 18  03 38 30 32  2E 31 31 61  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477248] RTW: 0x120: 63 20 57 4C  41 4E 20 41  64 61 70 74  65 72 20 00  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477313] RTW: 0x130: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477378] RTW: 0x140: FF FF FF FF  FF FF FF 0F  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477442] RTW: 0x150: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477726] RTW: 0x160: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477792] RTW: 0x170: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477857] RTW: 0x180: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477922] RTW: 0x190: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.477986] RTW: 0x1A0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.478051] RTW: 0x1B0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.478115] RTW: 0x1C0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.478180] RTW: 0x1D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.478244] RTW: 0x1E0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.478309] RTW: 0x1F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
    Apr 10 21:22:39 pi4hyper kernel: [  711.478466] RTW: hal_com_config_channel_plan chplan:0x7F
    Apr 10 21:22:39 pi4hyper kernel: [  711.479353] RTW: [RF_PATH] ver_id.RF_TYPE:RF_1T1R
    Apr 10 21:22:39 pi4hyper kernel: [  711.479361] RTW: [RF_PATH] HALSPEC's rf_reg_trx_path_bmp:0x11, rf_reg_path_avail_num:1, max_tx_cnt:1
    Apr 10 21:22:39 pi4hyper kernel: [  711.479367] RTW: [RF_PATH] PG's trx_path_bmp:0x00, max_tx_cnt:0
    Apr 10 21:22:39 pi4hyper kernel: [  711.479372] RTW: [RF_PATH] Registry's trx_path_bmp:0x00, tx_path_lmt:0, rx_path_lmt:0
    Apr 10 21:22:39 pi4hyper kernel: [  711.479377] RTW: [RF_PATH] HALDATA's trx_path_bmp:0x11, max_tx_cnt:1
    Apr 10 21:22:39 pi4hyper kernel: [  711.479381] RTW: [RF_PATH] HALDATA's rf_type:RF_1T1R, NumTotalRFPath:1
    Apr 10 21:22:39 pi4hyper kernel: [  711.479387] RTW: [TRX_Nss] HALSPEC - tx_nss:1, rx_nss:1
    Apr 10 21:22:39 pi4hyper kernel: [  711.479392] RTW: [TRX_Nss] Registry - tx_nss:0, rx_nss:0
    Apr 10 21:22:39 pi4hyper kernel: [  711.479397] RTW: [TRX_Nss] HALDATA - tx_nss:1, rx_nss:1
    Apr 10 21:22:39 pi4hyper kernel: [  711.479403] RTW: txpath=0x1, rxpath=0x1
    Apr 10 21:22:39 pi4hyper kernel: [  711.479408] RTW: txpath_1ss:0x1, num:1
    Apr 10 21:22:39 pi4hyper kernel: [  711.480247] RTW: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1
    Apr 10 21:22:39 pi4hyper kernel: [  711.482441] RTW: rtw_ndev_init(wlan1) if1 mac_addr=44:a5:6e:53:0f:4c
    Apr 10 21:22:39 pi4hyper kernel: [  711.486174] usbcore: registered new interface driver rtl8821au
    Apr 10 21:22:39 pi4hyper kernel: [  711.486197] RTW: module init ret=0
    Apr 10 21:22:39 pi4hyper systemd[1]: Starting Load/Save RF Kill Switch Status...
    Apr 10 21:22:39 pi4hyper mtp-probe: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3"
    Apr 10 21:22:39 pi4hyper mtp-probe: bus: 1, device: 4 was not an MTP device
    Apr 10 21:22:39 pi4hyper systemd-udevd[1992]: Using default interface naming scheme 'v247'.
    Apr 10 21:22:40 pi4hyper systemd[1]: Started Load/Save RF Kill Switch Status.
    Apr 10 21:22:40 pi4hyper systemd[1]: Found device A6100 AC600 DB Wireless Adapter [Realtek RTL8811AU].
    Apr 10 21:22:40 pi4hyper systemd[1]: Started ifup for wlan1.
    Apr 10 21:22:45 pi4hyper systemd[1]: systemd-rfkill.service: Succeeded.
    Apr 10 21:23:40 pi4hyper systemd-udevd[170]: mon1: Worker [2015] processing SEQNUM=1879 is taking a long time
    Apr 10 21:24:55 pi4hyper kernel: [  846.827010] INFO: task systemd-udevd:2015 blocked for more than 120 seconds.
    Apr 10 21:24:55 pi4hyper kernel: [  846.827048]       Tainted: G         C O      5.15.32-v8+ #1538
    Apr 10 21:24:55 pi4hyper kernel: [  846.827061] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Apr 10 21:24:55 pi4hyper kernel: [  846.827073] task:systemd-udevd   state:D stack:    0 pid: 2015 ppid:   170 flags:0x00000800
    Apr 10 21:24:55 pi4hyper kernel: [  846.827106] Call trace:
    Apr 10 21:24:55 pi4hyper kernel: [  846.827116]  __switch_to+0x114/0x1c8
    Apr 10 21:24:55 pi4hyper kernel: [  846.827151]  __schedule+0x30c/0x8e8
    Apr 10 21:24:55 pi4hyper kernel: [  846.827174]  schedule+0x48/0x100
    Apr 10 21:24:55 pi4hyper kernel: [  846.827193]  schedule_preempt_disabled+0x20/0x38
    Apr 10 21:24:55 pi4hyper kernel: [  846.827213]  __mutex_lock.isra.15+0x2a4/0x5b0
    Apr 10 21:24:55 pi4hyper kernel: [  846.827232]  __mutex_lock_slowpath+0x1c/0x28
    Apr 10 21:24:55 pi4hyper kernel: [  846.827247]  mutex_lock+0x40/0x58
    Apr 10 21:24:55 pi4hyper kernel: [  846.827261]  rtnl_lock+0x20/0x30
    Apr 10 21:24:55 pi4hyper kernel: [  846.827281]  dev_ioctl+0x1f4/0x400
    Apr 10 21:24:55 pi4hyper kernel: [  846.827297]  sock_do_ioctl+0xbc/0x100
    Apr 10 21:24:55 pi4hyper kernel: [  846.827313]  sock_ioctl+0x2dc/0x3c0
    Apr 10 21:24:55 pi4hyper kernel: [  846.827340]  __arm64_sys_ioctl+0xb0/0xf0
    Apr 10 21:24:55 pi4hyper kernel: [  846.827368]  invoke_syscall+0x4c/0x110
    Apr 10 21:24:55 pi4hyper kernel: [  846.827387]  el0_svc_common.constprop.3+0x98/0x120
    Apr 10 21:24:55 pi4hyper kernel: [  846.827405]  do_el0_svc+0x2c/0x90
    Apr 10 21:24:55 pi4hyper kernel: [  846.827422]  el0_svc+0x24/0x60
    Apr 10 21:24:55 pi4hyper kernel: [  846.827438]  el0t_64_sync_handler+0x90/0xb8
    Apr 10 21:24:55 pi4hyper kernel: [  846.827455]  el0t_64_sync+0x1a0/0x1a4
    Apr 10 21:24:55 pi4hyper kernel: [  846.827473] INFO: task iw:2020 blocked for more than 120 seconds.
    Apr 10 21:24:55 pi4hyper kernel: [  846.827488]       Tainted: G         C O      5.15.32-v8+ #1538
    Apr 10 21:24:55 pi4hyper kernel: [  846.827500] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    Apr 10 21:24:55 pi4hyper kernel: [  846.827510] task:iw              state:D stack:    0 pid: 2020 ppid:  2019 flags:0x00000008
    Apr 10 21:24:55 pi4hyper kernel: [  846.827536] Call trace:
    Apr 10 21:24:55 pi4hyper kernel: [  846.827545]  __switch_to+0x114/0x1c8
    Apr 10 21:24:55 pi4hyper kernel: [  846.827565]  __schedule+0x30c/0x8e8
    Apr 10 21:24:55 pi4hyper kernel: [  846.827584]  schedule+0x48/0x100
    Apr 10 21:24:55 pi4hyper kernel: [  846.827601]  schedule_preempt_disabled+0x20/0x38
    Apr 10 21:24:55 pi4hyper kernel: [  846.827620]  __mutex_lock.isra.15+0x2a4/0x5b0
    Apr 10 21:24:55 pi4hyper kernel: [  846.827640]  __mutex_lock_slowpath+0x1c/0x28
    Apr 10 21:24:55 pi4hyper kernel: [  846.827653]  mutex_lock+0x40/0x58
    Apr 10 21:24:55 pi4hyper kernel: [  846.827666]  cfg80211_netdev_notifier_call+0x1f8/0x5a8 [cfg80211]
    Apr 10 21:24:55 pi4hyper kernel: [  846.827882]  raw_notifier_call_chain+0x5c/0x80
    Apr 10 21:24:55 pi4hyper kernel: [  846.827902]  call_netdevice_notifiers_info+0x60/0xb0
    Apr 10 21:24:55 pi4hyper kernel: [  846.827920]  register_netdevice+0x388/0x400
    Apr 10 21:24:55 pi4hyper kernel: [  846.827936]  cfg80211_rtw_add_virtual_intf+0x1e4/0x47c [8821au]
    Apr 10 21:24:55 pi4hyper kernel: [  846.828269]  nl80211_new_interface+0x15c/0x448 [cfg80211]
    Apr 10 21:24:55 pi4hyper kernel: [  846.828449]  genl_family_rcv_msg_doit.isra.15+0x114/0x158
    Apr 10 21:24:55 pi4hyper kernel: [  846.828469]  genl_rcv_msg+0xf8/0x1e0
    Apr 10 21:24:55 pi4hyper kernel: [  846.828485]  netlink_rcv_skb+0x64/0x128
    Apr 10 21:24:55 pi4hyper kernel: [  846.828500]  genl_rcv+0x40/0x58
    Apr 10 21:24:55 pi4hyper kernel: [  846.828515]  netlink_unicast+0x1c0/0x280
    Apr 10 21:24:55 pi4hyper kernel: [  846.828530]  netlink_sendmsg+0x1d0/0x418
    Apr 10 21:24:55 pi4hyper kernel: [  846.828545]  sock_sendmsg+0x54/0x60
    Apr 10 21:24:55 pi4hyper kernel: [  846.828561]  ____sys_sendmsg+0x260/0x2a0
    Apr 10 21:24:55 pi4hyper kernel: [  846.828576]  ___sys_sendmsg+0x8c/0xd0
    Apr 10 21:24:55 pi4hyper kernel: [  846.828591]  __sys_sendmsg+0x74/0xc8
    Apr 10 21:24:55 pi4hyper kernel: [  846.828607]  __arm64_sys_sendmsg+0x2c/0x38
    Apr 10 21:24:55 pi4hyper kernel: [  846.828622]  invoke_syscall+0x4c/0x110
    Apr 10 21:24:55 pi4hyper kernel: [  846.828640]  el0_svc_common.constprop.3+0xfc/0x120
    Apr 10 21:24:55 pi4hyper kernel: [  846.828658]  do_el0_svc+0x2c/0x90
    Apr 10 21:24:55 pi4hyper kernel: [  846.828675]  el0_svc+0x24/0x60
    Apr 10 21:24:55 pi4hyper kernel: [  846.828693]  el0t_64_sync_handler+0x90/0xb8
    Apr 10 21:24:55 pi4hyper kernel: [  846.828710]  el0t_64_sync+0x1a0/0x1a4
    Apr 10 21:25:40 pi4hyper systemd-udevd[170]: mon1: Worker [2015] processing SEQNUM=1879 killed
    
    
    opened by Musiker 8
  • Use the fallthrough pseudo-keyword

    Use the fallthrough pseudo-keyword

    This seems to be required when building with Linux 5.18 (unless I set -Wno-implict-fallthrough). fallthrough was introduced in Linux 5.4, so as far as I can tell should be present in all kernel versions supported by the driver.

    opened by alyssais 7
  • Driver works as well in openSUSE Tumbleweed

    Driver works as well in openSUSE Tumbleweed

    Not an issue just to add a line to your list of tested distributions. I have used this driver successfully in openSUSE Tumbleweed since last August (previous version first, this version now).

    openSUSE Tumbleweed is a rolling distribution that is continuously upgraded, so a number of kernel versions have come and gone since last August. All of them have worked flawlessly. Current kernel is 5.15.2.

    The WiFI adapter is a generic USB dongle based on RTL8811AU (0bda:a811 Realtek Semiconductor Corp. RTL8811AU 802.11a/b/g/n/ac WLAN Adapter).

    Thank you for this effort, much appreciated!

    opened by dhdeangelis 6
  • Missing channel (like 157)

    Missing channel (like 157)

    I'm with Ubuntu 20.04.3 and when my wifi is on channel is 157, I can't connect to 5ghz. With Windows I don't have any issue.

    iwlist chan :

    wlx7cc2c61c4a31 32 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 36 : 5.18 GHz Channel 40 : 5.2 GHz Channel 44 : 5.22 GHz Channel 48 : 5.24 GHz Channel 52 : 5.26 GHz Channel 56 : 5.28 GHz Channel 60 : 5.3 GHz Channel 64 : 5.32 GHz Channel 100 : 5.5 GHz Channel 104 : 5.52 GHz Channel 108 : 5.54 GHz Channel 112 : 5.56 GHz Channel 116 : 5.58 GHz Channel 120 : 5.6 GHz Channel 124 : 5.62 GHz Channel 128 : 5.64 GHz Channel 132 : 5.66 GHz Channel 136 : 5.68 GHz Channel 140 : 5.7 GHz Channel 149 : 5.745 GHz Channel 153 : 5.765 GHz Current Frequency:5.22 GHz (Channel 44)

    I have an TP-Link Mini - AC600 USB 2.0 (Archer T2U Nano)

    opened by frcs6 6
  • Stoping wifi

    Stoping wifi

    Hi there! I hope you are going great! First of all I would like to congrats all people evolved on this project you are amazing! Thank you all!

    So, my issue is a sudden stop of the wifi. I'm using a dungle USB TP-Link Archer T2u AC600 dual band. However, I don't know why the internet connection sudden stop on my Xerolinux OS and when I touch the wifi icon the internet returns to work in a few seconds. I use the same dungle on Windows and I have no issues at all. My question to you guys is there a setting on the rtl8821au config file that I could do to sort it out or some? Thank you in advance! Be fine out there!

    opened by Joarell 5
  • (solved) Not working for Kernel 5.15

    (solved) Not working for Kernel 5.15

    Hi. I have tried to install the driver on kernel (5.15.0-41-generic), but it doesn't seem to work.

    Thank you.

    sudo uname -a; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev
    
    Linux jongvis 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
    SecureBoot disabled
    Platform is in Setup Mode
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 003: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
    Bus 002 Device 002: ID 1058:25e2 Western Digital Technologies, Inc. My Passport (WD40NMZW)
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 005: ID 05ac:024f Apple, Inc. Aluminium Keyboard (ANSI)
    Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
    Bus 001 Device 003: ID 0bda:0811 Realtek Semiconductor Corp. Realtek 8812AU/8821AU 802.11ac WLAN Adapter [USB Wireless Dual-Band Adapter 2.4/5Ghz]
    Bus 001 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    0: hci0: Bluetooth
    	Soft blocked: no
    	Hard blocked: no
    rtl8821au/5.12.5.2, 5.15.0-41-generic, x86_64: installed
    
    
    opened by jonghkim 6
  • Doesn't compile in Alpine Linux

    Doesn't compile in Alpine Linux

    My dystrohop turned me on to Alpine Linux, but I can't compile a driver for it Here's what I did:

    git clone https://github.com/morrownr/8821au-20210708.git
    apk add make g++ linux-headers
    cd 8821au-20210708
    sh install-driver-no-dkms.sh
    

    image

    opened by KirMozor 9
  • Thanks for a great driver!

    Thanks for a great driver!

    Hi there! After spending many hours going through drivers, I finally thought to just search Netgear A6100 in github, and saw this as being the most up-to-date. It works! Thanks for your great work!

    opened by thomcom 1
  • (solved) Can I use 2 wifi adaptors on the my laptop on linux?

    (solved) Can I use 2 wifi adaptors on the my laptop on linux?

    $ sudo uname -a
    Linux xfce 5.15.0-41-generic #44~20.04.1-Ubuntu SMP Fri Jun 24 13:27:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
    
    $ mokutil --sb-state
    SecureBoot disabled
    
    $ lsusb
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 005: ID 04f3:0c00 Elan Microelectronics Corp. ELAN:ARM-M4
    Bus 001 Device 004: ID 30c9:0013 DJKCVA1WSD73IE HP TrueVision HD Camera
    Bus 001 Device 007: ID 2357:0120 TP-Link 802.11ac WLAN Adapter 
    Bus 001 Device 006: ID 046d:c534 Logitech, Inc. Unifying Receiver
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    
    $ rfkill list all
    0: phy0: Wireless LAN
    	Soft blocked: no
    	Hard blocked: no
    
    $ dkms status
    8812au, 5.6.4.2_35491.20191025, 5.15.0-41-generic, x86_64: installed
    rtl8821au, 5.12.5.2, 5.15.0-41-generic, x86_64: installed
    
    $ iw dev
    phy#0
    	Interface wlo1
    		ifindex 3
    		wdev 0x1
    		addr XX:XX:XX:XX:XX:XX
    		type managed
    		txpower 20.00 dBm
    		multicast TXQ:
    			qsz-byt	qsz-pkt	flows	drops	marks	overlmt	hashcol	tx-bytes	tx-packets
    			0	0	0	0	0	0	0	0		0
    

    Can I install my TP-Link Adapter on wlo2 interface?

    opened by LowNightSnack 27
  • Unable to connect 5 GHZ and showing two wifi

    Unable to connect 5 GHZ and showing two wifi

    https://ibb.co/FhLwHWs

    sudo uname -a; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev Linux blackbox 5.17.5-76051705-generic #202204271406~1655476786~22.04~62dd706 SMP PREEMPT Fri Jun 17 16 x86_64 x86_64 x86_64 GNU/Linux SecureBoot disabled Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 04f3:0c5e Elan Microelectronics Corp. ELAN:ARM-M4 Bus 003 Device 003: ID 04f2:b6c0 Chicony Electronics Co., Ltd HP HD Camera Bus 003 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 003 Device 002: ID 2357:011e TP-Link AC600 wireless Realtek RTL8811AU [Archer T2U Nano] Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: phy1: Wireless LAN Soft blocked: no Hard blocked: no rtl8821au/5.12.5.2, 5.17.5-76051705-generic, x86_64: installed system76/1.0.14~1643391291~22.04~78ede46, 5.17.5-76051705-generic, x86_64: installed system76_acpi/1.0.2~1640122755~22.04~04145b8, 5.17.5-76051705-generic, x86_64: installed (original_module exists) system76-io/1.0.2~1655490480~22.04~0217576, 5.17.5-76051705-generic, x86_64: installed phy#1 Interface wlxb6b024bf2d82 ifindex 5 wdev 0x100000002 addr b6:b0:24:bf:2d:82 ssid Wizards V2 type managed txpower 14.00 dBm Interface wlxb4b024bf2d82 ifindex 4 wdev 0x100000001 addr b4:b0:24:bf:2d:82 type managed txpower -100.00 dBm phy#0 Interface wlp0s20f3 ifindex 3 wdev 0x1 addr 48:51:c5:41:d3:c7 type managed txpower 0.00 dBm multicast TXQ: qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets 0 0 0 0 0 0 0 0 0

    opened by zainulhasan 1
Owner
Nick
Nick
Linux Driver for USB WiFi Adapters that are based on the RTL8811CU, RTL8821CU and RTL8731AU Chipsets - v5.12.0

Click here for USB WiFi Adapter Information for Linux A FAQ is available at the end of this document. Problem reports go in Issues. Include the inform

Nick 102 Aug 9, 2022
Linux Driver for USB WiFi Adapters that are based on the RTL8812AU Chipset - v5.13.6

Click for USB WiFi Adapter Information for Linux A FAQ is available at the end of this document. Problem reports go in Issues. Problem reports should

Nick 165 Aug 8, 2022
LLVM IR and optimizer for shaders, including front-end adapters for GLSL and SPIR-V and back-end adapter for GLSL

Licensing LunarGLASS is available via a three clause BSD-style open source license. Goals The primary goals of the LunarGLASS project are: Reduce the

LunarG, Inc. 151 Jun 18, 2022
Kexts enabling native support for Intel Bluetooth chipsets in macOS.

IntelBluetoothFamily Kexts enabling native support for Intel Bluetooth chipsets in macOS. Most of the code is complete, and I am now in the testing ph

null 128 Jul 26, 2022
LoRa Driver for Semtech SX1262 on Linux (PineDio USB Adapter) and BL602 (PineDio Stack BL604)

LoRa Driver for Semtech SX1262 on Linux (PineDio USB Adapter) and BL602 (PineDio Stack BL604) Read the articles... "Build a Linux Driver for PineDio L

Lee Lup Yuen 7 Mar 15, 2022
Loads a signed kernel driver which allows you to map any driver to kernel mode without any traces of the signed / mapped driver.

CosMapper Loads a signed kernel driver (signed with leaked cert) which allows you to map any driver to kernel mode without any traces of the signed /

null 118 Jul 26, 2022
Linux USB driver for the MOTU AVB series interfaces

motu-avb Linux USB driver for the MOTU AVB series interfaces Kernel parameters: samplerate: set the samplerate (its currently fixed at module load) de

null 42 Jul 20, 2022
Tiny and portable usb host and device stack for mcu with usb ip

Tiny and portable usb host and device stack for mcu with usb ip

sakumisu 404 Aug 2, 2022
USB-C_PCB_experiments - USB-C ports made from a flex PCB and an ATtiny84A

USB-C PCB Experiments This is part of an ongoing series of projects involving creative interpretations of the USB mechanical standards. You've probabl

Sam Ettinger 22 May 21, 2022
An unofficial Realtek PCIe/USB-based SD card reader driver for macOS

Realtek Card Reader Driver for macOS Unleash the full potential of your SDXC UHS-I cards Introduction An unofficial macOS kernel extension for Realtek

FireWolf 131 Jul 30, 2022
ESP32 software USB host through general IO pins. We can connect up to 4 USB-LS HID (keyboard mouse joystick) devices simultaneously.

esp32_usb_soft_host esp32 USB-LS pure software host thru general IO pins. Up to 4 HID devices simultaneously. board ~$3 :https://www.aliexpress.com/pr

Samsonov Dima 273 Jul 25, 2022
ESP8266 software USB host through general IO pins. We can connect up to 2 USB-LS HID (keyboard mouse joystick) devices simultaneously.

esp8266_usb_soft_host Test for esp8266 usb host . Works with ESP-IDF v3.4 80MHz and 160MHz. WorkInProgress Test run with mouse & combined mouse & keyb

Samsonov Dima 27 Jul 30, 2022
Anotter USB temperature logger that can record up to four channels with thermocouple or NTCs connected via CDC directly or SCPI to USB.

temperature-logger Anotter USB temperature logger that can record up to four channels with thermocouple or NTCs connected via CDC directly or SCPI to

Jana Marie Hemsing 47 Apr 6, 2022
Windows kernel-mode driver emulating well-known USB game controllers.

Windows kernel-mode driver emulating well-known USB game controllers.

Virtual Gamepad Emulation Framework 1.5k Jul 27, 2022
Scrollytroller is a crank-based USB controller, initially inteneded for use with Playdate's Pulp web-based game development tool

Scrollytroller Scrollytroller is a crank-based USB controller, initially inteneded for use with Playdate's Pulp web-based game development tool. This

Scott Lawrence 4 Feb 17, 2022
x64 Windows kernel driver mapper, inject unsigned driver using anycall

anymapper x64 Windows kernel driver mapper, inject unsigned driver using anycall This project is WIP. Todo Fix: Can't make API calls from IAT nor func

Kento Oki 68 Jun 22, 2022
Driver leap - Self-sustainable fork of SteamVR driver for Leap Motion controller with updated vendor libraries

Driver Leap Self-sustainable fork of SteamVR driver for Leap Motion controller with updated vendor libraries Installation (for users) Install Ultralea

null 46 Jul 28, 2022
Hygieia, a vulnerable driver traces scanner written in C++ as an x64 Windows kernel driver.

Hygieia The Greek goddess of health, her name is the source for the word "hygiene". Hygieia is a windows driver that works similarly to how pagewalkr

Deputation 69 Jul 27, 2022
SinMapper - usermode driver mapper that forcefully loads any signed kernel driver

usermode driver mapper that forcefully loads any signed kernel driver (legit cert) with a big enough section (example: .data, .rdata) to map your driver over. the main focus of this project is to prevent modern anti-cheats (BattlEye, EAC) from finding your driver and having the power to hook anything due to being inside of legit memory (signed legit driver).

null 109 Aug 6, 2022