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

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


Comments
  • (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

  • (info) Bit more information on the kernel headers path not found with dkms?

    (info) Bit more information on the kernel headers path not found with dkms?

    Trip over this again, Odd, this time a simple reboot did not fix the issue. This was on Pi Zero, but not sure that matters.

    Since the install-driver.sh failed, I ran the remove-driver.sh, did not reboot and did a make clean then make, just so see what happened, and this was the result:

    [email protected]:~/8821au-20210708-morrownr# make make ARCH=arm CROSS_COMPILE= -C /lib/modules/5.15.78+/build M=/root/8821au-20210708-morrownr modules make[1]: *** /lib/modules/5.15.78+/build: No such file or directory. Stop. make: *** [Makefile:2517: modules] Error 2 [email protected]:~/8821au-20210708-morrownr# ls -l /lib/modules/5.15.78+/ total 2436 drwxr-xr-x 11 root root 4096 Nov 13 23:19 kernel -rw-r--r-- 1 root root 581281 Nov 13 23:19 modules.alias -rw-r--r-- 1 root root 610734 Nov 13 23:19 modules.alias.bin -rw-r--r-- 1 root root 13930 Nov 13 23:19 modules.builtin -rw-r--r-- 1 root root 0 Nov 13 23:19 modules.builtin.alias.bin -rw-r--r-- 1 root root 15282 Nov 13 23:19 modules.builtin.bin -rw-r--r-- 1 root root 77245 Nov 13 23:19 modules.builtin.modinfo -rw-r--r-- 1 root root 220535 Nov 13 23:19 modules.dep -rw-r--r-- 1 root root 297158 Nov 13 23:19 modules.dep.bin -rw-r--r-- 1 root root 324 Nov 13 23:19 modules.devname -rw-r--r-- 1 root root 66705 Nov 13 23:19 modules.order -rw-r--r-- 1 root root 913 Nov 13 23:19 modules.softdep -rw-r--r-- 1 root root 262188 Nov 13 23:19 modules.symbols -rw-r--r-- 1 root root 318677 Nov 13 23:19 modules.symbols.bin

    Pi headers for the given kernel is there... # uname -a Linux template 5.15.78+ #1599 Fri Nov 11 12:20:14 GMT 2022 armv6l GNU/Linux

    # apt install raspberrypi-kernel-headers Reading package lists... Done Building dependency tree... Done Reading state information... Done raspberrypi-kernel-headers is already the newest version (1:1.20221104-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

    # find /usr/lib | grep 15.78+ | grep build [no output]

    Really weird, since the correct headers are there.

    I am going to recreate the image, and see if I can recreate it again.

  • 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

  • Linux mint 21 xfce with Archer T2U nano can't connect to 5ghz of Tplink arhcer ax72 router.

    Linux mint 21 xfce with Archer T2U nano can't connect to 5ghz of Tplink arhcer ax72 router.

    I am only able to connect to 2.4ghz, when I connect to 5ghz it just keep on asking for password. I made a detailed description on Tplink routers forum because I don't know if its the wifi dongle or the router that has the problem. https://community.tp-link.com/us/home/forum/topic/578692

  • I have error, please, help me

    I have error, please, help me

    [email protected]host:~/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> 
    
    
  • 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.
    
  • 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?

  • 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: команда не найдена
    
  • (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?

  • Netgear ac600 wont use the driver

    Netgear ac600 wont use the driver

    I have installed the driver 3 times on new installs and on 2 different sd cards and I still cannot get it to work with my Netgear ac600 the driver installs normally and after installing the device isn't used for wlan

  • (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
    
    
  • awus036acs and android/nethunter

    awus036acs and android/nethunter

    Hi I have awus036acs and in kali linux this driver works great. Does it support android? I have nethunter and android 11 using kernel 4.14.290-agni-miatoll_kali-nethunter_v14.2-stable is there any way to get you driver into android/nethunter? thank you for your time and help

  • driver appears installed but iwconfig shows adapter not connecting to the wifi network

    driver appears installed but iwconfig shows adapter not connecting to the wifi network

    I searched all of the issues and don't see how to fix this. The USB dongle is wlan1 in the following. Any help will be greatly appreciated.

    Background: Linux raspberrypi 5.15.76-v7+ #1597 SMP Fri Nov 4 12:13:17 GMT 2022 armv7l

    lsusb Bus 001 Device 004: ID 0bda:0811 Realtek Semiconductor Corp. Realtek 8812AU/8821AU 802.11ac WLAN Adapter [USB Wireless Dual-Band Adapter 2.4/5Ghz] Bus 001 Device 005: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC) Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    iwconfig lo no wireless extensions.

    eth0 no wireless extensions.

    wlan0 IEEE 802.11 ESSID:"djnet-1"
    Mode:Managed Frequency:2.452 GHz Access Point: 04:D4:C4:07:EF:F8
    Bit Rate=39 Mb/s Tx-Power=31 dBm
    Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=37/70 Signal level=-73 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    wlan1 unassociated Nickname:"[email protected]" Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
    Sensitivity:0/0
    Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    ifconfig eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether b8:27:eb:9c:78:e0 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 634 bytes 224038 (218.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 634 bytes 224038 (218.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.57.175 netmask 255.255.255.0 broadcast 192.168.57.255 inet6 fdfd:21f0:e140:495d:e99a:8d16:53e1:89db prefixlen 64 scopeid 0x0 inet6 fe80::99ef:3632:cec7:b88c prefixlen 64 scopeid 0x20 ether b8:27:eb:c9:2d:b5 txqueuelen 1000 (Ethernet) RX packets 994 bytes 262013 (255.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 287 bytes 38127 (37.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    wlan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 00:c0:ca:a7:88:7c txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0

    dkms status rtl8821au, 5.12.5.2, 5.15.76-v7+, armv7l: installed


    grep [[:alnum:]] /sys/module/8821au/parameters/* /sys/module/8821au/parameters/rtw_ampdu_enable:1 /sys/module/8821au/parameters/rtw_beamform_cap:10 /sys/module/8821au/parameters/rtw_channel:1 /sys/module/8821au/parameters/rtw_drv_ant_band_switch:1 /sys/module/8821au/parameters/rtw_dynamic_agg_enable:1 /sys/module/8821au/parameters/rtw_en_dyn_rrsr:1 /sys/module/8821au/parameters/rtw_en_gro:1 /sys/module/8821au/parameters/rtw_en_napi:1 /sys/module/8821au/parameters/rtw_hiq_filter:1 /sys/module/8821au/parameters/rtw_ht_enable:1 /sys/module/8821au/parameters/rtw_hw_wps_pbc:1 /sys/module/8821au/parameters/rtw_ips_mode:1 /sys/module/8821au/parameters/rtw_led_ctrl:1 /sys/module/8821au/parameters/rtw_lps_chk_by_tp:1 /sys/module/8821au/parameters/rtw_pll_ref_clk_sel:15 /sys/module/8821au/parameters/rtw_power_mgnt:1 /sys/module/8821au/parameters/rtw_rrsr_value:-1 /sys/module/8821au/parameters/rtw_rx_stbc:1 /sys/module/8821au/parameters/rtw_scan_interval_thr:16000 /sys/module/8821au/parameters/rtw_stbc_cap:19 /sys/module/8821au/parameters/rtw_vcs_type:1 /sys/module/8821au/parameters/rtw_vht_24g_enable:1 /sys/module/8821au/parameters/rtw_vht_enable:1 /sys/module/8821au/parameters/rtw_wmm_enable:1


    rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no


    iw reg get global country US: DFS-FCC (902 - 904 @ 2), (N/A, 30), (N/A) (904 - 920 @ 16), (N/A, 30), (N/A) (920 - 928 @ 8), (N/A, 30), (N/A) (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, NO-IR (57240 - 71000 @ 2160), (N/A, 40), (N/A)

    phy#0 country 99: DFS-UNSET (2402 - 2482 @ 40), (6, 20), (N/A) (2474 - 2494 @ 20), (6, 20), (N/A) (5140 - 5360 @ 160), (6, 20), (N/A) (5460 - 5860 @ 160), (6, 20), (N/A)

  • Ubuntu installed succesfully, but not detected

    Ubuntu installed succesfully, but not detected

    Opening new thread for Ubuntu issues. The USB devices is detected and driver is installed, but the system does not recognize any WiFi device and does not offer any networks. Any help would be appreciated.

    dkms status rtl8821au/5.12.5.2, 5.19.0-23-generic, x86_64: installed

    lsusb Bus 001 Device 002: ID 2357:0120 TP-Link Archer T2U PLUS [RTL8821AU]

    iw reg get
    global country 00: DFS-UNSET
     (755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN
     (2402 - 2472 @ 40), (N/A, 20), (N/A)
     (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN 
    (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN 
    (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN 
    (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN 
    (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN 
    (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN 
    (57240 - 63720 @ 2160), (N/A, 0), (N/A)
    

    mokutil --sb-state SecureBoot disabled

    iwconfig

    lo no wireless extensions.
    
    eno1 no wireless extensions.
    

    I have been struggling with it all day, but no luck.

    I have tried to set the proper iw

    sudo iw reg set CZ
    and I get
    global country CZ: DFS-ETSI
    
    

    but it is gone after reboot

    System is

    Kubuntu 22.10
    Kernel 5.19.0-23-generic
    
  • Not working on kernel 6.0.8

    Not working on kernel 6.0.8

    Hey, I tried to install the driver on Fedora 37 with kernel 6.0.8 and it fails with the following dmesg output:

    [  114.552965] 8821au: Unknown symbol __cfg80211_alloc_event_skb (err -2)
    [  114.552992] 8821au: Unknown symbol wiphy_register (err -2)
    [  114.553005] 8821au: Unknown symbol cfg80211_remain_on_channel_expired (err -2)
    [  114.553028] 8821au: Unknown symbol cfg80211_vendor_cmd_reply (err -2)
    [  114.553043] 8821au: Unknown symbol cfg80211_del_sta_sinfo (err -2)
    [  114.553056] 8821au: Unknown symbol wiphy_unregister (err -2)
    [  114.553090] 8821au: Unknown symbol cfg80211_ch_switch_notify (err -2)
    [  114.553103] 8821au: Unknown symbol cfg80211_ch_switch_started_notify (err -2)
    [  114.553113] 8821au: Unknown symbol ieee80211_get_channel_khz (err -2)
    [  114.553126] 8821au: Unknown symbol cfg80211_ready_on_channel (err -2)
    [  114.553179] 8821au: Unknown symbol wiphy_free (err -2)
    [  114.553188] 8821au: Unknown symbol wiphy_new_nm (err -2)
    [  114.553197] 8821au: Unknown symbol cfg80211_get_bss (err -2)
    [  114.553213] 8821au: Unknown symbol ieee80211_freq_khz_to_channel (err -2)
    [  114.553222] 8821au: Unknown symbol __cfg80211_send_event_skb (err -2)
    [  114.553241] 8821au: Unknown symbol cfg80211_disconnected (err -2)
    [  114.553250] 8821au: Unknown symbol cfg80211_michael_mic_failure (err -2)
    [  114.553264] 8821au: Unknown symbol cfg80211_ibss_joined (err -2)
    [  114.553300] 8821au: Unknown symbol cfg80211_scan_done (err -2)
    [  114.553316] 8821au: Unknown symbol cfg80211_roamed (err -2)
    [  114.553324] 8821au: Unknown symbol cfg80211_put_bss (err -2)
    [  114.553342] 8821au: Unknown symbol cfg80211_connect_done (err -2)
    [  114.553368] 8821au: Unknown symbol cfg80211_unlink_bss (err -2)
    [  114.553391] 8821au: Unknown symbol cfg80211_inform_bss_frame_data (err -2)
    [  114.553413] 8821au: Unknown symbol cfg80211_new_sta (err -2)
    [  114.553437] 8821au: Unknown symbol __cfg80211_alloc_reply_skb (err -2)
    [  114.553450] 8821au: Unknown symbol cfg80211_rx_mgmt_ext (err -2)
    [  114.553472] 8821au: Unknown symbol cfg80211_mgmt_tx_status_ext (err -2)
    [  114.553482] 8821au: Unknown symbol cfg80211_external_auth_request (err -2)
    [  340.153684] 8821au: Unknown symbol __cfg80211_alloc_event_skb (err -2)
    [  340.153708] 8821au: Unknown symbol wiphy_register (err -2)
    [  340.153722] 8821au: Unknown symbol cfg80211_remain_on_channel_expired (err -2)
    [  340.153742] 8821au: Unknown symbol cfg80211_vendor_cmd_reply (err -2)
    [  340.153757] 8821au: Unknown symbol cfg80211_del_sta_sinfo (err -2)
    [  340.153768] 8821au: Unknown symbol wiphy_unregister (err -2)
    [  340.153801] 8821au: Unknown symbol cfg80211_ch_switch_notify (err -2)
    [  340.153813] 8821au: Unknown symbol cfg80211_ch_switch_started_notify (err -2)
    [  340.153823] 8821au: Unknown symbol ieee80211_get_channel_khz (err -2)
    [  340.153836] 8821au: Unknown symbol cfg80211_ready_on_channel (err -2)
    [  340.153874] 8821au: Unknown symbol wiphy_free (err -2)
    [  340.153883] 8821au: Unknown symbol wiphy_new_nm (err -2)
    [  340.153891] 8821au: Unknown symbol cfg80211_get_bss (err -2)
    [  340.153906] 8821au: Unknown symbol ieee80211_freq_khz_to_channel (err -2)
    [  340.153921] 8821au: Unknown symbol __cfg80211_send_event_skb (err -2)
    [  340.153939] 8821au: Unknown symbol cfg80211_disconnected (err -2)
    [  340.153947] 8821au: Unknown symbol cfg80211_michael_mic_failure (err -2)
    [  340.153961] 8821au: Unknown symbol cfg80211_ibss_joined (err -2)
    [  340.153995] 8821au: Unknown symbol cfg80211_scan_done (err -2)
    [  340.154009] 8821au: Unknown symbol cfg80211_roamed (err -2)
    [  340.154016] 8821au: Unknown symbol cfg80211_put_bss (err -2)
    [  340.154033] 8821au: Unknown symbol cfg80211_connect_done (err -2)
    [  340.154057] 8821au: Unknown symbol cfg80211_unlink_bss (err -2)
    [  340.154078] 8821au: Unknown symbol cfg80211_inform_bss_frame_data (err -2)
    [  340.154093] 8821au: Unknown symbol cfg80211_new_sta (err -2)
    [  340.154116] 8821au: Unknown symbol __cfg80211_alloc_reply_skb (err -2)
    [  340.154128] 8821au: Unknown symbol cfg80211_rx_mgmt_ext (err -2)
    [  340.154149] 8821au: Unknown symbol cfg80211_mgmt_tx_status_ext (err -2)
    [  340.154159] 8821au: Unknown symbol cfg80211_external_auth_request (err -2)
    
  • Does the drive support Monitor Mode ?

    Does the drive support Monitor Mode ?

    To start with, I want to thank you for this piece of work. It works for me K5.15.

    I am using TP-LINK Archer T2U USB wireless adapter to take sniff using virtual machine (vBox). Thanks to your driver I am seeing this within my VM as wireless card. But, when it comes to taking this to monitor mode, it seems not working. I opened this just to ask your recommendations or maybe it is a driver problem i dont know. However, wireless card supposedly supports monitor mode. image

  • (info) A lot of 5 GHz Wi-Fi channels are disabled

    (info) A lot of 5 GHz Wi-Fi channels are disabled

    I'm using a TP-Link Archer T2U Nano and I cannot connect to certain Wi-Fi AP. My phone does connect just fine, and when I check the frequency, it was on channel 157 which is disabled in the driver according to iw phy0.

    I have tried changing iw reg, but this did nothing to improve the channel situation.

    The following Wi-Fi channels are disabled, according to iw phy0 info

    			* 5075 MHz [15] (disabled)
    			* 5080 MHz [16] (disabled)
    			* 5085 MHz [17] (disabled)
    			* 5090 MHz [18] (disabled)
    			* 5100 MHz [20] (disabled)
    			* 5120 MHz [24] (disabled)
    			* 5140 MHz [28] (disabled)
    			* 5160 MHz [32] (disabled)
    			* 5180 MHz [36] (13.0 dBm)
    			* 5200 MHz [40] (13.0 dBm)
    			* 5220 MHz [44] (13.0 dBm)
    			* 5240 MHz [48] (13.0 dBm)
    			* 5260 MHz [52] (13.0 dBm) (radar detection)
    			* 5280 MHz [56] (13.0 dBm) (radar detection)
    			* 5300 MHz [60] (13.0 dBm) (radar detection)
    			* 5320 MHz [64] (13.0 dBm) (radar detection)
    			* 5340 MHz [68] (disabled)
    			* 5360 MHz [72] (disabled)
    			* 5380 MHz [76] (disabled)
    			* 5400 MHz [80] (disabled)
    			* 5420 MHz [84] (disabled)
    			* 5440 MHz [88] (disabled)
    			* 5460 MHz [92] (disabled)
    			* 5480 MHz [96] (disabled)
    			* 5500 MHz [100] (13.0 dBm) (radar detection)
    			* 5520 MHz [104] (13.0 dBm) (radar detection)
    			* 5540 MHz [108] (13.0 dBm) (radar detection)
    			* 5560 MHz [112] (13.0 dBm) (radar detection)
    			* 5580 MHz [116] (13.0 dBm) (radar detection)
    			* 5600 MHz [120] (13.0 dBm) (radar detection)
    			* 5620 MHz [124] (13.0 dBm) (radar detection)
    			* 5640 MHz [128] (13.0 dBm) (radar detection)
    			* 5660 MHz [132] (13.0 dBm) (radar detection)
    			* 5680 MHz [136] (13.0 dBm) (radar detection)
    			* 5700 MHz [140] (13.0 dBm) (radar detection)
    			* 5720 MHz [144] (disabled)
    			* 5745 MHz [149] (disabled)
    			* 5765 MHz [153] (disabled)
    			* 5785 MHz [157] (disabled)
    			* 5805 MHz [161] (disabled)
    			* 5825 MHz [165] (disabled)
    			* 5845 MHz [169] (disabled)
    			* 5865 MHz [173] (disabled)
    			* 5885 MHz [177] (disabled)
    

    Output requested by maintainer

    6.0.2-1-MANJARO-ARM-ODROID aarch64
    Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 2357:011e TP-Link AC600 wireless Realtek RTL8811AU [Archer T2U Nano]
    Bus 001 Device 006: ID 046d:c092 Logitech, Inc. G102/G203 LIGHTSYNC Gaming Mouse
    Bus 001 Device 005: ID 258a:002a SINO WEALTH Keyboard
    Bus 001 Device 004: ID 0a05:7211 Unknown Manufacturer hub
    Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 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: yes
    	Hard blocked: no
    8821au/5.12.5.2.r155.gb46c98d, 6.0.2-1-MANJARO-ARM-ODROID, aarch64: installed
    phy#0
    	Interface wlan0
    		ifindex 4
    		wdev 0x1
    		addr 12:34:56:78:90:AA
    		ssid XXXXXXXXXXXXXXX
    		type managed
    		channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz
    		txpower 16.00 dBm
    global
    country NZ: DFS-ETSI
    	(2402 - 2482 @ 40), (N/A, 30), (N/A)
    	(5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW
    	(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
    	(5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS
    	(5735 - 5835 @ 80), (N/A, 30), (N/A)
    
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

Jan 1, 2023
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

Dec 29, 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

Dec 8, 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

Dec 19, 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)

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

Sep 17, 2022
Loads a signed kernel driver which allows you to map any driver to kernel mode without any traces of the signed / mapped driver.
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 /

Jan 2, 2023
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

Dec 23, 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

Jan 2, 2023
USB-C_PCB_experiments - USB-C ports made from a flex PCB and an ATtiny84A
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

Sep 5, 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

Jan 1, 2023
ESP8266 software USB host through general IO pins. We can connect up to 2 USB-LS HID (keyboard mouse joystick) devices simultaneously.
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

Sep 1, 2022
Anotter USB temperature logger that can record up to four channels with thermocouple or NTCs connected via CDC directly or SCPI to USB.
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

Nov 24, 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

Dec 28, 2022
Windows kernel-mode driver emulating well-known USB game controllers.

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

Jan 4, 2023
Scrollytroller is a crank-based USB controller, initially inteneded for use with Playdate's Pulp web-based game development tool
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

Feb 17, 2022
x64 Windows kernel driver mapper, inject unsigned driver using anycall
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

Dec 26, 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

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

Jan 5, 2023
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

Dec 4, 2022
SinMapper - usermode driver mapper that forcefully loads any signed kernel driver
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).

Dec 29, 2022