I'm not really up on WiFi card so I'm not sure if I'm on track. Is it possible to get a phy0 and phy1 device for each band? I want to set up a dual band, different SSID access point using this device if possible. I've looked at the docs for hostapd and it says it requires two physical devices and then says that dual physical devices are rare. I'm not sure if this is a driver trick or not.

Hi

I have been poking around in the driver code when I noticed that the code had several references to Beamforming. But a iw phyX info only revealed the capability for SU-Beamformee. This is ok when the nic is used in managed mode. But in AP it would seem to be more useful to have SU-Beamformer capabilities. MU-Beamformer and MU-Beamformee would be even better for AP and managed mode.

I found the driver parameter rtw_beamform_cap:int and at first I did not know what integers it would accept. The following code fragement from os_dep/linux/os_intfs.c explains the int as a bit pattern:

/*
 298 * BIT0: Enable VHT SU Beamformer
 299 * BIT1: Enable VHT SU Beamformee
 300 * BIT2: Enable VHT MU Beamformer, depend on VHT SU Beamformer
 301 * BIT3: Enable VHT MU Beamformee, depend on VHT SU Beamformee
 302 * BIT4: Enable HT Beamformer
 303 * BIT5: Enable HT Beamformee
 304 */
 305 int rtw_beamform_cap = BIT(1) | BIT(3);

The Bit pattern 11 activates BIT0 and BIT1, which converted to a decimal int value is a 3. So, when I set rtw_beamform_cap=3 as a param, we actually get SU-Beamforming and SU-Beamformee in the capability output of iw.
I then also tried to verify if that change actually made any difference, or if it is just words appearing on the screen. Using another wifi nic, I wiresharked the air for 8814au AP beacons and the SU-Beamformer and SU-Beamforee are mentioned. I have to look more into it if client devices actually make use of the function when upon conections.

But what would be more interesting would be to get MU-Beamforming working. regardless of what Bit converted value I add as a param, MU-capabilities are never shown. For instance: if one were to activate all the Bit related to Beamforming, would be 111111 as a bit pattern, and when converted to dec int it is 63. But this doesn't work.

Somewhere, in the beamforming code, I came cross a check for antenna count or stream count. But I did not understand it enough to be certain. I have a 4x4:3 device with 2 external rp-sma antennas and 2 internal ceramic antennas. The device is advertised, like most 8814au devices, as a 3T3R device. When the device is plugged in, I noticed debug entries that would declare the device as an 2T4R when probing the EEPROM (sorry, I dont have the logs on me at the moment). Maybe related?

Beamforming might not be that important afterall. This chip is falling out of favour anyways, but since I have it...
Anyways, just wanted to share this.
Cheers.

somehow it seems that latest git (d36c087) does not allow channel for ap anymore.
i've roll back a few commit (ab1d7f2) and i can use channel 44 for AP.

edit: i didn't test all commit. i just picked a random one

Strange problems here when using ASUS USB-AC68 to connect to Huawei AX3 router.
When connected to 2Ghz network, the speed of connection is actualy that of 5Ghz connection (tested with iperf).
Other devices (like phones) and also the same USB adapter plugged into Windows 10 host connect just fine, the result is correct speed for both frequencies.

The Linux is:

Linux debian 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux

Connection shows 2Ghz:

wlxb06ebfa94f43  IEEE 802.11bgn  ESSID:"TEST_Huawei_AX3_2Ghz"  Nickname:"WIFI@RTL8814AU"
          Mode:Managed  Frequency:2.437 GHz  Access Point: B0:CC:FE:77:85:00   
          Bit Rate:400 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:****-****-****-****-****-****-****-****   Security mode:open
          Power Management:off
          Link Quality=100/100  Signal level=-46 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

But iperf is way too fast:

$ iperf3 -c 192.168.3.113
Connecting to host 192.168.3.113, port 5201
[  5] local 192.168.3.3 port 44140 connected to 192.168.3.113 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  17.3 MBytes   145 Mbits/sec    0    901 KBytes       
[  5]   1.00-2.00   sec  23.8 MBytes   199 Mbits/sec    0   1.10 MBytes       
[  5]   2.00-3.00   sec  31.2 MBytes   262 Mbits/sec    0   1.31 MBytes       
[  5]   3.00-4.00   sec  32.5 MBytes   273 Mbits/sec    0   1.47 MBytes       
[  5]   4.00-5.00   sec  30.0 MBytes   252 Mbits/sec    0   2.05 MBytes       
[  5]   5.00-6.00   sec  31.2 MBytes   262 Mbits/sec    0   2.32 MBytes       
[  5]   6.00-7.00   sec  30.0 MBytes   252 Mbits/sec    0   2.32 MBytes       
[  5]   7.00-8.00   sec  31.2 MBytes   262 Mbits/sec    0   2.32 MBytes       
[  5]   8.00-9.00   sec  32.5 MBytes   273 Mbits/sec    0   2.32 MBytes       
[  5]   9.00-10.00  sec  31.2 MBytes   262 Mbits/sec    0   2.32 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   291 MBytes   244 Mbits/sec    0             sender
[  5]   0.00-10.01  sec   289 MBytes   242 Mbits/sec                  receiver

iperf Done.

The driver is latest from git:

filename:       /lib/modules/4.19.0-16-amd64/kernel/drivers/net/wireless/8814au.ko
version:        v5.8.5.1_35583.20191029
author:         Realtek Semiconductor Corp.
description:    Realtek Wireless Lan Driver
license:        GPL
srcversion:     D77CF5AF84235DF5728F810
alias:          usb:v0846p9054d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v20F4p809Bd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v20F4p809Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2357p0106d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0E66p0026d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDAp8813d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v7392pA833d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v7392pA834d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v056Ep400Dd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v056Ep400Bd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0B05p1853d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0B05p1852d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0B05p1817d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2001p331Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDAp8813d*dc*dsc*dp*ic*isc*ip*in*
depends:        usbcore,cfg80211
retpoline:      Y
name:           8814au
vermagic:       4.19.0-16-amd64 SMP mod_unload modversions 
parm:           rtw_wireless_mode:int
parm:           rtw_ips_mode:The default IPS mode (int)
parm:           rtw_lps_level:The default LPS level (int)
parm:           rtw_lps_chk_by_tp:int
parm:           rtw_max_bss_cnt:int
parm:           rtw_usb_rxagg_mode:int
parm:           rtw_dynamic_agg_enable:int
parm:           rtw_drv_log_level:set log level when insert driver module, default log level is _DRV_INFO_ = 4 (uint)
parm:           rtw_tx_aclt_flags:device TX AC queue packet lifetime control flags (uint)
parm:           rtw_tx_aclt_conf_default:device TX AC queue lifetime config for default status (array of uint)
parm:           rtw_tx_aclt_conf_ap_m2u:device TX AC queue lifetime config for AP mode M2U status (array of uint)
parm:           rtw_tx_bw_mode:The max tx bw for 2.4G and 5G. format is the same as rtw_bw_mode (uint)
parm:           rtw_rx_ampdu_sz_limit_1ss:RX AMPDU size limit for 1SS link of each BW, 0xFF: no limitation (array of uint)
parm:           rtw_rx_ampdu_sz_limit_2ss:RX AMPDU size limit for 2SS link of each BW, 0xFF: no limitation (array of uint)
parm:           rtw_rx_ampdu_sz_limit_3ss:RX AMPDU size limit for 3SS link of each BW, 0xFF: no limitation (array of uint)
parm:           rtw_rx_ampdu_sz_limit_4ss:RX AMPDU size limit for 4SS link of each BW, 0xFF: no limitation (array of uint)
parm:           rtw_vht_enable:int
parm:           rtw_vht_rx_mcs_map:VHT RX MCS map (uint)
parm:           rtw_rf_path:int
parm:           rtw_tx_nss:int
parm:           rtw_rx_nss:int
parm:           rtw_country_code:The default country code (in alpha2) (charp)
parm:           rtw_channel_plan:The default chplan ID when rtw_alpha2 is not specified or valid (int)
parm:           rtw_excl_chs:exclusive channel array (array of uint)
parm:           rtw_pci_dynamic_aspm_linkctrl:int
parm:           rtw_qos_opt_enable:int
parm:           ifname:The default name to allocate for first interface (charp)
parm:           if2name:The default name to allocate for second interface (charp)
parm:           rtw_wowlan_sta_mix_mode:int
parm:           rtw_pwrtrim_enable:int
parm:           rtw_initmac:charp
parm:           rtw_chip_version:int
parm:           rtw_rfintfs:int
parm:           rtw_lbkmode:int
parm:           rtw_network_mode:int
parm:           rtw_channel:int
parm:           rtw_mp_mode:int
parm:           rtw_wmm_enable:int
parm:           rtw_vrtl_carrier_sense:int
parm:           rtw_vcs_type:int
parm:           rtw_busy_thresh:int
parm:           rtw_ht_enable:int
parm:           rtw_bw_mode:int
parm:           rtw_ampdu_enable:int
parm:           rtw_rx_stbc:int
parm:           rtw_rx_ampdu_amsdu:int
parm:           rtw_tx_ampdu_amsdu:int
parm:           rtw_beamform_cap:int
parm:           rtw_lowrate_two_xmit:int
parm:           rtw_power_mgnt:int
parm:           rtw_smart_ps:int
parm:           rtw_low_power:int
parm:           rtw_wifi_spec:int
parm:           rtw_full_ch_in_p2p_handshake:int
parm:           rtw_antdiv_cfg:int
parm:           rtw_antdiv_type:int
parm:           rtw_drv_ant_band_switch:int
parm:           rtw_single_ant_path:int
parm:           rtw_switch_usb_mode:int
parm:           rtw_enusbss:int
parm:           rtw_hwpdn_mode:int
parm:           rtw_hwpwrp_detect:int
parm:           rtw_hw_wps_pbc:int
parm:           rtw_check_hw_status:int
parm:           rtw_led_ctrl:Led Control: 0=Always off, 1=Normal blink, 2=Always on (int)
parm:           rtw_max_roaming_times:The max roaming times to try (uint)
parm:           rtw_mc2u_disable:int
parm:           rtw_notch_filter:0:Disable, 1:Enable, 2:Enable only for P2P (uint)
parm:           rtw_hiq_filter:0:allow all, 1:allow special, 2:deny all (uint)
parm:           rtw_adaptivity_en:0:disable, 1:enable (uint)
parm:           rtw_adaptivity_mode:0:normal, 1:carrier sense (uint)
parm:           rtw_adaptivity_th_l2h_ini:th_l2h_ini for Adaptivity (int)
parm:           rtw_adaptivity_th_edcca_hl_diff:th_edcca_hl_diff for Adaptivity (int)
parm:           rtw_amplifier_type_2g:BIT3:2G ext-PA, BIT4:2G ext-LNA (uint)
parm:           rtw_amplifier_type_5g:BIT6:5G ext-PA, BIT7:5G ext-LNA (uint)
parm:           rtw_RFE_type:default init value:64 (uint)
parm:           rtw_powertracking_type:default init value:64 (uint)
parm:           rtw_GLNA_type:default init value:0 (uint)
parm:           rtw_TxBBSwing_2G:default init value:0xFF (uint)
parm:           rtw_TxBBSwing_5G:default init value:0xFF (uint)
parm:           rtw_OffEfuseMask:default open Efuse Mask value:0 (uint)
parm:           rtw_FileMaskEfuse:default drv Mask Efuse value:0 (uint)
parm:           rtw_rxgain_offset_2g:default RF Gain 2G Offset value:0 (uint)
parm:           rtw_rxgain_offset_5gl:default RF Gain 5GL Offset value:0 (uint)
parm:           rtw_rxgain_offset_5gh:uint
parm:           rtw_rxgain_offset_5gm:default RF Gain 5GM Offset value:0 (uint)
parm:           rtw_pll_ref_clk_sel:force pll_ref_clk_sel, 0xF:use autoload value (uint)
parm:           rtw_tx_pwr_by_rate:0:Disable, 1:Enable, 2: Depend on efuse (int)
parm:           rtw_tx_pwr_lmt_enable:0:Disable, 1:Enable, 2: Depend on efuse (int)
parm:           rtw_target_tx_pwr_2g_a:2.4G target tx power (unit:dBm) of RF path A for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_2g_b:2.4G target tx power (unit:dBm) of RF path B for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_2g_c:2.4G target tx power (unit:dBm) of RF path C for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_2g_d:2.4G target tx power (unit:dBm) of RF path D for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_5g_a:5G target tx power (unit:dBm) of RF path A for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_5g_b:5G target tx power (unit:dBm) of RF path B for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_5g_c:5G target tx power (unit:dBm) of RF path C for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_5g_d:5G target tx power (unit:dBm) of RF path D for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_tsf_update_pause_factor:num of bcn intervals to stay TSF update pause status (int)
parm:           rtw_tsf_update_restore_factor:num of bcn intervals to stay TSF update restore status (int)
parm:           rtw_phy_file_path:The path of phy parameter (charp)
parm:           rtw_load_phy_file:PHY File Bit Map (int)
parm:           rtw_decrypt_phy_file:Enable Decrypt PHY File (int)
parm:           rtw_phydm_ability:uint
parm:           rtw_halrf_ability:uint
parm:           rtw_en_napi:int
parm:           rtw_en_gro:int
parm:           rtw_iqk_fw_offload:int
parm:           rtw_ch_switch_offload:int

