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 information obtained with:

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

8821cu ( 8821cu.ko ) 🚀

Linux Driver for USB WiFi Adapters that are based on the RTL8811CU, RTL8821CU and RTL8731AU Chipsets

  • v5.12.0 (Realtek) (20210118) 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)
  • WPA3 (see FAQ)
  • 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
    • Supports WPA/WPA2 TLS client
  • Power saving modes
  • Wireshark compatible
  • Aircrack-ng compatible
  • Packet injection
  • hostapd compatible
  • AP mode DFS channel support
  • Miracast
  • Supported interface modes
    • IBSS
    • Managed
    • Monitor (see Monitor_Mode.md in the docs folder.)
    • AP (see AP_Mode-Bridged_Wireless_Access_Point.md in the docs folder.)
    • P2P-client
    • P2P-GO
    • Concurrent (see Concurrent_Mode.md in the docs folder.)
  • Log level control
  • Power saving control
  • VHT control (allows 80 MHz channel width in AP mode)
  • SU Beamformee and MU Beamformee control
  • AP mode DFS channel control

Compatible CPUs

  • x86, amd64
  • ARM, ARM64

Compatible Kernels

  • Kernels: 4.14 - 5.11 (Realtek)
  • Kernels: 5.12 - 5.17 (community support)

Tested Linux Distributions

Note: One of the goals of this project is to provide driver support that is easy to install and works reliably on many distros. Meeting this goal depends on you to report your recommendations and updated information. If you see information that needs to be updated, please report the updated information and if you do not see adequate support for items such as Installation Steps 2, 3 and 9, and you know what updates need to added or you can get that information, please provide it so that the Installation Steps can be improved.

  • 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.13)

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

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

  • openSUSE Tumbleweed (rolling) (kernel 5.15)

  • Raspberry Pi OS (2021-10-30) (ARM 32 bit) (kernel 5.10)

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

  • Solus

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

Download Locations for Tested Linux Distributions

Tested Hardware

Compatible Devices

  • Cudy WU700
  • BrosTrend AC5L
  • EDUP EP-AC1651
  • EDUP EP-AC1635
  • TOTOLINK A650UA v3
  • Mercusys MU6H (multi-state)
  • Numerous additional products 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

Warning: Installing multiple drivers for the same hardware usually does not end well. If a previous attempt to install this driver failed or if you have previously installed another driver for chipsets supported by this driver, you MUST remove anything that the previous attempt installed BEFORE attempting to install this driver. This driver can be removed with the script called ./remove-driver.sh. Information is available in the section called Removal of the Driver. You can get a good idea as to whether you need to remove a previously installed driver by running the following command:

sudo dkms status

The installation instructions are for the novice user. Experienced users are welcome to alter the installation to meet their needs.

Temporary internet access is required for installation. There are numerous ways to enable temporary internet access depending on your hardware and situation. One method is to use tethering from a phone.. Another method 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 commands can be executed as the root user. (If the command sudo echo Yes returns "Yes", with or without having to enter your password, you do have sufficient access rights.)

DKMS is used for the installation. DKMS is a system utility which will automatically recompile and reinstall this driver when a new kernel is installed. DKMS is provided by and maintained by Dell.

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 the system package information (select the option for the OS you are using)

Note: If your Linux distro does not fall into one of options listed below, you will need to research how to update your system package information.

  • 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
  • Option for openSUSE based distributions
sudo zypper update

Note: If you do not regularly maintain your system by installing updated packages, please do so now and then reboot. The rest of the installation will appreciate having a fully up to date system to work with. The installation can then be continued with Step 3.

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

  • Option for Raspberry Pi OS (ARM/ARM64), for Raspberry Pi Desktop (x86) see below
sudo apt install -y raspberrypi-kernel-headers bc build-essential dkms git
  • Option for Debian, Kali, Linux Mint Debian Edition (LMDE) and Raspberry Pi Desktop (x86)
sudo apt install -y linux-headers-$(uname -r) build-essential dkms git libelf-dev
  • Option for Ubuntu (all flavors) and Linux Mint
sudo apt install -y dkms git build-essential
  • Option for Fedora
sudo dnf -y install git dkms kernel-devel kernel-debug-devel
  • Option for openSUSE
sudo zypper install -t pattern devel_kernel dkms
  • Option for Solus
sudo eopkg install gcc linux-current-headers make git binutils
  • Options for Arch and 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 install the correct version.

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

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/8821cu-20210118.git

Step 7: Move to the newly created driver directory

cd ~/src/8821cu-20210118

Step 8: (optional) Enable Concurrent Mode ( cmode-on.sh )

Note: see Concurrent_Mode.md in the docs folder to help determine whether you want to enable Concurrent Mode.

