Linux Driver for USB WiFi Adapters that are based on the RTL8812AU Chipset - v5.13.6

Overview

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 include the information obtained with the following command:

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

8812au ( 8812au.ko ) 🚀

Linux Driver for USB WiFi Adapters that are based on the RTL8812AU Chipset

  • v5.13.6 (Realtek) (20210629)
  • 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 issue #17)
  • 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
    • AP (see Bridged_Wireless_Access_Point.md the docs folder.)
    • Monitor (see Monitor_Mode.md in the docs folder.)
    • P2P-client
    • P2P-GO
    • Concurrent (see Concurrent_Mode.md in the docs folder.)
  • 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
  • AP mode DFS channel control
  • USB mode control

Compatible CPUs

  • x86, amd64
  • ARM, ARM64
  • MIPS

Compatible Kernels

  • Kernels: 4.4 - 5.11 (Realtek)
  • Kernels: 5.12 - 5.16 (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.13)

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

Download Locations for Tested Linux Distributions

Tested Hardware

Compatible Devices

  • ALFA AWUS036AC
  • ALFA AWUS036ACH
  • ALFA AWUS036EAC
  • ASUS USB-AC56 Dual-Band AC1200 Adapter (H/W ver. A1)
  • Belkin F9L1109
  • Buffalo - WI-U3-866D
  • Edimax EW-7822UAC
  • Linksys WUSB6300 V1
  • Rosewill RNX-AC1200UBE
  • TRENDnet TEW-805UB
  • Numerous adapters that are based on the supported chipset.

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

  • Option for Debian based distributions such as Ubuntu, Linux Mint, 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

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.

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 and Linux Mint Debian Edition (LMDE)
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
  • 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 reinstall 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/8812au-20210629.git

Step 7: Move to the newly created driver directory

cd ~/src/8812au-20210629

Step 8: Enable Concurrent Mode (optional)

Note: see Concurrent_Mode.md in the docs folder.

./cmode-on.sh

Step 9: Run a script to reconfigure the driver for Raspberry Pi hardware

Warning: This step only applies if you are installing to Raspberry Pi hardware.

Warning: You should skip this step if installing to x86 or amd64 based systems.

  • Option for the 32 bit Raspberry Pi OS to be installed to Raspberry Pi hardware
./raspiOS-32.sh
  • Option for the 64 bit Raspberry Pi OS to be installed to Raspberry Pi hardware
./raspiOS-64.sh

Note: Use the 64 bit option for other 64 bit operating systems to be installed to Raspberry Pi hardware. An example is Ubuntu for Raspberry Pi.

Note: Other ARM or ARM64 based systems will likely require modifications similar to those provided in the above scripts for Raspberry Pi hardware 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.

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

Driver Options

A file called 8812au.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/8812au.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 8812au.conf.

Removal of the Driver

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

  • if driver installation fails
  • if the driver is no longer needed
  • if a fresh start with default settings is needed
  • if a new 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/8812au-20210629

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.

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

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

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 with some current Linux distros, you will need to download, compile and install the current development version of wpa_supplicant at the following site:

https://w1.fi/cgit/

See issue #17

Question: I bought two rtl8812au 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. However, testing has shown that the Mediatek drivers do support more than one adapter with the same chipset in various configurations.

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 (mac80211) for USB WiFi adapters and the drivers are not maintained in the Linux kernel. These issues make Realtek drivers problematic in many ways. You have been WARNED. For more information about USB WiFi adapters:

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: The following article may help:

https://null-byte.wonderhowto.com/forum/wifi-hacking-attach-usb-wireless-adapter-with-virtual-box-0324433/