there's a bunch of warnings in the syslog while kismet is running. it still receives devices and everything seems to work ok. the warnings are coming in at around one per second and they slowly blow up the logfile.

platform: raspi4 8GB
hardware: alfa AWUS1900
Linux kali 5.4.83-Re4son-v8l+ aarch64

driver built from git revision: 32b6c9e
built according to instructions (raspi64.sh and install-driver.sh)

iwconfig

wlan1     IEEE 802.11b  ESSID:""  Nickname:"WIFI@RTL8814AU"
          Mode:Monitor  Frequency:5.805 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

Can these warnings be ignored? If yes, can they be suppressed somehow?

Here's a sample of the warnings

Oct  7 18:15:22 kali kernel: [ 1642.425379] ------------[ cut here ]------------
Oct  7 18:15:22 kali kernel: [ 1642.435387] WARNING: CPU: 3 PID: 1173 at /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rf.c:215 rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:22 kali kernel: [ 1642.445395] Modules linked in: cdc_acm rfcomm algif_hash aes_neon_bs aes_neon_blk crypto_simd cryptd algif_skcipher af_alg bnep btusb btrtl btintel btbcm bluetooth ecdh_generic ecc 8814au(O) binfmt_misc sg brcmfmac brcmutil bcm2835_isp(C) cfg80211 bcm2835_codec(C) bcm2835_v4l2(C) videobuf2_vmalloc v4l2_mem2mem bcm2835_mmal_vchiq(C) snd_bcm2835(C) videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common rfkill snd_pcm snd_timer raspberrypi_hwmon snd videodev vc_sm_cma(C) mc rpivid_mem uio_pdrv_genirq uio fuse drm drm_panel_orientation_quirks ip_tables x_tables ipv6
Oct  7 18:15:22 kali kernel: [ 1642.466674] CPU: 3 PID: 1173 Comm: RTW_CMD_THREAD Tainted: G        WC O      5.4.83-Re4son-v8l+ #1
Oct  7 18:15:22 kali kernel: [ 1642.477629] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
Oct  7 18:15:22 kali kernel: [ 1642.486088] pstate: 60000005 (nZCv daif -PAN -UAO)
Oct  7 18:15:22 kali kernel: [ 1642.493267] pc : rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:22 kali kernel: [ 1642.500256] lr : rtw_hal_set_chnl_bw+0x144/0x14c [8814au]
Oct  7 18:15:22 kali kernel: [ 1642.507209] sp : ffffffc01185bd00
Oct  7 18:15:22 kali kernel: [ 1642.514108] x29: ffffffc01185bd00 x28: ffffff81f2564a00 
Oct  7 18:15:22 kali kernel: [ 1642.520972] x27: 0000000000000002 x26: 0000000000000000 
Oct  7 18:15:22 kali kernel: [ 1642.527835] x25: 0000000000000000 x24: 000000000000003a 
Oct  7 18:15:22 kali kernel: [ 1642.534666] x23: 000000000000003a x22: 000000000000003e 
Oct  7 18:15:22 kali kernel: [ 1642.541527] x21: 0000000000000000 x20: 0000000000000001 
Oct  7 18:15:22 kali kernel: [ 1642.548313] x19: 000000000000003e x18: 0000000000000000 
Oct  7 18:15:22 kali kernel: [ 1642.555073] x17: 0000000000000000 x16: 0000000000000000 
Oct  7 18:15:22 kali kernel: [ 1642.561876] x15: 0000000000000390 x14: 0000000000005d3f 
Oct  7 18:15:22 kali kernel: [ 1642.568670] x13: 00000199319449b0 x12: 0000000000000000 
Oct  7 18:15:22 kali kernel: [ 1642.575527] x11: 0000000000000000 x10: 00000000000019a0 
Oct  7 18:15:22 kali kernel: [ 1642.582354] x9 : ffffffc01185bc20 x8 : ffffff81e5427340 
Oct  7 18:15:22 kali kernel: [ 1642.589159] x7 : 0000017e62a60d99 x6 : ffffffc010eb9000 
Oct  7 18:15:22 kali kernel: [ 1642.596037] x5 : ffffffc010eb9098 x4 : ffffffc01185c000 
Oct  7 18:15:22 kali kernel: [ 1642.602904] x3 : 0000000000000000 x2 : 0000000000000000 
Oct  7 18:15:22 kali kernel: [ 1642.609815] x1 : 0000000000000001 x0 : ffffffc008f6a0d0 
Oct  7 18:15:22 kali kernel: [ 1642.616662] Call trace:
Oct  7 18:15:22 kali kernel: [ 1642.623514]  rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:22 kali kernel: [ 1642.630494]  rtw_hal_set_chnl_bw+0x144/0x14c [8814au]
Oct  7 18:15:22 kali kernel: [ 1642.637452]  set_channel_bwmode+0xc0/0x130 [8814au]
Oct  7 18:15:22 kali kernel: [ 1642.644448]  rtw_set_chbw_hdl+0x5c/0xa0 [8814au]
Oct  7 18:15:22 kali kernel: [ 1642.651391]  rtw_cmd_thread+0x43c/0x5e4 [8814au]
Oct  7 18:15:22 kali kernel: [ 1642.658249]  kthread+0x144/0x150
Oct  7 18:15:22 kali kernel: [ 1642.665117]  ret_from_fork+0x10/0x18
Oct  7 18:15:22 kali kernel: [ 1642.671968] ---[ end trace df86b4807935df2a ]---
Oct  7 18:15:23 kali kernel: [ 1643.372868] ------------[ cut here ]------------
Oct  7 18:15:23 kali kernel: [ 1643.382459] WARNING: CPU: 3 PID: 1173 at /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rf.c:215 rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:23 kali kernel: [ 1643.391001] Modules linked in: cdc_acm rfcomm algif_hash aes_neon_bs aes_neon_blk crypto_simd cryptd algif_skcipher af_alg bnep btusb btrtl btintel btbcm bluetooth ecdh_generic ecc 8814au(O) binfmt_misc sg brcmfmac brcmutil bcm2835_isp(C) cfg80211 bcm2835_codec(C) bcm2835_v4l2(C) videobuf2_vmalloc v4l2_mem2mem bcm2835_mmal_vchiq(C) snd_bcm2835(C) videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common rfkill snd_pcm snd_timer raspberrypi_hwmon snd videodev vc_sm_cma(C) mc rpivid_mem uio_pdrv_genirq uio fuse drm drm_panel_orientation_quirks ip_tables x_tables ipv6
Oct  7 18:15:23 kali kernel: [ 1643.405988] CPU: 3 PID: 1173 Comm: RTW_CMD_THREAD Tainted: G        WC O      5.4.83-Re4son-v8l+ #1
Oct  7 18:15:23 kali kernel: [ 1643.413672] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
Oct  7 18:15:23 kali kernel: [ 1643.421076] pstate: 80000005 (Nzcv daif -PAN -UAO)
Oct  7 18:15:23 kali kernel: [ 1643.428290] pc : rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:23 kali kernel: [ 1643.435294] lr : rtw_hal_set_chnl_bw+0x144/0x14c [8814au]
Oct  7 18:15:23 kali kernel: [ 1643.442259] sp : ffffffc01185bd00
Oct  7 18:15:23 kali kernel: [ 1643.449176] x29: ffffffc01185bd00 x28: ffffff81f2564a00 
Oct  7 18:15:23 kali kernel: [ 1643.456061] x27: 0000000000000001 x26: 0000000000000000 
Oct  7 18:15:23 kali kernel: [ 1643.462931] x25: 0000000000000000 x24: 000000000000007a 
Oct  7 18:15:23 kali kernel: [ 1643.469781] x23: 000000000000007a x22: 0000000000000076 
Oct  7 18:15:23 kali kernel: [ 1643.476653] x21: 0000000000000000 x20: 0000000000000001 
Oct  7 18:15:23 kali kernel: [ 1643.483451] x19: 0000000000000076 x18: 0000000000000000 
Oct  7 18:15:23 kali kernel: [ 1643.490240] x17: 0000000000000000 x16: 0000000000000000 
Oct  7 18:15:23 kali kernel: [ 1643.497041] x15: 0000000000000127 x14: 000000000000ba7e 
Oct  7 18:15:23 kali kernel: [ 1643.503858] x13: ffffffc01000d000 x12: 0000000000000001 
Oct  7 18:15:23 kali kernel: [ 1643.510711] x11: 0000000000040930 x10: 00000000000019a0 
Oct  7 18:15:23 kali kernel: [ 1643.517545] x9 : ffffffc01185bc20 x8 : ffffff81e5427340 
Oct  7 18:15:23 kali kernel: [ 1643.524378] x7 : 0000000000000000 x6 : ffffffc010eb9000 
Oct  7 18:15:23 kali kernel: [ 1643.531233] x5 : ffffffc010eb9098 x4 : ffffffc01185c000 
Oct  7 18:15:23 kali kernel: [ 1643.538085] x3 : 0000000000000000 x2 : 0000000000000000 
Oct  7 18:15:23 kali kernel: [ 1643.544975] x1 : 0000000000000001 x0 : ffffffc008f6a0d0 
Oct  7 18:15:23 kali kernel: [ 1643.551812] Call trace:
Oct  7 18:15:23 kali kernel: [ 1643.558686]  rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:23 kali kernel: [ 1643.565601]  rtw_hal_set_chnl_bw+0x144/0x14c [8814au]
Oct  7 18:15:23 kali kernel: [ 1643.572545]  set_channel_bwmode+0xc0/0x130 [8814au]
Oct  7 18:15:23 kali kernel: [ 1643.579531]  rtw_set_chbw_hdl+0x5c/0xa0 [8814au]
Oct  7 18:15:23 kali kernel: [ 1643.586456]  rtw_cmd_thread+0x43c/0x5e4 [8814au]
Oct  7 18:15:23 kali kernel: [ 1643.593291]  kthread+0x144/0x150
Oct  7 18:15:23 kali kernel: [ 1643.600141]  ret_from_fork+0x10/0x18
Oct  7 18:15:23 kali kernel: [ 1643.606979] ---[ end trace df86b4807935df2b ]---
Oct  7 18:15:26 kali kernel: [ 1646.173619] ------------[ cut here ]------------
Oct  7 18:15:26 kali kernel: [ 1646.183594] WARNING: CPU: 3 PID: 1173 at /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rf.c:215 rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:26 kali kernel: [ 1646.193453] Modules linked in: cdc_acm rfcomm algif_hash aes_neon_bs aes_neon_blk crypto_simd cryptd algif_skcipher af_alg bnep btusb btrtl btintel btbcm bluetooth ecdh_generic ecc 8814au(O) binfmt_misc sg brcmfmac brcmutil bcm2835_isp(C) cfg80211 bcm2835_codec(C) bcm2835_v4l2(C) videobuf2_vmalloc v4l2_mem2mem bcm2835_mmal_vchiq(C) snd_bcm2835(C) videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common rfkill snd_pcm snd_timer raspberrypi_hwmon snd videodev vc_sm_cma(C) mc rpivid_mem uio_pdrv_genirq uio fuse drm drm_panel_orientation_quirks ip_tables x_tables ipv6
Oct  7 18:15:26 kali kernel: [ 1646.214845] CPU: 3 PID: 1173 Comm: RTW_CMD_THREAD Tainted: G        WC O      5.4.83-Re4son-v8l+ #1
Oct  7 18:15:26 kali kernel: [ 1646.225650] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
Oct  7 18:15:26 kali kernel: [ 1646.236215] pstate: 60000005 (nZCv daif -PAN -UAO)
Oct  7 18:15:26 kali kernel: [ 1646.243854] pc : rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:26 kali kernel: [ 1646.250892] lr : rtw_hal_set_chnl_bw+0x144/0x14c [8814au]
Oct  7 18:15:26 kali kernel: [ 1646.257724] sp : ffffffc01185bd00
Oct  7 18:15:26 kali kernel: [ 1646.264659] x29: ffffffc01185bd00 x28: ffffff81f2564a00 
Oct  7 18:15:26 kali kernel: [ 1646.271527] x27: 0000000000000002 x26: 0000000000000000 
Oct  7 18:15:26 kali kernel: [ 1646.278385] x25: 0000000000000000 x24: 000000000000002a 
Oct  7 18:15:26 kali kernel: [ 1646.285258] x23: 000000000000002a x22: 000000000000002e 
Oct  7 18:15:26 kali kernel: [ 1646.292007] x21: 0000000000000000 x20: 0000000000000001 
Oct  7 18:15:26 kali kernel: [ 1646.298837] x19: 000000000000002e x18: 0000000000000000 
Oct  7 18:15:26 kali kernel: [ 1646.305622] x17: 0000000000000000 x16: 0000000000000000 
Oct  7 18:15:26 kali kernel: [ 1646.312408] x15: 0000000000000000 x14: 000000000000ba7e 
Oct  7 18:15:26 kali kernel: [ 1646.319249] x13: 0000bdf2b7509aa6 x12: 0000000000000000 
Oct  7 18:15:26 kali kernel: [ 1646.325984] x11: 000000000000bdf2 x10: 00000000000019a0 
Oct  7 18:15:26 kali kernel: [ 1646.332797] x9 : ffffffc01185bc20 x8 : ffffff81e5427340 
Oct  7 18:15:26 kali kernel: [ 1646.339688] x7 : 0000017f4437da86 x6 : ffffffc010eb9000 
Oct  7 18:15:26 kali kernel: [ 1646.346532] x5 : ffffffc010eb9098 x4 : ffffffc01185c000 
Oct  7 18:15:26 kali kernel: [ 1646.353435] x3 : 0000000000000000 x2 : 0000000000000000 
Oct  7 18:15:26 kali kernel: [ 1646.360218] x1 : 0000000000000001 x0 : ffffffc008f6a0d0 
Oct  7 18:15:26 kali kernel: [ 1646.367065] Call trace:
Oct  7 18:15:26 kali kernel: [ 1646.374018]  rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:26 kali kernel: [ 1646.380945]  rtw_hal_set_chnl_bw+0x144/0x14c [8814au]
Oct  7 18:15:26 kali kernel: [ 1646.387920]  set_channel_bwmode+0xc0/0x130 [8814au]
Oct  7 18:15:26 kali kernel: [ 1646.394818]  rtw_set_chbw_hdl+0x5c/0xa0 [8814au]
Oct  7 18:15:26 kali kernel: [ 1646.401793]  rtw_cmd_thread+0x43c/0x5e4 [8814au]
Oct  7 18:15:26 kali kernel: [ 1646.408666]  kthread+0x144/0x150
Oct  7 18:15:26 kali kernel: [ 1646.415528]  ret_from_fork+0x10/0x18
Oct  7 18:15:26 kali kernel: [ 1646.422374] ---[ end trace df86b4807935df2c ]---
Oct  7 18:15:27 kali kernel: [ 1647.123754] ------------[ cut here ]------------
Oct  7 18:15:27 kali kernel: [ 1647.133754] WARNING: CPU: 3 PID: 1173 at /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rf.c:215 rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:27 kali kernel: [ 1647.143751] Modules linked in: cdc_acm rfcomm algif_hash aes_neon_bs aes_neon_blk crypto_simd cryptd algif_skcipher af_alg bnep btusb btrtl btintel btbcm bluetooth ecdh_generic ecc 8814au(O) binfmt_misc sg brcmfmac brcmutil bcm2835_isp(C) cfg80211 bcm2835_codec(C) bcm2835_v4l2(C) videobuf2_vmalloc v4l2_mem2mem bcm2835_mmal_vchiq(C) snd_bcm2835(C) videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common rfkill snd_pcm snd_timer raspberrypi_hwmon snd videodev vc_sm_cma(C) mc rpivid_mem uio_pdrv_genirq uio fuse drm drm_panel_orientation_quirks ip_tables x_tables ipv6
Oct  7 18:15:27 kali kernel: [ 1647.162880] CPU: 3 PID: 1173 Comm: RTW_CMD_THREAD Tainted: G        WC O      5.4.83-Re4son-v8l+ #1
Oct  7 18:15:27 kali kernel: [ 1647.170538] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
Oct  7 18:15:27 kali kernel: [ 1647.177924] pstate: 60000005 (nZCv daif -PAN -UAO)
Oct  7 18:15:27 kali kernel: [ 1647.185172] pc : rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:27 kali kernel: [ 1647.192101] lr : rtw_hal_set_chnl_bw+0x144/0x14c [8814au]
Oct  7 18:15:27 kali kernel: [ 1647.199000] sp : ffffffc01185bd00
Oct  7 18:15:27 kali kernel: [ 1647.205945] x29: ffffffc01185bd00 x28: ffffff81f2564a00 
Oct  7 18:15:27 kali kernel: [ 1647.212813] x27: 0000000000000002 x26: 0000000000000000 
Oct  7 18:15:27 kali kernel: [ 1647.219746] x25: 0000000000000000 x24: 000000000000003a 
Oct  7 18:15:27 kali kernel: [ 1647.226504] x23: 000000000000003a x22: 000000000000003e 
Oct  7 18:15:27 kali kernel: [ 1647.233320] x21: 0000000000000000 x20: 0000000000000001 
Oct  7 18:15:27 kali kernel: [ 1647.240154] x19: 000000000000003e x18: 0000000000000000 
Oct  7 18:15:27 kali kernel: [ 1647.246943] x17: 0000000000000000 x16: 0000000000000000 
Oct  7 18:15:27 kali kernel: [ 1647.253768] x15: 0000000000000000 x14: 0000000000000000 
Oct  7 18:15:27 kali kernel: [ 1647.260485] x13: 0000000000000000 x12: 0000000000000000 
Oct  7 18:15:27 kali kernel: [ 1647.267243] x11: 0000000000000000 x10: 00000000000019a0 
Oct  7 18:15:27 kali kernel: [ 1647.274071] x9 : ffffffc01185bc20 x8 : ffffff81e5427340 
Oct  7 18:15:27 kali kernel: [ 1647.280878] x7 : 0000000000000000 x6 : ffffffc010eb9000 
Oct  7 18:15:27 kali kernel: [ 1647.287726] x5 : ffffffc010eb9098 x4 : ffffffc01185c000 
Oct  7 18:15:27 kali kernel: [ 1647.294494] x3 : 0000000000000000 x2 : 0000000000000000 
Oct  7 18:15:27 kali kernel: [ 1647.301309] x1 : 0000000000000001 x0 : ffffffc008f6a0d0 
Oct  7 18:15:27 kali kernel: [ 1647.308162] Call trace:
Oct  7 18:15:27 kali kernel: [ 1647.315039]  rtw_get_scch_by_cch_offset+0xa4/0x120 [8814au]
Oct  7 18:15:27 kali kernel: [ 1647.321940]  rtw_hal_set_chnl_bw+0x144/0x14c [8814au]
Oct  7 18:15:27 kali kernel: [ 1647.328822]  set_channel_bwmode+0xc0/0x130 [8814au]
Oct  7 18:15:27 kali kernel: [ 1647.335720]  rtw_set_chbw_hdl+0x5c/0xa0 [8814au]
Oct  7 18:15:27 kali kernel: [ 1647.342662]  rtw_cmd_thread+0x43c/0x5e4 [8814au]
Oct  7 18:15:27 kali kernel: [ 1647.349487]  kthread+0x144/0x150
Oct  7 18:15:27 kali kernel: [ 1647.356298]  ret_from_fork+0x10/0x18
Oct  7 18:15:27 kali kernel: [ 1647.363084] ---[ end trace df86b4807935df2d ]---