./cmode-on.sh

Step 9: Run a script to reconfigure for ARM or ARM64 based systems

Warning: This driver defaults to supporting x86 and amd64 based systems and this step should be skipped if your system is powered by an x86, amd64 or compatible CPU.

Note: If your system is powered by an ARM or ARM64 based Raspberry Pi, then one of the following scripts should be executed:

  • Option for the following listed operating systems to be installed to Raspberry Pi hardware
       * Raspberry Pi OS (32 bit)
./ARM_RPI.sh
  • Option for the following listed operating systems to be installed to Raspberry Pi hardware
       * Raspberry Pi OS (64 bit)
       * Kali Linux RPI ARM64
       * Ubuntu for Raspberry Pi
./ARM64_RPI.sh

Note: ARM or ARM64 based systems not listed above will likely require modifications similar to those provided in the above scripts but the number and variety of different ARM and ARM64 based systems makes supporting each system unpractical so you will need to research the needs of your system and make the appropriate modifications. If you discover the settings and make a new script that works with your ARM or ARM64 based system, you are welcome to submit the script and information to be included here.

Step 10: Run the installation script ( install-driver.sh )

Note: 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 load immediately and the driver options will not be applied. Rebooting is strongly recommended.

Note: Solus Linux does not support dkms and will require a manual build. See Manual build instructions below.

Manual build instructions: The script install-driver.sh automates the installation process, however, it may be necessary to build and install the driver manually with some Linux distros:

make clean
make
sudo make install
sudo reboot

Note: If you use the manual build instructions, you will need to repeat the process each time a new kernel is installed in your distro.


Driver Options ( edit-options.sh )

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

Note: The installation script will prompt you to edit the options.

Location: /etc/modprobe.d/8821cu.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 8821cu.conf.


Removal of the Driver ( remove-driver.sh )

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

  • if driver installation fails
  • if the driver is no longer needed
  • if a new or updated version of the driver needs to be installed
  • if a distro version upgrade is going to be installed

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 this script.

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

Step 2: Move to the driver directory

cd ~/src/8821cu-20210118

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 so changing the name of one of the networks is recommended. Since many IoT devices use the 2.4 GHz network, it may be better to change the name of the 5 GHz network.

  • 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 165 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.


Check and set regulatory domain

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.

  • 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.

  • If your USB WiFi adapter is USB 3 capable and you want it to operate in USB3 mode, 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).

  • Extention cables can be problematic. A way to check if the extension cable is the problem is to plug the adapter temporarily into a USB port on the computer.

  • Some USB WiFi adapters require considerable electrical current and push the capabilities of the power available via USB port. One example is adapters 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 forget a saved WiFi network on a Raspberry Pi

Step 1: Edit wpa_supplicant.conf

sudo nano /etc/wpa_supplicant/wpa_supplicant.conf

