On 8/10/19 1:13 PM, Sergey Kharitonov wrote:
Dear Mr. Finger! Thank you for paying attention to the problem. I've just posted an updated information to that bug before receiving this message. I get these results ~]$ ping 192.168.88.1 PING 192.168.88.1 (192.168.88.1) 56(84) bytes of data. 64 bytes from 192.168.88.1: icmp_seq=1 ttl=64 time=0.746 ms 64 bytes from 192.168.88.1: icmp_seq=2 ttl=64 time=0.868 ms 64 bytes from 192.168.88.1: icmp_seq=3 ttl=64 time=0.853 ms 64 bytes from 192.168.88.1: icmp_seq=4 ttl=64 time=0.868 ms 64 bytes from 192.168.88.1: icmp_seq=5 ttl=64 time=0.818 ms 64 bytes from 192.168.88.1: icmp_seq=6 ttl=64 time=0.844 ms 64 bytes from 192.168.88.1: icmp_seq=7 ttl=64 time=0.841 ms 64 bytes from 192.168.88.1: icmp_seq=8 ttl=64 time=0.913 ms 64 bytes from 192.168.88.1: icmp_seq=9 ttl=64 time=0.844 ms 64 bytes from 192.168.88.1: icmp_seq=10 ttl=64 time=0.886 ms ^C --- 192.168.88.1 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 387ms rtt min/avg/max/mdev = 0.746/0.848/0.913/0.044 ms with a driver from rtl8192ee_revised.tar.bz2 file in https://github.com/lwfinger/rtlwifi_new/tree/extended repository built against Linux 4.19.65-1-lts ArchLinux current LTS kernel. Connection speed and stability on a heavy load are also perfect. Hope this info would help solving current rtl8192ee problem. Please let me know if any additional info is needed.
That driver is totally different from the one in the kernel. It comes from the group that writes the combined drivers for Windows, FreeBSD, and Linux. The coding there is completely inappropriate for inclusion in the kernel. I'm glad that it works for you.
I will use its PCI communications to see what it does differently from the kernel version, and I will extract the embedded firmware in that driver and try it with the kernel driver.
Larry