A pull request was submitted and merged today by @MatteoPaier. He may had found the problem with AP Mode. Early results look promising.

I am requesting everyone that has an interest to test and report on AP Mode here in this issue.

Regards,

Nick

I know it is not supported, but here is the log showing what fails
log.log

No common command seems to work. Is it possible to change this via the parameters in "/ sys / module / 8814au / parameters /"?

Thanks

When I run "iw phy"

Wiphy phy0
        wiphy index: 0
        max # scan SSIDs: 9
        max scan IEs length: 2304 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Supported Ciphers:
                * WEP40 (00-0f-ac:1)
                * WEP104 (00-0f-ac:5)
                * TKIP (00-0f-ac:2)
                * CCMP-128 (00-0f-ac:4)
                * CMAC (00-0f-ac:6)
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * monitor
        Band 1:
                Capabilities: 0x1863
                        RX LDPC
                        HT20/HT40
                        Static SM Power Save
                        RX HT20 SGI
                        RX HT40 SGI
                        No RX STBC
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 16 usec (0x07)
                HT Max RX data rate: 450 Mbps
                HT TX/RX MCS rate indexes supported: 0-23
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps
                        * 5.5 Mbps
                        * 11.0 Mbps
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
                Frequencies:
                        * 2412 MHz [1] (20.0 dBm)
                        * 2417 MHz [2] (20.0 dBm)
                        * 2422 MHz [3] (20.0 dBm)
                        * 2427 MHz [4] (20.0 dBm)
                        * 2432 MHz [5] (20.0 dBm)
                        * 2437 MHz [6] (20.0 dBm)
                        * 2442 MHz [7] (20.0 dBm)
                        * 2447 MHz [8] (20.0 dBm)
                        * 2452 MHz [9] (20.0 dBm)
                        * 2457 MHz [10] (20.0 dBm)
                        * 2462 MHz [11] (20.0 dBm)
                        * 2467 MHz [12] (20.0 dBm) (no IR)
                        * 2472 MHz [13] (20.0 dBm) (no IR)
                        * 2484 MHz [14] (disabled)
        Band 2:
                Capabilities: 0x1863
                        RX LDPC
                        HT20/HT40
                        Static SM Power Save
                        RX HT20 SGI
                        RX HT40 SGI
                        No RX STBC
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 16 usec (0x07)
                HT Max RX data rate: 450 Mbps
                HT TX/RX MCS rate indexes supported: 0-23
                VHT Capabilities (0x03c001b2):
                        Max MPDU length: 11454
                        Supported Channel Width: neither 160 nor 80+80
                        RX LDPC
                        short GI (80 MHz)
                        TX STBC
                        +HTC-VHT
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: MCS 0-9
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT RX highest supported: 1300 Mbps
                VHT TX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: MCS 0-9
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT TX highest supported: 1300 Mbps
                Bitrates (non-HT):
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
                Frequencies:
                        * 5180 MHz [36] (30.0 dBm)
                        * 5200 MHz [40] (30.0 dBm)
                        * 5220 MHz [44] (30.0 dBm)
                        * 5240 MHz [48] (30.0 dBm)
                        * 5260 MHz [52] (30.0 dBm) (no IR, radar detection)
                        * 5280 MHz [56] (30.0 dBm) (no IR, radar detection)
                        * 5300 MHz [60] (30.0 dBm) (no IR, radar detection)
                        * 5320 MHz [64] (30.0 dBm) (no IR, radar detection)
                        * 5500 MHz [100] (30.0 dBm) (no IR, radar detection)
                        * 5520 MHz [104] (30.0 dBm) (no IR, radar detection)
                        * 5540 MHz [108] (30.0 dBm) (no IR, radar detection)
                        * 5560 MHz [112] (30.0 dBm) (no IR, radar detection)
                        * 5580 MHz [116] (30.0 dBm) (no IR, radar detection)
                        * 5600 MHz [120] (30.0 dBm) (no IR, radar detection)
                        * 5620 MHz [124] (30.0 dBm) (no IR, radar detection)
                        * 5640 MHz [128] (30.0 dBm) (no IR, radar detection)
                        * 5660 MHz [132] (30.0 dBm) (no IR, radar detection)
                        * 5680 MHz [136] (30.0 dBm) (no IR, radar detection)
                        * 5700 MHz [140] (30.0 dBm) (no IR, radar detection)
                        * 5720 MHz [144] (disabled)
                        * 5745 MHz [149] (30.0 dBm)
                        * 5765 MHz [153] (30.0 dBm)
                        * 5785 MHz [157] (30.0 dBm)
                        * 5805 MHz [161] (30.0 dBm)
                        * 5825 MHz [165] (30.0 dBm)
                        * 5845 MHz [169] (disabled)
                        * 5865 MHz [173] (disabled)
                        * 5885 MHz [177] (disabled)
        Supported commands:
                 * new_interface
                 * set_interface
                 * new_key
                 * start_ap
                 * new_station
                 * set_bss
                 * join_ibss
                 * set_pmksa
                 * del_pmksa
                 * flush_pmksa
                 * remain_on_channel
                 * frame
                 * set_channel
                 * connect
                 * disconnect
        WoWLAN support:
                 * wake up on anything (device continues operating normally)
        software interface modes (can always be added):
                 * monitor
        interface combinations are not supported
        Device supports SAE with AUTHENTICATE command
        Device supports scan flush.
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Supported TX frame types:
                 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
        Supported RX frame types:
                 * IBSS: 0xd0
                 * managed: 0x40 0xb0 0xd0
                 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * P2P-client: 0x40 0xd0
                 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
        Supported extended features:

As you can see, "no IR" is displayed on the 5Ghz band. so, this frequency band cannot be used as an access point.
I changed to various countries using "iw reg set" and repeatedly uninstalled / installed the driver, but it didn't work at all.
Why are there such annoying restrictions?
Please fix the driver.

Hi,

I Just a refresh, but you know what I have as hardware: 2 TP-Link with RT8814u working as AP mode, one for 2.5G and another for 5G.

Everything working fine (as part of the test in https://github.com/morrownr/8814au/issues/26), except that last week I've updated the driver (why I did it!) and hardware freeze (server freeze) back again.

Same kernel (5.11.0-38-generic), same OS (Ubuntu 20.04, same hardware.

I will update today to lastet git and test just in case.

I am kind of new to linux. I get an error on the last step of building the drivers. I have done sudo update and upgrade and i still get it.

All i want is to get my Netgear A7000 to work on my raspberry Pi 400, that's all i care.

after i execute airmon-ng start ,every thing about network crash (every network interface) ,but i can still edit file ,
log:
[ 681.046805] RTW: rtw_wx_get_rts, rts_thresh=2347
[ 681.046816] RTW: rtw_wx_get_frag, frag_len=2346
[ 681.325120] RTW: rtw_ndev_notifier_call(wlp0s20f0u1) state:10
[ 681.325250] RTW: netdev_close(wlp0s20f0u1) , bup=1
[ 681.325259] RTW: -871x_drv - drv_close, bup=1
[ 681.328266] RTW: rtw_ndev_notifier_call(wlp0s20f0u1) state:2
[ 681.357292] RTW: cfg80211_rtw_add_virtual_intf(phy2) name:wlp0s20f0u1mon, type:6

This works perfectly on Fedora

Hi, thank you for sharing this awesome work.
My problem is that I checked the driver was Installed well, but my wifi is not turning on.
Could you help me what I can do for next?

Here is my environment information.

• Ubuntu 20.04
• Kernel 5.13.0-51-generic
• Device: USB wifi adaptor (EFM ipTIME A5000UA)
• The wifi adaptor uses USB 3.0.

This is more a question than an issue. Sorry if there is a better place to put this.

I'm going to use this on an Rpi 3b+ as an access point, but only 2.4ghz.

What are the best settings for modprobe and hostapd.conf so to be most stable in that environment? It's just talking with IOT devices in the local network, no internet. I am having problems now with locking up, but it may have been the version of raspian. I just installed a lite version and am reinstalling everything. Thx!

Hi
so I've done some more digging into the code base and I have merged some commits into my DEV Branch. The code is ugly.

I first cherrypicked some features I saw on the aircrack-ng version of this driver as I thought more features is better. But while I was going through the debug logs, I noticed that the driver presents the physical device differently to the system depending if it is plugged in into an usb2 port or an usb3 port (This requires properly telling the driver to make use of USB3 with the module param).

This could only be very specific to my device. But I noticed that when in USB3 mode the driver configures the device as a 3T3R with 3 streams. When plugged into a USB2 mode it configures the device as a 2T4R device. This can be confirmed by loocking at the the system journal when the driver is loading, or by doing a cat hal_info under /proc/net/rtl8814au/{devicename}/.
I removed the decision block where it checks for USB2/USB3 in the code and now the driver configures the device as a 3T3R regardless of USB2 or 3.

This then subsequently also activated 3 spatial streams in HT and VHT mode, which can be confirmed with iw phyX info This now allows to specify ht_capab=[..][RX-STBC3][..] and vht_capab=[..][RX-STBC-3][..]. I have uploaded some hostapd configs in my branch as well.

I build the driver on raspbian 32bit os and configured it for AC mode with 80Mhz bandwidth. hostpad would come up, but the moment I would use an AC device that can use 80Mhz, the driver driver would be killed by the system and reloaded. the journal would say that there is an over-current on the USB port. But it would not make the entire system hang. My setup is a rpi 3b+ using the built in wifi in station mode to connect to my main wifi on 5Ghz.

I remembered from an earlier project, that the raspbian os has some stability issues when used in 5ghz mode and I had found that arch arm 64 bit is much better. So I setup arch arm 64bit for this as well and installed the driver (no problems at all). Once the same hostapd conf for AC was set up, I ran the test. And this time it would not crash the kernel module and hostapd stayed up.

I even went as far as setting up a second usb wifi device with an older ralink chip(driver rt2800usb) on the same rpi3b+. Now it is hosting 2 wifis: one for 2.4G (ralink) and one for 5G(8814a). Its been up for 24hours so far and clients can connect and disconnect no problem. But like someone else said about this driver, the crashes happen randomly, so I am only testing and sharing it here with no PR.

I might snap some iperf3 stats for the different configurations.

cheers

PS: don't activate Beamforming for AP mode in hostapd nor module config. It really cripples the throughput from what I have found.

Well, it seems that surely something indeed goes wrong here... Here's the output of the kernel installation (I was sitting on 5.10 LTS, installed the driver and it was working fine so I tried to install 5.12 as additional kernel):

The following packages will be installed:
linux512
linux512-headers
linux512-nvidia
Starting
resolving dependencies...
looking for conflicting packages...
Packages (3) linux512-5.12.19-1  linux512-headers-5.12.19-1  linux512-nvidia-470.63.01-1
Total Download Size:   157.06 MiB
Total Installed Size:  264.69 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
linux512-5.12.19-1-x86_64 downloading...
 linux512-headers-5.12.19-1-x86_64 downloading...
 linux512-nvidia-470.63.01-1-x86_64 downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing linux512...
NOTE, 5.12.19 was the last maintenance release by Greg Kroah-Hartman.
This kernel series is now marked EOL (end of life).
It is recommend to move on to linux510 for LTS series or to
linux513 for the current stable.
Use followed cmd to do that: sudo mhwd-kernel -i linux510
or for current stable:       sudo mhwd-kernel -i linux513
Optional dependencies for linux512
rda: to set the correct wireless channels of your country [installed]
installing linux512-headers...
installing linux512-nvidia...
In order to use nvidia module, reboot the system.
:: Running post-transaction hooks...
(1/7) Arming ConditionNeedsUpdate...
(2/7) Updating module dependencies...
(3/7) Install DKMS modules
==> dkms install --no-depmod -m rtl8814au -v 5.8.5.1 -k 5.12.19-1-MANJARO
Error! Bad return status for module build on kernel: 5.12.19-1-MANJARO (x86_64)
Consult /var/lib/dkms/rtl8814au/5.8.5.1/build/make.log for more information.
==> Warning, dkms install --no-depmod -m rtl8814au -v 5.8.5.1 -k 5.12.19-1-MANJARO returned 10
==> depmod 5.12.19-1-MANJARO
(4/7) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux512.preset: default
-> -k /boot/vmlinuz-5.12-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.12-x86_64.img
==> Starting build: 5.12.19-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.12-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux512.preset: fallback
-> -k /boot/vmlinuz-5.12-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.12-x86_64-fallback.img -S autodetect
==> Starting build: 5.12.19-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.12-x86_64-fallback.img
==> Image generation successful
(5/7) Updating Kernel initcpios for Nvidia-DRM...
(6/7) Refreshing PackageKit...
(7/7) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.12-x86_64.img
Found initrd fallback image: /boot/initramfs-5.12-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Root partition isn't a btrfs filesystem.
This script only supports snapshots of the btrfs filesystem.
If you think an error has occurred , please file a bug report at  https://github.com/Antynea/grub-btrfs 
Nothing to do. Abort.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

And that's the build.log file:
DKMS make.log for rtl8814au-5.8.5.1 for kernel 5.12.19-1-MANJARO (x86_64) Mon Aug 30 21:43:02 CEST 2021 make: uname: No such file or directory make: pwd: No such file or directory make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.12.19-1-MANJARO/build M= modules make: pwd: No such file or directory make: make: No such file or directory make: *** [Makefile:2383: modules] Error 127

Hi,

Just curious if anyone has tried this driver with the 5.10.7 kernel release? Am successfully using it with 5.10.6 but if I switch to the 10.7 kernel it no longer shows the device is present even though a USB query shows the device is present...

I'd suggest mentioning that you'd need to install the correct version of the kernel headers, because (at least on manjaro) typing in pacman -S linux-headers gives you a bunch of options for versions to install.

As a complete newbie to linux, I had no idea what the choice even meant, and I picked the default, which was wrong, though I figured this out eventually after a bunch of research

Hi Im able to compile and load the 8814au module. But I have a problem creating 80211ac 5ghz AP on RPi4. Ive tried playing around with the channels and seg0 and seg1 settings but continue to get the "Could not set channel for kernel driver". It appears to be in the "static int hostapd_setup_interface_complete_sync" function of hostapd. The conditional section is below:

hostapd source
if (!delay_apply_cfg &&
hostapd_set_freq(hapd, hapd->iconf->hw_mode, iface->freq,
hapd->iconf->channel,
hapd->iconf->enable_edmg,
hapd->iconf->edmg_channel,
hapd->iconf->ieee80211n,
hapd->iconf->ieee80211ac,
hapd->iconf->ieee80211ax,
hapd->iconf->secondary_channel,
hostapd_get_oper_chwidth(hapd->iconf),
hostapd_get_oper_centr_freq_seg0_idx(
hapd->iconf),
hostapd_get_oper_centr_freq_seg1_idx(
hapd->iconf))) {
wpa_printf(MSG_ERROR, "Could not set channel for "
"kernel driver");
goto fail;

Hostapd output
random: getrandom() support available
Configuration file: /etc/hostapd/hostapd.conf
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-0f-ac:6
nl80211: Supported vendor command: vendor_id=0x1a11 subcmd=4106
nl80211: Supported vendor command: vendor_id=0x1a11 subcmd=4107
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 3 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0xdd7318 (device SME)
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=04
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=0501
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=0503
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=0504
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=08
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=0a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=12
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xdd7318 match=7f
nl80211: Enable Probe Request reporting nl_preq=0xdd7d80
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ) nl_handle=0xdd7d80 match=
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: Add own interface ifindex 3 (ifidx_reason -1)
nl80211: if_indices[16]: 3(-1)
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code US, new country code US
nl80211: Regulatory information - country=US (DFS-FCC)
nl80211: 2402-2472 @ 40 MHz 30 mBm
nl80211: 5170-5250 @ 80 MHz 23 mBm
nl80211: 5250-5330 @ 80 MHz 23 mBm (DFS)
nl80211: 5490-5730 @ 160 MHz 23 mBm (DFS)
nl80211: 5735-5835 @ 80 MHz 30 mBm
nl80211: 57240-63720 @ 2160 MHz 40 mBm
nl80211: Added 802.11b mode based on 802.11g information
nl80211: Mode IEEE 802.11g: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[NO_IR] 2472[NO_IR] 2484[DISABLED]
nl80211: Mode IEEE 802.11a: 5180 5200 5220 5240 5260[NO_IR][RADAR] 5280[NO_IR][RADAR] 5300[NO_IR][RADAR] 5320[NO_IR][RADAR] 5500[NO_IR][RADAR] 5520[NO_IR][RADAR] 5540[NO_IR][RADAR] 5560[NO_IR][RADAR] 5580[NO_IR][RADAR]
nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467[NO_IR] 2472[NO_IR] 2484[DISABLED]
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=30 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=30 dBm
Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=23 dBm
Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=23 dBm
Allowed channel: mode=2 chan=44 freq=5220 MHz max_tx_power=23 dBm
Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=23 dBm
Allowed channel: mode=2 chan=149 freq=5745 MHz max_tx_power=30 dBm
Allowed channel: mode=2 chan=153 freq=5765 MHz max_tx_power=30 dBm
Allowed channel: mode=2 chan=157 freq=5785 MHz max_tx_power=30 dBm
Allowed channel: mode=2 chan=161 freq=5805 MHz max_tx_power=30 dBm
Allowed channel: mode=2 chan=165 freq=5825 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=30 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=30 dBm
DFS support is enabled
Completing interface initialization
Mode: IEEE 802.11a Channel: 36 Frequency: 5180 MHz
DFS 0 channels required radar detection
Could not set channel for kernel driver
Interface initialization failed
wlan0: interface state COUNTRY_UPDATE->DISABLED
wlan0: AP-DISABLED
wlan0: Unable to setup interface.
hostapd_interface_deinit_free(0xdd5020)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0xdd5020)
wlan0: interface state DISABLED->DISABLED
hostapd_bss_deinit: deinit bss wlan0
wlan0: Deauthenticate all stations
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> -22 (Invalid argument)
wlan0: AP-DISABLED
hostapd_cleanup(hapd=0xdd5da0 (wlan0))
wlan0: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wlan0 wasn't started
hostapd_interface_deinit_free: driver=0x13220c drv_priv=0xdd7220 -> hapd_deinit
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
nl80211: Disable Probe Request reporting nl_preq=0x8855f509
nl80211: Remove monitor interface: refcount=0
nl80211: Remove beacon (ifindex=3)
netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 3 iftype 2 (STATION)
nl80211: Teardown AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Unsubscribe mgmt frames handle 0x8855fb91 (AP teardown (dev SME))
hostapd_interface_free(0xdd5020)
hostapd_interface_free: free hapd 0xdd5da0
hostapd_cleanup_iface(0xdd5020)
hostapd_cleanup_iface_partial(0xdd5020)
hostapd_cleanup_iface: free iface=0xdd5020

hostapd.conf
interface=wlan0
driver=nl80211
ssid=borg

macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=toe54321
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP

hw_mode=a
channel=36
#wmm_enabled=1

country_code=US

ieee80211n=0
#require_ht=1

ieee80211h=1
ieee80211d=1
ieee80211ac=1
require_vht=1
vht_capab=[MAX-MPDU-11454][RXLDPC][SHORT-GI-80][TX-STBC]
#[SU-BEAMFORMEE][MU-BEAMFORMEE][HTC-VHT]
#This belo w is supposed to get us 867Mbps and works on rtl8814au doesn't work on this driver yet
vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=42
vht_oper_centr_freq_seg1_idx=157

make.log
Attempt to install on CENTOS LINUX 8.3 with kernel 4.18

uname -r

4.18.0-240.22.1.el8_3.x86_64

[root@localhost 8814au]# pwd
/root/GIT/rtl8814au-morrownr/8814au
[root@localhost 8814au]# ls
8814au.conf edit-options.sh install-driver.sh Makefile raspi32.sh remove-driver.sh
core hal Kconfig os_dep raspi64.sh save-log.sh
dkms.conf include LICENSE platform README.md
[root@localhost 8814au]# ./install-driver.sh

install-driver.sh version 20210416
Start installation.
Copying source files to: /usr/src/rtl8814au-5.8.5.1
Copying 8814au.conf to: /etc/modprobe.d

Creating symlink /var/lib/dkms/rtl8814au/5.8.5.1/source ->
/usr/src/rtl8814au-5.8.5.1

DKMS: add completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area...
'make' -j8 KVER=4.18.0-240.22.1.el8_3.x86_64 KSRC=/lib/modules/4.18.0-240.22.1.el8_3.x86_64/build.....(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.18.0-240.22.1.el8_3.x86_64 (x86_64)
Consult /var/lib/dkms/rtl8814au/5.8.5.1/build/make.log for more information.
An error occurred. dkms build error = 10
Please report this error.

I have a computer without a built in wlan adapter and have no access to LAN and can therefore not install any package.

To get a internet connection, it should be possible to compile the driver on an other linux machine and then install the driver manually offline. Compiling the driver works fine with make (ko and mod files are generated).

However, how do I now install the driver manually on the other machine? I tried to "replicate" the install-driver.sh script but this uses dkms and probably other packages under the hood which are not installed on my target machine.

My approach would be to load this kernel module temporarily and install all necessary packages and then install this driver the intended way:

• build driver
• copy *.ko file to other machine
• add signature due to secure boot
• load the driver with insmod
• install the required packages
• unload the driver
• install the driver the intended way (install-driver.sh)

What's your opinion on this approach? Will this work or have I missed anything?

Hi,
I have installed the driver for my USB Wifi adapter but when I perform the check:
aireplay-ng --test -i wlan0 wlan1
I got the following results:

19:32:26  Trying card-to-card injection...
19:32:26  Attack -0:           OK
19:32:26  Attack -1 (open):    OK
19:32:26  Attack -1 (psk):     OK
19:32:26  Attack -2/-3/-4/-6:  OK
19:32:26  Got a reply with an incorrect sequence number (wanted 0x0a00 got 0x9a9b).
19:32:26  Got a reply with an incorrect sequence number (wanted 0x0a00 got 0x9a9b).
19:32:26  Got a reply with an incorrect sequence number (wanted 0x0a00 got 0x9a9b).
19:32:26  Got a reply with an incorrect sequence number (wanted 0x0a00 got 0x9a9b).
19:32:29  Got a reply with an incorrect sequence number (wanted 0x0a00 got 0x5a9c).
19:32:34  Got a reply with an incorrect sequence number (wanted 0x0a00 got 0x8a9f).
19:32:35  Got a reply with an incorrect sequence number (wanted 0x0a00 got 0xaa9f).
19:32:38  Attack -5/-7:        Failed

What do I miss?

Thx

Kernel: 5.11.12-200.fc33.x86_64
My toy is an i7 based Dell Inspiron.
Device: USB 3.0 WiFi Adapter AC1900 Mbps by the horribly named Edup Love but it is extremely well built.

#sudo dnf -y update
#sudo dnf -y install git dkms kernel-devel kernel-debug-devel
#git clone https://github.com/morrownr/8814au.git
#cd 8814au
#./install-driver.sh

The only problem I have experienced is one kernel barfed on dkms. Using the provided scripts I removed and installed and everything worked perfectly. Lightning fast on my network. I can stream 2160/Atmos without a hiccup.

I have the Alfa AWUS1900 wifi card. I previously used those wifi drivers from Kali repos, then switched to Aircrack-NG driver but no injection from that driver. I uninstalled all those, then installed Morrownr/8814au driver. Injection works, but I noticed these repeat messages in 'dmesg' output:

183.429238] start_addr=(0x30000), end_addr=(0x40000), buffer_size=(0x10000), smp_number_max=(8192)
[ 226.441230] start_addr=(0x30000), end_addr=(0x40000), buffer_size=(0x10000), smp_number_max=(8192)

Maybe someone already knows what these are but it does pertain to the driver, because when I remove the driver per the installation scripts, these messages disappear. But with the driver installed, these messages fill up the dmesg output, and I want to get rid of them.
Also, when the wifi card is in monitor mode, per airmon-ng, these messages don't show up. These messages show up when the awus1900 is in 'managed mode'.
I'm running two cards, one with Alfa driver, other card with 'iwlwifi' driver. Could this be the issue of both cards in 'managed mode'?
Willing to post more info if needed.

Deauthentication does not work with AWUS1900 and kali Linux Updated to latest version
The adapter sets correctly the channel but ACKs are 0 / 0.

For your information, in bettercap the rfmon Error does not start the web UI. The workaround is downgrade libpcap to 1.9.1-4 version

Hello! This is the only way i found to contact with you, developers, so, is there description of these many options in /sys/module/8814au/parameters/ somewhere?

Hi everyone, I'm working on a project that needs to read the channel estimation matrix out from the NDP procedure.
To do so, I used an EDUP-1622 wireless card (with up to 3 spatial stream supported) and planed to do some minor modifications on rtl8814au driver for my project.

In the first step, I setuped 2 devices in AP/STA scheme, and confirmed the connection is using 802.11AC standard.

$ sudo lshw -C network
... ...
  *-network:2
       description: Wireless interface
       physical id: 3
       bus info: usb@2:1
       logical name: wlan1
       serial: e8:4e:06:95:28:cd
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rtl8814au driverversion=5.10.63-v7l+ ip=169.254.138.77 multicast=yes wireless=IEEE 802.11AC

To better describe the protocol-related parameters of my setup, I pasted my hostapd.conf as below:

interface=wlan1
driver=nl80211
ssid=Beamformer
macaddr_acl=0
auth_algs=1
ignore_broadcast_sisd=0
beacon_int=100
dtim_period=1
wpa=2
wpa_passphrase=xxxxxxxx
wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256
wpa_pairwise=CCMP
rsn_pairwise=CCMP

hw_mode=a
ieee80211n=1
ieee80211ac=1
channel=36
wmm_enabled=1
wme_enabled=1
country_code=US

ht_capab=[LDPC][HT40-][HT40+][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935]
vht_capab=[RXLDPC][MAX-MPDU-11454][SHORT-GI-80][SU-BEAMFORMER][SU-BEAMFORMEE][BF-ANTENNA-2][SOUNDING-DIMENSION-2][HTC-VHT]

vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=42

Next, I checked dmesg -wH report which shows that each time the TX initiates an NDP procedure the driver will put a line in the kernel log.

$ sudo dmesg -wH
... ...
[  +4.080076] RTW: [C2H], C2H_TXBF!!
[  +4.080137] RTW: [C2H], C2H_TXBF!!
[  +4.080012] RTW: [C2H], C2H_TXBF!!
[  +4.080075] RTW: [C2H], C2H_TXBF!!
[  +4.080042] RTW: [C2H], C2H_TXBF!!
[  +4.079979] RTW: [C2H], C2H_TXBF!!
[  +4.080090] RTW: [C2H], C2H_TXBF!!
[  +4.080073] RTW: [C2H], C2H_TXBF!!
[Oct23 21:14] RTW: [C2H], C2H_TXBF!!
[  +4.080024] RTW: [C2H], C2H_TXBF!!
[  +4.079886] RTW: [C2H], C2H_TXBF!!
[  +4.080050] RTW: [C2H], C2H_TXBF!!
[  +4.080142] RTW: [C2H], C2H_TXBF!!
[  +4.079968] RTW: [C2H], C2H_TXBF!!
[  +4.080043] RTW: [C2H], C2H_TXBF!!
[  +4.080037] RTW: [C2H], C2H_TXBF!!
[  +4.080112] RTW: [C2H], C2H_TXBF!!
[  +4.080107] RTW: [C2H], C2H_TXBF!

However, when I look into the source code to investigate where the channel estimation matrix is stored and how it is being modified by the NDP procedure, I found the implementation seems dummy. The related source code is pasted below

source code here:

#elif (DM_ODM_SUPPORT_TYPE == ODM_CE)

u32 beamforming_get_report_frame(
	void *dm_void,
	union recv_frame *precv_frame)
{
	struct dm_struct *dm = (struct dm_struct *)dm_void;
	u32 ret = _SUCCESS;
	struct _RT_BEAMFORMEE_ENTRY *beamform_entry = NULL;
	u8 *pframe = precv_frame->u.hdr.rx_data;
	u32 frame_len = precv_frame->u.hdr.len;
	u8 *TA;
	u8 idx, offset;

	/*@Memory comparison to see if CSI report is the same with previous one*/
	TA = get_addr2_ptr(pframe);
	beamform_entry = phydm_beamforming_get_bfee_entry_by_addr(dm, TA, &idx);
	if (beamform_entry->beamform_entry_cap & BEAMFORMER_CAP_VHT_SU)
		offset = 31; /*@24+(1+1+3)+2  MAC header+(Category+ActionCode+MIMOControlField)+SNR(nc=2)*/
	else if (beamform_entry->beamform_entry_cap & BEAMFORMER_CAP_HT_EXPLICIT)
		offset = 34; /*@24+(1+1+6)+2  MAC header+(Category+ActionCode+MIMOControlField)+SNR(nc=2)*/
	else
		return ret;

	return ret;
}

To my understanding of the 802.11ac vht standard and this driver, when each time beamformer initials a NDP procedure and the beamformee responds with a compressed channel matrix, the beamformer shall enter this beamforming_get-report_frame() function to collect the compressed channel matrix and store it in the beamforming_entry->csi_matrix. But in the implementation, I did not see the csi_matrix being modified.

Also, I print the values of the csi_matrix in the kernel long after the connection is established, but it seems to me the csi_matrix stays unchanged (the value of all the elements in csi_matrix[] are zeros and will never changed).

Is that mean this driver has not implemented beamforming functionality yet?

This is well and good for most systems, but means this is unsuitable for Alpine (which does not have dkms available)

It would be excellent if some basic instruction were provided for doing a "manual" build. Currently we have to weed through install-driver.sh, raspi[32|64].sh if applicable, dkms.conf, and the Makefile to figure it out.

After installing the driver on RaspberryPiOs (Buster latest release) the network manager (GUI) no longer works.
It shows: "Set wifi country".
I tried to set with:
-sudo raspi-config: Error: Could not communicate with wpa_supplicant.

-sudo ip link set wlan0 down,
sudo ip link set wlan1 down,
sudo iw reg set DE (or any other),
sudo ip link set wlan0 up,
sudo ip link set wlan1 up:
No Error and -iw reg get shows:
globalcountry DE: DFS-ETSI
(2400 - 2483 @ 40), (N / A, 20), (N / A)
(5150 - 5250 @ 80), (N / A, 20), (N / A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N / A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N / A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N / A, 13), (N / A)
(57000 - 66000 @ 2160), (N / A, 40), (N / A)
but GUINetworkmanager not working

-setting the wifi country over GUI-Settings: Same

• killing processes:
  PID Name
  381 wpa_supplicant
  408 dhcpcd
  476 wpa_supplicant
  3684 avahi-daemon
  3686 avahi-daemon
  and restarting these : Nope

-setting wifi connection with /etc/wpa_supplicant/wpa_supplicant.conf works fine.

I´m done, I've tried everything I know.... Maybe you can help me further

Thanks a lot

Hey! I wonder, if I want to update the driver with the newest version from git, should I simply pull changes and launch the install script again with driver already installed, or remove the driver and install it again? If the second is the case, maybe repo could have some sort of update script, so the downloaded directory doesn't get deleted and nobody has to be pulling it again from scratch?

The driver was installed successfully.
Do you want to edit the driver options file now? [y/N] o
Do you want to reboot now? [y/N] n

seems that o equals n :)