Step 2: Delete the relevant WiFi network block (including the 'network=' and opening/closing braces.

Step 3: Press ctrl-x followed by 'y' and enter to save the file.

Step 4: Reboot


FAQ:

Question: Is WPA3 supported?

Answer: WPA3-SAE support is in this driver according to Realtek, however, for it to work in client mode with some current Linux distros, you will need to download, compile and install the current development version of wpa_supplicant from the following site:

https://w1.fi/cgit/

WPA3-SAE is working well in AP mode using hostapd with the Raspberry Pi OS.

Question: I bought two rtl8811cu 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 without considerable technical skills. Realtek drivers do not support more than one adapter with the same chipset in the same computer. You can have multiple Realtek based adapters in the same computer as long as the adapters are based on different chipsets.

Question: Why do you recommend Mediatek based adapters when you maintain this repo for a Realtek driver?

Answer: Many new and existing Linux users already have adapters based on Realtek chipsets. This repo is for Linux users to support their existing adapters but my STRONG recommendation is for Linux users to seek out USB WiFi solutions based on Mediatek,

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

Question: Will you put volunteers to work?

Answer: Yes. Post a message in Issues or Discussions if interested.

Question: I am having problems with my adapter and I use Virtualbox?

Answer: This article may help.


Credits:


Comments
  • Kali 5.19.0 is not booting after shutdown and startup again.

    Kali 5.19.0 is not booting after shutdown and startup again.

    Issue:

    Wifi driver works fine with rtl8811cu, after installation i rebooted my system everything works fine until i shutdown my pc and start again, the problem is after selecting kali from grub kali is not booting up isntead there is a black screen with blinking curser but when i remove the usb adapter it boots up. Everytime i need to do this when booting.

    OS & device info:

    5.19.0-kali2-amd64 x86_64 SecureBoot disabled Platform is in Setup Mode Bus 002 Device 006: ID 0bda:c811 Realtek Semiconductor Corp. 802.11ac NIC Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 30fa:2350 INSTANT USB Keyboard Bus 001 Device 003: ID 18f8:0fc0 [Maxxter] USB GAMING MOUSE Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no rtl8821cu/5.12.0, 5.19.0-kali2-amd64, x86_64: installed phy#0 Interface wlan0 ifindex 3 wdev 0x1 addr 9c:88:2b:00:33:8c ssid "mobile device" type managed channel 6 (2437 MHz), width: 40 MHz, center1: 2427 MHz txpower 19.00 dBm

  • Not sure how to resolve this?

    Not sure how to resolve this?

    Running install-driver.sh version 20220705 5.15.52-v7+ armv7l Starting installation... Copying source files to: /usr/src/rtl8821cu-5.12.0 Copying 8821cu.conf to: /etc/modprobe.d

    Creating symlink /var/lib/dkms/rtl8821cu/5.12.0/source -> /usr/src/rtl8821cu-5.12.0

    DKMS: add completed. Error! echo Your kernel headers for kernel 5.15.52-v7+ cannot be found at /lib/modules/5.15.52-v7+/build or /lib/modules/5.15.52-v7+/source. You can use the --kernelsourcedir option to tell DKMS where it's located. An error occurred. dkms build error = 1 Please report this error. You will need to run the following before reattempting installation. $ sudo ./remove-driver.sh

  • Low speed

    Low speed

    Hello.

    I have rtl8821cu based usb wi-fi adapter (without bluetooth). This driver works fine but download/upload speed is low, up to 60Mbit/s. Tested using iperf3 with home server that connected to the same router directly to ethernet port.

    The adapter plugged in to rear usb port, pc is 2 meters away from wi-fi router. Other wi-fi clients shows up to 200-250Mbit/s, so router performance seems good.

    Probably some driver options needs to be tuned to get better performance. Already tried to turn off power saving option, but it didn't help.

    Could anyone please suggest what else can be checked/tuned?

    $ uname -a
    Linux casper-pc 5.19.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 17 Aug 2022 13:48:51 +0000 x86_64 GNU/Linux
    
    $ lsusb
    Bus 002 Device 003: ID 0bda:c811 Realtek Semiconductor Corp. 802.11ac NIC
    
    $ grep -v ^# /etc/modprobe.d/8821cu.conf
    options 8821cu rtw_drv_log_level=0 rtw_led_ctrl=1 rtw_vht_enable=1 rtw_power_mgnt=0 rtw_dfs_region_domain=0 rtw_RFE_type=7
    
    $ iwconfig
    wlp0s29u1u2  IEEE 802.11an  ESSID:"CasperAP_5G"  Nickname:"<[email protected]>"
              Mode:Managed  Frequency:5.24 GHz  Access Point: ***   
              Bit Rate:72.2 Mb/s   Sensitivity:0/0  
              Retry:off   RTS thr:off   Fragment thr:off
              Power Management:off
              Link Quality=78/100  Signal level=58/100  Noise level=0/100
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:0
    
    $ iw dev
    phy#0
            Interface wlp0s29u1u2
                    ifindex 3
                    wdev 0x1
                    addr ***
                    ssid CasperAP_5G
                    type managed
                    channel 48 (5240 MHz), width: 20 MHz, center1: 5240 MHz
                    txpower 17.00 dBm
    
    $ sudo iw phy
    Wiphy phy0
            wiphy index: 0
            max # scan SSIDs: 9
            max scan IEs length: 2304 bytes
            max # sched scan SSIDs: 0
            max # match sets: 0
            Retry short limit: 7
            Retry long limit: 4
            Coverage class: 0 (up to 0m)
            Supported Ciphers:
                    * WEP40 (00-0f-ac:1)
                    * WEP104 (00-0f-ac:5)
                    * TKIP (00-0f-ac:2)
                    * CCMP-128 (00-0f-ac:4)
                    * CMAC (00-0f-ac:6)
                    * GCMP-128 (00-0f-ac:8)
                    * GCMP-256 (00-0f-ac:9)
                    * CCMP-256 (00-0f-ac:10)
                    * GMAC-128 (00-0f-ac:11)
                    * GMAC-256 (00-0f-ac:12)
                    * CMAC-256 (00-0f-ac:13)
            Available Antennas: TX 0 RX 0
            Supported interface modes:
                     * IBSS
                     * managed
                     * AP
                     * monitor
                     * P2P-client
                     * P2P-GO
            Band 1:
                    Capabilities: 0x1862
                            HT20/HT40
                            Static SM Power Save
                            RX HT20 SGI
                            RX HT40 SGI
                            No RX STBC
                            Max AMSDU length: 7935 bytes
                            DSSS/CCK HT40
                    Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                    Minimum RX AMPDU time spacing: 16 usec (0x07)
                    HT Max RX data rate: 150 Mbps
                    HT TX/RX MCS rate indexes supported: 0-7
                    Bitrates (non-HT):
                            * 1.0 Mbps
                            * 2.0 Mbps
                            * 5.5 Mbps
                            * 11.0 Mbps
                            * 6.0 Mbps
                            * 9.0 Mbps
                            * 12.0 Mbps
                            * 18.0 Mbps
                            * 24.0 Mbps
                            * 36.0 Mbps
                            * 48.0 Mbps
                            * 54.0 Mbps
                    Frequencies:
                            * 2412 MHz [1] (19.0 dBm)
                            * 2417 MHz [2] (19.0 dBm)
                            * 2422 MHz [3] (19.0 dBm)
                            * 2427 MHz [4] (19.0 dBm)
                            * 2432 MHz [5] (19.0 dBm)
                            * 2437 MHz [6] (19.0 dBm)
                            * 2442 MHz [7] (19.0 dBm)
                            * 2447 MHz [8] (19.0 dBm)
                            * 2452 MHz [9] (19.0 dBm)
                            * 2457 MHz [10] (19.0 dBm)
                            * 2462 MHz [11] (19.0 dBm)
                            * 2467 MHz [12] (19.0 dBm) (no IR)
                            * 2472 MHz [13] (19.0 dBm) (no IR)
                            * 2484 MHz [14] (disabled)
            Band 2:
                    Capabilities: 0x862
                            HT20/HT40
                            Static SM Power Save
                            RX HT20 SGI
                            RX HT40 SGI
                            No RX STBC
                            Max AMSDU length: 7935 bytes
                            No DSSS/CCK HT40
                    Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                    Minimum RX AMPDU time spacing: 16 usec (0x07)
                    HT Max RX data rate: 150 Mbps
                    HT TX/RX MCS rate indexes supported: 0-7
                    VHT Capabilities (0x03c00022):
                            Max MPDU length: 11454
                            Supported Channel Width: neither 160 nor 80+80
                            short GI (80 MHz)
                            +HTC-VHT
                    VHT RX MCS set:
                            1 streams: MCS 0-9
                            2 streams: not supported
                            3 streams: not supported
                            4 streams: not supported
                            5 streams: not supported
                            6 streams: not supported
                            7 streams: not supported
                            8 streams: not supported
                    VHT RX highest supported: 434 Mbps
                    VHT TX MCS set:
                            1 streams: MCS 0-9
                            2 streams: not supported
                            3 streams: not supported
                            4 streams: not supported
                            5 streams: not supported
                            6 streams: not supported
                            7 streams: not supported
                            8 streams: not supported
                    VHT TX highest supported: 434 Mbps
                    VHT extended NSS: not supported
                    Bitrates (non-HT):
                            * 6.0 Mbps
                            * 9.0 Mbps
                            * 12.0 Mbps
                            * 18.0 Mbps
                            * 24.0 Mbps
                            * 36.0 Mbps
                            * 48.0 Mbps
                            * 54.0 Mbps
                    Frequencies:
                            * 5180 MHz [36] (17.0 dBm)
                            * 5200 MHz [40] (17.0 dBm)
                            * 5220 MHz [44] (17.0 dBm)
                            * 5240 MHz [48] (17.0 dBm)
                            * 5260 MHz [52] (17.0 dBm) (radar detection)
                            * 5280 MHz [56] (17.0 dBm) (radar detection)
                            * 5300 MHz [60] (17.0 dBm) (radar detection)
                            * 5320 MHz [64] (17.0 dBm) (radar detection)
                            * 5500 MHz [100] (17.0 dBm) (radar detection)
                            * 5520 MHz [104] (17.0 dBm) (radar detection)
                            * 5540 MHz [108] (17.0 dBm) (radar detection)
                            * 5560 MHz [112] (17.0 dBm) (radar detection)
                            * 5580 MHz [116] (17.0 dBm) (radar detection)
                            * 5600 MHz [120] (17.0 dBm) (radar detection)
                            * 5620 MHz [124] (17.0 dBm) (radar detection)
                            * 5640 MHz [128] (17.0 dBm) (radar detection)
                            * 5660 MHz [132] (17.0 dBm) (radar detection)
                            * 5680 MHz [136] (17.0 dBm) (radar detection)
                            * 5700 MHz [140] (17.0 dBm) (radar detection)
                            * 5720 MHz [144] (disabled)
                            * 5745 MHz [149] (17.0 dBm)
                            * 5765 MHz [153] (17.0 dBm)
                            * 5785 MHz [157] (17.0 dBm)
                            * 5805 MHz [161] (17.0 dBm)
                            * 5825 MHz [165] (17.0 dBm)
                            * 5845 MHz [169] (disabled)
                            * 5865 MHz [173] (disabled)
                            * 5885 MHz [177] (disabled)
            Supported commands:
                     * new_interface
                     * set_interface
                     * new_key
                     * start_ap
                     * new_station
                     * set_bss
                     * join_ibss
                     * set_pmksa
                     * del_pmksa
                     * flush_pmksa
                     * remain_on_channel
                     * frame
                     * set_channel
                     * connect
                     * disconnect
            WoWLAN support:
                     * wake up on anything (device continues operating normally)
            software interface modes (can always be added):
                     * monitor
            interface combinations are not supported
            Device supports SAE with AUTHENTICATE command
            Device supports scan flush.
            max # scan plans: 1
            max scan plan interval: -1
            max scan plan iterations: 0
            Supported TX frame types:
                     * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                     * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                     * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                     * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                     * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                     * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
            Supported RX frame types:
                     * IBSS: 0xd0
                     * managed: 0x40 0xb0 0xd0
                     * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                     * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                     * P2P-client: 0x40 0xd0
                     * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
            Supported extended features:
                    * [ RRM ]: RRM
    
    $ iperf3 -s
    -----------------------------------------------------------
    Server listening on 5201 (test #1)
    -----------------------------------------------------------
    Accepted connection from 10.16.0.4, port 56488
    [  5] local 10.16.0.10 port 5201 connected to 10.16.0.4 port 56500
    [ ID] Interval           Transfer     Bitrate
    [  5]   0.00-1.00   sec  3.65 MBytes  30.6 Mbits/sec                  
    [  5]   1.00-2.00   sec  3.58 MBytes  30.1 Mbits/sec                  
    [  5]   2.00-3.00   sec  3.94 MBytes  33.0 Mbits/sec                  
    [  5]   3.00-4.00   sec  6.16 MBytes  51.7 Mbits/sec                  
    [  5]   4.00-5.00   sec  6.59 MBytes  55.3 Mbits/sec                  
    [  5]   4.00-5.00   sec  6.59 MBytes  55.3 Mbits/sec                  
    - - - - - - - - - - - - - - - - - - - - - - - - -
    [ ID] Interval           Transfer     Bitrate
    [  5]   0.00-5.00   sec  25.5 MBytes  42.8 Mbits/sec                  receiver
    iperf3: the client has terminated
    
  • Had to re-install the driver to get the module working

    Had to re-install the driver to get the module working

    Hello,

    So I had installed the driver back in December of 2021. And it was working fine on Ubuntu 20.04. But then somewhere around May 2022. It stopped working for the new batch of EDUP wifi modules. As soon as I installed the new driver it started working.

    I suspect there is something with the new batch of EDUP modules that is the cause of this issue. Or a combination of both the driver and new batch. Now EDUP maintains that they have not changed dongle in any way. Is there a way to get log file that might point out what was the issue and why it is working with the new driver.

    I don't understand dmesg that much. But if there are some log files that I could get, that would shed some light into this issue that might help me a lot.

    [email protected]:~$ lsusb 
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 007: ID 14e1:3508 Dialogue Technology Corp. 
    Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
    Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 001 Device 006: ID 0bda:c820 Realtek Semiconductor Corp. USB Receiver
    Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
    Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    [email protected]:~$ mokutil --sb-state 
    This system doesn't support Secure Boot
    [email protected]:~$ rfkill list all
    0: hci0: Bluetooth
    	Soft blocked: no
    	Hard blocked: no
    1: phy0: Wireless LAN
    	Soft blocked: no
    	Hard blocked: no
    [email protected]:~$ dkms status
    rtl8821cu, 5.12.0, 5.13.0-41-generic, x86_64: installed
    rtl8821cu, 5.8.1.7, 5.13.0-40-generic, x86_64: installed
    rtl8821cu, 5.8.1.7, 5.13.0-41-generic, x86_64: built
    [email protected]:~$ iw dev
    phy#0
    	Interface wlxe84e0696e702
    		ifindex 3
    		wdev 0x1
    		addr e8:4e:06:96:e7:02
    		ssid Blue
    		type managed
    		channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
    		txpower 17.00 dBm
    [email protected]:~$ sudo uname -a
    Linux blue 5.13.0-41-generic #46~20.04.1-Ubuntu SMP Wed Apr 20 13:16:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
    [email protected]:~
    
  • Doesn't compile (unreachable instruction)

    Doesn't compile (unreachable instruction)

    Okay, first of all an information dump:

    Output of sudo uname -mr; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev; iw reg get:

    6.0.8-arch1-1 x86_64
    mokutil: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 003: ID 0bda:c820 Realtek Semiconductor Corp. 802.11ac NIC
    Bus 003 Device 004: ID 2808:9338 Focal-systems.Corp FT9201Fingerprint.̚
    Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
    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 004: ID 0edc:5830 HRY USB Camera
    Bus 001 Device 005: ID 05ac:12a8 Apple, Inc. iPhone 5/5C/5S/6/SE
    Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
    Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    0: hci0: Bluetooth
    	Soft blocked: no
    	Hard blocked: no
    rtl8821cu/5.12.0: added
    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)`
    

    Contents of make.log (the interesting part):

    CC [M]  /var/lib/dkms/rtl8821cu/5.12.0/build/core/rtw_mp.o
      LD [M]  /var/lib/dkms/rtl8821cu/5.12.0/build/8821cu.o
    /var/lib/dkms/rtl8821cu/5.12.0/build/8821cu.o: warning: objtool: mp_xmit_packet_thread+0x9e: unreachable instruction
      MODPOST /var/lib/dkms/rtl8821cu/5.12.0/build/Module.symvers
      CC [M]  /var/lib/dkms/rtl8821cu/5.12.0/build/8821cu.mod.o
      LD [M]  /var/lib/dkms/rtl8821cu/5.12.0/build/8821cu.ko
      BTF [M] /var/lib/dkms/rtl8821cu/5.12.0/build/8821cu.ko
    Failed to parse base BTF 'vmlinux': -22
    make[3]: *** [scripts/Makefile.modfinal:60: /var/lib/dkms/rtl8821cu/5.12.0/build/8821cu.ko] Error 1
    make[3]: *** Deleting file '/var/lib/dkms/rtl8821cu/5.12.0/build/8821cu.ko'
    make[2]: *** [scripts/Makefile.modpost:134: __modpost] Error 2
    make[1]: *** [Makefile:1766: modules] Error 2
    make[1]: Leaving directory '/usr/lib/modules/6.0.8-arch1-1/build'
    make: *** [Makefile:2503: modules] Error 2
    

    Full log: make.log

    OS: EndeavourOS Host: Gateway GWNR71517 Wifi (according to Gateway): Realtek AB b/g/n /RTL8821CU Current I have my iPhone usb tethered to provide internet.

    It's interesting that wifi doesn't even show up in rfkill or ifconfig, so I'm thinking that this may or may not even be a problem with this driver. Wifi works fine in windows however.

    If any other information is needed I will be happy to provide.

  • Totolink AC650UA can't connect on Pop OS

    Totolink AC650UA can't connect on Pop OS

    A brief description of the problem Followed the steps until install the driver then reboot. Adapter detected, attempt to connect but it keep asking password. Please I need a help.

    The name and version of the Linux distro PopOS 22.04

    The name and model of the computer Ryzen 5 2600, Asrock B450 Pro

    The information obtained

    5.19.0-76051900-generic x86_64
    SecureBoot disabled
    Platform is in Setup Mode
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
    Bus 003 Device 002: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio
    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 004: ID 2717:ff88 Xiaomi Inc. Mi/Redmi series (RNDIS + ADB)
    Bus 001 Device 003: ID 0bda:2006 Realtek Semiconductor Corp. 802.11ac NIC
    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
    rtl8821cu/5.12.0, 5.19.0-76051900-generic, x86_64: installed
    system76/1.0.14~1643391291~22.04~78ede46, 5.19.0-76051900-generic, x86_64: installed
    system76_acpi/1.0.2~1659568831~22.04~a88dcce, 5.19.0-76051900-generic, x86_64: installed (original_module exists)
    system76-io/1.0.2~1655490480~22.04~0217576, 5.19.0-76051900-generic, x86_64: installed
    phy#0
    	Interface wlx5c925ed335a2
    		ifindex 3
    		wdev 0x1
    		addr 5c:92:5e:d3:35:a2
    		type managed
    		txpower -100.00 dBm
    global
    country 00: DFS-UNSET
    	(2402 - 2472 @ 40), (6, 20), (N/A)
    	(2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
    	(2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
    	(5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
    	(5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
    	(5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN
    	(5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN
    	(57240 - 63720 @ 2160), (N/A, 0), (N/A)
    
  • Module not found

    Module not found

    I tried to install the driver on various linux distros: void, garuda, mint and the driver is installed (with dkms or with make) but I always get this message: "FATAL: Module rtl8821cu not found in directory /lib/modules/5.4.0-104-generic" . No wifi interface, whereas the bluetooth works rtl8821cu_log.txt .

  • failing to install on Raspberry Pi 3B+

    failing to install on Raspberry Pi 3B+

    Hi, I fail to install the driver on Raspberry Pi 3B+ with the following error:

    sudo ./install-driver.sh Running install-driver.sh version 20221018 5.15.61-v8+ aarch64 Installing rtw88_8821cu.conf to: /etc/modprobe.d Installing 8821cu.conf to: /etc/modprobe.d The dkms installation routines are in use. Copying source files to: /usr/src/rtl8821cu-5.12.0

    Creating symlink /var/lib/dkms/rtl8821cu/5.12.0/source -> /usr/src/rtl8821cu-5.12.0

    DKMS: add completed. Error! Your kernel headers for kernel 5.15.61-v8+ cannot be found. Please install the linux-headers-5.15.61-v8+ package, or use the --kernelsourcedir option to tell DKMS where it's located An error occurred. dkms build error = 1 Please report this error. Please copy all screen output and paste it into the report. Run the following before reattempting installation. $ sudo ./remove-driver.sh

    I am using Debian Bullseye 64-bit (Raspberry Pi Lite one) May I have some help here? Thanks

  • Very low speed and unstable on 6.0.2-2-MANJARO

    Very low speed and unstable on 6.0.2-2-MANJARO

    I have a AC650 MERCUSYS (MU6H) Wi-Fi begins work after install this driver, but with very low speed. Screen1 - on my phone Screen2 - pc 6.0.2-2-MANJARO image image

  • fix: build warning

    fix: build warning

    warning: cast between incompatible function types from ‘void ()(void )’ to ‘void ()(long unsigned int)’ The void type has been used, no need to convert to long unsigned type

  • D-Link DWA-171 AC600

    D-Link DWA-171 AC600

    Hi everyone,

    I recently bought this USB dongle quite naively believing that everything would be fine. When I plugged it into my Linux PC, I found out that I need to do some work before it actually works.

    I've managed to install the driver following all the instructions, especially ones found on this page. However, I didn't manage to get it working.

    Commands and their respective output is following:

    • cmd: uname -r
    • out: Linux goran-GL553VD 5.4.0-120-generic #136~18.04.1-Ubuntu SMP Fri Jun 10 18:00:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
    • cmd: mokutil --sb-state
    • out: SecureBoot disabled
    • cmd: lsusb
    • out:
     Bus 002 Device 002: ID 0bda:0423 Realtek Semiconductor Corp. 
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 005: ID 8087:0a2a Intel Corp. 
    Bus 001 Device 004: ID 0bda:57f5 Realtek Semiconductor Corp. 
    Bus 001 Device 003: ID 046d:0825 Logitech, Inc. Webcam C270
    Bus 001 Device 007: ID 0b05:1854 ASUSTek Computer, Inc. 
    Bus 001 Device 008: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 001 Device 006: ID 0bda:5423 Realtek Semiconductor Corp. 
    Bus 001 Device 002: ID 0bda:1a2b Realtek Semiconductor Corp. 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
    
    • cmd: rfkill list all
    • out:
    0: hci0: Bluetooth
    	Soft blocked: no
    	Hard blocked: no
    1: phy0: Wireless LAN
    	Soft blocked: no
    	Hard blocked: no
    
    • cmd: `dkms status:
    • out:
    evdi, 1.11.0, 5.4.0-120-generic, x86_64: installed
    evdi, 5.2.14: added
    nvidia, 470.129.06, 5.4.0-113-generic, x86_64: installed
    nvidia, 470.129.06, 5.4.0-120-generic, x86_64: installed
    rtl8821cu, 5.12.0, 5.4.0-120-generic, x86_64: installed
    
    • cmd: iw dev:
    • out:
    phy#0
    	Unnamed/non-netdev interface
    		wdev 0x2
    		addr e4:42:a6:6b:76:06
    		type P2P-device
    		txpower 0.00 dBm
    	Interface wlp2s0
    		ifindex 3
    		wdev 0x1
    		addr e4:42:a6:6b:76:05
    		ssid dlink-65C0
    		type managed
    		channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
    		txpower 22.00 dBm
    
    • cmd : dmesg | grep usb
    • out:
    [  368.310547] usb 1-10.3: USB disconnect, device number 10
    [ 1390.240303] usb 1-1: USB disconnect, device number 2
    [ 1392.340366] usb 1-1: new high-speed USB device number 11 using xhci_hcd
    [ 1392.488976] usb 1-1: New USB device found, idVendor=0bda, idProduct=1a2b, bcdDevice= 2.00
    [ 1392.488978] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 1392.488979] usb 1-1: Product: DISK
    [ 1392.488980] usb 1-1: Manufacturer: D-Link Corporation
    [ 1392.490272] usb-storage 1-1:1.0: USB Mass Storage device detected
    [ 1392.490593] scsi host3: usb-storage 1-1:1.0
    

    I know that i have one WiFi interface already running, but I would really need to have 2 different WiFi interfaces and that's why I'm trying to get it up and running.

    Thank you for your help.

  • Struggle to build on Pi 4 B (1GB)

    Struggle to build on Pi 4 B (1GB)

    When running install-driver on Raspberry Pi 4 model B with 1GB RAM running 64-bit Raspberry Pi OS 11, compilation is incredibly slow and may fail (with a SIGKILL). This is reproducible. When used previously with same hardware running 32-bit Raspberry Pi OS 10, the problem didn't occur.

    Appears to be because the "-j5" make flag causes all available RAM to be used and the device to start swapping. A simple workaround is to edit dkms.conf, replacing -j$(nproc) by -j1 (which actually makes it faster and complete successfully).

    Is there some way the install script could automatically reduce the number of simultaneous jobs in this scenario?

    P.S. Thanks for supporting these adapters. I have 8821cu (as client with BrosTrend AC650 AC5L) and 88x2bu (as AP with BrosTrend AC1200 AC3L) working well on the same Pi 4, used as firewall/gateway.

  • (info) help with kali wireless

    (info) help with kali wireless

    i am VERY new to linux, i cannot seem to enablke my realtek 8821CE device i have tried to install the compat driver among other "things" i really need some help i am connected through virtual box using my laptops wireless so i have connectivity but i wish to use some aircrack and i cannot see any wireless networks help!

  • (hot) Need Testers for a new version of this driver...

    (hot) Need Testers for a new version of this driver...

    Hello Everyone,

    Myself and another individual have been working to bring a new version of this driver online. It is based on new source code from Realtek and it appears to fix a few things. We are also taking the opportunity to greatly enhance the installation and removal scripts as well as the README. This work will then be used on all Realtek drivers located at this site so it is important that we test. Testing is currently being done in a private repo with an expected release during the first quarter of next year.

    If you are interested in testing, please reply to this message.

    Nick

  • (info) fails on latest 5.15.76-v7+ (raspian)

    (info) fails on latest 5.15.76-v7+ (raspian)

    Fails on the latest Nov 2022 release tried building from src as well same result

    Running Raspian Lite

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

    
    [email protected]<serial>:~/8821cu-20210118 $ sudo ./install-driver.sh
    Running install-driver.sh version 20221101
    Kernel=5.15.76-v7+
    Architecture=armv7l
    Installing rtw88_8821cu.conf to: /etc/modprobe.d
    Installing 8821cu.conf to: /etc/modprobe.d
    The dkms installation routines are in use.
    Copying source files to: /usr/src/rtl8821cu-5.12.0
    
    Creating symlink /var/lib/dkms/rtl8821cu/5.12.0/source ->
                     /usr/src/rtl8821cu-5.12.0
    
    DKMS: add completed.
    The driver was added successfully.
    
    Kernel preparation unnecessary for this kernel.  Skipping...
    
    Building module:
    cleaning build area...
    'make' -j4 KVER=5.15.76-v7+ KSRC=/lib/modules/5.15.76-v7+/build...(bad exit status: 2)
    Error! Bad return status for module build on kernel: 5.15.76-v7+ (armv7l)
    Consult /var/lib/dkms/rtl8821cu/5.12.0/build/make.log for more information.
    An error occurred. dkms build error = 10
    Please report this error.
    Please copy all screen output and paste it into the report.
    Run the following before reattempting installation.
    
    $ sudo ./remove-driver.sh
    [email protected]<serial>:~/8821cu-20210118 $ sudo ./remove-driver.sh
    Running remove-driver.sh version 20221101
    Kernel=5.15.76-v7+
    Architecture=armv7l
    
    ------------------------------
    Deleting module version: 5.12.0
    completely from the DKMS tree.
    ------------------------------
    Done.
    rtl8821cu/5.12.0 has been removed
    If older versions of rtl8821cu are installed, run:
    $ sudo dkms remove rtl8821cu/<version> --all
    dkms shows the following drivers are still installed:
    Removing rtw88_8821cu.conf from /etc/modprobe.d
    Removing 8821cu.conf from /etc/modprobe.d
    Removing source files from /usr/src/rtl8821cu-5.12.0
    The driver was removed successfully.
    You may now delete the driver directory if desired.
    Do you want to reboot now? (recommended) [y/N]
    
Linux Driver for USB WiFi Adapters that are based on the RTL8812BU and RTL8822BU Chipsets

Click for USB WiFi Adapter Information for Linux 88x2bu ( 88x2bu.ko ) ?? Linux Driver for USB WiFi Adapters that are based on the RTL8812BU and RTL882

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