rtl8192ee 0000:05:00.0: swiotlb buffer is full (sz: 4000 bytes), total 32768 (slots), used 32768 (slots)

Dmesg starts flooding with this ^

The driver works just fine for a day, but then it stops accepting new connections or responding to existing ones. Shutting the interface down by ifconfig or reloading the module 8192ee does not clean this buffer, the system has to be rebooted.

How do we get this buffer to clean itself automatically? It's pretty... annoying, but I'm not sure where to look first.

Hello Larry! Thank you for sharing your work with us.

I am facing the fatal errors below during make. May you help me with this?

make: "/rtl8192ee/Makefile" line 1864: warning: duplicate script for target "ifneq" ignored
make: "/rtl8192ee/Makefile" line 1840: warning: using previous script for "ifneq" defined here
make: "/rtl8192ee/Makefile" line 1864: warning: duplicate script for target "(,)" ignored
make: "/rtl8192ee/Makefile" line 1840: warning: using previous script for "(,)" defined here
make: "/rtl8192ee/Makefile" line 1865: warning: duplicate script for target "ifneq" ignored
make: "/rtl8192ee/Makefile" line 1840: warning: using previous script for "ifneq" defined here
make: "/rtl8192ee/Makefile" line 1865: warning: duplicate script for target "(,)" ignored
make: "/rtl8192ee/Makefile" line 1840: warning: using previous script for "(,)" defined here
make: "/rtl8192ee/Makefile" line 1866: Need an operator
make: "/rtl8192ee/Makefile" line 1891: Need an operator
make: Fatal errors encountered -- cannot continue
make: stopped in /rtl8192ee

WHAT IS MY KERNEL:

FreeBSD 12.2-RELEASE r366954 GENERIC amd64

WHAT I DID:

• I've downloaded the repository using GIT.
• I've executed GIT PULL.
• I executed make clean

WHAT I NEED TO DO

I am running a pfSense 2.5.0-RELEASE (amd64) FreeBSD 12.2-STABLE and It has a Realtek RTL8192EE PCI-e Wireless Adapter installed, but I couldn't load its driver on boot, even using RTWN, so I was trying your repository. I am using a Virtual Machine running FreeBSD 12.2-RELEASE to compile the drivers. Once compiled I copy the drivers files to pfSense.

I appreciate any help and suggestion.

Cheers
JLS

Remember the swiotlb buffer issue, this one #3 ?
Well, the iommu workaround keeps the system running and transmitting data wirelessly alright, for as long as it has enough memory.

However, the system must be rebooted often or it will suffer from performance loss due to the driver hogging memory. This has been especially impactful in my home server. Is there any way this could be solved?

So I tried to compile these drivers under ubuntu server 18.04, but it keeps exiting on this error:

make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.15.0-91-generic/build M=/home/minecraft/rtl8192ee  modules
make[1]: ingresso nella directory "/usr/src/linux-headers-4.15.0-91-generic"
  CC [M]  /home/minecraft/rtl8192ee/os_dep/linux/rtw_proc.o
/home/minecraft/rtl8192ee/os_dep/linux/rtw_proc.c: In function ‘rtw_odm_proc_init’:
/home/minecraft/rtl8192ee/os_dep/linux/rtw_proc.c:3275:67: error: ‘rtw_odm_proc_seq_ops’ undeclared (first use in this function); did you mean ‘rtw_odm_proc_seq_fops’?
    entry = rtw_proc_create_entry(odm_proc_hdls[i].name, dir_odm, &rtw_odm_proc_seq_ops, (void *)i);
                                                                   ^~~~~~~~~~~~~~~~~~~~
                                                                   rtw_odm_proc_seq_fops
/home/minecraft/rtl8192ee/os_dep/linux/rtw_proc.c:3275:67: note: each undeclared identifier is reported only once for each function it appears in
scripts/Makefile.build:330: recipe for target '/home/minecraft/rtl8192ee/os_dep/linux/rtw_proc.o' failed
make[2]: *** [/home/minecraft/rtl8192ee/os_dep/linux/rtw_proc.o] Error 1
Makefile:1577: recipe for target '_module_/home/minecraft/rtl8192ee' failed
make[1]: *** [_module_/home/minecraft/rtl8192ee] Error 2
make[1]: uscita dalla directory "/usr/src/linux-headers-4.15.0-91-generic"
Makefile:1816: recipe for target 'modules' failed
make: *** [modules] Error 2

I already looked if i hadn't installed the headers, but they are correctly installed, I did a new git pull/clone like 3 times but nothing has changed. Am I missing some other required package?

Or is it something wrong in the code, like the compiler is suggesting? Because I fixed it and now the compiling is all ok.