I've had no problem with the driver on Ubuntu 20.04 and Debian 11, as long as I use only the first interface.

But every time when I try to create a second interface, with type "station", I had the same error :

iw dev phy0 interface add xxxx type station
command failed: No such device (-19)

But this command is successfull :

iw dev phy0 interface add xxxx type monitor

Any ideas ?

Hi,

It is possible that the PC where I have this device (2 in fact, TP-Link Archer T9UH) is causing hardware Freeze?, Motherboard is new (Gigabyte A320M-S2H V2), Ram in new, CPU from another working computer (AMD A10-9700), Video card from another working computer (AMD RX460). The only things I didn't changed to test are these 2 WIFI adapters, that I use one for each band as AP (with hostapd).
I am having random hardware freeze, with no related error on logs.

Latest source from this driver, Ubuntu 20.04 and tested right now with mainline kernel 5.11.16 (same happen with 5.8).

Both adapters are connected to a self powered USB 3.0 (another thing I've added just in case).

Hi
I am using this driver with TPlink T9UH(EU) v2 and noticed that in monitor mode with WireShark I cannot capture ACKs packets i.e when using display filter wlan.fc.type_subtype == 0x001d nothing is captured .
I did try capture packets with inSSIDer software for win10 and same adapter and Acknolegment packets are captured .
Please can you advise ?

At this point I have managed to thoroughly confuse myself. Stuff I learned since RH7.x has gone down the crapper.

Running install-driver.sh version 20210917
Starting installation...
Copying source files to: /usr/src/rtl8814au-5.8.5.1
Copying 8814au.conf to: /etc/modprobe.d
Error! DKMS tree already contains: rtl8814au-5.8.5.1
You cannot add the same module/version combo more than once.
An error occurred. dkms add error = 3
Please report this error.

After I have built the driver with make, I get following error:

sudo depmod 8814au.ko
depmod: ERROR: Bad version passed 8814au.ko

I am on Fedora 34. When I use the dkms install method, the module does not load too, yielding the same error.
Is there any way to fix this?

uname -r
5.16.18-100.fc34.x86_64

modinfo 8814au
[...]
vermagic:       5.16.18-100.fc34.x86_64 SMP preempt mod_unload 

All headers are installed.

When I try to install from source

Running install-driver.sh version 20210725
Starting installation.
Copying source files to: /usr/src/rtl8814au-5.8.5.1
Copying 8814au.conf to: /etc/modprobe.d

Creating symlink /var/lib/dkms/rtl8814au/5.8.5.1/source ->
                 /usr/src/rtl8814au-5.8.5.1

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'make' -j24 KVER=5.9.11-zen2-1-zen KSRC=/lib/modules/5.9.11-zen2-1-zen/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.9.11-zen2-1-zen (x86_64)
Consult /var/lib/dkms/rtl8814au/5.8.5.1/build/make.log for more information.
An error occurred. dkms build error = 10
Please report this error.

/var/lib/dkms/rtl8814au/5.8.5.1/build/make.log:

DKMS make.log for rtl8814au-5.8.5.1 for kernel 5.9.11-zen2-1-zen (x86_64)
Sat 14 Aug 22:39:15 CEST 2021
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.9.11-zen2-1-zen/build M=/var/lib/dkms/rtl8814au/5.8.5.1/build  modules
make[1]: Entering directory '/usr/lib/modules/5.9.11-zen2-1-zen/build'
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_cmd.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_security.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_debug.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_io.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ioctl_query.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ioctl_set.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_mlme_ext.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ieee80211.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_mlme.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_vht.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_mi.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_wlan_util.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rf.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_pwrctrl.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_sta_mgt.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_chplan.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ap.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/mesh/rtw_mesh_pathtbl.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_recv.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/mesh/rtw_mesh_hwmp.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_xmit.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/mesh/rtw_mesh.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_p2p.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rson.o
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rf.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ioctl_set.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_chplan.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rson.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_wlan_util.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_cmd.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_xmit.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/mesh/rtw_mesh.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_p2p.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_mi.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_vht.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_sta_mgt.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_debug.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ieee80211.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_security.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_io.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_recv.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ap.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_pwrctrl.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ioctl_query.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_mlme.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/mesh/rtw_mesh_pathtbl.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/mesh/rtw_mesh_hwmp.o] Error 1
make[2]: *** [scripts/Makefile.build:283: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_mlme_ext.o] Error 1
make[1]: *** [Makefile:1781: /var/lib/dkms/rtl8814au/5.8.5.1/build] Error 2
make[1]: Leaving directory '/usr/lib/modules/5.9.11-zen2-1-zen/build'
make: *** [Makefile:2383: modules] Error 2

