Linux Driver for USB WiFi Adapters that are based on the RTL8812BU and RTL8822BU Chipsets

Overview
Click for USB WiFi Adapter Information for Linux

88x2bu ( 88x2bu.ko ) πŸš€

Linux Driver for USB WiFi Adapters that are based on the RTL8812BU and RTL8822BU Chipsets

  • v5.13.1 (Realtek) (20210702)
  • 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 note in 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
  • Power saving modes
  • hostapd compatible
  • AP mode DFS support
  • Supported interface modes
    • IBSS
    • Managed
    • AP (see Bridged_Wireless_Access_Point.md)
    • P2P-client
    • P2P-GO
  • Log level control
  • LED control
  • Power saving control
  • VHT control (allows 80 MHz channel width in AP mode)
  • SU Beamformee and MU Beamformee control
  • SU Beamformer control
  • AP mode DFS Channel control
  • USB mode control

A FAQ is available at the end of this document.

Problem Reporting

Problem reports go in Issues.

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

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

Compatible CPUs

  • x86, amd64
  • ARM, ARM64

Compatible Kernels

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

Tested Linux Distributions

  • Arch Linux (kernels 5.4 and 5.11)

  • Fedora (kernel 5.11)

  • Debian 11 (kernels 5.10 and 5.15)

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

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

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

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

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

  • RHEL 8.4 (kernel 4.18.0)

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

Download Locations for Tested Linux Distributions

Tested Hardware

Compatible Devices

  • ASUS AC1300 USB-AC55 B1
  • ASUS AC53 Nano
  • ASUS U2
  • Cudy WU1400
  • Edimax EW-7822ULC
  • Edimax EW-7822UTC
  • EDUP EP-AC1605GS
  • FIDECO 6B21-AC1200M
  • Linksys WUSB6300 V2
  • NetGear A6150
  • TRENDnet TEW-808UBM
  • 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

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/88x2bu-20210702.git

Step 7: Move to the newly created driver directory

cd ~/src/88x2bu-20210702

Step 8: This step is only for Raspberry Pi systems

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

Run a preparation script

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

Note: Other ARM or ARM64 based systems will 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 9: Run the installation script (For automated builds, use NoPrompt as an option)

sudo ./install-driver.sh

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

Driver Options

A file called 88x2bu.conf will be installed in /etc/modprobe.d by default.

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

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

Removal of the Driver

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

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

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

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

Step 2: Move to the driver directory

cd ~/src/88x2bu-20210702

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, however, for it to work with current Linux distros, you will need to download, compile and install the current master of wpa_supplicant at the following site:

https://w1.fi/cgit/

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

Question: What interface combinations does this driver support?

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

Question: What extended features does this driver support?

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

Question: I bought two rtl8812bu 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 the same computer.

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