can you please check compiling for kernel-6.3.1 ?
i have a little issue
DKMS make.log for rtl8192ee_lwf-5.2.19-1pclos2022 for kernel 6.3.1-pclos1 (x86_64) Sun May 7 13:06:53 UTC 2023 #make -C /lib/modules/6.3.1-pclos1/build M=/var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build clean cd hal ; rm -fr */*/*/*.mod.c */*/*/*.mod */*/*/*.o */*/*/.*.cmd */*/*/*.ko* cd hal ; rm -fr */*/*.mod.c */*/*.mod */*/*.o */*/.*.cmd */*/*.ko* cd hal ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko* cd hal ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko* cd core/efuse ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko* cd core ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko* cd os_dep/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko* cd os_dep ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko* cd platform ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko* rm -fr Module.symvers ; rm -fr Module.markers ; rm -fr modules.order rm -fr *.mod.c *.mod *.o .*.cmd *.ko* *~ rm -fr .tmp_versions make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.3.1-pclos1/build M=/var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build modules make[1]: Entering directory '/usr/src/kernel-devel-6.3.1-pclos1' CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_sta_mgt.o /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_sta_mgt.c: In function 'rtw_mfree_stainfo': /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_sta_mgt.c:312:25: warning: the comparison will always evaluate as 'true' for the address of 'lock' will never be NULL [-Waddress] 312 | if (&psta->lock != NULL) | ^~ In file included from /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/include/drv_types.h:106, from /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_sta_mgt.c:17: /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/include/sta_info.h:215:17: note: 'lock' declared here 215 | _lock lock; | ^~~~ CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_ap.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_rson.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_tdls.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_sreset.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_btcoex.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/pci_intf.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/pci_ops_linux.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/xmit_linux.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/mlme_linux.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/recv_linux.o CC [M] /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/ioctl_cfg80211.o /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/ioctl_cfg80211.c: In function 'rtw_cfg80211_ch_switch_notify': /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/ioctl_cfg80211.c:399:9: error: too few arguments to function 'cfg80211_ch_switch_notify' 399 | cfg80211_ch_switch_notify(adapter->pnetdev, &chdef, 0); | ^~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/include/osdep_service_linux.h:93, from /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/include/osdep_service.h:47, from /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/include/drv_types.h:27, from /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/ioctl_cfg80211.c:17: ./include/net/cfg80211.h:8375:6: note: declared here 8375 | void cfg80211_ch_switch_notify(struct net_device *dev, | ^~~~~~~~~~~~~~~~~~~~~~~~~ make[2]: *** [scripts/Makefile.build:252: /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build/os_dep/linux/ioctl_cfg80211.o] Error 1 make[1]: *** [Makefile:2004: /var/lib/dkms/rtl8192ee_lwf/5.2.19-1pclos2022/build] Error 2 make[1]: Leaving directory '/usr/src/kernel-devel-6.3.1-pclos1' make: *** [Makefile:1830: modules] Error 2

THANK YOU !!!
your work is so good,
I was able to solve a user problem with it.
look here:
https://www.pclinuxos.com/forum/index.php/topic,158854.0.html
Your rtl8192ee is BETTER than the kernel-in-tree!

All the best for the next year!

Just information in case someone has the same problem.

It has always worked after kernel updates with

make all
sudo make install

After updating from Kernel 5.4.0-64 to 5.4.0-65 it wont load, got it working by

make clean
make all
sudo make install

I am getting the below build errors.

I am building on a fresh Arch install. Headers are installed, and I'm using the latest gcc.

CC [M]  /root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.o
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_cfg80211_ch_switch_notify’:
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c:396:9: error: too few arguments to function ‘cfg80211_ch_switch_notify’
  396 |         cfg80211_ch_switch_notify(adapter->pnetdev, &chdef);
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /root/Documents/rtl8192ee/include/osdep_service_linux.h:93,
                 from /root/Documents/rtl8192ee/include/osdep_service.h:47,
                 from /root/Documents/rtl8192ee/include/drv_types.h:27,
                 from /root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c:17:
./include/net/cfg80211.h:8261:6: note: declared here
 8261 | void cfg80211_ch_switch_notify(struct net_device *dev,
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_cfg80211_indicate_connect’:
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c:984:26: error: ‘struct cfg80211_roam_info’ has no member named ‘bssid’
  984 |                 roam_info.bssid = cur_network->network.MacAddress;
      |                          ^
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c: In function ‘cfg80211_rtw_scan’:
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c:2605:33: warning: the comparison will always evaluate as ‘true’ for the address of ‘ssid’ will never be NULL [-Waddress]
 2605 |                 if (ssids->ssid != NULL
      |                                 ^~
./include/net/cfg80211.h:2357:12: note: ‘ssid’ declared here
 2357 |         u8 ssid[IEEE80211_MAX_SSID_LEN];
      |            ^~~~
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c: At top level:
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c:7320:20: error: initialization of ‘int (*)(struct wiphy *, struct net_device *, unsigned int)’ from incompatible pointer type ‘int (*)(struct wiphy *, struct net_device *)’ [-Werror=incompatible-pointer-types]
 7320 |         .stop_ap = cfg80211_rtw_stop_ap,
      |                    ^~~~~~~~~~~~~~~~~~~~
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c:7320:20: note: (near initialization for ‘rtw_cfg80211_ops.stop_ap’)
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_wdev_unregister’:
/root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.c:7566:17: error: ‘struct wireless_dev’ has no member named ‘current_bss’
 7566 |         if (wdev->current_bss) {
      |                 ^~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:249: /root/Documents/rtl8192ee/os_dep/linux/ioctl_cfg80211.o] Error 1

Hello folks,

While trying to resolve some instabilities with my wifi card, I found the following report in dmesg:

[   18.028269] ================================================================================
[   19.130673] rfkill: input handler disabled
[   19.464558] ================================================================================
[   19.464561] UBSAN: shift-out-of-bounds in /mnt/ssd/projects/rtl8192ee/hal/phydm/phydm_phystatus.c:1704:73
[   19.464563] shift exponent 63 is too large for 32-bit type 'int'
[   19.464565] CPU: 7 PID: 0 Comm: swapper/7 Tainted: G           OE      6.5.0-27-generic #28~22.04.1-Ubuntu
[   19.464566] Hardware name: Gigabyte Technology Co., Ltd. Z490 UD/Z490 UD, BIOS F20d 03/11/2021
[   19.464567] Call Trace:
[   19.464568]  <IRQ>
[   19.464570]  dump_stack_lvl+0x48/0x70
[   19.464574]  dump_stack+0x10/0x20
[   19.464575]  __ubsan_handle_shift_out_of_bounds+0x1ac/0x360
[   19.464579]  mpt_ProQueryCalTxPower+0x1804/0x2940 [8192ee]
[   19.464605]  odm_phy_status_query+0x4f/0x60 [8192ee]
[   19.464636]  rx_query_phy_status+0x161/0x410 [8192ee]
[   19.464676]  pre_recv_entry+0x3b/0x140 [8192ee]
[   19.464714]  rtl8192ee_recv_tasklet+0x1a9/0x5c0 [8192ee]
[   19.464748]  tasklet_action_common.constprop.0+0xfa/0x1e0
[   19.464750]  tasklet_hi_action+0x1f/0x30
[   19.464751]  __do_softirq+0xd9/0x349
[   19.464754]  ? handle_irq_event+0x52/0x80
[   19.464756]  ? handle_edge_irq+0xda/0x250
[   19.464757]  __irq_exit_rcu+0x75/0xa0
[   19.464759]  irq_exit_rcu+0xe/0x20
[   19.464760]  common_interrupt+0xa4/0xb0
[   19.464762]  </IRQ>
[   19.464762]  <TASK>
[   19.464763]  asm_common_interrupt+0x27/0x40
[   19.464765] RIP: 0010:cpuidle_enter_state+0xda/0x720
[   19.464767] Code: 16 06 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 16 c2 04 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 09 0f 87 19 05 00 00
[   19.464768] RSP: 0018:ffffb93e0016be18 EFLAGS: 00000246
[   19.464769] RAX: 0000000000000000 RBX: ffffd93dffdc0400 RCX: 0000000000000000
[   19.464770] RDX: 0000000000000007 RSI: 0000000000000000 RDI: 0000000000000000
[   19.464771] RBP: ffffb93e0016be68 R08: 0000000000000000 R09: 0000000000000000
[   19.464771] R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff87ed1d60
[   19.464781] R13: 0000000000000002 R14: 0000000000000002 R15: 00000004882d55ea
[   19.464782]  ? cpuidle_enter_state+0xca/0x720
[   19.464783]  ? finish_task_switch.isra.0+0x85/0x2a0
[   19.464785]  cpuidle_enter+0x2e/0x50
[   19.464787]  call_cpuidle+0x23/0x60
[   19.464789]  cpuidle_idle_call+0x11d/0x190
[   19.464790]  do_idle+0x82/0xf0
[   19.464791]  cpu_startup_entry+0x2a/0x30
[   19.464792]  start_secondary+0x129/0x160
[   19.464794]  secondary_startup_64_no_verify+0x190/0x19b
[   19.464797]  </TASK>
[   19.464804] ================================================================================

This seems legit since packet_map is u8 but it is attempted to be shifted by 63. I am not familiar with the code and cannot reason what was the intened behavior, but I'm wondering if this may be causing any stability-related issues with the card?

Hello, lwfinger! Thank you for sharing your work with others.

May you help me with this? I am facing the fatal errors below during make.

make: "/rtl8192ee/Makefile" line 1864: warning: duplicate script for target "ifneq" ignored
make: "/rtl8192ee/Makefile" line 1840: warning: using previous script for "ifneq" defined here
make: "/rtl8192ee/Makefile" line 1864: warning: duplicate script for target "(,)" ignored
make: "/rtl8192ee/Makefile" line 1840: warning: using previous script for "(,)" defined here
make: "/rtl8192ee/Makefile" line 1865: warning: duplicate script for target "ifneq" ignored
make: "/rtl8192ee/Makefile" line 1840: warning: using previous script for "ifneq" defined here
make: "/rtl8192ee/Makefile" line 1865: warning: duplicate script for target "(,)" ignored
make: "/rtl8192ee/Makefile" line 1840: warning: using previous script for "(,)" defined here
make: "/rtl8192ee/Makefile" line 1866: Need an operator
make: "/rtl8192ee/Makefile" line 1891: Need an operator
make: Fatal errors encountered -- cannot continue
make: stopped in /rtl8192ee

WHAT I DID:

• I've downloaded the repository using GIT.
• I've executed GIT PULL.
• I've tried "make clean"

WHAT IS MY KERNEL:

FreeBSD 12.2-RELEASE r366954 GENERIC amd64

WHAT I NEED TO DO:

I am running a Firewall pfSense 2.5.0-RELEASE (amd64) built on Tue Feb 16 08:56:29 EST 2021 FreeBSD 12.2-STABLE.

It's a RTL8192EE adapter installed, but I can't get its driver attached on boot. I've tried RTWN, but it didn't work, so I was trying use your repository. I am using a Virtual Machine running FreeBSD 12.2-RELEASE to compile the drivers. After compiled them I move the files to pfSense.

You can find more detials here https://forum.netgate.com/topic/161257/rtl8192ee-pcie-wireless-network-adapter-chip-0x818b10ec/1

Unable to build module on opensuse.

make.log

Thanks in advance.

I am using Linux system running kernel 5.4 and 5.10 series. Module get compile for 5.4 series kernel. But having issue with 5.10 series.

Please check the error log.

MAKELOG.TXT

Hello, Larry. I have been wondering if it is possible to profile the driver's actions during normal use to know where it spends the most time waiting or doing "nothing". The intent is optimization purposes. However I have never touched this part of driver development and don't have a clue where to start from. Any ideas? Is it even feasible?

I've moved over to an AR93xx card supported by ath9k for my router card, and it has been a big upgrade overall.
Unfortunately, I cannot use both cards together as AP because the rtl8192ee adapter being present will make the ath9k adapter stop beaconing completely after a while. I tried to pinpoint it to faulty hardware, but that wasn't the case.

Since all devices in my home now support the 5ghz band, I might try again and put in both cards together in the router box so I have a fallback 2.4n AP and a hi-speed 5.0an AP. I have moved over to using my own software (https://gitlab.com/yagocl/x86routertools) over Oblique's create_ap so that I may have broader control over hostapd. Perhaps if I put the two cards under the same hostapd process it might work.

I might start debugging this issue someday in the future, but if you have any clues to what it may be please let me know.
This issue will be here to track such progress.

Hi.
The driver does not work on the kernel version 5.11 series.
Successfully builded and loaded, but not work.
Kernel: Arch Linux Zen 5.11
Build method: DKMS

Wonder what could be causing this? Seems to affect all realtek drivers.

8192eu case: Mange/rtl8192eu-linux-driver#150

Got my 8192ee some high gain antennas, put it on a empty channel, and loaded up the speedtest on the phone. Iwconfig reports bitrate at 300 properly, but actual download speed on the phone never rises higher than 50Mbps. This is on wireless N, 40MHz and 20MHz show no difference.

RX STBC1 is on as well

Perhaps looking into this could shed some light on improving the performance of rtlwifi drivers.

Good day -

I just bought a TL-WN8881ND wireless card today, it being the only wireless card available for sale today in my rural locality ,
and found that the default rtl8192ee driver causes multiple pcieport bus errors and failes to enter WAP (hostapd) mode , so I tried
cloning your rtl8192 GIT repo and building it.

Firstly, your repo needed some patches in order to build:

--- BEGIN PATCH:
$ git diff
diff --git a/os_dep/linux/os_intfs.c b/os_dep/linux/os_intfs.c
index fd3f555..991472c 100644
--- a/os_dep/linux/os_intfs.c
+++ b/os_dep/linux/os_intfs.c
@@ -1407,7 +1407,7 @@ static const struct net_device_ops rtw_netdev_ops = {
.ndo_stop = netdev_close,
.ndo_start_xmit = rtw_xmit_entry,
#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 35))

• .ndo_select_queue = rtw_select_queue,

• .ndo_select_queue = ((typeof(((struct net_device_ops*)0UL)->ndo_select_queue)) rtw_select_queue),
  #endif
  .ndo_set_mac_address = rtw_net_set_mac_address,
  .ndo_get_stats = rtw_net_get_stats,
  diff --git a/os_dep/linux/rtw_android.c b/os_dep/linux/rtw_android.c
  index 2100bfc..7af6848 100644
  --- a/os_dep/linux/rtw_android.c
  +++ b/os_dep/linux/rtw_android.c
  @@ -37,6 +37,8 @@
  #include <linux/irq.h>
  #endif

+#include <asm/uaccess.h>
+
#include "rtw_version.h"

extern void macstr2num(u8 *dst, u8 *src);
@@ -624,7 +626,7 @@ int rtw_android_priv_cmd(struct net_device *net, struct ifreq *ifr, int cmd)
goto exit;
}

-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5, 0, 0))
+#if (LINUX_VERSION_CODE < KERNEL_VERSION(5, 0, 0))
if (!access_ok(priv_cmd.buf, priv_cmd.total_len)){
#else
if (!access_ok(VERIFY_READ, priv_cmd.buf, priv_cmd.total_len)){
--END PATCH

Then, once I got it to build and install, and added your recommended blacklist of rtl8192ee
and forced load of 8192ee, hundreds of pcieport errors still appear, as with stock rtl819ee driver,
but also these Oops-es which cause the device to be totally ignored by the kernel and not to
appear in an 'ifconfig -a' listing at all :

May 10 15:55:28 devbox01.ptti.co.uk kernel: 8192ee: loading out-of-tree module taints kernel.
May 10 15:55:28 devbox01.ptti.co.uk systemd-vconsole-setup[706]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
May 10 15:55:28 devbox01.ptti.co.uk systemd-vconsole-setup[706]: Fonts will not be copied to remaining consoles
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: AER: Multiple Corrected error received: 0000:00:1c.4
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: device [8086:a294] error status/mask=00000001/00002000
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: [ 0] RxErr
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: AER: can't find device of ID00e4
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: device [8086:a294] error status/mask=00000001/00002000
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: [ 0] RxErr
...
followed by 315 re-occurenece of same error sequence
...
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: device [8086:a294] error status/mask=00000001/00002000
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: [ 0] RxErr
May 10 15:55:28 devbox01.ptti.co.uk kernel: WARNING: CPU: 2 PID: 697 at net/wireless/core.c:901 wiphy_register+0x676/0x9e0 [cfg80211]
May 10 15:55:28 devbox01.ptti.co.uk kernel: Modules linked in: nfsd(E) 8192ee(OE+) auth_rpcgss(E) nfs_acl(E) lockd(E) cfg80211(E) grace(E) sunrpc(E) rfkill(E) xfs(E) libcrc32c(E) sd_mod(E) t10_pi(E) sg(E) i915(E) cec(E) intel_gtt(E) drm_buddy(E) drm_dp_helper(E) drm_kms_helper(E) ahci(E) syscopyarea(E) igb(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) ttm(E) crc32c_intel(E) drm(E) libahci(E) libata(E) dca(E) i2c_algo_bit(E) video(E) fuse(E)
May 10 15:55:28 devbox01.ptti.co.uk kernel: CPU: 2 PID: 697 Comm: systemd-modules Tainted: G OE --------- - - 4.18.0-425.19.2.el8_8.x86_64 #1
May 10 15:55:28 devbox01.ptti.co.uk kernel: Hardware name: Shuttle Inc. SZ270/FZ270, BIOS 1.10 03/19/2018
May 10 15:55:28 devbox01.ptti.co.uk kernel: RIP: 0010:wiphy_register+0x676/0x9e0 [cfg80211]
May 10 15:55:28 devbox01.ptti.co.uk kernel: Code: 29 83 ea 01 48 8d 14 52 48 c1 e2 04 48 01 c2 48 83 78 10 00 74 20 48 39 d0 0f 84 fd 00 00 00 48 83 c0 30 48 83 78 20 00 75 e5 <0f> 0b b8 ea ff ff ff e9 a2 fa ff ff 48 83 78 18 00 75 d9 0f 0b b8
May 10 15:55:28 devbox01.ptti.co.uk kernel: RSP: 0018:ffffa510c3c879c0 EFLAGS: 00010246
May 10 15:55:28 devbox01.ptti.co.uk kernel: RAX: ffffffffc0e0b660 RBX: ffff9189457695c0 RCX: ffff918946bb8868
May 10 15:55:28 devbox01.ptti.co.uk kernel: RDX: 0000000000000003 RSI: 0000000000000000 RDI: 0000000000000006
May 10 15:55:28 devbox01.ptti.co.uk kernel: RBP: ffffa510c3c87a48 R08: 0000000000000001 R09: 0000000000000005
May 10 15:55:28 devbox01.ptti.co.uk kernel: R10: 0000000000000005 R11: 000000000000000d R12: 0000000000000001
May 10 15:55:28 devbox01.ptti.co.uk kernel: R13: ffffa510c3d807c0 R14: ffffa510c3d8073b R15: ffff918944516000
May 10 15:55:28 devbox01.ptti.co.uk kernel: FS: 00007f7511222f80(0000) GS:ffff91908ec80000(0000) knlGS:0000000000000000
May 10 15:55:28 devbox01.ptti.co.uk kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 10 15:55:28 devbox01.ptti.co.uk kernel: CR2: 00007f1487f804bc CR3: 00000001601a4005 CR4: 00000000003706e0
May 10 15:55:28 devbox01.ptti.co.uk kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May 10 15:55:28 devbox01.ptti.co.uk kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
May 10 15:55:28 devbox01.ptti.co.uk kernel: Call Trace:
May 10 15:55:28 devbox01.ptti.co.uk kernel: ? __rtnl_unlock+0x25/0x50
May 10 15:55:28 devbox01.ptti.co.uk kernel: ? netdev_run_todo+0x5e/0x2a0
May 10 15:55:28 devbox01.ptti.co.uk kernel: ? wiphy_apply_custom_regulatory+0xd7/0x110 [cfg80211]
May 10 15:55:28 devbox01.ptti.co.uk kernel: rtw_cfg80211_ndev_res_register+0x2e/0x60 [8192ee]
May 10 15:55:28 devbox01.ptti.co.uk kernel: rtw_os_ndev_register+0x66/0x140 [8192ee]
May 10 15:55:28 devbox01.ptti.co.uk kernel: rtw_os_ndevs_register+0x54/0xe0 [8192ee]
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: device [8086:a294] error status/mask=00000001/00002000
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: [ 0] RxErr
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: device [8086:a294] error status/mask=00000001/00002000
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: [ 0] RxErr
May 10 15:55:28 devbox01.ptti.co.uk kernel: rtw_os_ndevs_init+0x7b/0x110 [8192ee]
May 10 15:55:28 devbox01.ptti.co.uk kernel: pci_alloc_irq+0x7cf/0xd60 [8192ee]
May 10 15:55:28 devbox01.ptti.co.uk kernel: local_pci_probe+0x42/0x80
May 10 15:55:28 devbox01.ptti.co.uk kernel: pci_device_probe+0x109/0x1c0
May 10 15:55:28 devbox01.ptti.co.uk kernel: __driver_probe_device+0x1ec/0x440
May 10 15:55:28 devbox01.ptti.co.uk kernel: driver_probe_device+0x1f/0x90
May 10 15:55:28 devbox01.ptti.co.uk kernel: __driver_attach+0x77/0x170
May 10 15:55:28 devbox01.ptti.co.uk kernel: ? __device_attach_driver+0x100/0x100
May 10 15:55:28 devbox01.ptti.co.uk kernel: bus_for_each_dev+0x77/0xc0
May 10 15:55:28 devbox01.ptti.co.uk kernel: ? klist_add_tail+0x3b/0x70
May 10 15:55:28 devbox01.ptti.co.uk kernel: bus_add_driver+0x151/0x1f0
May 10 15:55:28 devbox01.ptti.co.uk kernel: ? 0xffffffffc069a000
May 10 15:55:28 devbox01.ptti.co.uk kernel: driver_register+0x6b/0xc0
May 10 15:55:28 devbox01.ptti.co.uk kernel: ? 0xffffffffc069a000
May 10 15:55:28 devbox01.ptti.co.uk kernel: init_module+0x5a/0x1000 [8192ee]
May 10 15:55:28 devbox01.ptti.co.uk kernel: do_one_initcall+0x46/0x1d0
May 10 15:55:28 devbox01.ptti.co.uk kernel: ? do_init_module+0x22/0x230
May 10 15:55:28 devbox01.ptti.co.uk kernel: ? kmem_cache_alloc_trace+0x142/0x280
May 10 15:55:28 devbox01.ptti.co.uk kernel: do_init_module+0x5a/0x230
May 10 15:55:28 devbox01.ptti.co.uk kernel: load_module+0x14bf/0x17f0
May 10 15:55:28 devbox01.ptti.co.uk kernel: ? __do_sys_finit_module+0xb1/0x110
May 10 15:55:28 devbox01.ptti.co.uk kernel: __do_sys_finit_module+0xb1/0x110
May 10 15:55:28 devbox01.ptti.co.uk kernel: do_syscall_64+0x5b/0x1b0
May 10 15:55:28 devbox01.ptti.co.uk kernel: entry_SYSCALL_64_after_hwframe+0x61/0xc6
May 10 15:55:28 devbox01.ptti.co.uk kernel: RIP: 0033:0x7f75103c89bd
May 10 15:55:28 devbox01.ptti.co.uk kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 9b 54 38 00 f7 d8 64 89 01 48
May 10 15:55:28 devbox01.ptti.co.uk kernel: RSP: 002b:00007ffc2e77a9a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
May 10 15:55:28 devbox01.ptti.co.uk kernel: RAX: ffffffffffffffda RBX: 0000558f7c3c2990 RCX: 00007f75103c89bd
May 10 15:55:28 devbox01.ptti.co.uk kernel: RDX: 0000000000000000 RSI: 00007f751097e86d RDI: 0000000000000007
May 10 15:55:28 devbox01.ptti.co.uk kernel: RBP: 00007f751097e86d R08: 0000000000000000 R09: 0000558f7b191568
May 10 15:55:28 devbox01.ptti.co.uk kernel: R10: 0000000000000007 R11: 0000000000000246 R12: 0000000000000000
May 10 15:55:28 devbox01.ptti.co.uk kernel: R13: 0000558f7c3c2a10 R14: 0000000000020000 R15: 0000000000000000
May 10 15:55:28 devbox01.ptti.co.uk kernel: ---[ end trace a234105b44d668e9 ]---
May 10 15:55:28 devbox01.ptti.co.uk kernel: Failed to register cfg80211
May 10 15:55:28 devbox01.ptti.co.uk kernel: Failed to register device
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: device [8086:a294] error status/mask=00000001/00002000
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: [ 0] RxErr
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
May 10 15:55:28 devbox01.ptti.co.uk kernel: pcieport 0000:00:1c.4: AER: can't find device of ID00e4

I also added your suggested 'HT_CAPAB' line to my /etc/hostapd.conf file

This will give you a minimal, insecure wireless network.

DO NOT BE SATISFIED WITH THAT!!!

A complete, well commented example configuration file is

available here:

/usr/share/doc/hostapd/hostapd.conf

For more information, look here:

http://wireless.kernel.org/en/users/Documentation/hostapd

ctrl_interface=/var/run/hostapd
ctrl_interface_group=wheel

Some usable default settings...

macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0

Uncomment these for base WPA & WPA2 support with a pre-shared key

wpa=3
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP

DO NOT FORGET TO SET A WPA PASSPHRASE!!

wpa_passphrase=PTTi1066

Most modern wireless drivers in the kernel need driver=nl80211

driver=nl80211

Customize these for your local configuration...

interface=wlp5s0
ssid=PTTIDB01
hw_mode=g
channel=8

recommended by 'lwfinger', author of 8192ee driver:

HT_CAPAB=[RX-STBC1][SHORT-GI-40][SHORT-GI-20][DSSS_CCK-40][MAX-AMSDU-7935]

It is a very urgent work-related issue for me to configure this particular linux host with a WiFi card, which it does not have,
by Friday, to demo our software, which needs a WAP in this configuration, to a client .

Please can you suggest any way to fix to get your module to operate under Linux 4.18-425 (latest LTS RHEL-8 release),
or where I am going wrong with my config ? A prompt response would be much appreciated, else I will have to spend
£500 tomorrow to get a card delivered 300 miles by courier from my nearest metropolis tomorrow .

Thank you & Best Regards,
Jason Vas Dias [email protected] - a software engineer .

Currently, using this particular driver, the transmission power used is extremely low.

The kernel's default driver (when no regulatory domain is set), uses a default of 20 dBm (~100 mW) output txpower as reported by iwconfig.

This driver however, only transmits at an extremely low 12 dBm (~16 mW) and it cannot be modified at all even using iwconfig <dev> txpower 20dBm.

(Quick note, this card also supports overclocking beyond 20 dBm if modifying the regulatory database. Maximum I've managed to get it -- with a heatsink -- is 30 dBm or 1 W).

This low power seems to be due to the regulatory database not actually being used since modifying any REG_RULE in os_dep/linux/wifi_regd.c has no effect on the output. This decreases the overall connection quality for me in contrast to the kernel's driver.

For contrast, here's the result of a modified REG_RULE to set a default of 30 dBm output.

# iwconfig wlp4s70

wlp4s0    IEEE 802.11  ESSID:"<snip>"  
          Mode:Managed  Frequency:2.4XX GHz  Access Point: <snip>
          Bit Rate=144.4 Mb/s   Tx-Power=30 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Power Management:off
          Link Quality=70/70  Signal level=-24 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:

This may be related to why this driver performs worse in upstream tasks rather than downstream tasks.

Note: This was done on the PCIe version on a desktop so I'm able to safely increase the output by adding a moderately sized heatsink to the card.

Hello,

I am having an issue with this driver -- when used, the wireless device seems to be missing (it does not show when I run networkctl or iwctl). Furthermore, it causes my computer to hang on shutdown/reboot.

dmesg and journalctl show (the same) error regarding some buffer overflow issue.

Installation

I installed the driver using make:

git clone https://github.com/lwfinger/rtl8192ee.git
cd rtl8192ee
make all
sudo make install
echo "blacklist rtl8192ee" | sudo tee -a /etc/modprobe.d/50-blacklist.conf
echo "8192ee" | sudo tee -a /etc/modules-load.d/8192ee.conf

All of which completed successfully.

System

I am using Arch Linux with Linux Kernel version 6.5.3.

Logs

Sep 14 11:17:07 pc-zachary kernel: rtl8192ee 0000:05:00.0: enabling device (0000 -> 0003)
Sep 14 11:17:07 pc-zachary kernel: detected buffer overflow in __fortify_strlen
Sep 14 11:17:07 pc-zachary kernel: ------------[ cut here ]------------
Sep 14 11:17:07 pc-zachary kernel: kernel BUG at lib/string_helpers.c:1031!
Sep 14 11:17:07 pc-zachary kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
Sep 14 11:17:07 pc-zachary kernel: CPU: 1 PID: 263 Comm: systemd-modules Tainted: G           OE      6.5.3-arch1-1 #1 ed5b3b894d0aeb37298a77837232ca9b353c>
Sep 14 11:17:07 pc-zachary kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B98/Z390-A PRO (MS-7B98), BIOS 1.C0 10/10/2020
Sep 14 11:17:07 pc-zachary kernel: RIP: 0010:fortify_panic+0x13/0x20
Sep 14 11:17:07 pc-zachary kernel: Code: 41 5d c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 48 89 fe 48 c7 c7 40 1d e8 8c e8 >
Sep 14 11:17:07 pc-zachary kernel: RSP: 0018:ffffc0a0415b7868 EFLAGS: 00010246
Sep 14 11:17:07 pc-zachary kernel: RAX: 000000000000002c RBX: ffff995905533740 RCX: 0000000000000000
Sep 14 11:17:07 pc-zachary kernel: RDX: 0000000000000000 RSI: ffff995c5dc616c0 RDI: ffff995c5dc616c0
Sep 14 11:17:07 pc-zachary kernel: RBP: ffff995905533ab0 R08: 0000000000000000 R09: ffffc0a0415b7710
Sep 14 11:17:07 pc-zachary kernel: R10: 0000000000000003 R11: ffffffff8d6ca068 R12: ffff995905533ae8
Sep 14 11:17:07 pc-zachary kernel: R13: ffffc0a040275000 R14: 0000000000000000 R15: 0000000000000000
Sep 14 11:17:07 pc-zachary kernel: FS:  00007f46e985c480(0000) GS:ffff995c5dc40000(0000) knlGS:0000000000000000
Sep 14 11:17:07 pc-zachary kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 14 11:17:07 pc-zachary kernel: CR2: 00007fa4868da130 CR3: 0000000100d1c003 CR4: 00000000003706e0
Sep 14 11:17:07 pc-zachary kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 14 11:17:07 pc-zachary kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 14 11:17:07 pc-zachary kernel: Call Trace:
Sep 14 11:17:07 pc-zachary kernel:  <TASK>
Sep 14 11:17:07 pc-zachary kernel:  ? die+0x36/0x90
Sep 14 11:17:07 pc-zachary kernel:  ? do_trap+0xda/0x100
Sep 14 11:17:07 pc-zachary kernel:  ? fortify_panic+0x13/0x20
Sep 14 11:17:07 pc-zachary kernel:  ? do_error_trap+0x6a/0x90
Sep 14 11:17:07 pc-zachary kernel:  ? fortify_panic+0x13/0x20
Sep 14 11:17:07 pc-zachary kernel:  ? exc_invalid_op+0x50/0x70
Sep 14 11:17:07 pc-zachary kernel:  ? fortify_panic+0x13/0x20
Sep 14 11:17:07 pc-zachary kernel:  ? asm_exc_invalid_op+0x1a/0x20
Sep 14 11:17:07 pc-zachary kernel:  ? fortify_panic+0x13/0x20
Sep 14 11:17:07 pc-zachary kernel:  ? fortify_panic+0x13/0x20
Sep 14 11:17:07 pc-zachary kernel:  rtw_ps_deny_get+0x22d/0x500 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? rtw_txpwr_lmt_add+0x6d/0xb0 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? phy_set_tx_power_limit+0x382/0x3f0 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? odm_read_and_config_mp_8192e_txpwr_lmt+0x4a/0x90 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? odm_config_rf_with_header_file+0xc9/0x140 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? phy_load_tx_power_limit+0xb2/0x330 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? rtw_init_drv_sw+0x2ee/0x340 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? rtw_pci_primary_adapter_init+0x163/0xf740 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? rtw_pci_primary_adapter_init+0x8e5/0xf740 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? local_pci_probe+0x42/0xa0
Sep 14 11:17:07 pc-zachary kernel:  ? pci_device_probe+0xc1/0x260
Sep 14 11:17:07 pc-zachary kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
Sep 14 11:17:07 pc-zachary kernel:  ? really_probe+0x19b/0x3e0
Sep 14 11:17:07 pc-zachary kernel:  ? __pfx___driver_attach+0x10/0x10
Sep 14 11:17:07 pc-zachary kernel:  ? __driver_probe_device+0x78/0x160
Sep 14 11:17:07 pc-zachary kernel:  ? driver_probe_device+0x1f/0x90
Sep 14 11:17:07 pc-zachary kernel:  ? __driver_attach+0xd2/0x1c0
Sep 14 11:17:07 pc-zachary kernel:  ? bus_for_each_dev+0x85/0xd0
Sep 14 11:17:07 pc-zachary kernel:  ? bus_add_driver+0x116/0x220
Sep 14 11:17:07 pc-zachary kernel:  ? driver_register+0x59/0x100
Sep 14 11:17:07 pc-zachary kernel:  ? __UNIQUE_ID_vermagic196+0x3f5f7e1e6b54/0x3f5f7e1e6b54 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? init_module+0x52/0xff0 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? __UNIQUE_ID_vermagic196+0x3f5f7e1e6b54/0x3f5f7e1e6b54 [8192ee f61d033aa746dd1ccfc87b28cb494620d0226135]
Sep 14 11:17:07 pc-zachary kernel:  ? do_one_initcall+0x5a/0x320
Sep 14 11:17:07 pc-zachary kernel:  ? do_init_module+0x60/0x240
Sep 14 11:17:07 pc-zachary kernel:  ? init_module_from_file+0x89/0xe0
Sep 14 11:17:07 pc-zachary kernel:  ? idempotent_init_module+0x120/0x2b0
Sep 14 11:17:07 pc-zachary kernel:  ? __x64_sys_finit_module+0x5e/0xb0
Sep 14 11:17:07 pc-zachary kernel:  ? do_syscall_64+0x5d/0x90
Sep 14 11:17:07 pc-zachary kernel:  ? ksys_mmap_pgoff+0xec/0x1f0
Sep 14 11:17:07 pc-zachary kernel:  ? do_syscall_64+0x6c/0x90
Sep 14 11:17:07 pc-zachary kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Sep 14 11:17:07 pc-zachary kernel:  ? do_syscall_64+0x6c/0x90
Sep 14 11:17:07 pc-zachary kernel:  ? do_syscall_64+0x6c/0x90
Sep 14 11:17:07 pc-zachary kernel:  ? syscall_exit_to_user_mode+0x2b/0x40
Sep 14 11:17:07 pc-zachary kernel:  ? do_syscall_64+0x6c/0x90
Sep 14 11:17:07 pc-zachary kernel:  ? entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Sep 14 11:17:07 pc-zachary kernel:  </TASK>
Sep 14 11:17:07 pc-zachary kernel: Modules linked in: 8192ee(OE+) cfg80211 rfkill fuse dm_mod loop vfat fat ip_tables x_tables ext4 crc32c_generic crc16 mb>
Sep 14 11:17:07 pc-zachary kernel: ---[ end trace 0000000000000000 ]---
Sep 14 11:17:07 pc-zachary kernel: RIP: 0010:fortify_panic+0x13/0x20
Sep 14 11:17:07 pc-zachary kernel: Code: 41 5d c3 cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 48 89 fe 48 c7 c7 40 1d e8 8c e8 >
Sep 14 11:17:07 pc-zachary kernel: RSP: 0018:ffffc0a0415b7868 EFLAGS: 00010246
Sep 14 11:17:07 pc-zachary kernel: RAX: 000000000000002c RBX: ffff995905533740 RCX: 0000000000000000
Sep 14 11:17:07 pc-zachary kernel: RDX: 0000000000000000 RSI: ffff995c5dc616c0 RDI: ffff995c5dc616c0
Sep 14 11:17:07 pc-zachary kernel: RBP: ffff995905533ab0 R08: 0000000000000000 R09: ffffc0a0415b7710
Sep 14 11:17:07 pc-zachary kernel: R10: 0000000000000003 R11: ffffffff8d6ca068 R12: ffff995905533ae8
Sep 14 11:17:07 pc-zachary kernel: R13: ffffc0a040275000 R14: 0000000000000000 R15: 0000000000000000
Sep 14 11:17:07 pc-zachary kernel: FS:  00007f46e985c480(0000) GS:ffff995c5dc40000(0000) knlGS:0000000000000000
Sep 14 11:17:07 pc-zachary kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 14 11:17:07 pc-zachary kernel: CR2: 00007fa4868da130 CR3: 0000000100d1c003 CR4: 00000000003706e0
Sep 14 11:17:07 pc-zachary kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 14 11:17:07 pc-zachary kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

I manually changed the file "hal/rl8192e/rtl8192e_phycfg.c". Changes to the code made :
int transmit_power_override = 20;

However the power transmission is still coming as 12dB, which is the minimum. Are there any other changes required to increase the power ?

Hi,i am trying to use this driver on kernel version that are higher than 5.10 but i am having some issues. The installation goes successful but after i reboot the system is very slow and i am not able to use sudo, audio and connectiviy also are not working. How can i fix this issue ? Right now i am on arch linux and the 5.10 kernel is not anymore in the repositories and the new lts kernel is. Can i at least get this working on the lts version 5.15 ?

Could you ask Realtek if they have a newer version of this beta private driver? (and then upload it here) I am interested in what performance improvements they could have made.

My wireless router has been working very well with this driver since I finished the scripts controlling the network and any quirks I noticed on my trials.

I have just now retried the rtlwifi_new driver, but it is not yet fit for this application. Yet, there seems to be advancements being made. Great work, keep it up.

Hi,

I have the Wireless PCI Express adapter installed -> TL-WN881ND:

root@luffy:~/rtl8192ee# lspci | grep -i --color wireless
01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE PCIe Wireless Network Adapter

and I noticed that while trying to install the driver from your repository I am getting the following errors:

/root/rtl8192ee/core/rtw_recv.c: In function ‘rtw_signal_stat_timer_hdl’:
/root/rtl8192ee/core/rtw_recv.c:4361:6: error: argument ‘RTW_TIMER_HDL_ARGS’ doesn’t match prototype
void rtw_signal_stat_timer_hdl(RTW_TIMER_HDL_ARGS)
^
/root/rtl8192ee/core/rtw_recv.c:29:13: error: prototype declaration
static void rtw_signal_stat_timer_hdl(void *ctx);
^
/root/rtl8192ee/core/rtw_recv.c:4367:34: error: ‘FunctionContext’ undeclared (first use in this function)
_adapter *adapter = (_adapter *)FunctionContext;
^
/root/rtl8192ee/core/rtw_recv.c:4367:34: note: each undeclared identifier is reported only once for each function it appears in
scripts/Makefile.build:285: recipe for target '/root/rtl8192ee/core/rtw_recv.o' failed
make[2]: *** [/root/rtl8192ee/core/rtw_recv.o] Error 1
Makefile:1457: recipe for target 'module/root/rtl8192ee' failed
make[1]: *** [module/root/rtl8192ee] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-184-generic'
Makefile:1816: recipe for target 'modules' failed
make: *** [modules] Error 2

Checking further though I see that the driver is loaded:

root@luffy:~/rtl8192ee# lsmod | grep rtl
rtl8192ee 102400 0
btcoexist 53248 1 rtl8192ee
rtl_pci 32768 1 rtl8192ee
rtlwifi 77824 2 rtl_pci,rtl8192ee
mac80211 741376 3 rtl_pci,rtlwifi,rtl8192ee
cfg80211 565248 2 mac80211,rtlwifi

but while trying to authenticate on my ESSID I cannot make my wireless connection work:

wlan0: CTRL-EVENT-DISCONNECTED bssid=44:fe:3b:db:b1:b6 reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CentralPerk" auth_failures=1 duration=10 reason=CONN_FAILED
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

I am using wpa_supplicant for my ESSID setup (WPA2-Personal auth). I have been reading around a lot but I couldn't find the solution yet. I also check the VT-d on BIOS to see if it is enabled and it is.

Could you please help me on this? Any idea how to overcome the issue and make the wireless card work would be much appreciated.

Thank in advance,
Stamatis

Hi.

I've got a problem for compiling on debain bullseye :
sudo make all
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.10.0-6-amd64/build M=/home/kayarec/rtl8192ee modules
make[1]: *** /lib/modules/5.10.0-6-amd64/build: No such file or directory. Stop.
make: *** [Makefile:1823: modules] Error 2

Will you update the kernel library ? or is it an other problem ?

My kernel is :
Linux 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) x86_64 GNU/Linux

Thanks

Set CONFIG_BT_COEXIST in Makefile to y (it is set at n by default) to build in btcoexist. However the compilation hangs up at a single line. (rtl8192ee/hal/hal_btcoex.c:2591:2:)

 2591 |  rtw_init_timer(&GLBtcBtMpOperTimer, padapter, _btmpoper_timer_hdl, pBtCoexist);
      |  ^~~~~~~~~~~~~~
      |  rtw_init_netdev

Commenting out the line lets it compile, but I doubt that is the intended behaviour.