Hi !

Trying to install this on last fedora 35 on linux kernel 5.15.14, with a ID know by device. Everything should be fine, except it doesn't.

So, install don't show error, but module not loaded automatically at boot. Trying to make it, and journalctl | grep 8814au show this :

janv. 18 11:55:59 fedora kernel: 8814au: loading out-of-tree module taints kernel.
janv. 18 11:55:59 fedora kernel: 8814au: module verification failed: signature and/or required key missing - tainting kernel
janv. 18 11:55:59 fedora kernel: 8814au: unknown parameter 'rtw_dfs_region_domain' ignored
janv. 18 11:55:59 fedora kernel: usbcore: registered new interface driver rtl8814au
janv. 18 11:55:52 fedora systemd-modules-load[536]: Inserted module '8814au'

So i wonder why rtw_dfs_region_domain doesn't work anymore (got no mention on this anywhere) and also want to testify that this driver don't work for me on fedora 35 (no secure boot, no CSM).

Think maybe it's related to this line ?

OpenWrt 21.02.2, r16495-bf0c965af0

Just curious if you have had any experience or suggestions on compiling for use with this version of OpenWrt. I haven't tried to do anything with OpenWrt as far a compiling. I d/led for rPi 4 and installed but trying to research compiling seems to be a TMI drama. I can't even seem to find any clarity as to whether I can just to a build package or have to do a complete build system build. I appreciate any tldr style suggestions! I found something of a patch for using 8812au (1Jeff1 I think) but not sure where to go with that for 8814. I have a virtualbox ubuntu 20.04 setup ready to go.