Answer: Many new Linux users already have adapters based on Realtek chipsets. This repo is for Linux users to support their existing adapters but my STRONG recommendation is for Linux users to seek out WiFi solutions based on Mediatek, Intel or Atheros chipsets and drivers. If users are looking at a USB solution, Mediatek and Atheros based adapters are the best solution. Realtek based USB adapters are not a good solution because Realtek does not follow Linux Wireless standards (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


Comments
  • (on hold) Limited Connectivity on 5Ghz

    (on hold) Limited Connectivity on 5Ghz

    I am using the driver with an EDUP 1300AC dongle and OpenSuse Tumbleweed. 2.4Ghz works great, but 5Ghz has issues. The most common symptom is that NetworkManager says 'limited connectivity.' Sometimes it says 'full connectivity,' but then it takes forever to render a web page - rendering the web page may fail and it will go back to limited connectivity. Once, after resetting the router, 5Ghz worked great for a couple of days, getting the kind of speed I expect, but then it went back to limited connectivity. I reset the router again, thinking it would bring the 5Ghz back, but but after running one successful speed test, it went back to limited connectivity. This is a dual boot system and 5Ghz seems to have no issues on Windows 10.

    I am happy to do more diagnosis myself if I can get some tips on things I should try.

    opened by rmjantz 26
  • disconnect on openwrt

    disconnect on openwrt

    OPENWRT LOG:

    [    8.135500] usbcore: registered new interface driver rtl88x2bu
    [    8.147232] batman_adv: B.A.T.M.A.N. advanced 2022.0-openwrt-1 (compatibility version 15) loaded
    [    8.153265] kmodloader: done loading kernel modules from /etc/modules.d/*
    [    8.706479] usb 5-1: new high-speed USB device number 3 using xhci-hcd
    [    9.194228] usb 5-1: USB disconnect, device number 3
    [    9.491136] EXT4-fs (mmcblk1p1): warning: mounting unchecked fs, running e2fsck is recommended
    [    9.492904] EXT4-fs (mmcblk1p1): mounted filesystem without journal. Opts: 
    [    9.786283] usb 5-1: new high-speed USB device number 4 using xhci-hcd
    [   10.210113] usb 5-1: USB disconnect, device number 4
    [   10.786257] usb 5-1: new high-speed USB device number 5 using xhci-hcd
    [   11.156244] Generic FE-GE Realtek PHY r8169-0-100:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-0-100:00, irq=IGNORE)
    [   11.216895] usb 5-1: USB disconnect, device number 5
    [   11.446362] r8169 0000:01:00.0 eth1: Link is Down
    [   11.446985] br-lan: port 1(eth1) entered blocking state
    [   11.447458] br-lan: port 1(eth1) entered disabled state
    [   11.448157] device eth1 entered promiscuous mode
    [   11.496239] phy_rtl8211e_led_fixup in
    [   11.498394] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:01] driver [RTL8211E Gigabit Ethernet] (irq=85)
    [   11.501349] cma: cma_alloc: alloc failed, req-size: 2 pages, ret: -12
    [   11.501959] cma: cma_alloc: alloc failed, req-size: 2 pages, ret: -12
    [   11.816241] usb 5-1: new high-speed USB device number 6 using xhci-hcd
    [   12.249945] usb 5-1: USB disconnect, device number 6
    [   12.846315] usb 5-1: new high-speed USB device number 7 using xhci-hcd
    [   13.046236] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
    [   13.046956] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
    [   13.048233] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode
    [   13.325997] usb 5-1: USB disconnect, device number 7
    [   13.906238] usb 5-1: new high-speed USB device number 8 using xhci-hcd
    [   14.341398] usb 5-1: USB disconnect, device number 8
    [   14.602884] r8169 0000:01:00.0 eth1: Link is Up - 1Gbps/Full - flow control rx/tx
    [   14.603596] br-lan: port 1(eth1) entered blocking state
    [   14.604060] br-lan: port 1(eth1) entered forwarding state
    [   14.604876] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
    [   14.946241] usb 5-1: new high-speed USB device number 9 using xhci-hcd
    [   15.390161] usb 5-1: USB disconnect, device number 9
    [   15.986263] usb 5-1: new high-speed USB device number 10 using xhci-hcd
    [   16.430071] usb 5-1: USB disconnect, device number 10
    [   17.016458] usb 5-1: new high-speed USB device number 11 using xhci-hcd
    [   17.459799] usb 5-1: USB disconnect, device number 11
    [   18.036427] usb 5-1: new high-speed USB device number 12 using xhci-hcd
    [   18.469379] usb 5-1: USB disconnect, device number 12
    [   19.046448] usb 5-1: new high-speed USB device number 13 using xhci-hcd
    [   19.499726] usb 5-1: USB disconnect, device number 13
    [   20.076486] usb 5-1: new high-speed USB device number 14 using xhci-hcd
    

    UNAME -A: Linux OpenWrt 5.10.108 #0 SMP PREEMPT Sat Mar 26 10:20:17 2022 aarch64 GNU/Linux

    IF CONNECT: lsusb -t

    /sys/bus/usb/devices/5-1/configuration: No such file or directory
    /sys/bus/usb/devices/5-1/devnum: No such file or directory
    /sys/bus/usb/devices/5-1/idProduct: No such file or directory
    /sys/bus/usb/devices/5-1/idVendor: No such file or directory
    /sys/bus/usb/devices/5-1/maxchild: No such file or directory
    /:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    /:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    /:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    /:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
        |__ Port 1: Dev 0, If 0, Class=, Driver=rtl88x2bu, M
    /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    

    DISCONNET: lsusb -t

    /:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    /:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    /:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    /:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    

    MY DEVICE: rockchip friendlyarm nanopi R4S

    CADA4C29-D6AE-4F68-B51B-AC82C676D757

    MY OPENWRT PACKAGE: https://github.com/immortalwrt/immortalwrt/tree/master/package/kernel/rtl88x2bu

    thanks for your job !

    opened by Boos4721 25
  • wlan0: CTRL-EVENT-SCAN-FAILED ret=-1

    wlan0: CTRL-EVENT-SCAN-FAILED ret=-1

    Greetings. I have been facing odd issues as of late with my TP-LINK Archer T3U; WiFi would randomly cut off, stutter throughout the day, and behave weird as a whole. While looking in confusion into the systemd logs, i found that wpa_supplicant spams the error message mentioned in the title. NetworkManager says the following:

    platform-linux: do-change-link[3]: failure changing link: failure 1 (Operation not permitted) device (wlan0): set-hw-addr: failed to set MAC address to ((blank)) (scanning) (NME_UNSPEC) device (wlan0): supplicant ninterface state: disconnected - inactive

    I installed the driver without modifying any settings later on or while having installed said driver. Is there a fix for this issue? Thank you.

    PS: disabling random MAC address configurations did not help.

    opened by MephresGH 16
  • New 88x2bu driver v5.13.1-20-gbd7c7eb9d.20210702

    New 88x2bu driver v5.13.1-20-gbd7c7eb9d.20210702

    Request that you test and report any problems. Specific bugs should be reported by opening a new issue. Discussion can go here.

    Of note: I am requesting that you follow the documentation so as to check and provide correction to the documentation. It could be easy to miss issues in the documentation if you used the prior version of this driver.

    Of particular interest is AP mode operation. Hopefully AP mode is MUCH better now.

    Nick

    opened by morrownr 16
  • (solved) 2 new devices after install (this is normal if you run cmode-on.sh during installation)

    (solved) 2 new devices after install (this is normal if you run cmode-on.sh during installation)

    Hi,

    i am using a RaspberryPi 4B and a USB-Wifi Adapter with RTL8822bu chipset. After installing the driver, there are two new devices showing up (wlan1 and wlan2).

    How can I remove that wifi adapter?

    image

    opened by JanB97 14
  • building drivers on ubuntu 22.10 beta issue

    building drivers on ubuntu 22.10 beta issue

    I am using beta version of ubuntu 22.10 and I have this issue while compiling module for kernel 5.19.0-18-generic : Skipping BTF generation for /data/tools/drivers/rtl88x2bu/88x2bu.ko due to unavailability of vmlinux while force to load the module : sudo modprobe -v 88x2bu insmod /lib/modules/5.19.0-18-generic/kernel/drivers/net/wireless/88x2bu.ko modprobe: ERROR: could not insert '88x2bu': Unknown symbol in module, or unknown parameter (see dmesg)

    I do not have any issue with the previous kernel version 5.19.0-15-generic

    opened by dreambo 10
  • (solved) RTW: ERROR [HALMAC][ERR]Dump efuse in suspend

    (solved) RTW: ERROR [HALMAC][ERR]Dump efuse in suspend

    I built a new kernel for the Raspberry pi 4 then built and installed the 88x2bu-20210702 driver, for a TP-Link USB Wi-Fi adapter I have never used before. It seems to work fine as a wifi interface (no AP mode, no 867 MHz, no concurrent mode, USB2). But I’m getting kernel error messages in /var/log/messages and dmesg when the driver is loaded at boot.

    The adapter is a TP-Link Archer 3U Plus, connected to a USB2 hub. I know USB2 is not ideal, but it would be difficult to replace it with a USB3 hub in my existing project. I am connected to a 2.4 GHz AP so throughput should not be an issue.

    Thanks in advance for any help you can offer.

    β€”β€”- Config & Requested Info β€”β€”- Pi 4, 4GB Ram, Pi OS 10 β€˜Buster’ with upgraded kernel 5.10.89. System was updated before kernel & driver build with sudo apt update && sudo apt full-upgrade Then kernel 5.10.89 was installed from the rpi-5.10.y branch at https://github.com/raspberrypi/linux No errors in kernel or driver build. No other non-standard drivers have been installed.

    Config: contents of /etc/modprobe.d/88x2bu.conf: options 88x2bu rtw_drv_log_level=2 rtw_led_ctrl=2 rtw_vht_enable=0 rtw_power_mgnt=0 rtw_beamform_cap=0 rtw_dfs_region_domain=1 rtw_sel_p2p_iface=1 rtw_switch_usb_mode=2

    Internal wifi disabled in /boot/config.txt with: dtoverlay=disable-wifi

    gcc version: gcc version 7.3.0 (Raspbian 7.3.0-19)

    Here is the information requested in the README:

    $ uname -a Linux magic-mirror 5.10.89-v7l+ #1 SMP Mon Jan 3 20:47:31 EST 2022 armv7l GNU/Linux

    $ 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 005: ID 0556:0001 Asahi Kasei Microsystems Co., Ltd AK5370 I/F A/D Converter Bus 001 Device 007: ID 2357:0138 TP-Link Bus 001 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 003: ID 041e:324d Creative Technology, Ltd 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

    $ dkms status rtl88x2bu, 5.13.1, 5.10.89-v7l+, armv7l: installed

    $ iw dev phy#0 Interface wlx984827ea0ed6 ifindex 3 wdev 0x1 addr 98:48:27:ea:0e:d6 ssid xxxxxxxx type managed channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz txpower 23.00 dBm

    β€”β€”β€” ERROR Messages β€”β€”β€” There are numerous instances of [HALMAC][ERR]Dump efuse in suspend and [HALMAC][ALWAYS]shall R reg twice!! in /var/log/messages at startup. This is all of the output related to RTW: Jan 4 11:03:42 magic-mirror kernel: [ 50.211837] RTW: module init start Jan 4 11:03:42 magic-mirror kernel: [ 50.211858] RTW: rtl88x2bu v5.13.1-20-gbd7c7eb9d.20210702_COEX20210316-18317b7b Jan 4 11:03:42 magic-mirror kernel: [ 50.211874] RTW: rtl88x2bu BT-Coex version = COEX20210316-18317b7b Jan 4 11:03:42 magic-mirror kernel: [ 50.212337] RTW: [HALMAC]55772M Jan 4 11:03:42 magic-mirror kernel: [ 50.212337] HALMAC_MAJOR_VER = 1 Jan 4 11:03:42 magic-mirror kernel: [ 50.212337] HALMAC_PROTOTYPE_VER = 6 Jan 4 11:03:42 magic-mirror kernel: [ 50.212337] HALMAC_MINOR_VER = 6 Jan 4 11:03:42 magic-mirror kernel: [ 50.212337] HALMAC_PATCH_VER = 23 Jan 4 11:03:42 magic-mirror kernel: [ 50.227151] RTW: ERROR [HALMAC][ERR]Dump efuse in suspend Jan 4 11:03:43 magic-mirror kernel: [ 50.863847] RTW: HW EFUSE Jan 4 11:03:43 magic-mirror kernel: [ 50.863900] RTW: 0x000: 29 81 00 3C 09 00 A1 00 B6 04 64 10 00 00 A3 00 Jan 4 11:03:43 magic-mirror kernel: [ 50.864160] RTW: 0x010: 2B 2B 2C 2C 2C 2C 2A 2B 2B 2B 2B 14 00 00 FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.864415] RTW: 0x020: FF FF 26 25 24 23 20 20 21 21 23 24 26 24 24 24 Jan 4 11:03:43 magic-mirror kernel: [ 50.864669] RTW: 0x030: 13 00 FF FF 00 FF 1C 00 FF FF 2A 2B 2B 2C 2C 2C Jan 4 11:03:43 magic-mirror kernel: [ 50.864951] RTW: 0x040: 2B 2B 2B 2B 2B 14 00 00 FF FF FF FF 25 25 25 24 Jan 4 11:03:43 magic-mirror kernel: [ 50.865254] RTW: 0x050: 21 21 21 21 22 24 26 26 26 26 13 00 FF FF 00 FF Jan 4 11:03:43 magic-mirror kernel: [ 50.865527] RTW: 0x060: 1C 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.865966] RTW: 0x070: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.866221] RTW: 0x080: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.866473] RTW: 0x090: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.866723] RTW: 0x0A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.866974] RTW: 0x0B0: FF FF FF FF FF FF FF FF A5 27 1D 00 FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.867224] RTW: 0x0C0: FF 01 00 11 00 00 00 00 00 FF 03 FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.867475] RTW: 0x0D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.867725] RTW: 0x0E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.867976] RTW: 0x0F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.868227] RTW: 0x100: 57 23 38 01 E1 67 02 98 48 27 EA 0E D6 09 03 52 Jan 4 11:03:43 magic-mirror kernel: [ 50.868480] RTW: 0x110: 65 61 6C 74 65 6B 0E 03 38 30 32 2E 31 31 61 63 Jan 4 11:03:43 magic-mirror kernel: [ 50.868734] RTW: 0x120: 20 4E 49 43 08 03 31 32 33 34 35 36 FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.868986] RTW: 0x130: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.869238] RTW: 0x140: 33 0A 1F 01 00 00 21 0F FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.869492] RTW: 0x150: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.869744] RTW: 0x160: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.869996] RTW: 0x170: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.870251] RTW: 0x180: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.870504] RTW: 0x190: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.870758] RTW: 0x1A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.871012] RTW: 0x1B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.871267] RTW: 0x1C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.871519] RTW: 0x1D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.871771] RTW: 0x1E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.872023] RTW: 0x1F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.872275] RTW: 0x200: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.872528] RTW: 0x210: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.872783] RTW: 0x220: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.873034] RTW: 0x230: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.873286] RTW: 0x240: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.873541] RTW: 0x250: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.873793] RTW: 0x260: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.874046] RTW: 0x270: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.874299] RTW: 0x280: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.874553] RTW: 0x290: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.874804] RTW: 0x2A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.875055] RTW: 0x2B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.875307] RTW: 0x2C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.875560] RTW: 0x2D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.875871] RTW: 0x2E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.876195] RTW: 0x2F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Jan 4 11:03:43 magic-mirror kernel: [ 50.876538] RTW: hal_com_config_channel_plan chplan:0x25 Jan 4 11:03:43 magic-mirror kernel: [ 50.892863] RTW: ERROR [HALMAC][ERR]Dump efuse in suspend Jan 4 11:03:43 magic-mirror kernel: [ 50.915602] RTW: [HALMAC][ALWAYS]shall R reg twice!! Jan 4 11:03:43 magic-mirror udisksd[387]: Acquired the name org.freedesktop.UDisks2 on the system message bus Jan 4 11:03:43 magic-mirror kernel: [ 51.045469] RTW: ERROR [HALMAC][ERR]Dump efuse in suspend Jan 4 11:03:43 magic-mirror kernel: [ 51.045727] RTW: ERROR [HALMAC][ERR]Dump efuse in suspend Jan 4 11:03:43 magic-mirror kernel: [ 51.046061] RTW: ERROR [HALMAC][ERR]Dump efuse in suspend Jan 4 11:03:43 magic-mirror kernel: [ 51.046334] RTW: [RF_PATH] ver_id.RF_TYPE:RF_2T2R Jan 4 11:03:43 magic-mirror kernel: [ 51.046353] RTW: [RF_PATH] HALSPEC's rf_reg_trx_path_bmp:0x33, rf_reg_path_avail_num:2, max_tx_cnt:2 Jan 4 11:03:43 magic-mirror kernel: [ 51.046371] RTW: [RF_PATH] PG's trx_path_bmp:0x00, max_tx_cnt:0 Jan 4 11:03:43 magic-mirror kernel: [ 51.046388] RTW: [RF_PATH] Registry's trx_path_bmp:0x00, tx_path_lmt:0, rx_path_lmt:0 Jan 4 11:03:43 magic-mirror kernel: [ 51.046405] RTW: [RF_PATH] HALDATA's trx_path_bmp:0x33, max_tx_cnt:2 Jan 4 11:03:43 magic-mirror kernel: [ 51.046421] RTW: [RF_PATH] HALDATA's rf_type:RF_2T2R, NumTotalRFPath:2 Jan 4 11:03:43 magic-mirror kernel: [ 51.046438] RTW: [TRX_Nss] HALSPEC - tx_nss:2, rx_nss:2 Jan 4 11:03:43 magic-mirror kernel: [ 51.046454] RTW: [TRX_Nss] Registry - tx_nss:0, rx_nss:0 Jan 4 11:03:43 magic-mirror kernel: [ 51.046469] RTW: [TRX_Nss] HALDATA - tx_nss:2, rx_nss:2 Jan 4 11:03:43 magic-mirror kernel: [ 51.046488] RTW: txpath=0x3, rxpath=0x3 Jan 4 11:03:43 magic-mirror kernel: [ 51.046506] RTW: txpath_1ss:0x1, num:1 Jan 4 11:03:43 magic-mirror kernel: [ 51.046522] RTW: txpath_2ss:0x3, num:2 Jan 4 11:03:43 magic-mirror kernel: [ 51.048164] RTW: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1 Jan 4 11:03:43 magic-mirror kernel: [ 51.050290] RTW: rtw_ndev_init(wlan0) if1 mac_addr=98:48:27:ea:0e:d6 Jan 4 11:03:43 magic-mirror kernel: [ 51.052850] usbcore: registered new interface driver rtl88x2bu Jan 4 11:03:43 magic-mirror kernel: [ 51.052873] RTW: module init ret=0 Jan 4 11:03:43 magic-mirror mtp-probe: checking bus 1, device 7: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.3" Jan 4 11:03:43 magic-mirror mtp-probe: bus: 1, device: 7 was not an MTP device Jan 4 11:03:43 magic-mirror kernel: [ 51.119655] rtl88x2bu 1-1.2.3:1.0 wlx984827ea0ed6: renamed from wlan0 Jan 4 11:03:43 magic-mirror kernel: [ 51.454094] RTW: [HALMAC][ALWAYS]shall R reg twice!! Jan 4 11:03:44 magic-mirror kernel: [ 52.510207] start_addr=(0x20000), end_addr=(0x40000), buffer_size=(0x20000), smp_number_max=(16384) Jan 4 11:03:44 magic-mirror kernel: [ 52.541755] IPv6: ADDRCONF(NETDEV_CHANGE): wlx984827ea0ed6: link becomes ready Jan 4 11:03:49 magic-mirror kernel: [ 57.042693] RTW: rtw_set_802_11_connect(wlx984827ea0ed6) fw_state=0x00000008 Jan 4 11:03:49 magic-mirror kernel: [ 57.204203] RTW: start auth Jan 4 11:03:49 magic-mirror kernel: [ 57.209342] RTW: auth success, start assoc Jan 4 11:03:49 magic-mirror kernel: [ 57.220243] RTW: assoc success Jan 4 11:03:49 magic-mirror kernel: [ 57.222835] RTW: ============ STA [98:da:c4:7c:df:e0] =================== Jan 4 11:03:49 magic-mirror kernel: [ 57.222855] RTW: mac_id : 0 Jan 4 11:03:49 magic-mirror kernel: [ 57.222870] RTW: wireless_mode : 0x0b Jan 4 11:03:49 magic-mirror kernel: [ 57.222886] RTW: mimo_type : 2 Jan 4 11:03:49 magic-mirror kernel: [ 57.222901] RTW: static smps : N Jan 4 11:03:49 magic-mirror kernel: [ 57.222919] RTW: bw_mode : 20MHz, ra_bw_mode : 20MHz Jan 4 11:03:49 magic-mirror kernel: [ 57.222936] RTW: rate_id : 2 Jan 4 11:03:49 magic-mirror kernel: [ 57.222952] RTW: rssi : -1 (%), rssi_level : 0 Jan 4 11:03:49 magic-mirror kernel: [ 57.222968] RTW: is_support_sgi : Y, is_vht_enable : N Jan 4 11:03:49 magic-mirror kernel: [ 57.222985] RTW: disable_ra : N, disable_pt : N Jan 4 11:03:49 magic-mirror kernel: [ 57.223000] RTW: is_noisy : N Jan 4 11:03:49 magic-mirror kernel: [ 57.223015] RTW: txrx_state : 0 Jan 4 11:03:49 magic-mirror kernel: [ 57.223032] RTW: curr_tx_rate : CCK_1M (L) Jan 4 11:03:49 magic-mirror kernel: [ 57.223047] RTW: curr_tx_bw : 20MHz Jan 4 11:03:49 magic-mirror kernel: [ 57.223062] RTW: curr_retry_ratio : 0 Jan 4 11:03:49 magic-mirror kernel: [ 57.223078] RTW: ra_mask : 0x000000000fffffff Jan 4 11:03:49 magic-mirror kernel: [ 57.223078] Jan 4 11:03:49 magic-mirror kernel: [ 57.223270] RTW: recv eapol packet 1/4 Jan 4 11:03:49 magic-mirror kernel: [ 57.225426] RTW: send eapol packet 2/4 Jan 4 11:03:49 magic-mirror kernel: [ 57.233492] RTW: recv eapol packet 3/4 Jan 4 11:03:49 magic-mirror kernel: [ 57.234239] RTW: send eapol packet 4/4 Jan 4 11:03:49 magic-mirror kernel: [ 57.234619] RTW: set pairwise key camid:0, addr:98:da:c4:7c:df:e0, kid:0, type:AES Jan 4 11:03:49 magic-mirror kernel: [ 57.237709] RTW: set group key camid:1, addr:98:da:c4:7c:df:e0, kid:1, type:AES

    β€”β€”β€” dmesg ERROR Output β€”β€”β€” [ 49.951868] bcmgenet fd580000.ethernet: configuring instance for external RGMII (RX delay) [ 49.952929] bcmgenet fd580000.ethernet eth0: Link is Down [ 50.017841] 88x2bu: loading out-of-tree module taints kernel. [ 50.208297] 88x2bu: unknown parameter 'rtw_sel_p2p_iface' ignored [ 50.211837] RTW: module init start [ 50.211858] RTW: rtl88x2bu v5.13.1-20-gbd7c7eb9d.20210702_COEX20210316-18317b7b [ 50.211874] RTW: rtl88x2bu BT-Coex version = COEX20210316-18317b7b [ 50.212337] RTW: [HALMAC]55772M HALMAC_MAJOR_VER = 1 HALMAC_PROTOTYPE_VER = 6 HALMAC_MINOR_VER = 6 HALMAC_PATCH_VER = 23 [ 50.227151] RTW: ERROR [HALMAC][ERR]Dump efuse in suspend [ 50.863847] RTW: HW EFUSE [ 50.863900] RTW: 0x000: 29 81 00 3C 09 00 A1 00 B6 04 64 10 00 00 A3 00 [ 50.864160] RTW: 0x010: 2B 2B 2C 2C 2C 2C 2A 2B 2B 2B 2B 14 00 00 FF FF [ 50.864415] RTW: 0x020: FF FF 26 25 24 23 20 20 21 21 23 24 26 24 24 24 [ 50.864669] RTW: 0x030: 13 00 FF FF 00 FF 1C 00 FF FF 2A 2B 2B 2C 2C 2C [ 50.864951] RTW: 0x040: 2B 2B 2B 2B 2B 14 00 00 FF FF FF FF 25 25 25 24 [ 50.865254] RTW: 0x050: 21 21 21 21 22 24 26 26 26 26 13 00 FF FF 00 FF [ 50.865527] RTW: 0x060: 1C 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.865966] RTW: 0x070: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.866221] RTW: 0x080: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.866473] RTW: 0x090: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.866723] RTW: 0x0A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.866974] RTW: 0x0B0: FF FF FF FF FF FF FF FF A5 27 1D 00 FF FF FF FF [ 50.867224] RTW: 0x0C0: FF 01 00 11 00 00 00 00 00 FF 03 FF FF FF FF FF [ 50.867475] RTW: 0x0D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.867725] RTW: 0x0E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.867976] RTW: 0x0F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.868227] RTW: 0x100: 57 23 38 01 E1 67 02 98 48 27 EA 0E D6 09 03 52 [ 50.868480] RTW: 0x110: 65 61 6C 74 65 6B 0E 03 38 30 32 2E 31 31 61 63 [ 50.868734] RTW: 0x120: 20 4E 49 43 08 03 31 32 33 34 35 36 FF FF FF FF [ 50.868986] RTW: 0x130: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.869238] RTW: 0x140: 33 0A 1F 01 00 00 21 0F FF FF FF FF FF FF FF FF [ 50.869492] RTW: 0x150: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.869744] RTW: 0x160: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.869996] RTW: 0x170: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.870251] RTW: 0x180: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.870504] RTW: 0x190: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.870758] RTW: 0x1A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.871012] RTW: 0x1B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.871267] RTW: 0x1C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.871519] RTW: 0x1D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.871771] RTW: 0x1E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.872023] RTW: 0x1F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.872275] RTW: 0x200: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.872528] RTW: 0x210: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.872783] RTW: 0x220: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.873034] RTW: 0x230: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.873286] RTW: 0x240: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.873541] RTW: 0x250: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.873793] RTW: 0x260: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.874046] RTW: 0x270: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.874299] RTW: 0x280: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.874553] RTW: 0x290: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.874804] RTW: 0x2A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.875055] RTW: 0x2B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.875307] RTW: 0x2C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.875560] RTW: 0x2D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.875871] RTW: 0x2E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.876195] RTW: 0x2F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF [ 50.876538] RTW: hal_com_config_channel_plan chplan:0x25 [ 50.892863] RTW: ERROR [HALMAC][ERR]Dump efuse in suspend [ 50.915602] RTW: [HALMAC][ALWAYS]shall R reg twice!! [ 51.045469] RTW: ERROR [HALMAC][ERR]Dump efuse in suspend [ 51.045727] RTW: ERROR [HALMAC][ERR]Dump efuse in suspend [ 51.046061] RTW: ERROR [HALMAC][ERR]Dump efuse in suspend [ 51.046334] RTW: [RF_PATH] ver_id.RF_TYPE:RF_2T2R [ 51.046353] RTW: [RF_PATH] HALSPEC's rf_reg_trx_path_bmp:0x33, rf_reg_path_avail_num:2, max_tx_cnt:2 [ 51.046371] RTW: [RF_PATH] PG's trx_path_bmp:0x00, max_tx_cnt:0 [ 51.046388] RTW: [RF_PATH] Registry's trx_path_bmp:0x00, tx_path_lmt:0, rx_path_lmt:0 [ 51.046405] RTW: [RF_PATH] HALDATA's trx_path_bmp:0x33, max_tx_cnt:2 [ 51.046421] RTW: [RF_PATH] HALDATA's rf_type:RF_2T2R, NumTotalRFPath:2 [ 51.046438] RTW: [TRX_Nss] HALSPEC - tx_nss:2, rx_nss:2 [ 51.046454] RTW: [TRX_Nss] Registry - tx_nss:0, rx_nss:0 [ 51.046469] RTW: [TRX_Nss] HALDATA - tx_nss:2, rx_nss:2 [ 51.046488] RTW: txpath=0x3, rxpath=0x3 [ 51.046506] RTW: txpath_1ss:0x1, num:1 [ 51.046522] RTW: txpath_2ss:0x3, num:2 [ 51.048164] RTW: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1 [ 51.050290] RTW: rtw_ndev_init(wlan0) if1 mac_addr=98:48:27:ea:0e:d6 [ 51.052850] usbcore: registered new interface driver rtl88x2bu [ 51.052873] RTW: module init ret=0 [ 51.119655] rtl88x2bu 1-1.2.3:1.0 wlx984827ea0ed6: renamed from wlan0 [ 51.454094] RTW: [HALMAC][ALWAYS]shall R reg twice!! [ 52.510207] start_addr=(0x20000), end_addr=(0x40000), buffer_size=(0x20000), smp_number_max=(16384) [ 52.541755] IPv6: ADDRCONF(NETDEV_CHANGE): wlx984827ea0ed6: link becomes ready [ 57.042693] RTW: rtw_set_802_11_connect(wlx984827ea0ed6) fw_state=0x00000008 [ 57.204203] RTW: start auth [ 57.209342] RTW: auth success, start assoc [ 57.220243] RTW: assoc success [ 57.222835] RTW: ============ STA [98:da:c4:7c:df:e0] =================== [ 57.222855] RTW: mac_id : 0 [ 57.222870] RTW: wireless_mode : 0x0b [ 57.222886] RTW: mimo_type : 2 [ 57.222901] RTW: static smps : N [ 57.222919] RTW: bw_mode : 20MHz, ra_bw_mode : 20MHz [ 57.222936] RTW: rate_id : 2 [ 57.222952] RTW: rssi : -1 (%), rssi_level : 0 [ 57.222968] RTW: is_support_sgi : Y, is_vht_enable : N [ 57.222985] RTW: disable_ra : N, disable_pt : N [ 57.223000] RTW: is_noisy : N [ 57.223015] RTW: txrx_state : 0 [ 57.223032] RTW: curr_tx_rate : CCK_1M (L) [ 57.223047] RTW: curr_tx_bw : 20MHz [ 57.223062] RTW: curr_retry_ratio : 0 [ 57.223078] RTW: ra_mask : 0x000000000fffffff

    [ 57.223270] RTW: recv eapol packet 1/4 [ 57.225426] RTW: send eapol packet 2/4 [ 57.233492] RTW: recv eapol packet 3/4 [ 57.234239] RTW: send eapol packet 4/4 [ 57.234619] RTW: set pairwise key camid:0, addr:98:da:c4:7c:df:e0, kid:0, type:AES [ 57.237709] RTW: set group key camid:1, addr:98:da:c4:7c:df:e0, kid:1, type:AES [ 67.024755] broken atomic modeset userspace detected, disabling atomic [ 70.699163] fuse: init (API version 7.32)

    opened by mlewus 10
  • dkms issue?

    dkms issue?

    First of all, thank you for maintaining this repo. It is the only driver that works for me. Without it, I would have to bear with a long cable running across the entire house.

    Short story, install-driver.sh succeeds but the usb adapter won't work (blinks for a few seconds then off). On the other hand, install-driver-no-dkms.sh works.

    Here's the longer story. I have an old Dell precision T1500, it is running Ubuntu 20.04. I've been using the 88x2bu-5.8.7.4 driver for the past year and it worked fine until about two weeks ago when suddenly the system cannot recognize the usb wifi adapter. I removed the driver and tried to install-driver.sh again, but make failed with fatal error: net/ipx.h: No such file or directory (due to changes in kernel 5.15?). Then I found this new repo 88x2bu-20210702. The install-driver.sh script runs successfully, dkms confirms that the driver is installed. The usb adapter blinks for a couple of seconds, giving a list of available wifi networks, then the light turns off. Connecting to the networks failed with the message activation of network connection failed (light on usb adapter never turns on again). After multiple unsuccessful attempts with different combinations of options, I decided to give install-driver-no-dkms.sh a try, and voila, it works! I have no clue where (or which log) to look for potential causes of the issue but thought posting it here may be helpful.

    More details: Desktop: Dell precision T1500, only has usb 2.0. The usb adapter says usb 3.0 on it but it has been working fine with a decent speed (60/10 Mbps comparing to 75/11 Mbps on my tablet which is on the same network). uname: 5.15.0-41-generic #44~20.04.1-Ubuntu SMP Fri Jun 24 13:27:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux (I don't have mokutil...) lsusb: Bus 001 Device 003: ID 0bda:b812 Realtek Semiconductor Corp. rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no (dkms only has driver for nvidia graphics card, when using install-driver.sh, this driver does show up.)

    opened by kanatos92 9
  • NetGear A6150 does not work on Ubuntu kernel 5.11

    NetGear A6150 does not work on Ubuntu kernel 5.11

    The driver does not work on ubuntu kernel: 5.11.0-38-generic(Realtek) with NetGear A6150. I have successful used 88x2bu driver on ubuntu kernel: 5.8(Realtek) but it does not work after I upgrade ubuntu to 5.11(Realtek). So I reinstalled 88x2bu-20210702, it still does not work. No wireless interface show in 'lshw -C network'. Could you have a check? Thank you.

    opened by loocy3 9
  • (solved) Device not appearing (this driver is not for the 8192EU chipset)

    (solved) Device not appearing (this driver is not for the 8192EU chipset)

    I need to make this work with an older 4.4 kernel, and I'm up for patching this rtl88x2bu driver if necessary, but I could do with a few clues on where to start.

    I've compiled the module and successfully used insmod (& rmmod) on it, but no (new) devices are presented on ip link or iw dev, even though it shows up correctly in dmesg and lsusb. (Until I can get that far, it seems pointless trying to configure

    I've even tried insmod, insert device, rmmod, remove device, insert device, insmod, but no change.

    Are there any command line parameters I could add to insmod to help find out what's going wrong?

    This is a Dell d630 Latitude with a T-7100 2-core CPU and 8 GiB RAM; it has built-in ethernet (which I use most of the time), and WiFi (which is turned off by a hardware kill switch, but is still the only thing that shows up in the iw commands below). It's effectively running Ubuntu 16-LTS, despite reporting 14.04.

    $ uname -mr
    4.4.0-140-generic x86_64
    $ mokutil --sb-state
    bash: mokutil: command not found
    $ rfkill list all
    0: phy0: Wireless LAN
            Soft blocked: no
            Hard blocked: yes
    1: dell-wifi: Wireless LAN
            Soft blocked: no
            Hard blocked: yes
    $ dkms status
    bash: dkms: command not found
    $ iw dev
    phy#0
            Interface wlan0
                    ifindex 3
                    wdev 0x1
                    addr 00:1b:RE:DA:CT:ED
                    type managed
    $ iw reg get
    country 00: DFS-UNSET
            (2402 - 2472 @ 40), (N/A, 20), (N/A)
            (2457 - 2482 @ 20), (N/A, 20), (N/A), NO-IR
            (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, NO-IR
            (5170 - 5250 @ 80), (N/A, 20), (N/A), NO-IR
            (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, NO-IR
            (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, NO-IR
            (5735 - 5835 @ 80), (N/A, 20), (N/A), NO-IR
            (57240 - 63720 @ 2160), (N/A, 0), (N/A)
    $ lsmod | grep 88x
    88x2bu               3047424  0
    cfg80211              565248  4 iwl3945,iwlegacy,mac80211,88x2bu
    $ grep -B1 -A4 idVendor=2357 /var/log/messages | cut -d' ' -f5-
    usb 2-1: new high-speed USB device number 5 using ehci-pci
    usb 2-1: New USB device found, idVendor=2357, idProduct=0126
    usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    usb 2-1: Product: 802.11n NIC
    usb 2-1: Manufacturer: Realtek
    usb 2-1: SerialNumber: 60A4REDACTED
    $ lsusb | grep 2357:0126
    Bus 003 Device 003: ID 2357:0126 TL-WN8200ND ver.2 [Realtek RTL8812BU]
    $ lspci | grep Net
    09:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5755M Gigabit Ethernet PCI Express (rev 02)
    0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
    $ free
                  total        used        free      shared  buff/cache   available
    Mem:        8165488     2886024      765580      289700     4513884     4618236
    Swap:       5001212      530124     4471088
    $ grep ^model /proc/cpuinfo 
    model           : 15
    model name      : Intel(R) Core(TM)2 Duo CPU     T7100  @ 1.80GHz
    model           : 15
    model name      : Intel(R) Core(TM)2 Duo CPU     T7100  @ 1.80GHz
    

    ("Upgrade your kernel" isn't as easy as it sounds on this 14-year-old device; many times the graphics and/or network devices are unsupported in newer kernels. I do have dual root partitions, but sometimes even Grub gets messed up, so I'm not going to undertake an upgrade until I know I can take a week off work if necessary. In the meantime, new neighbours have moved in next to our WiFi AP at the other end of the house, so it can't reliably "hear" this device; and I'd really like to stop relying on an Ethernet cable running along the hallway.)

    opened by kurahaupo 8
  • Is it possible to install this driver in nethunter?

    Is it possible to install this driver in nethunter?

    Is it possible to install the driver on a phone?

    I have an S20 FE 5G but whenever I plug in the wifi adapter to my phone the wrong driver shows up, 88XXau instead of 88XXBu

    I tested this driver on my computer and it worked perfectly, but I don't know how to get it working on my phone

    opened by EDLLT 8
  • Error installing: make error 2

    Error installing: make error 2

    Running install-driver.sh version 20221007
    5.15.76-v7l+
    armv7l
    Starting installation...
    Copying rtw88_8822bu.conf to: /etc/modprobe.d
    Copying 88x2bu.conf to: /etc/modprobe.d
    The non-dkms installation routines are in use.
    #make -C /lib/modules/5.15.76-v7l+/build M=/home/pi/Downloads/88x2bu-20210702 clean
    cd hal ; rm -fr */*/*/*.mod.c */*/*/*.mod */*/*/*.o */*/*/.*.cmd */*/*/*.ko
    cd hal ; rm -fr */*/*.mod.c */*/*.mod */*/*.o */*/.*.cmd */*/*.ko
    cd hal ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
    cd hal ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
    cd core ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
    cd core ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
    cd os_dep/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
    cd os_dep ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
    cd platform ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
    rm -fr Module.symvers ; rm -fr Module.markers ; rm -fr modules.order
    rm -fr *.mod.c *.mod *.o .*.cmd *.ko *~
    rm -fr .tmp_versions
    make ARCH=armv7l CROSS_COMPILE= -C /lib/modules/5.15.76-v7l+/build M=/home/pi/Downloads/88x2bu-20210702  modules
    make[1]: Entering directory '/usr/lib/modules/5.15.76-v7l+/build'
    make[1]: *** No rule to make target 'modules'.  Stop.
    make[1]: Leaving directory '/usr/lib/modules/5.15.76-v7l+/build'
    make: *** [Makefile:2503: modules] Error 2
    An error occurred. Error = 2
    Please report this error.
    Please copy all screen output and paste it into the report.
    You will need to run the following before reattempting installation.
    $ sudo ./remove-driver-no-dkms.sh
    

    Also, there is no such file remove-driver-no-dkms.sh

    opened by beaver700nh 1
  • error when compiling

    error when compiling

    【platform】 nanopi-r6s, rk3588s, aarch64, gcc-11

    【in terminal】 'make' -j8 KVER=5.10.110 KSRC=/lib/modules/5.10.110/build..................(bad exit status: 2) ERROR (dkms apport): binary package for rtl88x2bu: 5.13.1 not found Error! Bad return status for module build on kernel: 5.10.110 (aarch64) Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more information.

    【in /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log】 ERROR: modpost: module 88x2bu uses symbol kernel_write from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it. ERROR: modpost: module 88x2bu uses symbol kernel_read from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it. ERROR: modpost: module 88x2bu uses symbol filp_open from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it.

    opened by aini6658 7
  • (solved) Error when installing

    (solved) Error when installing

    Error:

    [email protected] ~/src/88x2bu-20210702 $ sudo ./install-driver.sh
    Running install-driver.sh version 20221007
    4.1.7-v7+
    armv7l
    Starting installation...
    Copying rtw88_8822bu.conf to: /etc/modprobe.d
    Copying 88x2bu.conf to: /etc/modprobe.d
    The non-dkms installation routines are in use.
    /bin/sh: 1: bc: not found
    #make -C /lib/modules/4.1.7-v7+/build M=/home/pi/src/88x2bu-20210702 clean
    cd hal ; rm -fr */*/*/*.mod.c */*/*/*.mod */*/*/*.o */*/*/.*.cmd */*/*/*.ko
    cd hal ; rm -fr */*/*.mod.c */*/*.mod */*/*.o */*/.*.cmd */*/*.ko
    cd hal ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
    cd hal ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
    cd core ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
    cd core ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
    cd os_dep/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
    cd os_dep ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
    cd platform ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
    rm -fr Module.symvers ; rm -fr Module.markers ; rm -fr modules.order
    rm -fr *.mod.c *.mod *.o .*.cmd *.ko *~
    rm -fr .tmp_versions
    /bin/sh: 1: bc: not found
    make ARCH=arm CROSS_COMPILE= -C /lib/modules/4.1.7-v7+/build M=/home/pi/src/88x2bu-20210702  modules
    make[1]: *** /lib/modules/4.1.7-v7+/build: No such file or directory.  Stop.
    Makefile:2503: recipe for target 'modules' failed
    make: *** [modules] Error 2
    An error occurred. Error = 2
    Please report this error.
    Please copy all screen output and paste it into the report.
    You will need to run the following before reattempting installation.
    $ sudo ./remove-driver-no-dkms.sh
    
    opened by JoseDzRFP 6
  • Adapter not recognized after ubuntu kernel updated to 5.15.0-50

    Adapter not recognized after ubuntu kernel updated to 5.15.0-50

    I have a EDUP USB WiFi 6 Adapter for PC, AX1800 USB 3.0 dongle installed with Ubuntu 20.04. The driver works OK by re-installing driver for each kernel update until 5.15.0-48.

    The driver rebuild and install smoothly, just the OS cannot recognize the adapter any more. Below is the failed attempt with kernel 5.15.0-52 and the latest code.

    5.15.0-52-generic x86_64 SecureBoot disabled Platform is in Setup Mode Bus 002 Device 003: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 002: ID 152d:1561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS561U two ports SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0c76:161f JMTek, LLC. USB PnP Audio Device Bus 001 Device 005: ID 1532:006e Razer USA, Ltd Razer DeathAdder Essential Bus 001 Device 004: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 0bda:885c Realtek Semiconductor Corp. 802.11ax WLAN Adapter Bus 001 Device 002: ID 0bda:0811 Realtek Semiconductor Corp. 802.11ac WLAN Adapter Bus 001 Device 007: ID 046d:c53d Logitech, Inc. USB Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: hci0: Bluetooth Soft blocked: no Hard blocked: no nvidia, 510.47.03, 5.13.0-52-generic, x86_64: installed nvidia, 510.47.03, 5.15.0-48-generic, x86_64: installedError! Could not locate dkms.conf file. File: /var/lib/dkms/rtl8812au/4.3.14/source/dkms.conf does not exist.

    nvidia, 510.47.03, 5.15.0-52-generic, x86_64: installed nvidia, 510.47.03, 5.4.0-131-generic, x86_64: installed openrazer-driver, 3.1.0, 5.11.0-46-generic, x86_64: installed openrazer-driver, 3.1.0, 5.13.0-52-generic, x86_64: installed openrazer-driver, 3.1.0, 5.15.0-48-generic, x86_64: installed openrazer-driver, 3.1.0, 5.15.0-52-generic, x86_64: installed openrazer-driver, 3.1.0, 5.4.0-131-generic, x86_64: installed 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)

    opened by pc2005 1
  • [not a bug] Undefined behavior warnings by UBSAN

    [not a bug] Undefined behavior warnings by UBSAN

    The driver works fine but there are some call stack dump in my dmesg. So I think I should share them.

    The commit I'm using is:

    commit 95a17181003c2d777cfc0fc70ef729af6f6a5ed8 (HEAD -> main, origin/main, origin/HEAD)
    Author: morrownr <[email protected]>
    Date:   Sun Jul 10 15:36:10 2022 -0500
    
        update README.md
    

    I have two kernel modules from this repo. 88x2bu1 and 88x2bu2. They are from the same commit.

    I think I did not see this kind of logs on Ubuntu 20.04. Recently I upgraded to 22.04, so perhaps these logs started to show up because of the kernel version change?

    [   11.787959] UBSAN: invalid-load in /var/lib/dkms/rtl88x2bu1/5.13.1/build/hal/phydm/phydm_ccx.c:696:17
    [   11.672305] load of value 255 is not a valid value for type '_Bool'
    [   11.672308] CPU: 3 PID: 926 Comm: RTW_CMD_THREAD Tainted: P           OE     5.15.0-47-generic #51-Ubuntu
    [   11.672311] Hardware name: AAEON MIX-EHLD1/MIX-EHLD1, BIOS 0006 01/07/2022
    [   11.672313] Call Trace:
    [   11.672316]  <TASK>
    [   11.672320]  show_stack+0x52/0x5c
    [   11.672327]  dump_stack_lvl+0x4a/0x63
    [   11.672334]  dump_stack+0x10/0x16
    [   11.672336]  ubsan_epilogue+0x9/0x49
    [   11.672338]  __ubsan_handle_load_invalid_value.cold+0x44/0x49
    [   11.672341]  ? rtw_hal_mgnt_xmit+0x7d/0xa2 [88x2bu1]
    [   11.672440]  phydm_nhm_mntr_set+0x121/0x123 [88x2bu1]
    [   11.672513]  phydm_env_mntr_trigger+0x3c/0x160 [88x2bu1]
    [   11.672594]  rtw_acs_trigger+0x90/0xfd [88x2bu1]
    [   11.672692]  sitesurvey_cmd_hdl+0xe9c/0x1192 [88x2bu1]
    [   11.672770]  ? kfree+0x161/0x250
    [   11.672774]  ? up+0x37/0x70
    [   11.672778]  ? _rtw_up_sema+0xe/0x14 [88x2bu1]
    [   11.672865]  ? init_mlme_ext_priv+0x217/0x217 [88x2bu1]
    [   11.672950]  rtw_cmd_thread+0x41c/0x76b [88x2bu1]
    [   11.673013]  ? rtw_stop_cmd_thread+0x49/0x49 [88x2bu1]
    [   11.673077]  kthread+0x127/0x150
    [   11.673081]  ? set_kthread_struct+0x50/0x50
    [   11.673084]  ret_from_fork+0x1f/0x30
    [   11.673088]  </TASK>
    
    [   11.787959] UBSAN: array-index-out-of-bounds in /var/lib/dkms/rtl88x2bu2/5.13.1/build/hal/phydm/phydm_dfs.c:1286:51
    [   11.787962] index 6 is out of range for type 'u8 [6]'
    [   11.787965] CPU: 3 PID: 881 Comm: RTW_CMD_THREAD Tainted: P           OE     5.15.0-47-generic #51-Ubuntu
    [   11.787968] Hardware name: AAEON MIX-EHLD1/MIX-EHLD1, BIOS 0006 01/07/2022
    [   11.787970] Call Trace:
    [   11.787973]  <TASK>
    [   11.787977]  show_stack+0x52/0x5c
    [   11.787983]  dump_stack_lvl+0x4a/0x63
    [   11.787989]  dump_stack+0x10/0x16
    [   11.787992]  ubsan_epilogue+0x9/0x49
    [   11.787994]  __ubsan_handle_out_of_bounds.cold+0x44/0x49
    [   11.787997]  ? rtw_hal_write_bbreg+0x17/0x25 [88x2bu2]
    [   11.788093]  ? odm_set_bb_reg+0x24/0x73 [88x2bu2]
    [   11.788169]  phydm_dfs_histogram_radar_distinguish+0x4d4/0x1d80 [88x2bu2]
    [   11.788241]  phydm_radar_detect+0x1ce/0x249 [88x2bu2]
    [   11.788311]  rtw_odm_radar_detect+0x17/0x1d [88x2bu2]
    [   11.788382]  rtw_dfs_rd_hdl+0x1d0/0x3e1 [88x2bu2]
    [   11.788431]  rtw_drvextra_cmd_hdl+0x202/0x580 [88x2bu2]
    [   11.788478]  ? _rtw_up_sema+0xe/0x14 [88x2bu2]
    [   11.788553]  ? rtw_ac_parm_cmd_hdl+0x19b/0x19b [88x2bu2]
    [   11.788599]  rtw_cmd_thread+0x41c/0x76b [88x2bu2]
    [   11.788645]  ? rtw_stop_cmd_thread+0x49/0x49 [88x2bu2]
    [   11.788690]  kthread+0x127/0x150
    [   11.788693]  ? set_kthread_struct+0x50/0x50
    [   11.788696]  ret_from_fork+0x1f/0x30
    [   11.788700]  </TASK>
    

    Here are some warnings similar to the previous one (call stack removed):

    [   11.788712] UBSAN: array-index-out-of-bounds in /var/lib/dkms/rtl88x2bu2/5.13.1/build/hal/phydm/phydm_dfs.c:1287:46
    [   11.788714] index 6 is out of range for type 'u8 [6]'
    
    [   11.789460] UBSAN: array-index-out-of-bounds in /var/lib/dkms/rtl88x2bu2/5.13.1/build/hal/phydm/phydm_dfs.c:1286:24
    [   11.789462] index 6 is out of range for type 'u8 [6]'
    
    [   11.790185] UBSAN: array-index-out-of-bounds in /var/lib/dkms/rtl88x2bu2/5.13.1/build/hal/phydm/phydm_dfs.c:1288:53
    [   11.790187] index 6 is out of range for type 'u8 [6]'
    
    [   11.790919] UBSAN: array-index-out-of-bounds in /var/lib/dkms/rtl88x2bu2/5.13.1/build/hal/phydm/phydm_dfs.c:1289:47
    [   11.790922] index 6 is out of range for type 'u8 [6]'
    
    [   11.791672] UBSAN: array-index-out-of-bounds in /var/lib/dkms/rtl88x2bu2/5.13.1/build/hal/phydm/phydm_dfs.c:1288:25
    [   11.791674] index 6 is out of range for type 'u8 [6]
    
    opened by spcharc 2
  • (info) ? blacklist rtw88_8822bu ?

    (info) ? blacklist rtw88_8822bu ?

    i search on all what can find, but rtw88 brings not a module rtw_8822bu, lwfingers and also in kernel-tree nothing rtw88 build only modules for pci/pcie not for usb-devices

    so ithink: if a rtw_8822be conflicts with 88x2bu (or with a renamed rtl88x2bu), then the correct entry would here: blacklist rtw88_8822be not bu

    is it right ?

    if YES; then add Hint: in few cases a usb-adapter with rtl88(12/22)bu chip can conflict with a onboard realtek 88(12/22)be (e = pci/pcie) driver, so you can add blacklist rtw88_8822be on the /etc/modprobe.d/blacklist Don't forgett to delete this entry, if you will use the onboard device! Please feel free to correcting!

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

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

Nick 191 Nov 30, 2022
Linux Driver for USB WiFi Adapters that are based on the RTL8812AU Chipset - v5.13.6

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

Nick 224 Nov 26, 2022
LLVM IR and optimizer for shaders, including front-end adapters for GLSL and SPIR-V and back-end adapter for GLSL

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

LunarG, Inc. 154 Sep 12, 2022
Kexts enabling native support for Intel Bluetooth chipsets in macOS.

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

null 133 Nov 21, 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
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 154 Nov 25, 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 46 Nov 6, 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 514 Nov 29, 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
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 141 Nov 22, 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 304 Nov 25, 2022
ESP8266 software USB host through general IO pins. We can connect up to 2 USB-LS HID (keyboard mouse joystick) devices simultaneously.

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

Samsonov Dima 28 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.

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 50 Nov 24, 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.7k Nov 23, 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 71 Nov 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 Installation (for users) Install Ultralea

null 58 Nov 11, 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 101 Oct 28, 2022
SinMapper - usermode driver mapper that forcefully loads any signed kernel driver

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

null 166 Nov 25, 2022