Comments
  • ap 5G(802.11n)  is unstable

    ap 5G(802.11n) is unstable

    /etc/modprobe.d/8812au.conf

    options 8812au rtw_drv_log_level=4 rtw_vht_enable=1 rtw_power_mgnt=0 rtw_beamform_cap=1 rtw_switch_usb_mode=2

    hostapd.conf

    interface=hotspot driver=nl80211 logger_syslog=-1 logger_syslog_level=2 logger_stdout=-1 logger_stdout_level=2 ctrl_interface=/var/run/hostapd ctrl_interface_group=0 country_code=US max_num_sta=255 macaddr_acl=0 auth_algs=1 ignore_broadcast_ssid=0 ap_max_inactivity=300 eapol_key_index_workaround=0 eap_server=0 own_ip_addr=127.0.0.1

    ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40] #vht_capab=[MAX-MPDU-11454][SHORT-GI-80][SU-BEAMFORMER][HTC-VHT] #vht_oper_chwidth=1

    ieee80211n=1 wmm_enabled=1

    wpa=2 wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP

    hw_mode=a channel=36 ssid=xxxx wpa_passphrase=xxxxxxxx

    dmesg

    [16080.360494] RTW: OnAction_back [16080.360518] RTW: OnAction_back, action=0 [16080.361219] RTW: issue_addba_rsp_wait_ack(hotspot) ra=d4:6d:6d:fa:9b:eb status:=0 tid=0 size:64, acked, 1/3 in 0 ms [16085.714850] RTW: OnAction_back [16085.714870] RTW: OnAction_back, action=2 [16085.714880] RTW: OnAction_back(): DELBA: 0(0) [16090.302208] RTW: OnAction_back [16090.302227] RTW: OnAction_back, action=0 [16090.302889] RTW: issue_addba_rsp_wait_ack(hotspot) ra=d4:6d:6d:fa:9b:eb status:=0 tid=0 size:64, acked, 1/3 in 0 ms [16095.784811] RTW: OnAction_back [16095.784841] RTW: OnAction_back, action=2 [16095.784863] RTW: OnAction_back(): DELBA: 0(0) [16100.275394] RTW: OnAction_back [16100.275404] RTW: OnAction_back, action=0 [16100.276274] RTW: issue_addba_rsp_wait_ack(hotspot) ra=d4:6d:6d:fa:9b:eb status:=0 tid=0 size:64, acked, 1/3 in 0 ms [16105.458923] RTW: OnAction_back [16105.458957] RTW: OnAction_back, action=2 [16105.458974] RTW: OnAction_back(): DELBA: 0(0) [16110.273053] RTW: OnAction_back [16110.273072] RTW: OnAction_back, action=0 [16110.274130] RTW: issue_addba_rsp_wait_ack(hotspot) ra=d4:6d:6d:fa:9b:eb status:=0 tid=0 size:64, acked, 1/3 in 0 ms [16116.477928] RTW: OnAction_back [16116.477958] RTW: OnAction_back, action=2 [16116.477976] RTW: OnAction_back(): DELBA: 0(0)

    [16118.583465] RTW: +OnAuth [16118.583480] RTW: auth alg=0, seq=1 [16118.583517] RTW: issue_auth [16118.585552] RTW: OnAssocReq [16118.585580] RTW: OnAssocReq(hotspot) old AID=2 [16118.585598] RTW: HT: STA d4:6d:6d:fa:9b:eb HT Capabilities Info: 0x09e7 [16118.585620] RTW: bss_cap_update_on_sta_join STA d4:6d:6d:fa:9b:eb - no greenfield, num of non-gf stations 3 [16118.585642] RTW: rtw_ht_operation_update current operation mode=0x15 [16118.585655] RTW: rtw_ht_operation_update new operation mode=0x15 changes=0 [16118.585666] RTW: bss_cap_update_on_sta_join, updated=0 [16118.585677] RTW: update_sta_info_apmode [16118.585727] RTW: issue_del_ba(hotspot) ra=d4:6d:6d:fa:9b:eb reason=37, tid=0, initiator=1 [16118.585750] RTW: ### Set STA_(3) info ### [16118.585775] RTW: issue_asocrsp [16118.585812] RTW: report_add_sta_event: add STA [16118.587225] RTW: rtw_get_sta_tx_nss: 2 SS [16118.587240] RTW: rtw_get_sta_rx_nss: 2 ss [16118.587252] RTW: STA - MAC_ID:3, Tx - 2 SS, Rx - 2 SS [16118.587263] RTW: STA - MAC_ID:3, SM_PS 3 [16118.587279] RTW: ht_mcs_set=ff ff 00 00, nss=1, bitmap=000000ff [16118.587293] RTW: rtw_ap_update_sta_ra_info=> mac_id:3 , tx_ra_bitmap:0x00000000000ffff0, networkType:0x14 [16118.588462] RTW: ============ STA [d4:6d:6d:fa:9b:eb] =================== [16118.588484] RTW: mac_id : 3 [16118.588495] RTW: wireless_mode : 0x14 [16118.588506] RTW: mimo_type : 2 [16118.588517] RTW: static smps : N [16118.588528] RTW: bw_mode : 40MHz, ra_bw_mode : 40MHz [16118.588538] RTW: rate_id : 4 [16118.588549] RTW: rssi : 50 (%), rssi_level : 5 [16118.588560] RTW: is_support_sgi : Y, is_vht_enable : N [16118.588571] RTW: disable_ra : N, disable_pt : N [16118.588582] RTW: is_noisy : Y [16118.588592] RTW: txrx_state : 2 [16118.588603] RTW: curr_tx_rate : MCS7 (S) [16118.588614] RTW: curr_tx_bw : CHANNEL_WIDTH_MAX [16118.588624] RTW: curr_retry_ratio : 255 [16118.588635] RTW: ra_mask : 0x00000000000ffff0

    [16118.588647] RTW: indicate_sta_assoc_event to upper layer - hostapd [16118.588662] RTW: rtw_cfg80211_indicate_sta_assoc(hotspot) [16118.588709] RTW: rtw_set_rts_bw connect_to_8812=0,enable=1 [16118.589200] RTW: cfg80211_rtw_change_station(hotspot) mac:d4:6d:6d:fa:9b:eb [16118.589460] RTW: cfg80211_rtw_del_key(hotspot) key_index=0, addr=d4:6d:6d:fa:9b:eb [16118.589586] RTW: cfg80211_rtw_del_key(hotspot) key_index=0, addr=d4:6d:6d:fa:9b:eb [16118.590194] RTW: send eapol packet 1/4 [16118.593882] RTW: recv eapol packet 2/4 [16118.594269] RTW: cfg80211_rtw_get_key(hotspot) keyid=1, pairwise=0, addr=(null) ret 0 [16118.594282] RTW: cfg80211_rtw_get_key(hotspot) seq:0x1a4 [16118.594446] RTW: send eapol packet 3/4 [16118.598708] RTW: recv eapol packet 4/4 [16118.599090] RTW: cfg80211_rtw_add_key(hotspot) adding key for d4:6d:6d:fa:9b:eb [16118.599108] RTW: cfg80211_rtw_add_key(hotspot) cipher=0xfac04 [16118.599129] RTW: cfg80211_rtw_add_key(hotspot) key_len=16, key_index=0 [16118.599143] RTW: cfg80211_rtw_add_key(hotspot) pairwise=1 [16118.599157] RTW: rtw_cfg80211_ap_set_encryption [16118.599175] RTW: rtw_cfg80211_ap_set_encryption(hotspot) set CCMP PTK of d4:6d:6d:fa:9b:eb idx:0, len:16 [16118.599275] RTW: cfg80211_rtw_change_station(hotspot) mac:d4:6d:6d:fa:9b:eb [16118.599534] RTW: set pairwise key camid:2, addr:d4:6d:6d:fa:9b:eb, kid:0, type:AES [16118.686759] RTW: rtw_issue_addbareq_cmd, p=0 [16118.686910] RTW: BA_starting_seqctrl = 47 for TID=0 [16118.686930] RTW: issue_addba_req(hotspot) ra=d4:6d:6d:fa:9b:eb tid=0 [16118.688798] RTW: OnAction_back [16118.688807] RTW: OnAction_back, action=1 [16118.688812] RTW: agg_enable for TID=0 [16120.459968] RTW: OnAction_back [16120.459977] RTW: OnAction_back, action=0 [16120.468080] RTW: issue_addba_rsp_wait_ack(hotspot) ra=d4:6d:6d:fa:9b:eb status:=0 tid=0 size:64, acked, 1/3 in 0 ms [16125.620854] RTW: OnAction_back [16125.620876] RTW: OnAction_back, action=2 [16125.620887] RTW: OnAction_back(): DELBA: 0(0) [16130.212910] RTW: OnAction_back [16130.212927] RTW: OnAction_back, action=0 [16130.214179] RTW: issue_addba_rsp_wait_ack(hotspot) ra=d4:6d:6d:fa:9b:eb status:=0 tid=0 size:64, acked, 1/3 in 0 ms [16136.843793] RTW: +OnAuth [16136.843801] RTW: auth alg=0, seq=1 [16136.843818] RTW: issue_auth [16136.853851] RTW: OnAssocReq [16136.853872] RTW: OnAssocReq(hotspot) old AID=2 [16136.853881] RTW: HT: STA d4:6d:6d:fa:9b:eb HT Capabilities Info: 0x09e7 [16136.853887] RTW: bss_cap_update_on_sta_join STA d4:6d:6d:fa:9b:eb - no greenfield, num of non-gf stations 3 [16136.853894] RTW: rtw_ht_operation_update current operation mode=0x15 [16136.853899] RTW: rtw_ht_operation_update new operation mode=0x15 changes=0 [16136.853904] RTW: bss_cap_update_on_sta_join, updated=0 [16136.853910] RTW: update_sta_info_apmode [16136.853937] RTW: issue_del_ba(hotspot) ra=d4:6d:6d:fa:9b:eb reason=37, tid=0, initiator=0 [16136.853954] RTW: issue_del_ba(hotspot) ra=d4:6d:6d:fa:9b:eb reason=37, tid=0, initiator=1 [16136.853961] RTW: ### Set STA_(3) info ### [16136.853968] RTW: issue_asocrsp [16136.853993] RTW: report_add_sta_event: add STA [16136.855180] RTW: rtw_get_sta_tx_nss: 2 SS [16136.855186] RTW: rtw_get_sta_rx_nss: 2 ss [16136.855192] RTW: STA - MAC_ID:3, Tx - 2 SS, Rx - 2 SS [16136.855197] RTW: STA - MAC_ID:3, SM_PS 3 [16136.855204] RTW: ht_mcs_set=ff ff 00 00, nss=1, bitmap=000000ff [16136.855211] RTW: rtw_ap_update_sta_ra_info=> mac_id:3 , tx_ra_bitmap:0x00000000000ffff0, networkType:0x14 [16136.856310] RTW: ============ STA [d4:6d:6d:fa:9b:eb] =================== [16136.856316] RTW: mac_id : 3 [16136.856322] RTW: wireless_mode : 0x14 [16136.856327] RTW: mimo_type : 2 [16136.856332] RTW: static smps : N [16136.856337] RTW: bw_mode : 40MHz, ra_bw_mode : 40MHz [16136.856342] RTW: rate_id : 4 [16136.856347] RTW: rssi : 51 (%), rssi_level : 5 [16136.856353] RTW: is_support_sgi : Y, is_vht_enable : N [16136.856358] RTW: disable_ra : N, disable_pt : N [16136.856363] RTW: is_noisy : Y [16136.856368] RTW: txrx_state : 2 [16136.856374] RTW: curr_tx_rate : MCS7 (S) [16136.856378] RTW: curr_tx_bw : CHANNEL_WIDTH_MAX [16136.856383] RTW: curr_retry_ratio : 255 [16136.856388] RTW: ra_mask : 0x00000000000ffff0

    [16136.856394] RTW: indicate_sta_assoc_event to upper layer - hostapd [16136.856402] RTW: rtw_cfg80211_indicate_sta_assoc(hotspot) [16136.856431] RTW: rtw_set_rts_bw connect_to_8812=0,enable=1 [16136.856745] RTW: cfg80211_rtw_change_station(hotspot) mac:d4:6d:6d:fa:9b:eb [16136.856843] RTW: cfg80211_rtw_del_key(hotspot) key_index=0, addr=d4:6d:6d:fa:9b:eb [16136.856906] RTW: cfg80211_rtw_del_key(hotspot) key_index=0, addr=d4:6d:6d:fa:9b:eb [16136.857241] RTW: send eapol packet 1/4 [16136.859782] RTW: recv eapol packet 2/4 [16136.860255] RTW: cfg80211_rtw_get_key(hotspot) keyid=1, pairwise=0, addr=(null) ret 0 [16136.860263] RTW: cfg80211_rtw_get_key(hotspot) seq:0x1b1 [16136.860354] RTW: send eapol packet 3/4 [16136.865443] RTW: recv eapol packet 4/4 [16136.865725] RTW: cfg80211_rtw_add_key(hotspot) adding key for d4:6d:6d:fa:9b:eb [16136.865736] RTW: cfg80211_rtw_add_key(hotspot) cipher=0xfac04 [16136.865742] RTW: cfg80211_rtw_add_key(hotspot) key_len=16, key_index=0 [16136.865747] RTW: cfg80211_rtw_add_key(hotspot) pairwise=1 [16136.865754] RTW: rtw_cfg80211_ap_set_encryption [16136.865763] RTW: rtw_cfg80211_ap_set_encryption(hotspot) set CCMP PTK of d4:6d:6d:fa:9b:eb idx:0, len:16 [16136.865792] RTW: set pairwise key camid:2, addr:d4:6d:6d:fa:9b:eb, kid:0, type:AES [16136.865810] RTW: cfg80211_rtw_change_station(hotspot) mac:d4:6d:6d:fa:9b:eb [16137.500476] RTW: rtw_issue_addbareq_cmd, p=0 [16137.500538] RTW: BA_starting_seqctrl = 3177 for TID=0 [16137.500576] RTW: issue_addba_req(hotspot) ra=d4:6d:6d:fa:9b:eb tid=0 [16137.502292] RTW: OnAction_back [16137.502328] RTW: OnAction_back, action=1 [16137.502344] RTW: agg_enable for TID=0 [16145.354805] RTW: issue_nulldata(hotspot) to d4:6d:6d:fa:9b:eb, ch:36, 3/3 in 150 ms [16145.354824] RTW: expire_timeout_chk(hotspot) asoc check, d4:6d:6d:fa:9b:eb keep_alive_trycnt=1 [16147.422665] RTW: issue_nulldata(hotspot) to d4:6d:6d:fa:9b:eb, ch:36, 3/3 in 140 ms [16147.422683] RTW: expire_timeout_chk(hotspot) asoc check, d4:6d:6d:fa:9b:eb keep_alive_trycnt=2 [16149.502705] RTW: issue_nulldata(hotspot) to d4:6d:6d:fa:9b:eb, ch:36, 3/3 in 140 ms [16149.502725] RTW: expire_timeout_chk(hotspot) asoc check, d4:6d:6d:fa:9b:eb keep_alive_trycnt=3 [16151.582799] RTW: issue_nulldata(hotspot) to d4:6d:6d:fa:9b:eb, ch:36, 3/3 in 140 ms [16151.582811] RTW: expire_timeout_chk(hotspot) asoc expire d4:6d:6d:fa:9b:eb, state=0x4001 [16151.582823] RTW: rtw_cfg80211_indicate_sta_disassoc(hotspot) [16151.582850] RTW: rtw_ht_operation_update current operation mode=0x15 [16151.582856] RTW: rtw_ht_operation_update new operation mode=0x15 changes=0 [16151.582861] RTW: bss_cap_update_on_sta_leave, updated=0 [16151.582870] RTW: rtw_stadel_event_callback(mac_id=3)=d4:6d:6d:fa:9b:eb [16151.582876] RTW: rtw_sta_mstatus_disc_rpt(hotspot) - mac_id=3 [16151.583139] RTW: cfg80211_rtw_del_key(hotspot) key_index=0, addr=d4:6d:6d:fa:9b:eb [16151.583216] RTW: cfg80211_rtw_del_key(hotspot) key_index=0, addr=d4:6d:6d:fa:9b:eb [16151.583262] RTW: cfg80211_rtw_change_station(hotspot) mac:d4:6d:6d:fa:9b:eb [16151.583323] RTW: +cfg80211_rtw_del_station(hotspot) mac=d4:6d:6d:fa:9b:eb [16151.583329] RTW: free sta macaddr =d4:6d:6d:fa:9b:eb [16151.583337] RTW: -cfg80211_rtw_del_station(hotspot) [16151.583933] RTW: start_addr=1026, data_H:00010500, data_L:80005010, macid=3, txrpt_h4b=10500 [16151.585556] RTW: hotspot wakeup macid=3, ori reg_0x4d4=0x00000000 [16151.585610] RTW: ### Clean STA_(3) info ### [16151.585618] RTW: rtw_release_macid(hotspot) if1, mac_addr:d4:6d:6d:fa:9b:eb macid:3 [16151.585628] RTW: rtw_set_rts_bw connect_to_8812=0,enable=1 [16151.585930] RTW: report_del_sta_event(hotspot) d4:6d:6d:fa:9b:eb mac_id=3, enqueue:0, res:1 [16151.585938] RTW: clear key for addr:d4:6d:6d:fa:9b:eb, camid:2

    opened by wanglouxiaozi 13
  • Linux verion 5.19.0+ hang and BUG: scheduling while atomic: swapper/1/0/0x00000504

    Linux verion 5.19.0+ hang and BUG: scheduling while atomic: swapper/1/0/0x00000504

    At first kenel hang is cansed on Linux version 5.19.0+ after 8812au.ko loaded. (Note: I have fixed the build error on Linux version 5.19.0+ locally to build 8812au.kio.) Then I changed the log level to 1: always to try to debug but the issue was not caused. (Note: Before the log leve change the issue was caused repeated every time.)

    CONFIG_RTW_LOG_LEVEL = 1
    

    To make sure I check the dmesg log but the folloing error message was recoreded.

    ...
    [ 2192.904736] RTW: rtw_ndev_init(wlan0) if1 mac_addr=60:84:bd:f0:58:b8
    [ 2192.905124] usbcore: registered new interface driver rtl8812au
    [ 2192.905127] RTW: module init ret=0
    [ 2192.909604] rtl8812au 1-3:1.0 wlx6084bdf058b8: renamed from wlan0
    [ 2194.493842] IPv6: ADDRCONF(NETDEV_CHANGE): wlx6084bdf058b8: link becomes ready
    [ 2198.798658] RTW: rtw_set_802_11_connect(wlx6084bdf058b8)  fw_state=0x00000008
    [ 2199.116467] RTW: start auth
    [ 2199.118372] RTW: auth success, start assoc
    [ 2199.126486] BUG: scheduling while atomic: swapper/1/0/0x00000504
    [ 2199.126495] Modules linked in: 8812au(OE) uhid rfcomm nvme_fabrics cmac algif_hash algif_skcipher af_alg xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nouveau nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables libcrc32c nfnetlink bridge stp llc snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio iwlmvm snd_hda_intel bnep snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr intel_rapl_common snd_usb_audio snd_hda_core video snd_usbmidi_lib snd_hwdep edac_mce_amd drm_ttm_helper mac80211 ttm snd_pcm drm_display_helper uvcvideo snd_seq_midi snd_seq_midi_event kvm_amd snd_rawmidi libarc4 videobuf2_vmalloc videobuf2_memops btusb kvm videobuf2_v4l2 snd_seq iwlwifi videobuf2_common cec btrtl btbcm crct10dif_pclmul ghash_clmulni_intel btintel videodev rc_core aesni_intel btmtk snd_seq_device drm_kms_helper snd_timer crypto_simd bluetooth nls_iso8859_1 cryptd cfg80211 snd mc fb_sys_fops joydev ccp
    [ 2199.126915]  syscopyarea sysfillrect input_leds rapl sysimgblt ecdh_generic serio_raw wmi_bmof ecc k10temp mxm_wmi soundcore mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler drm msr parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvme igb nvme_core crc32_pclmul i2c_algo_bit ahci xhci_pci i2c_piix4 libahci dca xhci_pci_renesas wmi
    [ 2199.127082] Preemption disabled at:
    [ 2199.127085] [<ffffffffb58bed2b>] copy_process+0x12b/0x1c10
    [ 2199.127101] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G           OE      5.19.0+ #4
    [ 2199.127107] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P4.60 08/03/2021
    [ 2199.127109] Call Trace:
    [ 2199.127112]  <IRQ>
    [ 2199.127116]  dump_stack_lvl+0x49/0x63
    [ 2199.127122]  ? copy_process+0x12b/0x1c10
    [ 2199.127126]  dump_stack+0x10/0x16
    [ 2199.127129]  __schedule_bug.cold+0x81/0x92
    [ 2199.127135]  __schedule+0xe6a/0x1470
    [ 2199.127141]  ? __mod_timer+0x21d/0x470
    [ 2199.127148]  schedule+0x6b/0x110
    [ 2199.127152]  schedule_timeout+0x87/0x160
    [ 2199.127156]  ? timer_migration_handler+0xa0/0xa0
    [ 2199.127161]  wait_for_completion_timeout+0x7d/0x140
    [ 2199.127166]  usb_start_wait_urb+0x8f/0x180
    [ 2199.127172]  usb_control_msg+0xe3/0x150
    [ 2199.127179]  usbctrl_vendorreq+0x355/0x42b [8812au]
    [ 2199.127289]  usb_read8+0x3e/0x5c [8812au]
    [ 2199.127389]  _rtw_read8+0x1f/0x25 [8812au]
    [ 2199.127463]  SwLedOn_8812AU+0xf2/0x17e [8812au]
    [ 2199.127556]  SwLedControlMode14+0xeb/0x1cb [8812au]
    [ 2199.127646]  LedControlUSB+0x1f0f/0x1f14 [8812au]
    [ 2199.127729]  rtw_led_control+0x79/0xc4 [8812au]
    [ 2199.127812]  rtw_indicate_connect+0x39/0x6b [8812au]
    [ 2199.127889]  rtw_joinbss_event_prehandle+0x2cf/0x795 [8812au]
    [ 2199.127964]  report_join_res+0xcc/0x11d [8812au]
    [ 2199.128025]  OnAssocRsp+0x1d8/0x317 [8812au]
    [ 2199.128083]  _mgt_dispatcher+0x73/0xaf [8812au]
    ...
    

    I am not sure if the error log is related the hang issue or not. (Note: The error log is only confirmed at the fist time after the log level change but not tested to repeat yet.) If any advice or comment about the issue and error please let me know. Note: Before I used rtl8812au-5.6.4.2 below also and some time found similar the hang issue but it was not repeated after reboot. ~~https://github.com/ikegami-t/rtl8812au-5.6.4.2~~ https://github.com/gordboy/rtl8812au-5.6.4.2 FYI: The local changes are below. (Note: I am thinking to creat a pull request but the changes will be updated.)

    [email protected]:~/8812au-20210629$ git diff
    diff --git a/Makefile b/Makefile
    index c80b777..053f40b 100644
    --- a/Makefile
    +++ b/Makefile
    @@ -111,7 +111,7 @@ endif
     CONFIG_RTW_DEBUG = y
     # default log level is _DRV_INFO_ = 4,
     # please refer to "How_to_set_driver_debug_log_level.doc" to set the available level.
    -CONFIG_RTW_LOG_LEVEL = 0
    +CONFIG_RTW_LOG_LEVEL = 1
    
     # enable /proc/net/rtlxxxx/ debug interfaces
     CONFIG_PROC_DEBUG = y
    diff --git a/os_dep/linux/ioctl_cfg80211.c b/os_dep/linux/ioctl_cfg80211.c
    index 791cd4c..03b9532 100644
    --- a/os_dep/linux/ioctl_cfg80211.c
    +++ b/os_dep/linux/ioctl_cfg80211.c
    @@ -475,7 +475,7 @@ u8 rtw_cfg80211_ch_switch_notify(_adapter *adapter, u8 ch, u8 bw, u8 offset,
            if (!rtw_cfg80211_allow_ch_switch_notify(adapter))
                    goto exit;
    
    -       cfg80211_ch_switch_notify(adapter->pnetdev, &chdef);
    +       cfg80211_ch_switch_notify(adapter->pnetdev, &chdef, 0);
    
     #else
            int freq = rtw_ch2freq(ch);
    @@ -490,7 +490,7 @@ u8 rtw_cfg80211_ch_switch_notify(_adapter *adapter, u8 ch, u8 bw, u8 offset,
            }
    
            ctype = rtw_chbw_to_nl80211_channel_type(ch, bw, offset, ht);
    -       cfg80211_ch_switch_notify(adapter->pnetdev, freq, ctype);
    +       cfg80211_ch_switch_notify(adapter->pnetdev, freq, ctype, 0);
     #endif
    
     exit:
    @@ -1139,7 +1139,7 @@ check_bss:
                    #endif
    
                    #if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 12, 0)
    -               roam_info.bssid = cur_network->network.MacAddress;
    +               roam_info.links[0].bssid = cur_network->network.MacAddress;
                    roam_info.req_ie = pmlmepriv->assoc_req + sizeof(struct rtw_ieee80211_hdr_3addr) + 2;
                    roam_info.req_ie_len = pmlmepriv->assoc_req_len - sizeof(struct rtw_ieee80211_hdr_3addr) - 2;
                    roam_info.resp_ie = pmlmepriv->assoc_rsp + sizeof(struct rtw_ieee80211_hdr_3addr) + 6;
    @@ -5377,7 +5377,8 @@ static int cfg80211_rtw_change_beacon(struct wiphy *wiphy, struct net_device *nd
            return ret;
     }
    
    -static int cfg80211_rtw_stop_ap(struct wiphy *wiphy, struct net_device *ndev)
    +static int cfg80211_rtw_stop_ap(struct wiphy *wiphy, struct net_device *ndev,
    +               unsigned int link_id)
     {
            _adapter *adapter = (_adapter *)rtw_netdev_priv(ndev);
    
    @@ -6753,7 +6754,7 @@ exit:
    
     #if (LINUX_VERSION_CODE >= KERNEL_VERSION(3, 8, 0))
     static int cfg80211_rtw_get_channel(struct wiphy *wiphy,
    -       struct wireless_dev *wdev,
    +       struct wireless_dev *wdev, unsigned int link_id,
            struct cfg80211_chan_def *chandef)
     {
            _adapter *padapter = wiphy_to_adapter(wiphy);
    @@ -10692,7 +10693,7 @@ void rtw_wdev_unregister(struct wireless_dev *wdev)
            rtw_cfg80211_indicate_scan_done(adapter, _TRUE);
    
            #if (LINUX_VERSION_CODE >= KERNEL_VERSION(3, 11, 0)) || defined(COMPAT_KERNEL_RELEASE)
    -       if (wdev->current_bss) {
    +       if (wdev->links[0].client.current_bss) {
                    RTW_INFO(FUNC_ADPT_FMT" clear current_bss by cfg80211_disconnected\n", FUNC_ADPT_ARG(adapter));
                    rtw_cfg80211_indicate_disconnect(adapter, 0, 1);
            }
    
    opened by ikegami-t 10
  •  Driver appears to install correctly but is not functional in network manager, and I think does show up with lsmod.

    Driver appears to install correctly but is not functional in network manager, and I think does show up with lsmod.

    I thank you for your patience. Artic LXqt openRC Linux 5.18.0-artix1-1

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

    Linux 5.18.0-artix1-1 #1 SMP PREEMPT_DYNAMIC Thu, 26 May 2022 13:26:58 +0000 x86_64 GNU/Linux bash: mokutil: command not found Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 004: ID 13fe:5500 Kingston Technology Company Inc. Flash drive Bus 009 Device 003: ID 0781:5583 SanDisk Corp. Ultra Fit Bus 009 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub
    Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

    Bus 008 Device 005: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter ^, right?

    0: hci0: Bluetooth Soft blocked: no Hard blocked: no 2: phy1: Wireless LAN Soft blocked: no Hard blocked: no

    rtl8812au/5.13.6, 5.18.0-artix1-1, x86_64: installed

    phy#1 Interface wlan1 ifindex 7 wdev 0x100000002 addr 9a:20:5c:d8:f1:1f type managed txpower -100.00 dBm Interface wlan0 ifindex 6 wdev 0x100000001 addr 52:1c:c7:53:0a:35 type managed txpower -100.00 dBm

    has wan interface, right?

    lsmod

    Module Size Used by tun 61440 2 rfcomm 94208 4 snd_seq_dummy 16384 0 snd_hrtimer 16384 1 snd_seq 94208 7 snd_seq_dummy snd_seq_device 16384 1 snd_seq fuse 176128 6 qrtr 57344 4 cmac 16384 2 algif_hash 16384 1 algif_skcipher 16384 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 32768 2 edac_mce_amd 57344 0 kvm_amd 167936 0 ccp 131072 1 kvm_amd rng_core 20480 1 ccp kvm 1118208 1 kvm_amd irqbypass 16384 1 kvm vfat 24576 3 fat 90112 1 vfat amdgpu 8941568 30 crct10dif_pclmul 16384 1 snd_hda_codec_realtek 167936 1 crc32_pclmul 16384 0 snd_hda_codec_generic 98304 1 snd_hda_codec_realtek btusb 65536 0 snd_hda_codec_hdmi 86016 1 ledtrig_audio 16384 1 snd_hda_codec_generic ghash_clmulni_intel 16384 0 btrtl 28672 1 btusb btbcm 20480 1 btusb 8812au 3039232 0 mxm_wmi 16384 0 snd_hda_intel 61440 4 btintel 49152 1 btusb
    snd_intel_dspcfg 36864 1 snd_hda_intel
    aesni_intel 380928 3
    btmtk 16384 1 btusb
    snd_intel_sdw_acpi 20480 1 snd_intel_dspcfg
    crypto_simd 16384 1 aesni_intel snd_hda_codec 184320 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek cryptd 28672 3 crypto_simd,ghash_clmulni_intel joydev 28672 0 r8169 106496 0 bluetooth 872448 36 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm k10temp 16384 0 snd_hda_core 118784 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek mousedev 24576 0 fam15h_power 16384 0 pcspkr 16384 0 realtek 36864 1 mdio_devres 16384 1 r8169 cfg80211 1085440 1 8812au snd_hwdep 16384 1 snd_hda_codec libphy 172032 3 r8169,mdio_devres,realtek sp5100_tco 20480 0 snd_pcm 172032 5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core ecdh_generic 16384 1 bluetooth i2c_piix4 36864 0 rfkill 36864 5 bluetooth,cfg80211 snd_timer 49152 3 snd_seq,snd_hrtimer,snd_pcm gpu_sched 53248 1 amdgpu drm_ttm_helper 16384 1 amdgpu snd 126976 19 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm ttm 86016 2 amdgpu,drm_ttm_helper soundcore 16384 1 snd drm_dp_helper 167936 1 amdgpu mac_hid 16384 0 wmi 45056 1 mxm_wmi acpi_cpufreq 32768 0 crypto_user 24576 0 ext4 1011712 3 crc32c_generic 16384 0 crc16 16384 2 bluetooth,ext4 mbcache 16384 1 ext4 jbd2 192512 1 ext4 uas 32768 0 usb_storage 81920 5 uas hid_elecom 16384 0 crc32c_intel 24576 6 xhci_pci 20480 0 usbhid 73728 0 xhci_pci_renesas 24576 1 xhci_pci

    I thank you for your time.

    opened by LargePrime 10
  • hostapd not editable

    hostapd not editable

    Hello,

    I don´t know if this issue really depends on the driver, but every time I edit my hostapd, save the file and reboot - my entries (channel, ssid...) are gone and replaced with the default ones.

    Is there a solution or what I´m doing wrong?

    Thank you.

    opened by RunningTarg3t 10
  • Add possibility of using secure boot

    Add possibility of using secure boot

    I found that the kernel will not allow insertion of the drive on my system. openSUSE 15.3 on an x86_64 system. Per the openSUSE forum, I found that the issue was caused because I used secure boot. Disabling secure boot fixed the issue, but I have Windows 11 on the same machine, which requires secure boot. Is there any chance of building an efi version or addition to the driver?

    opened by purevw 7
  • No ping on 2.4 GHz channels while 5 GHz works!

    No ping on 2.4 GHz channels while 5 GHz works!

    Hi,

    I am trying this driver, after the previous one let me down: https://github.com/aircrack-ng/rtl8812au.

    I have a RaspberryPi which has 5.4.0-1044-raspi Ubuntu 20.04.3 LTS and Asus ac56 WiFi dongle with RTL8812AU chipset. I have static ip on the wlan interface: 10.0.0.8

    When I set the WiFi network to any channel on the 2.4GHz band, like channel 4, RPI connects to it but I cannot ping the devices on the other side.

    If I change the channel to any on the 5GHz band, the ping works. I do not change anything except the channel number on my WiFi access point.

    Other devices like my phone or laptop can connect to the 2.4GHz network and I have ping. But RPi does not work. Could you please help me if you have any clue?

    These are the logs and commands (mokutil --sb-state does not work and says EFI variables are not supported on this system):

    $ sudo uname -a && lsusb && rfkill list all && dkms status && iw dev
    Linux workload-client-08 5.4.0-1044-raspi #48-Ubuntu SMP PREEMPT Thu Sep 9 15:24:01 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
    Bus 002 Device 002: ID 2001:4a00 D-Link Corp. D-Link DUB-1312
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 0b05:17d2 ASUSTek Computer, Inc. USB-AC56 802.11a/b/g/n/ac Wireless Adapter [Realtek RTL8812AU]
    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
    rtl8812au, 5.13.6, 5.4.0-1044-raspi, aarch64: installed
    phy#0
    	Interface wlan0
    		ifindex 3
    		wdev 0x1
    		addr f0:2f:74:63:5c:d9
    		ssid Wlan_New_Network_cots_4
    		type managed
    		channel 4 (2427 MHz), width: 20 MHz, center1: 2427 MHz
    		txpower 14.00 dBm
    

    Test with 2.4GHz channel:

    $ ip a
    5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2312 qdisc mq state UP group default qlen 1000
        link/ether f0:2f:74:63:5c:d9 brd ff:ff:ff:ff:ff:ff
        inet 10.0.0.8/24 brd 10.0.0.255 scope global wlan0
           valid_lft forever preferred_lft forever
        inet6 fe80::f22f:74ff:fe63:5cd9/64 scope link 
           valid_lft forever preferred_lft forever
    
    $ iw dev
    phy#0
    	Interface wlan0
    		ifindex 5
    		wdev 0x100000001
    		addr f0:2f:74:63:5c:d9
    		ssid Wlan_New_Network_cots_4
    		type managed
    		channel 4 (2427 MHz), width: 20 MHz, center1: 2427 MHz
    		txpower 20.00 dBm
    
    $ lshw
    *-network:1
           description: Wireless interface
           physical id: 4
           bus info: [email protected]:1.3
           logical name: wlan0
           serial: f0:2f:74:63:5c:d9
           capabilities: ethernet physical wireless
           configuration: broadcast=yes driver=rtl8812au driverversion=v5.13.6-15-gc40b977e2.20210629 firmware=52.14 ip=10.0.0.8 link=yes multicast=yes wireless=IEEE 802.11gn
    
    >> ping 10.0.0.7
    PING 10.0.0.7 (10.0.0.7) 56(84) bytes of data.
    From 10.0.0.8 icmp_seq=1 Destination Host Unreachable
    From 10.0.0.8 icmp_seq=2 Destination Host Unreachable
    From 10.0.0.8 icmp_seq=3 Destination Host Unreachable
    
    

    Test with 5GHz channel:

    $ ip a
    5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2312 qdisc mq state UP group default qlen 1000
        link/ether f0:2f:74:63:5c:d9 brd ff:ff:ff:ff:ff:ff
        inet 10.0.0.8/24 brd 10.0.0.255 scope global wlan0
           valid_lft forever preferred_lft forever
        inet6 fe80::f22f:74ff:fe63:5cd9/64 scope link 
           valid_lft forever preferred_lft forever
    
    $ iw dev
    phy#0
    	Interface wlan0
    		ifindex 5
    		wdev 0x100000001
    		addr f0:2f:74:63:5c:d9
    		ssid Wlan_New_Network_cots_36
    		type managed
    		channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
    		txpower 20.00 dBm
    
    $ lshw
    *-network:1
           description: Wireless interface
           physical id: 4
           bus info: [email protected]:1.3
           logical name: wlan0
           serial: f0:2f:74:63:5c:d9
           capabilities: ethernet physical wireless
           configuration: broadcast=yes driver=rtl8812au driverversion=v5.13.6-15-gc40b977e2.20210629 firmware=52.14 ip=10.0.0.8 link=yes multicast=yes wireless=IEEE 802.11an
    
    $ ping 10.0.0.7
    PING 10.0.0.7 (10.0.0.7) 56(84) bytes of data.
    64 bytes from 10.0.0.7: icmp_seq=1 ttl=64 time=4.03 ms
    64 bytes from 10.0.0.7: icmp_seq=2 ttl=64 time=1.87 ms
    64 bytes from 10.0.0.7: icmp_seq=3 ttl=64 time=2.23 ms
    64 bytes from 10.0.0.7: icmp_seq=4 ttl=64 time=1.93 ms
    64 bytes from 10.0.0.7: icmp_seq=5 ttl=64 time=1.90 ms
    64 bytes from 10.0.0.7: icmp_seq=6 ttl=64 time=2.13 ms
    
    
    

    I installed the driver according to the instructions and it was without any errors. I would appreciate if anyone can fix this.

    opened by samiemostafavi 5
  • Makefile Error: Raspberry Pi OS (64 bit) support was turned on in Makefile as planned

    Makefile Error: Raspberry Pi OS (64 bit) support was turned on in Makefile as planned

    Hi Nick,

    Moving this to the repo, apologies for the previously misplaced comment!

    I've been struggling with your installation script & I was hoping you might be able to point me in the right direction?

    I've been trying to install this driver package but I keep getting the following error. I've been trying to get it to work for a few days now.

    Raspberry Pi OS (64 bit) support was turned on in Makefile as planned.

    I have checked the makefile & toggled the flags for the respective 64 & 32 bit builds. No luck.

    I am running: Linux my-pi 5.10.74-v8+ #1471 SMP PREEMPT Mon Oct 18 17:11:19 BST 2021 aarch64 GNU/Linux

    As far as my experience is concerned, I'd say I am a moderate Linux user, not a noob, but not an expert.

    Many thanks M

    opened by markschechter 4
  • Compile error with Raspberry Pi 5.10

    Compile error with Raspberry Pi 5.10

    This is on a Pi Zero W with Buster (5.10). Am I doing something stupid?

    DKMS make.log for rtl8812au-5.13.6 for kernel 5.10.103+ (armv6l)
    Sat  2 Jul 20:19:32 BST 2022
    make ARCH=arm64 CROSS_COMPILE= -C /lib/modules/5.10.103+/build M=/var/lib/dkms/rtl8812au/5.13.6/build  modules
    make[1]: Entering directory '/usr/src/linux-headers-5.10.103+'
      CC [M]  /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_cmd.o
    gcc: error: unrecognized command line option ‘-mgeneral-regs-only’
    make[2]: *** [scripts/Makefile.build:280: /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_cmd.o] Error 1
    make[1]: *** [Makefile:1825: /var/lib/dkms/rtl8812au/5.13.6/build] Error 2
    make[1]: Leaving directory '/usr/src/linux-headers-5.10.103+'
    make: *** [Makefile:2514: modules] Error 2
    
    opened by CharlesButcher 3
  • (solved) TP-Link - Archer AC600 T2U Nano

    (solved) TP-Link - Archer AC600 T2U Nano

    {USB_DEVICE(0x2357, 0x011F), .driver_info = RTL8821}, /* TP-Link - Archer AC600 T2U Nano */ this from the https://github.com/aircrack-ng/rtl8812au but neither of the 2 codebases work properly... if I hack your code with this

    diff --git a/os_dep/linux/usb_intf.c b/os_dep/linux/usb_intf.c
    index 242ea99..b3c4d5b 100644
    --- a/os_dep/linux/usb_intf.c
    +++ b/os_dep/linux/usb_intf.c
    @@ -184,6 +184,7 @@ static struct usb_device_id rtw_usb_id_tbl[] = {
            {USB_DEVICE(0x2357, 0x010D), .driver_info = RTL8812}, /* TP-Link - Archer T4U AC1300 */
            {USB_DEVICE(0x2357, 0x010E), .driver_info = RTL8812}, /* TP-Link - Archer T4UH AC1300 */
            {USB_DEVICE(0x2357, 0x010F), .driver_info = RTL8812}, /* TP-Link - T4UHP */
    +       {USB_DEVICE(0x2357, 0x011F), .driver_info = RTL8812}, /* TP-Link - Archer AC600 T2U Nano */
            {USB_DEVICE(0x20F4, 0x805B), .driver_info = RTL8812}, /* TRENDnet - TEW-805UB */
            {USB_DEVICE(0x0411, 0x025D), .driver_info = RTL8812}, /* Buffalo - WI-U3-866D */
            {USB_DEVICE(0x050D, 0x1109), .driver_info = RTL8812}, /* Belkin F9L1109 - SerComm */
    

    it matches, loads and gives me details... but an iw scan returns no networks

    I'm testing with your code cuz the other repo/driver behaviour is pretty glitchy (lots of packet loss)

    p.s. https://linux-hardware.org/?id=usb:2357-011f

    opened by zeph 3
  • Connection activation failed: (53) The Wi-Fi network could not be found

    Connection activation failed: (53) The Wi-Fi network could not be found

    After following installation instructions, I successfully installed the driver for an AWUS036AC adapter. However, I cannot connect to a Wi-Fi network no matter what network I choose (all of them exist). I receive an Wi-Fi network could not be found issue. I'm working on HP/Kali VirtualBox installed on Ubuntu.

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

    Linux kali 5.16.0-kali3-amd64 #1 SMP PREEMPT Debian 5.16.11-1kali1 (2022-03-03) x86_64 GNU/Linux
    EFI variables are not supported on this system  
    Bus 001 Device 002: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter  
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  
    Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet  
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub  
    0: phy0: Wireless LAN  
            Soft blocked: no  
            Hard blocked: no  
    rtl8812au/5.13.6, 5.16.0-kali3-amd64, x86_64: installed  
    phy#0  
            Interface wlan0  
                    ifindex 3  
                    wdev 0x1  
                    addr 7e:3d:90:81:af:a6  
                    type managed  
                    txpower -100.00 dBm  
    

    Result of iwconfig wlan0 is:

    wlan0     unassociated  Nickname:"[email protected]"
              Mode:Managed  Frequency=2.462 GHz  Access Point: Not-Associated   
              Sensitivity:0/0  
              Retry:off   RTS thr:off   Fragment thr:off
              Encryption key: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
    
    
    opened by tplusone 3
  • Include New Device

    Include New Device

    Dear all,

    I would like to request the following device to be included:

    2357:0120 TP-Link 802.11ac WLAN Adapter

    TP Link Archer T2U Plus

    Thanks in advance.

    Best regards

    opened by FilipeSantana 3
  • No handshakes are shown in 5Ghz

    No handshakes are shown in 5Ghz

    Hello all,

    my device is working fine with this great driver.

    Only one thin is going wrong, the handshakes will not be shown in airodump-ng. 2,4 GHz WPA2 seems to work. 5 GHz not.

    I start it with: airodump-ng wlan1 --band abg --gpsd

    My Client is under 1m to the Alfa Awus036ach. No reaction when i reconnect my client to my AP.

    Have anyone an idea? :)

    Thanks Thomas

    Raspberry Pi 4B 4GB RAM with Alfa AWUS036ACH - Driver downloaded from git on Sep 18 2022

    uname -mr

    5.15.61-v7l+ armv7l

    mokutil --sb-state

    EFI variables are not supported on this system

    lsusb

    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    rfkill list all

    0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no

    dkms status

    rtl8812au, 5.13.6, 5.15.61-v7l+, armv7l: installed

    iw dev

    phy#1 Interface wlan1 ifindex 4 wdev 0x100000001 addr 00:c0:ca:b0:8a:0d type monitor channel 1 (2412 MHz), width: 20 MHz (no HT), center1: 2412 MHz txpower 17.00 dBm phy#0 Interface wlan0 ifindex 3 wdev 0x1 addr dc:a6:32:17:c9:91 type managed channel 34 (5170 MHz), width: 20 MHz, center1: 5170 MHz txpower 31.00 dBm

    iw reg get

    `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)

    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)`

    opened by tho-fu 0
  • (solved) kernel-6.0-rc1

    (solved) kernel-6.0-rc1

    I cant compile this for Kernel-6.0 and once again I can't work out a patch. I keeep creating more errors. With your original driver files this is the make.log:

    DKMS make.log for rtl8812au-5.13.6 for kernel 6.0.0-rc1-3.g7bd57d5-default (x86_64) Wed Aug 17 18:49:04 BST 2022 /bin/sh: line 1: bc: command not found make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.0.0-rc1-3.g7bd57d5-default/build M=/var/lib/dkms/rtl8812au/5.13.6/build modules make[1]: Entering directory '/usr/src/linux-6.0.0-rc1-3.g7bd57d5-obj/x86_64/default' /bin/sh: line 1: bc: command not found CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_chplan.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/monitor/rtw_radiotap.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_sta_mgt.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ap.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/wds/rtw_wds.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/mesh/rtw_mesh.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/mesh/rtw_mesh_pathtbl.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/mesh/rtw_mesh_hwmp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rson.o /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_sta_mgt.c: In function ‘rtw_mfree_stainfo’: /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_sta_mgt.c:391:25: warning: the comparison will always evaluate as ‘true’ for the address of ‘lock’ will never be NULL [-Waddress] 391 | if (&psta->lock != NULL) | ^~ In file included from /var/lib/dkms/rtl8812au/5.13.6/build/include/drv_types.h:112, from /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_sta_mgt.c:17: /var/lib/dkms/rtl8812au/5.13.6/build/include/sta_info.h:267:17: note: ‘lock’ declared here 267 | _lock lock; | ^~~~ CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_tdls.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_sreset.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_btcoex.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rm_fsm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ft.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_wnm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mbo.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rm_util.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_roch.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-internal.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-internal-enc.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-gcm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-ccm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-omac1.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/ccmp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/gcmp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-siv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-ctr.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/sha256-internal.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/sha256.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/sha256-prf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/rtw_crypto_wrap.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_swcrypto.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/usb_intf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/usb_ops_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/xmit_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/mlme_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/recv_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_cfgvendor.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/wifi_regd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_android.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_proc.o /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_cfg80211_ch_switch_notify’: /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c:478:9: error: too few arguments to function ‘cfg80211_ch_switch_notify’ 478 | cfg80211_ch_switch_notify(adapter->pnetdev, &chdef); | ^~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /var/lib/dkms/rtl8812au/5.13.6/build/include/osdep_service_linux.h:98, from /var/lib/dkms/rtl8812au/5.13.6/build/include/osdep_service.h:54, from /var/lib/dkms/rtl8812au/5.13.6/build/include/drv_types.h:27, from /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c:17: /usr/src/linux-6.0.0-rc1-3.g7bd57d5/include/net/cfg80211.h:8261:6: note: declared here 8261 | void cfg80211_ch_switch_notify(struct net_device dev, | ^~~~~~~~~~~~~~~~~~~~~~~~~ /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_cfg80211_indicate_connect’: /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c:1142:26: error: ‘struct cfg80211_roam_info’ has no member named ‘bssid’ 1142 | roam_info.bssid = cur_network->network.MacAddress; | ^ CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/nlrtw.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_rhashtable.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_intf.o /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c: At top level: /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c:10415:20: error: initialization of ‘int ()(struct wiphy *, struct net_device , unsigned int)’ from incompatible pointer type ‘int ()(struct wiphy *, struct net_device )’ [-Werror=incompatible-pointer-types] 10415 | .stop_ap = cfg80211_rtw_stop_ap, | ^~~~~~~~~~~~~~~~~~~~ /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c:10415:20: note: (near initialization for ‘rtw_cfg80211_ops.stop_ap’) /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c:10459:24: error: initialization of ‘int ()(struct wiphy *, struct wireless_dev *, unsigned int, struct cfg80211_chan_def )’ from incompatible pointer type ‘int ()(struct wiphy *, struct wireless_dev *, struct cfg80211_chan_def *)’ [-Werror=incompatible-pointer-types] 10459 | .get_channel = cfg80211_rtw_get_channel, | ^~~~~~~~~~~~~~~~~~~~~~~~ /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c:10459:24: note: (near initialization for ‘rtw_cfg80211_ops.get_channel’) /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_wdev_unregister’: /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.c:10695:17: error: ‘struct wireless_dev’ has no member named ‘current_bss’ 10695 | if (wdev->current_bss) { | ^~ CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_com.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_com_phycfg.o cc1: some warnings being treated as errors make[2]: *** [/usr/src/linux-6.0.0-rc1-3.g7bd57d5/scripts/Makefile.build:250: /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [../../../linux-6.0.0-rc1-3.g7bd57d5/Makefile:1869: /var/lib/dkms/rtl8812au/5.13.6/build] Error 2 make[1]: Leaving directory '/usr/src/linux-6.0.0-rc1-3.g7bd57d5-obj/x86_64/default' make: *** [Makefile:2510: modules] Error 2

    If you can find the time perhaps you can work this out. I'll be happy to test it again for you. Thanks. Pete

    opened by petehg 11
  • Raspberry PI 4 with Kismet is getting errors

    Raspberry PI 4 with Kismet is getting errors

    I noticed some messages in dmesg:

    [   15.808667] Bluetooth: RFCOMM ver 1.11
    [   31.709798] cam-dummy-reg: disabling
    [   59.467257] ------------[ cut here ]------------
    [   59.467281] WARNING: CPU: 2 PID: 663 at /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mlme.c:3475 rtw_sta_mstatus_report+0x80/0xd8 [8812au]
    [   59.467608] Modules linked in: rfcomm cmac algif_hash aes_arm64 algif_skcipher af_alg bnep hci_uart btbcm bluetooth ecdh_generic ecc 8021q garp stp llc snd_soc_hdmi_codec 8812au(O) brcmfmac brcmutil v3d gpu_sched cfg80211 vc4 rfkill bcm2835_codec(C) cec bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) drm_kms_helper videobuf2_vmalloc v4l2_mem2mem raspberrypi_hwmon videobuf2_dma_contig videobuf2_memops snd_soc_core videobuf2_v4l2 vc_sm_cma(C) snd_compress snd_bcm2835(C) videobuf2_common snd_pcm_dmaengine i2c_brcmstb videodev mc snd_pcm rpivid_mem snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops uio_pdrv_genirq uio nvmem_rmem i2c_dev drm drm_panel_orientation_quirks backlight fuse ip_tables x_tables ipv6
    [   59.467928] CPU: 2 PID: 663 Comm: RTW_CMD_THREAD Tainted: G        WC O      5.15.32-v8+ #1538
    [   59.467943] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
    [   59.467952] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    [   59.467965] pc : rtw_sta_mstatus_report+0x80/0xd8 [8812au]
    [   59.468228] lr : rtw_sta_mstatus_report+0x5c/0xd8 [8812au]
    [   59.468484] sp : ffffffc00a773d70
    [   59.468491] x29: ffffffc00a773d90 x28: ffffff8042386a00 x27: ffffffc009da21bc
    [   59.468515] x26: ffffffc0012fd0f0 x25: 0000000000001180 x24: ffffffc009da2140
    [   59.468537] x23: 00000000ffff151b x22: ffffffc001438980 x21: ffffff8048c1e000
    [   59.468558] x20: ffffff8042386a00 x19: ffffffc009da1000 x18: 0000000000000000
    [   59.468578] x17: 0000000000000000 x16: 0000000000000000 x15: 0000005577696610
    [   59.468599] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
    [   59.468620] x11: 0000000000000000 x10: 00000000000019d0 x9 : ffffffc008087d48
    [   59.468641] x8 : 00000000000001f4 x7 : ffffffffffd5c295 x6 : ffffffc00a773c70
    [   59.468661] x5 : 0000000000000001 x4 : 0000000000000000 x3 : ffffffc009319000
    [   59.468681] x2 : ffffffc009319238 x1 : 0000000100000000 x0 : 0000000000000000
    [   59.468703] Call trace:
    [   59.468710]  rtw_sta_mstatus_report+0x80/0xd8 [8812au]
    [   59.468968]  disconnect_hdl+0x54/0xc0 [8812au]
    [   59.469224]  rtw_cmd_thread+0x474/0x648 [8812au]
    [   59.469480]  kthread+0x140/0x158
    [   59.469495]  ret_from_fork+0x10/0x20
    [   59.469510] ---[ end trace f9bd759fa51fe430 ]---
    [   83.652664] ------------[ cut here ]------------
    [   83.652728] WARNING: CPU: 1 PID: 663 at /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mlme.c:3475 rtw_sta_mstatus_report+0x80/0xd8 [8812au]
    [   83.652902] Modules linked in: rfcomm cmac algif_hash aes_arm64 algif_skcipher af_alg bnep hci_uart btbcm bluetooth ecdh_generic ecc 8021q garp stp llc snd_soc_hdmi_codec 8812au(O) brcmfmac brcmutil v3d gpu_sched cfg80211 vc4 rfkill bcm2835_codec(C) cec bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) drm_kms_helper videobuf2_vmalloc v4l2_mem2mem raspberrypi_hwmon videobuf2_dma_contig videobuf2_memops snd_soc_core videobuf2_v4l2 vc_sm_cma(C) snd_compress snd_bcm2835(C) videobuf2_common snd_pcm_dmaengine i2c_brcmstb videodev mc snd_pcm rpivid_mem snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops uio_pdrv_genirq uio nvmem_rmem i2c_dev drm drm_panel_orientation_quirks backlight fuse ip_tables x_tables ipv6
    [   83.653021] CPU: 1 PID: 663 Comm: RTW_CMD_THREAD Tainted: G        WC O      5.15.32-v8+ #1538
    [   83.653027] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
    [   83.653031] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    [   83.653036] pc : rtw_sta_mstatus_report+0x80/0xd8 [8812au]
    [   83.653130] lr : rtw_sta_mstatus_report+0x5c/0xd8 [8812au]
    [   83.653216] sp : ffffffc00a773d70
    [   83.653218] x29: ffffffc00a773d90 x28: ffffff8042386a00 x27: ffffffc009da21bc
    [   83.653226] x26: ffffffc0012fd0f0 x25: 0000000000001180 x24: ffffffc009da2140
    [   83.653234] x23: 00000000ffff2cb9 x22: ffffffc001438980 x21: ffffff8048c1e000
    [   83.653241] x20: ffffff8042386a00 x19: ffffffc009da1000 x18: 0000000000000000
    [   83.653248] x17: 0000000000000000 x16: 0000000000000000 x15: 0000007ff8c35300
    [   83.653255] x14: ffffffffffffffff x13: 0000000000000028 x12: 0101010101010101
    [   83.653262] x11: ffffffc0093a2138 x10: 00000000000019d0 x9 : ffffffc008087d48
    [   83.653269] x8 : 00000000000001f4 x7 : ffffff80fb7a5bb0 x6 : ffffffc00a773c70
    [   83.653276] x5 : 0000000000000001 x4 : 0000000000000000 x3 : ffffffc009319000
    [   83.653283] x2 : ffffffc009319238 x1 : 0000000100000000 x0 : 0000000000000000
    [   83.653290] Call trace:
    [   83.653293]  rtw_sta_mstatus_report+0x80/0xd8 [8812au]
    [   83.653387]  disconnect_hdl+0x54/0xc0 [8812au]
    [   83.653473]  rtw_cmd_thread+0x474/0x648 [8812au]
    [   83.653559]  kthread+0x140/0x158
    [   83.653566]  ret_from_fork+0x10/0x20
    [   83.653573] ---[ end trace f9bd759fa51fe431 ]---
    [  107.820917] ------------[ cut here ]------------
    [  107.820939] WARNING: CPU: 0 PID: 663 at /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mlme.c:3475 rtw_sta_mstatus_report+0x80/0xd8 [8812au]
    [  107.821276] Modules linked in: rfcomm cmac algif_hash aes_arm64 algif_skcipher af_alg bnep hci_uart btbcm bluetooth ecdh_generic ecc 8021q garp stp llc snd_soc_hdmi_codec 8812au(O) brcmfmac brcmutil v3d gpu_sched cfg80211 vc4 rfkill bcm2835_codec(C) cec bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) drm_kms_helper videobuf2_vmalloc v4l2_mem2mem raspberrypi_hwmon videobuf2_dma_contig videobuf2_memops snd_soc_core videobuf2_v4l2 vc_sm_cma(C) snd_compress snd_bcm2835(C) videobuf2_common snd_pcm_dmaengine i2c_brcmstb videodev mc snd_pcm rpivid_mem snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops uio_pdrv_genirq uio nvmem_rmem i2c_dev drm drm_panel_orientation_quirks backlight fuse ip_tables x_tables ipv6
    [  107.821552] CPU: 0 PID: 663 Comm: RTW_CMD_THREAD Tainted: G        WC O      5.15.32-v8+ #1538
    [  107.821566] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
    [  107.821573] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    [  107.821585] pc : rtw_sta_mstatus_report+0x80/0xd8 [8812au]
    [  107.821810] lr : rtw_sta_mstatus_report+0x5c/0xd8 [8812au]
    [  107.822030] sp : ffffffc00a773d70
    [  107.822035] x29: ffffffc00a773d90 x28: ffffff8042386a00 x27: ffffffc009da21bc
    [  107.822056] x26: ffffffc0012fd0f0 x25: 0000000000001180 x24: ffffffc009da2140
    [  107.822075] x23: 00000000ffff4453 x22: ffffffc001438980 x21: ffffff8048c1e000
    [  107.822093] x20: ffffff8042386a00 x19: ffffffc009da1000 x18: 0000000000000000
    [  107.822110] x17: 0000000000000000 x16: 0000000000000000 x15: 0000007fedb42880
    [  107.822129] x14: ffffffffffffffff x13: 0000000000000028 x12: 0101010101010101
    [  107.822147] x11: ffffffc0093a2138 x10: 00000000000019d0 x9 : ffffffc008087d48
    [  107.822165] x8 : 00000000000001f4 x7 : ffffff80fb789bb0 x6 : ffffffc00a773c70
    [  107.822182] x5 : 0000000000000001 x4 : 0000000000000000 x3 : ffffffc009319000
    [  107.822199] x2 : ffffffc009319238 x1 : 0000000100000000 x0 : 0000000000000000
    [  107.822217] Call trace:
    [  107.822223]  rtw_sta_mstatus_report+0x80/0xd8 [8812au]
    [  107.822446]  disconnect_hdl+0x54/0xc0 [8812au]
    [  107.822664]  rtw_cmd_thread+0x474/0x648 [8812au]
    [  107.822883]  kthread+0x140/0x158
    [  107.822895]  ret_from_fork+0x10/0x20
    [  107.822909] ---[ end trace f9bd759fa51fe432 ]---
    [email protected]:/ $
    

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

    [email protected]:/ $ sudo uname -a; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev
    Linux wscn 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 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 005: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter
    Bus 001 Device 004: ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard
    Bus 001 Device 003: ID 0458:0186 KYE Systems Corp. (Mouse Systems) Genius DX-120 Mouse
    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: phy1: Wireless LAN
            Soft blocked: no
            Hard blocked: no
    2: hci0: Bluetooth
            Soft blocked: no
            Hard blocked: no
    rtl8812au, 5.13.6, 5.15.32-v8+, aarch64: installed
    phy#1
            Interface wlan1
                    ifindex 4
                    wdev 0x100000001
                    addr 00:c0:cb:aa:ed:1d
                    type managed
                    channel 2 (2417 MHz), width: 20 MHz, center1: 2417 MHz
                    txpower 14.00 dBm
    phy#0
            Unnamed/non-netdev interface
                    wdev 0x2
                    addr e6:5f:01:5b:f5:3d
                    type P2P-device
                    txpower 31.00 dBm
            Interface wlan0
                    ifindex 3
                    wdev 0x1
                    addr e4:5f:01:8b:f5:5e
                    ssid ******
                    type managed
                    channel 60 (5300 MHz), width: 80 MHz, center1: 5290 MHz
                    txpower 31.00 dBm
    
    opened by galaris 4
  • update kernel. Second driver installed.

    update kernel. Second driver installed.

    install driver

    sudo dkms status rtl8812au/5.13.6, 5.18.5-artix1-1, x86_64: installed

    update kernel

    sudo dkms status rtl8812au/5.13.6: added rtl8812au/5.13.6.r119.gedb17ca: added

    Please advise.

    opened by LargePrime 3
  • small error when using install-driver.sh

    small error when using install-driver.sh

    FYI

    Running install-driver.sh version 20220108
    **./install-driver.sh: line 55: hostnamectl: command not found**
    5.18.5-artix1-1
    x86_64
    Starting installation...
    Copying source files to: /usr/src/rtl8812au-5.13.6
    Copying 8812au.conf to: /etc/modprobe.d
    Creating symlink /var/lib/dkms/rtl8812au/5.13.6/source -> /usr/src/rtl8812au-5.13.6
    
    Building module:
    cleaning build area...
    'make' -j4 KVER=5.18.5-artix1-1 KSRC=/lib/modules/5.18.5-artix1-1/build.....................
    cleaning build area...
    
    8812au.ko.zst:
    Running module version sanity check.
     - Original module
       - No original module exists within this kernel
     - Installation
       - Installing to /usr/lib/modules/5.18.5-artix1-1/kernel/drivers/net/wireless/
    depmod....
    The driver was installed successfully.
    Do you want to reboot now? (recommended) [y/N]
    
    
    opened by LargePrime 1
  • Invalid MIT-MAGIC-COOKIE-1 key when wireless connected/driver in use.

    Invalid MIT-MAGIC-COOKIE-1 key when wireless connected/driver in use.

    if wireless is connected no apps will launch giving like error, which only shows when launched from CLI

    Invalid MIT-MAGIC-COOKIE-1 key
    qt.qpa.xcb: could not connect to display :0
    qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
    Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
    
    Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
    
    Aborted
    

    disconnect wireless and all is fine.

    Git fetch and sudo ./remove-driver.sh ./install-driver.sh today

    Please advise.

    artix LXQt OpenRC  https://artixlinux.org/
    sudo uname -a; mokutil --sb-state; lsusb; rfkill list all; dkms status; iw dev
    Linux redacted 5.18.5-artix1-1 #1 SMP PREEMPT_DYNAMIC Fri, 17 Jun 2022 05:53:18 +0000 x86_64 GNU/Linux
    This system doesn't support Secure Boot
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 005 Device 003: ID 056e:010c Elecom Co., Ltd M-HT1URBK HUGE Optical TrackBall
    Bus 005 Device 002: ID 046d:c248 Logitech, Inc. G105 Gaming Keyboard
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 009 Device 003: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub             
    Bus 009 Device 005: ID 13fe:5500 Kingston Technology Company Inc. Flash drive
    Bus 009 Device 004: ID 0781:5583 SanDisk Corp. Ultra Fit
    Bus 009 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub             
    Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 008 Device 004: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub             
    Bus 008 Device 005: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter
    Bus 008 Device 003: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub             
    Bus 008 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
    Bus 008 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
    rtl8812au/5.13.6, 5.18.5-artix1-1, x86_64: installed
    phy#0
            Interface wlan1
                    ifindex 4
                    wdev 0x2
                    addr 3e:a5:7b:a2:15:1d
                    type managed
                    channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
                    txpower -100.00 dBm
            Interface wlan0
                    ifindex 3
                    wdev 0x1
                    addr 08:10:7a:66:af:d7
                    ssid redacted
                    type managed
                    channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
                    txpower 16.00 dBm
    
    
    opened by LargePrime 2
Owner
Nick
Nick
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

Nick 289 Sep 25, 2022
Linux Driver for USB WiFi Adapters that are based on the RTL8811CU, RTL8821CU and RTL8731AU Chipsets - v5.12.0

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

Nick 133 Sep 20, 2022
Firmware for DMR transceivers using the NXP MK22 MCU, AT1846S RF chip and HR-C6000 DMR chipset. Including the Radioddiy GD-77, Baofeng DM-1801 and Baofeng RD-5R.

OpenGD77 Firmware for DMR transceivers using the NXP MK22 MCU, AT1846S RF chip and HR-C6000 DMR chipset. This includes the Radioddiy GD-77, Radioddity

Open Ham 93 Sep 25, 2022
lcd1602, HD44780 chipset, battery symbol

LCD_HD44780_BATTERY_SYMBOL lcd1602, HD44780 chipset, battery symbol HD44780 LCM battery gauge and symbol design Read This http://wp.me/ph3BR-1ZJ The H

xiaolaba 1 Nov 21, 2021
LLVM IR and optimizer for shaders, including front-end adapters for GLSL and SPIR-V and back-end adapter for GLSL

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

LunarG, Inc. 154 Sep 12, 2022
Loads a signed kernel driver which allows you to map any driver to kernel mode without any traces of the signed / mapped driver.

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

null 140 Sep 15, 2022
Linux USB driver for the MOTU AVB series interfaces

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

null 43 Sep 12, 2022
LoRa Driver for Semtech SX1262 on Linux (PineDio USB Adapter) and BL602 (PineDio Stack BL604)

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

Lee Lup Yuen 8 Sep 17, 2022
ESP32 software USB host through general IO pins. We can connect up to 4 USB-LS HID (keyboard mouse joystick) devices simultaneously.

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

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

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

Samsonov Dima 28 Sep 1, 2022
Tiny and portable usb host and device stack for mcu with usb ip

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

sakumisu 452 Sep 25, 2022
USB-C_PCB_experiments - USB-C ports made from a flex PCB and an ATtiny84A

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

Sam Ettinger 23 Sep 5, 2022
Anotter USB temperature logger that can record up to four channels with thermocouple or NTCs connected via CDC directly or SCPI to USB.

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

Jana Marie Hemsing 48 Aug 11, 2022
An unofficial Realtek PCIe/USB-based SD card reader driver for macOS

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

FireWolf 133 Sep 6, 2022
Windows kernel-mode driver emulating well-known USB game controllers.

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

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

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

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

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

Kento Oki 69 Aug 23, 2022
Driver leap - Self-sustainable fork of SteamVR driver for Leap Motion controller with updated vendor libraries

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

null 50 Sep 24, 2022
Hygieia, a vulnerable driver traces scanner written in C++ as an x64 Windows kernel driver.

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

Deputation 79 Sep 17, 2022