Hi,

I'm trying to create mesh interface via using Alfa Awus1900 Wi-Fi adapter, but I got error shown as below;

My os and driver versions ;
Os: Kali Linux 2020.4 , Kernel 5.10.0-kali5-amd4, Alfa AWUS1900 Driver: v5.8.5.1

After rapid search, I also tried to manipulate kernel mesh configuration as described on this link; https://www.kali.org/docs/nethunter/nethunter-kernel-3-config-2/

but so far, nothing changed. Do you have anything you can suggest ?

Best,

Hi,

I have problem with compilation driver, running Rasbperry pi 4, version B on OSMC distribution. OSMC is based on Debian.

I have problem with compilation drivers. Maybe you can help.

Here are some inofrmation about hardware:

root@osmc:/usr/src/8814au# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter

root@osmc:~# uname -a
Linux osmc 5.10.78-5-osmc #1 SMP PREEMPT Mon Feb 28 01:18:12 UTC 2022 aarch64 GNU/Linux

And when I try compile, I have this result:

root@osmc:/usr/src/8814au# ./ARM_RPI.sh
I386 support was turned off in Makefile as planned.
Raspberry Pi OS (32 bit) support was turned on in Makefile as planned.
root@osmc:/usr/src/8814au# make
make ARCH=arm CROSS_COMPILE= -C /lib/modules/5.10.78-5-osmc/build M=/usr/src/8814au modules
make[1]: Vstupuje se do adresáře „/usr/src/rbp464-headers-5.10.78-5-osmc“
CC [M] /usr/src/8814au/core/rtw_cmd.o
In file included from ./include/asm-generic/int-ll64.h:11,
from ./arch/arm/include/uapi/asm/types.h:5,
from ./include/uapi/linux/types.h:5,
from ./include/linux/types.h:6,
from /usr/src/8814au/include/basic_types.h:75,
from /usr/src/8814au/include/drv_types.h:26,
from /usr/src/8814au/core/rtw_cmd.c:17:
./include/uapi/asm-generic/int-ll64.h:12:10: fatal error: asm/bitsperlong.h: Adresář nebo soubor neexistuje
#include <asm/bitsperlong.h>
^~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [scripts/Makefile.build:280: /usr/src/8814au/core/rtw_cmd.o] Chyba 1
make[1]: *** [Makefile:1825: /usr/src/8814au] Chyba 2
make[1]: Opouští se adresář „/usr/src/rbp464-headers-5.10.78-5-osmc“
make: *** [Makefile:2383: modules] Chyba 2

I can't find, what is wrong.

root@osmc:/usr/src/rbp464-headers-5.10.78-5-osmc# find . -type f -name "bitsperlong.h"
./include/uapi/asm-generic/bitsperlong.h
./include/asm-generic/bitsperlong.h
./arch/arm64/include/uapi/asm/bitsperlong.h

root@osmc:/usr/src/rbp464-headers-5.10.78-5-osmc# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster

root@osmc:/usr/src/rbp464-headers-5.10.78-5-osmc# cat /etc/os-release
PRETTY_NAME="Open Source Media Center"
NAME="OSMC"
VERSION="March 2022"
VERSION_ID="2022.03-1"
ID=osmc
ID_LIKE=debian

ANSI_COLOR="1;31"
HOME_URL="https://www.osmc.tv"
SUPPORT_URL="https://www.osmc.tv"
BUG_REPORT_URL="https://www.osmc.tv"

cat /proc/device-tree/model
Raspberry Pi 4 Model B Rev 1.5

I tried ./ARM64_RPI.sh before compiling too, but the same result:

root@osmc:/usr/src/8814au# ./ARM64_RPI.sh
I386 support was turned off in Makefile as planned.
Raspberry Pi OS (64 bit) support was turned on in Makefile as planned.
root@osmc:/usr/src/8814au# make
make ARCH=arm CROSS_COMPILE= -C /lib/modules/5.10.78-5-osmc/build M=/usr/src/8814au modules
make[1]: Vstupuje se do adresáře „/usr/src/rbp464-headers-5.10.78-5-osmc“
CC [M] /usr/src/8814au/core/rtw_cmd.o
In file included from ./include/asm-generic/int-ll64.h:11,
from ./arch/arm/include/uapi/asm/types.h:5,
from ./include/uapi/linux/types.h:5,
from ./include/linux/types.h:6,
from /usr/src/8814au/include/basic_types.h:75,
from /usr/src/8814au/include/drv_types.h:26,
from /usr/src/8814au/core/rtw_cmd.c:17:
./include/uapi/asm-generic/int-ll64.h:12:10: fatal error: asm/bitsperlong.h: Adresář nebo soubor neexistuje
#include <asm/bitsperlong.h>
^~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [scripts/Makefile.build:280: /usr/src/8814au/core/rtw_cmd.o] Chyba 1
make[1]: *** [Makefile:1825: /usr/src/8814au] Chyba 2
make[1]: Opouští se adresář „/usr/src/rbp464-headers-5.10.78-5-osmc“
make: *** [Makefile:2383: modules] Chyba 2

Do you have any idea, what is wrong and what should I try? I was googling all day, but can't find any helpfull information. I think, there is some problem with paths and kernel headers.

I am using a TP-Link Archer T9UH with my desktop PC that has secure boot enabled.

It works flawlessly on my Ubuntu install following the installation instructions.

In Fedora 35 with kernel 5.15, it installs but doesn't sign it so the kernel doesn't load it.

Once secure boot was disabled, it works without an issue.

I tried signing the module, but got lost doing it so will run with secure boot disabled for the time being.

problem using USB 3 - 5.10.0-kali3-amd64 2021.1

I was on a previous old version of the driver on Arch Linux but after updating to kernel 5.15.2.arch1-1 today my WiFi was no longer working.

