Package Details: rtl8814au-dkms-git 4.3.21.r34.ga0c4479-2

Git Clone URL: (read-only)
Package Base: rtl8814au-dkms-git
Description: RTL8814AU and RTL8813AU chipset driver with firmware v4.3.21
Upstream URL:
Licenses: GPL2
Conflicts: rtl8814au
Submitter: zebulon
Maintainer: zebulon
Last Packager: erkexzcx
Votes: 16
Popularity: 0.035411
First Submitted: 2017-09-18 20:21
Last Updated: 2018-08-19 22:11

Dependencies (3)

Required by (0)

Sources (3)

Pinned Comments

zebulon commented on 2019-10-01 06:19

To all having an issue with this driver: please try alternatively.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

zebulon commented on 2018-08-31 18:24

Interesting, looks like an evolution of 5.2.20 and that they have integrated aircrack injection code. Possibly the future for all rtl8812/14/21 series?

erkexzcx commented on 2018-08-29 12:12 :)

zebulon commented on 2018-08-24 08:45

Unfortunately I cannot help due to the fact I do not own a 8814au device. As you write, you would need some metrics. But you may notice some bugs being removed (disconnection, etc.). Finally, there may be some security fixes/enhancements that are not visible.

erkexzcx commented on 2018-08-24 03:14

For sure I can test it, but why should I? I mean, even with rtl8812au-aircrack-dkms-git, the only thing I noticed is lower ping (3ms instead of 4ms with your driver. How can I validate it works "better"? :)

zebulon commented on 2018-08-21 12:10

In addition, on the Edimax website, there is a file which decompresses as rtl8814AU_linux_v4.3.21.1_20171108.tar.gz. This is the same version number than for the TP-link, but the timestamp changes by 9 days. I did a quick comparison with and indeed they are almost identical. The Edimax archive has an Edimax specific entry while the TP-link has, as expected, its own specific T9UH UIDs. Thus vendors only adapt the code to their adapter names, that's all. Otherwise the rest of code is mostly the same. This shows how Realtek just provides boiler plates to vendors that make their own archives, hence the mess. That said, it is probably worth trying v4.3.21.1 over v4.3.21 as it may have upstream corrections from Realtek.

zebulon commented on 2018-08-21 11:46

I did further searches, and found out this version: from Just found out that it is available in Github with kernel patches there: or Worth a try maybe? Do you want to try this code base and report? If they do work and fix bugs then it could be worth using them.

zebulon commented on 2018-08-21 11:37

@erkexzcx: this is the reason why I am very reluctant to use these sources. The 3 PKGBUILD I maintain so far use the latest code version from Realtek (allegedly) for each chipset, repectively. The only modifications are code to make them compatible with the latest Linux kernel versions. Other projects often use hybrid code bases to make the drivers compatible with many chipsets, and end up with drivers that are not up to date and carry a lot of hacks. But in the end it is Realtek to blame; they should be more open and transparent with their code and their multiple rewrites.

erkexzcx commented on 2018-08-20 19:21

Actually using AUR package rtl8812au-aircrack-dkms-git I got lower latency and overall better performance when using with my AWUS1900 but then suddenly it started to randomly "reload" itself and connection is getting lost about every 1-2 minutes. I then got back to this (your) AUR package/driver and all the issues went away. So I assume - rtl8812au-aircrack-dkms-git is a more complete driver with more pull requests than in original driver, but again - it was unstable to me.

zebulon commented on 2018-08-20 12:01

@erkexzcx: fantastic, many thanks. Besides, do you know if this is still the latest release from Realtek? It is infuriating the driver is much behind the rtl8812au version (if the version numbering is indeed significant, that is.)

erkexzcx commented on 2018-08-19 22:13

@zebulon I've updated this package. Nothing has changed for x86_64 and i686 architectures, just a very small patch for ARM devices to get it work. Just double checked it by installing this package on my ARM device - works perfectly. Thanks a lot!