Package Details: rtl8812au-dkms-git

Git Clone URL: (read-only, click to copy)
Package Base: rtl8812au-dkms-git
Description: rtl8812AU chipset driver with firmware v5.6.4.2
Upstream URL:
Licenses: GPL2
Conflicts: rtl8812au
Submitter: thelinuxguy
Maintainer: zebulon (zebulon)
Last Packager: zebulon
Votes: 63
Popularity: 1.75
First Submitted: 2015-06-08 13:04
Last Updated: 2020-03-19 20:26

Dependencies (3)

Required by (0)

Sources (2)

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 10 ... Next › Last »

Nudin commented on 2019-01-20 23:49

I installed it succesfully but I can't get the interface up:

$ sudo ip link set dev wlan1 up
RTNETLINK answers: Operation not permitted

Any ideas?

arthurwatt-veea commented on 2019-01-11 08:23

Hello folks (@zebulon) I have been trying to setup an AP on DFS channels with this driver. With a 4.14 kernel and hostapd version 2.6 this does work. Looking at the code it seems that the DFS radar cfg80211_ops have not been implemented. When testing I did the following changes: enabled CONFIG_DFS_MASTER build flag set cfg80211 country modprobe parameter (ieee80211_regdom) implemented a null cfg80211 radar interface to keep hostapd happy set the rtl8812au domain module parameter (rtw_dfs_region_domain) Setting the rtw_dfs_region_domain seemed to cause things to go a bit wonky (like not marking the DFS channels as radar detect, so hostapd did not do CAC). There seems like a fair bit of code to handle DFS channels in the driver, but it is not clear what level of support is present.

Do we expect DFS channels to work on this version of the driver?

Thank you Arthur

zebulon commented on 2018-12-10 09:12

@arthurwatt-veea: thanks a lot for your work on the code. When you are ready, please fork one of the rtl8812au repos (such as gordboy's or the aircrack-ng) and propose your patches. One patch per issue being better than a big one addressing several ones, as you might already know. The earliest these patches are being added and tested (to ensure they do not introduce side effects), the better.

arthurwatt-veea commented on 2018-12-07 07:57

The bug is present in 5.1 and 5.2 repos. I guess there is not much testing of IBSS. My next job is to try and get IBSS working securely with RSN.

zebulon commented on 2018-11-29 15:30

@arthurwatt-veea: that is great work. Has the bug been introduced in 5.2? The codebase is very different from 4.3 (and 5.1 as far as I remember). What I would recommend to do is for you to fork a github repo (such as gordboy's or aircrack-ng), commit your change and send a pull request to various rtl8812au repos. They do not need to be the same than the one you used for your fork of course.

arthurwatt-veea commented on 2018-11-29 14:33

Thanks Zebulon. Before cutting through the repos I wanted to make sure the driver was not receiving the multicast packets and then discarding them. I then found that the multicast frames were being received and then discarded. The fix is fairly straightforward, not sure which repo I should push the change to, there seem to be so many....

zebulon commented on 2018-11-28 12:29

@arthurwatt-veea: 2 possibilities here: 1) would you like to try 5.3.4 version of the driver from: and let me know if that corrects the issue. 2) Also, does reverting to 5.1.5 work? You can install package and check (this one works for 8812au too). Please let me know which one works.

arthurwatt-veea commented on 2018-11-28 11:43

Hello I am testing the RTL8812AU device on 4.14 kernel in IBSS mode. Beacon handing seems ok and we can create/join the IBSS network with this driver. However we have noticed that multicast/broadcast data reception is failing which causes issues. Unicast processing seems to be working correctly. The IBSS behaved well on 4.3 version of the 8812AU driver.

Has anyone else come across this problem?



moething commented on 2018-11-14 19:52

@gordboy It turned out that it was my mistake. Apologies. was missing in my local copy. That one contains the fix for my issue. It works fine now. Thanks for your support!

zebulon commented on 2018-11-14 11:01

@gordboy: thanks a lot for your notification and your swiftness. Just merged the change. As usual, please notify me issues or directly to the concerned Github repos.