So I ran the remove driver script, rebooted, cloned the newest version of the GitHub (connected to the internet via my phone's usb tethering).

When I tried running the driver install script with sudo, it said that a DKMs tree for rtl88q4au-5.8.5.1 already exists...

I tried rebooting again, I tried running the remove script (which says success) and rebooting and then trying again, I've also tried running the remove script without rebooting and then trying to install but it won't let me. It seems the remove script is broken...

Hola! Remember me?:P

So, my brother has this devil device, but using as client (not AP). When I've installed the driver, seems the device can't start. Here is the log:

Aug 10 08:44:53 MaceWindu kernel: [27434.977590] RTW: cfg80211_rtw_scan(wlx7cc2c60e6976)
Aug 10 08:44:53 MaceWindu kernel: [27434.977594] RTW: _rtw_pwr_wakeup call ips_leave....
Aug 10 08:44:53 MaceWindu kernel: [27434.977595] RTW: ==>ips_leave cnts:439
Aug 10 08:44:53 MaceWindu kernel: [27434.977596] RTW: ===> rtw_ips_pwr_up..............
Aug 10 08:44:53 MaceWindu kernel: [27434.977600] RTW: ===> ips_netdrv_open.........
Aug 10 08:44:53 MaceWindu kernel: [27434.977695] RTW: power-on :REG_SYS_CLKR 0x09=0xb0. REG_CR 0x100=0xea.
Aug 10 08:44:53 MaceWindu kernel: [27434.977696] RTW: MAC has not been powered on yet.
Aug 10 08:44:53 MaceWindu kernel: [27434.985569] RTW: ===>_InitQueueReservedPage_8814AUsb()
Aug 10 08:44:53 MaceWindu kernel: [27434.986009] RTW: <===_InitQueueReservedPage_8814AUsb()
Aug 10 08:44:53 MaceWindu kernel: [27434.986170] RTW: FirmwareDownload8814A fw source from Header
Aug 10 08:44:53 MaceWindu kernel: [27434.986171] RTW: FirmwareDownload8814A fw:NIC, size: 68320
Aug 10 08:44:53 MaceWindu kernel: [27434.986172] RTW: FirmwareDownload8814A: fw_ver=33 fw_subver=6 sig=0x8814
Aug 10 08:44:53 MaceWindu kernel: [27434.986690] RTW: HalROMDownloadFWRSVDPage8814A(): There is an Adapter is sending beacon.
Aug 10 08:44:53 MaceWindu kernel: [27434.986811] RTW: dmem_pkt_size = 5792, iram_pkt_size = 62464,FWHeaderSize = 64, Len = 68320!!
Aug 10 08:44:53 MaceWindu kernel: [27434.986811] RTW: MaxRsvdPageBufSize 1488, Total len 68320
Aug 10 08:44:53 MaceWindu kernel: [27434.988457] RTW: Check sum OK
Aug 10 08:44:53 MaceWindu kernel: [27434.988497] RTW: dmem check sum tmp 33
Aug 10 08:44:53 MaceWindu kernel: [27435.006392] RTW: Check sum OK
Aug 10 08:44:53 MaceWindu kernel: [27435.006432] RTW: imem check sum tmp 105
Aug 10 08:44:53 MaceWindu kernel: [27435.056585] RTW: FWDL success. write_fw:0, 68ms
Aug 10 08:44:53 MaceWindu kernel: [27435.056613] RTW: rtl8814au_hal_init: Download Firmware Success!!
Aug 10 08:44:53 MaceWindu kernel: [27435.374970] RTW: ==>PHY_SwitchWirelessBand8814() 2.4G
Aug 10 08:44:53 MaceWindu kernel: [27435.376292] RTW: <==PHY_SwitchWirelessBand8814():Switch Band OK.
Aug 10 08:44:53 MaceWindu kernel: [27435.388878] RTW: txpath=0x3, rxpath=0xf
Aug 10 08:44:53 MaceWindu kernel: [27435.388880] RTW: txpath_1ss:0x1, num:1
Aug 10 08:44:53 MaceWindu kernel: [27435.388881] RTW: txpath_2ss:0x3, num:2
Aug 10 08:44:53 MaceWindu kernel: [27435.392814] RTW: rtl8814au_hal_init in 412ms
Aug 10 08:44:53 MaceWindu kernel: [27435.392819] RTW: rtw_hal_set_macaddr_port wlx7cc2c60e6976- hw port(0) mac_addr =7c:c2:c6:0e:69:76
Aug 10 08:44:53 MaceWindu kernel: [27435.393295] RTW: rtw_hal_get_macaddr_port wlx7cc2c60e6976- hw port(0) mac_addr =7c:c2:c6:0e:69:76
Aug 10 08:44:53 MaceWindu kernel: [27435.393297] RTW: wlx7cc2c60e6976- hw port(0) mac_addr =7c:c2:c6:0e:69:76
Aug 10 08:44:53 MaceWindu kernel: [27435.393415] RTW: [HW_VAR_ENABLE_RX_BAR] 0x6A2=0x520
Aug 10 08:44:53 MaceWindu kernel: [27435.404919] RTW: rtw_hal_set_macaddr_port wlx7cc2c60e6976- hw port(0) mac_addr =7c:c2:c6:0e:69:76
Aug 10 08:44:53 MaceWindu kernel: [27435.405277] RTW: hw_var_set_opmode()-3339 mode = 2
Aug 10 08:44:53 MaceWindu kernel: [27435.405524] RTW: Registry kfree default force disable.
Aug 10 08:44:53 MaceWindu kernel: [27435.405548] RTW: <=== rtw_ips_pwr_up.............. in 428ms
Aug 10 08:44:53 MaceWindu kernel: [27435.405549] RTW: nolinked power save leave
Aug 10 08:44:53 MaceWindu kernel: [27435.405577] RTW: ==> ips_leave.....LED(0x0c228282)...
Aug 10 08:44:53 MaceWindu kernel: [27435.406116] RTW: SetHwReg8814A:(HW_VAR_CHECK_TXBUF)TXBUF Empty(1) in 0 ms
Aug 10 08:44:53 MaceWindu kernel: [27435.406242] RTW: wlx7cc2c60e6976 sleep m0=0x00000002, ori reg_0x4d4=0x00000000
Aug 10 08:44:54 MaceWindu kernel: [27436.593589] RTW: ==>PHY_SwitchWirelessBand8814() 5G
Aug 10 08:44:54 MaceWindu kernel: [27436.595614] RTW: <==PHY_SwitchWirelessBand8814():Switch Band OK.
Aug 10 08:44:57 MaceWindu kernel: [27438.865736] RTW: ==>PHY_SwitchWirelessBand8814() 2.4G
Aug 10 08:44:57 MaceWindu kernel: [27438.867990] RTW: <==PHY_SwitchWirelessBand8814():Switch Band OK.
Aug 10 08:44:57 MaceWindu kernel: [27438.888828] RTW: wlx7cc2c60e6976 wakeup m0=0x00000002, ori reg_0x4d4=0x00000002
Aug 10 08:44:57 MaceWindu kernel: [27438.888953] RTW: survey done event(44) band:0 for wlx7cc2c60e6976
Aug 10 08:44:57 MaceWindu kernel: [27438.889019] RTW: rtw_indicate_scan_done(wlx7cc2c60e6976)
Aug 10 08:44:57 MaceWindu kernel: [27438.899365] RTW: ==>rtw_ps_processor .fw_state(8)
Aug 10 08:44:57 MaceWindu kernel: [27438.899367] RTW: ==>ips_enter cnts:440
Aug 10 08:44:57 MaceWindu kernel: [27438.899367] RTW: nolinked power save enter
Aug 10 08:44:57 MaceWindu kernel: [27438.899368] RTW: ===> rtw_ips_pwr_down...................
Aug 10 08:44:57 MaceWindu kernel: [27438.899369] RTW: ====> rtw_ips_dev_unload...
Aug 10 08:44:57 MaceWindu kernel: [27438.909875] RTW: usb_read_port_cancel
Aug 10 08:44:57 MaceWindu kernel: [27438.909951] RTW: usb_read_port_complete() RX Warning! bDriverStopped(False) OR bSurpriseRemoved(False)
Aug 10 08:44:57 MaceWindu kernel: [27438.910067] RTW: usb_read_port_complete() RX Warning! bDriverStopped(False) OR bSurpriseRemoved(False)
Aug 10 08:44:57 MaceWindu kernel: [27438.910107] RTW: usb_read_port_complete() RX Warning! bDriverStopped(False) OR bSurpriseRemoved(False)
Aug 10 08:44:57 MaceWindu kernel: [27438.910147] RTW: usb_read_port_complete() RX Warning! bDriverStopped(False) OR bSurpriseRemoved(False)
Aug 10 08:44:57 MaceWindu kernel: [27438.910188] RTW: usb_read_port_complete() RX Warning! bDriverStopped(False) OR bSurpriseRemoved(False)
Aug 10 08:44:57 MaceWindu kernel: [27438.910226] RTW: usb_read_port_complete() RX Warning! bDriverStopped(False) OR bSurpriseRemoved(False)
Aug 10 08:44:57 MaceWindu kernel: [27438.910267] RTW: usb_read_port_complete() RX Warning! bDriverStopped(False) OR bSurpriseRemoved(False)
Aug 10 08:44:57 MaceWindu kernel: [27438.910307] RTW: usb_read_port_complete() RX Warning! bDriverStopped(False) OR bSurpriseRemoved(False)
Aug 10 08:44:57 MaceWindu kernel: [27438.910311] RTW: usb_write_port_cancel
Aug 10 08:44:57 MaceWindu kernel: [27438.910321] RTW: ==> rtl8814au_hal_deinit
Aug 10 08:44:57 MaceWindu kernel: [27438.910548] RTW: CardDisableRTL8814AU
Aug 10 08:44:57 MaceWindu kernel: [27438.913290] RTW: <=== rtw_ips_pwr_down..................... in 12ms

Is a TP-Link T9UH with of course RTL8814AU. Installed from the latest repo.

Ubuntu 20.04 (in fact,KDE Neon 20.04 which is the same thing).
Kernel: 5.4.0-80-generic

Any ideas? Thanks!

Thanks for all your effort on this project.
It looks that set_wiphy_netns is not available, I verified with 8814au, and 8812bu but not worked.

$ iw list
	Supported commands:
	.......
		 * set_wiphy_netns
	.......

Is there any workaround to enable this?

The latest DKMS installation for 8814au installed without any errors on ORACLE LINUX 8.5 which is 99% identical to Fedora, Red Hat and CentOS. HOWEVER, it doesn't work for my TP-LINK AC1900 WIFI Adapter ( ARCHER T9-UH ). The Adapter does not wake up and work at all. What might I need to do? What "option" might I need to change?

I have compiled source code on Ubuntu 21.10 (5.13.0-1028-raspi)
It works fine, but I can't find any RTS/CTS packets in capture.

Does anyone know why these packets being filtered, and how it can be captured?

hi, im a newbie in this domain, but im trying my best. i dont know how, but i succeed to install the driver 3 month ago for the awus1900. it's working fine in usb 3 activated, but i wanted to install this update to have the ap working.
and to be honest im block to step 3, i got an error :

root@kali:~# sudo apt-get install -y linux-headers-$(uname -r) build-essential dkms git libelf-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package linux-headers-5.4.83-Re4son-v7l
E: Couldn't find any package by glob 'linux-headers-5.4.83-Re4son-v7l'
E: Couldn't find any package by regex 'linux-headers-5.4.83-Re4son-v7l'

somebody can help me please :)