Package Details: rtl88xxau-aircrack-dkms-git r1200.cab4e4e-1

Git Clone URL: (read-only, click to copy)
Package Base: rtl88xxau-aircrack-dkms-git
Description: Aircrack-ng kernel module for Realtek 88XXau (USB adapters only) network cards (8811au, 8812au and 8821au chipsets) with monitor mode and injection support
Upstream URL:
Keywords: 8811au 8812au 8821au aircrack dkms driver injection rtl8811au rtl8812au rtl8821au rtl88xx wireless
Licenses: GPL
Conflicts: rtl8812au-aircrack-dkms-git, rtl8812au-dkms-git, rtl8812au-inject-dkms-git, rtl8814au-dkms-git, rtl8821au-dkms-git
Submitter: iyanmv
Maintainer: iyanmv
Last Packager: iyanmv
Votes: 43
Popularity: 0.013396
First Submitted: 2019-01-29 20:43 (UTC)
Last Updated: 2022-06-06 13:10 (UTC)

Required by (0)

Sources (2)

Pinned Comments

iyanmv commented on 2020-11-10 17:40 (UTC)

8814au chipset support is turned off in this driver. Please use this package instead. Also, if you plan to use both packages at the same time, make sure that you have an up-to-date package.

iyanmv commented on 2020-01-10 16:02 (UTC)

This package now forces to use the branch v5.6.4.2 (the one that works better for me), which is the default one in the remote repository although they still mention branch v5.3.4 as the stable one. If you have any issues, please leave a comment, and also tried to change the branch in the source array. For example, change it to:


Read the to learn how to set your interface in monitor mode (and other things).

Important: Use ip and iw instead of ifconfig and iwconfig

Latest Comments

alealexpro100 commented on 2022-07-10 14:08 (UTC) (edited on 2022-07-11 05:10 (UTC) by alealexpro100)

Please consider unpinning first commentary. This driver now supports rtl8814au and it builds and works. Mentioned package does NOT work on latest kernel (5.18.9-arch1-1).

iyanmv commented on 2022-06-06 13:11 (UTC)

larvan: one patched got merged 12 hours ago, and the other is irrelevant because support for 5.18 was added in a different commit. You just needed to remove the prepare function from the PKGBUILD.

I've removed the patches and now should work. Give it another try.

larvan commented on 2022-06-06 12:44 (UTC)

This package no longer builds.

I successfully installed it 4 days ago (June 2) but now, after a couple of daily updates, I get the following:

❯ makepkg
==> Making package: rtl88xxau-aircrack-dkms-git r1181.37e27f9-1 (Mon 06 Jun 2022 15:42:20 EEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating rtl88xxau git repo...
Fetching origin
  -> Found dkms.conf
  -> Found 961.patch
  -> Found 959.patch
==> Validating source files with sha256sums...
    rtl88xxau ... Skipped
    dkms.conf ... Passed
    961.patch ... Passed
    959.patch ... Passed
==> Extracting sources...
  -> Creating working copy of rtl88xxau git repo...
Reset branch 'makepkg'
==> Starting prepare()...
patching file include/ieee80211.h
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file include/ieee80211.h.rej
==> ERROR: A failure occurred in prepare().

I tried to build under both Linux 5.18.1.arch1-1 and 5.15.44-1-lts - same result.

mahir256 commented on 2022-05-30 16:27 (UTC)

It appears that after the release of kernel 5.18 this module does not build; in the interim, downgrading to 5.17.9 allows me to continue to use my WiFi adapter.

ignace72 commented on 2022-05-17 22:59 (UTC) (edited on 2022-05-17 23:02 (UTC) by ignace72)

Good evening, iyanmv.
Thank you for your answer.
I don't have any particular problem, it's just that I would like to buy the Netgear Nighthawk A7000 WIFI dongle (rtl8812au) because it's more powerful than my current AC1200 and before buying it, I want to be sure that it will work and so I'm looking for the right driver.
Sorry if I'm only answering now but I hadn't enabled notifications.

iyanmv commented on 2022-05-14 14:08 (UTC)

ignace72: it works for me. Do you have any particular issue?

ignace72 commented on 2022-05-13 18:26 (UTC)

I would like to know if for a rtl8812au the driver works with kernel 5.17.
Thank you.

iyanmv commented on 2021-11-21 14:11 (UTC)

Shished: I opened a PR upstream

Shished commented on 2021-11-21 12:56 (UTC)

DKMS complains about REMAKE_INITRD option

Deprecated feature: REMAKE_INITRD

Can you remove it from dkms.conf?

mokkurkalve commented on 2021-07-22 12:42 (UTC)

Just asking: Does anybody know how status is on this driver vs. FragAttacks? (Seems Realtek source is from 2019...)

mokkurkalve commented on 2021-06-28 15:23 (UTC)

Pull request 857 made it in. Patch can be removed:

leo95 commented on 2021-06-27 15:24 (UTC)

patch no longer necessary.

kotrfa commented on 2021-06-24 20:06 (UTC)

It unfortunately doesn't work for me. The device is "DOWN" and cannot be brought up:

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

winglesshinigami commented on 2021-05-24 00:45 (UTC)

is rtl8812au fixed? Haven't switched to Linux yet as I have been waiting for this to be fixed.

iyanmv commented on 2021-05-12 17:19 (UTC)

@konecny-ondrej thanks for sharing the PR. I have added it as a patch to current PKGBUILD until the PR gets accepted.

konecny-ondrej commented on 2021-05-12 17:06 (UTC)

Hopefully the Pull Request with the fix gets approved soon. In the meantime I have used the Pull Request's source branch as a source for this package and it works just fine.


iyanmv commented on 2021-05-08 17:50 (UTC) (edited on 2021-05-08 17:51 (UTC) by iyanmv)

It seems there is an issue with authentication when using the latest kernel 5.12.1 [1].

However, I do not have any issues with monitor mode and injection, which is the main use case of this driver.

Please, report your issues upstream. Here only issues regarding the PKGBUILD.


AnuragRao commented on 2021-05-08 17:31 (UTC) (edited on 2021-05-08 17:33 (UTC) by AnuragRao)

I tried installing this driver on my arch system running 5.12 kernel. I was previously using the same driver when I was on 5.11 and it used to work flawlessly. Unfortunately, it broke when I upgraded to 5.12. I tried installing the driver at this page: but it kept occasionally disconnecting. I would like to point out that it did not completely disconnect but just stopped internet access. I tried reinstalling the driver at this page and it installed fine, but I am not able to connect to my home network, however, I am able to see the list of all networks. Any help would be really appreciated!

iyanmv commented on 2021-04-29 19:03 (UTC)

@darkside: sorry, I forgot to answer your latest comment. I have no idea about the other driver, probably it does not allow for injection, which is the main feature/advantage of this one.

iyanmv commented on 2021-04-29 10:43 (UTC)

@samxl001: 5.12 is still on [testing] in Arch. Wait till it reaches [Core] and then I will test that everything works fine.

samxl001 commented on 2021-04-29 03:50 (UTC)

Doesn't work on the linux5.12 kernel. I tried on manjaro and it gives return code 10

darkside commented on 2021-04-23 04:47 (UTC) (edited on 2021-04-23 04:47 (UTC) by darkside)

@iyanmv thank you for fast answer. I wasn't precise enough. I'm aware that the sources are different. I have rtl8812au so both drivers should work just fine. For rtl8812au Is the aircraft the only difference? (No much info on github page)

iyanmv commented on 2021-04-22 21:04 (UTC)

@darkside: yes, different sources (and features) and different supported chipsets.

darkside commented on 2021-04-22 15:41 (UTC) (edited on 2021-04-22 15:51 (UTC) by darkside)

If this is possible then don't kill me for this question please, but is there any important difference between this driver and the: rtl8812au-dkms-git ?

iyanmv commented on 2021-03-17 20:27 (UTC)

@rjahanbakhshi Hi, thanks for the feedback, but I don't want to add archs that I cannot test myself. Everyone is welcome to modify the PKGBUILD and test it in different architectures as you did.

rjahanbakhshi commented on 2021-03-17 20:20 (UTC) (edited on 2021-03-17 20:21 (UTC) by rjahanbakhshi)

Could you please add aarch64 to the arch variable. I added it and built it for Alfa Network AWUS036AC on raspberry pi 4 and it works perfectly.

diff --git a/PKGBUILD b/PKGBUILD
index b46f9d3..ef3c54f 100644
@@ -4,12 +4,12 @@

 pkgdesc="Aircrack-ng kernel module for Realtek 88XXau (USB adapters only) network cards (8811au, 8812au and 8821au chipsets) with monitor mode and injection support"
+arch=('x86_64' 'aarch64')
 conflicts=('rtl8812au-aircrack-dkms-git' 'rtl8812au-dkms-git' 'rtl8821au-dkms-git' 'rtl8814au-dkms-git' 'rtl8812au-inject-dkms-git')

iyanmv commented on 2021-03-14 17:07 (UTC)

@elemat I don't have that issue. Are you using latest commit?

cheezsteak commented on 2021-03-04 17:30 (UTC)

@elemat I'm having the same problems after a recent update. My laptop can connect to the 5GHz network on channel 157 but my desktop with a rtl8812 card cannot see it. The rtl8812 card shows that it does support channel 157 at 5785 MHz but at 30.0 dBm where as my laptop has 22.0 dBm. I don't know if the dBm discrepency is relevant though.

elemat commented on 2021-03-03 23:35 (UTC)

I am using this module and it works well, except it may not provide the 5 GHz band. I upgraded to the 5.11.2 kernel. Is anyone experiencing the same problem?

SilverMight commented on 2021-02-20 19:29 (UTC)

If you're having issues building the module, make sure you have the package pahole installed.

dash42 commented on 2021-01-09 16:59 (UTC)

not working with rpi4

cedricbambooza commented on 2020-12-31 15:26 (UTC)

@iyanmv Sorry for the faulty report, I was sure I was using the newest commit but obviously wasn't, my fault pardon me :)

iyanmv commented on 2020-12-31 14:32 (UTC)

@cedricbambooza I cannot replicate your issue. And this is a git package, it is your responsibility to use the last commit since I will not update the pkver every time there is a new commit upstream [1]. If you are using an AUR helper, probably it is not pulling latest commits and you are stuck in r1123 (based on the logs you put upstream)


iyanmv commented on 2020-12-31 14:26 (UTC)

@cedricbambooza if it's an AUR issue, why do you report upstream? I will have a look.

cedricbambooza commented on 2020-12-31 14:06 (UTC) (edited on 2020-12-31 15:41 (UTC) by cedricbambooza)

[SOLVED] Package does build but won't install through dkms on Kernel 5.10.3 as described here Version from Github works with both dkms and make install

used an old commit, my fault ^^

gebau00a commented on 2020-12-16 06:33 (UTC)

Package does not build against kernel 5.10 anymore, explained in

Solution in New Git branch ee9619b

iyanmv commented on 2020-11-10 17:54 (UTC)

@kotrfa you were not using the last commit from upstream. When you did a fresh installation (I am assuming by fresh you mean to clone again the package or do a clean build using some AUR helper), you got the latest commit, which probably includes some fixes for the latest version of the linux kernel.

iyanmv commented on 2020-11-10 17:40 (UTC)

8814au chipset support is turned off in this driver. Please use this package instead. Also, if you plan to use both packages at the same time, make sure that you have an up-to-date package.

kotrfa commented on 2020-11-10 07:03 (UTC)

And if rlt8814au was moved elsewhere, the description and keywords are out of date

kotrfa commented on 2020-11-10 07:02 (UTC)

Just yesterday, I was getting:

31091   │ [2020-11-09T21:15:32+0100] [ALPM-SCRIPTLET] ==> dkms install --no-depmod -m rtl88xxau -v r1116.2801378 -k 5.9.6-arch1-1
31092   │ [2020-11-09T21:17:31+0100] [ALPM-SCRIPTLET] ==> dkms install --no-depmod -m rtl8812au -v 5.3.4 -k 5.9.6-arch1-1
31093   │ [2020-11-09T21:17:35+0100] [ALPM-SCRIPTLET] Error! Bad return status for module build on kernel: 5.9.6-arch1-1 (x86_64)
31094   │ [2020-11-09T21:17:35+0100] [ALPM-SCRIPTLET] Consult /var/lib/dkms/rtl8812au/5.3.4/build/make.log for more information.
31095   │ [2020-11-09T21:17:35+0100] [ALPM-SCRIPTLET] ==> Warning, `dkms install --no-depmod -m rtl8812au -v 5.3.4 -k 5.9.6-arch1-1' returned 10
31096   │ [2020-11-09T21:17:35+0100] [ALPM-SCRIPTLET] ==> depmod 5.9.6-arch1-1

when updating the system.

Reinstalling this package from fresh helped for some reason.

b00rt00s commented on 2020-11-02 10:25 (UTC)

New package:

voho commented on 2020-10-31 10:51 (UTC)

@b00rt00s thanks, please do!

b00rt00s commented on 2020-10-29 12:37 (UTC)

Looks like the support for rtl8814au was moved to separate git repo:

I prepared PKGBUILD and dkms.conf:

I could create new package if no one other will.

cartesius commented on 2020-10-13 19:18 (UTC) (edited on 2020-10-13 19:21 (UTC) by cartesius)

@iyanmv that commit, yes, I didn't look into it, sorry for the confusion. just built that driver version, yes, probably resolved earlier... I quickly googled for another 8812au driver and that one was the first github repo on Google :) Now removed and rtl8812au-dkms-git seems OK as well after 15 minutes of pinging. No lost/delayed packets so far.

iyanmv commented on 2020-10-13 18:42 (UTC)

@cartesius that commit you mentioned does not seem to make any big change. So maybe your issue was fixed in some earlier commit. This is a git PKGBUILD, so you should always get the last commit from the repo. By the way, why do you use this driver instead of rtl8812au-dkms-git?

cartesius commented on 2020-10-13 18:22 (UTC)

Having issues with this package with ID 2357:0103 TP-Link Archer T4UH wireless Realtek 8812AU. From time to time (5-10 times a day) local WiFi 2.4 Ghz N connection with excelent signal levels around -55 dBm shows strange lost packets and/or about 15% packets are heavily delayed (normal ping 1-3ms, problematic ping 500-1000 ms). Using latest 5.8.14 kernel, static IP, no other WiFi signal present.

Resolved (so far) using commit 280137863b08956c442ce0d3e67669ede781ee1c from:

iyanmv commented on 2020-10-05 14:09 (UTC)

@tigersoldier no, it should not. It has dkms as dependency, and that should be enough. It is your job to ensure that you have the right headers. Note that the linux kernel is just an optional package in base. People may have other kernels (linux-lts, linux-hardened), so why would they want to install linux-headers in their systems?

tigersoldier commented on 2020-10-05 00:11 (UTC)

This package should also depend on linux-headers

iyanmv commented on 2020-08-27 15:30 (UTC)

@capoeira I use yay which also supports that. If you install the package manually or with another helper, just be sure to run yay -Y --gendb the first time. And then you should get the upgrades when there are new commits upstream.

capoeira commented on 2020-08-18 12:44 (UTC)

@kyak thanks. will try that one out

kyak commented on 2020-08-18 05:41 (UTC)

@capoeira pikaur supports that.

capoeira commented on 2020-08-17 16:07 (UTC)

is there any aur-helper that will update git packages with -Syu?

kyak commented on 2020-08-17 14:45 (UTC)

@iyanmv of course, sorry for the noise!

iyanmv commented on 2020-08-17 11:13 (UTC)

@kyak: yes, it does. Probably you are using an old commit. Remember that this is a git PKGBUILD so it is your responsibility to keep it up to date.

kyak commented on 2020-08-17 11:03 (UTC)

This kernel module doesn't build with 5.8.1-arch1-1

jpegxguy commented on 2020-08-15 08:43 (UTC)

Ah, I thought they put the most stable branch as default, not the newest. Though it might not be as stable for all users.

iyanmv commented on 2020-08-15 08:07 (UTC)

@jpegxguy because they often change the default branch upstream, and not all the times the default one is necessary the one that works the best. Right now, yes, I'm pointing to the default one (see pinned comment), but maybe it changes in the future.

jpegxguy commented on 2020-08-02 13:46 (UTC)

Why are you forcing the branch in the source array?

solsticedhiver commented on 2020-07-09 09:05 (UTC)

You can make it build on arm (at least rpis) by patching the Makefile.

I suggest changing the PKGBUILD by adding a prepare() function like:

prepare() {
        if [[ $CARCH =~ ^arm ]] ;then
                cd ${srcdir}/${_pkgbase}
                sed -i 's/CONFIG_PLATFORM_I386_PC = y/CONFIG_PLATFORM_I386_PC = n/g' Makefile
                sed -i 's/CONFIG_PLATFORM_ARM_RPI = n/CONFIG_PLATFORM_ARM_RPI = y/g' Makefile

cardinal commented on 2020-07-05 14:26 (UTC)

since i dont have much experience, but cant make this to compile with 5.8 kernel

abgeranzt commented on 2020-05-24 04:11 (UTC) (edited on 2020-05-24 04:12 (UTC) by abgeranzt)

After having the driver from rtl8812au-dkms-git break with a system upgrade, I switched to this one and it works flawlessly without having to fiddle around with it.

iyanmv commented on 2020-04-17 12:49 (UTC)

@direc85 this is a git package as you can see from the name of the package, so according to AUR guidelines "AUR maintainers should not commit mere pkgver bumps".

You are responsible to update whenever you want. Notice that the PKGBUILD will always try to use the last commit from upstream so you just need to call makepkg. Or you can also use a helper, that's also your choice.

direc85 commented on 2020-04-16 17:52 (UTC)

If DKMS can't compile the driver for kernel 5.6 and 5.7, just install the package again on (top of itself). I was debugging my rig with cats and dogs, but installing the package updated it from r1038.945d6ed to r1059.8b29c11 which did the trick. (And as of writing this, the package version listed on the top of this page is r999.65174c4 to confuse me even more ;)

mokkurkalve commented on 2020-03-09 01:11 (UTC)

With commit

the workaround for iwd are no longer needed.

mokkurkalve commented on 2020-02-15 12:33 (UTC)

yshui's advice seem to have solved my long standing problem. :-)

yshui commented on 2020-02-14 18:20 (UTC) (edited on 2020-02-14 18:21 (UTC) by yshui)

For people who uses iwd and is experiencing problems with hangs after loading the module, you can try adding this to /etc/iwd/main.conf


k96hkh commented on 2020-02-06 12:15 (UTC)

@iyanmv, thanks for reply and yes indeed tricky. You inspired me to read some more and for anyone interested here are a few thoughts. I turns out its not more interfaces I should be looking for. Reading about IEEE 802.11ac at Wikipedia it seems like a adapter marked with AC1200 should be able to use 2.4+5GHz at the same time under the right circumstances. Reading about the rtl8812au chip on realtek homepage it seems the chip should be able to be used in 802.11ac/abgn or 802.11ac 2x2 combination. But how to configure it is a mystery and probably has more to do with how the AP is set-up. I'll see if I can find a good forum for hostapd and see if anyone there knows more.

Again, thanks and may the arch force be with you!

PS. I already have two USB adapters, one dedicated for 2.4 and one for 5 GHz APs, this is just because I'm curious and what to understand how stuff works. Now I'm also curious about aircracking so I'll dig more into that :)

iyanmv commented on 2020-02-02 23:10 (UTC)

@k96hkh this is a tricky question. To be honest, I do not know if this driver would work even in the case that your chipset supports that. But you can give it a try and figure it out. First, I would be sure that your device can simultaneously use both bands at the same time. iw list can help you find that out. Having two antennas doesn't mean that it can use both bands at the same time. Normally you can create as many software monitor interfaces as you want (iw dev YOUR_CHIPSET interface add NAME_MONITOR_INTERFACE type monitor), although with this driver I have issues with this thing, but they will compete for the resources, meaning that if you, for example use airodump-ng simultaneously with both interfaces on different channels, it will not work as you expected. There are some chipsets that support that though, but I guess you will have some lines in the "interface combinations" section when you run iw list.

What I usually do when I want to scan both 2.4 and 5 GHz bands is select the specific channels and let airodump-ng hop from one to another. It works quite good. For example, airodump-ng -WMU wlp0s20u1 -c 1,6,11,36,44

k96hkh commented on 2020-02-02 12:57 (UTC)

Thanks for a great work on this package! I have a question and maybe someone here knows or can point in the right direction. I have an USB external adapter with two antennas. Is it possible to create one AP at 2.4 GHz and and one at 5 GHz at the same time? What I have found on the internet is: Maybe if two interfaces are created for the adapter. Is this something rtl88xxau driver can do? Is it depending on adapter or maybe just "no can do".


iyanmv commented on 2020-02-01 21:07 (UTC)

@banzr not really, what if someone uses linux-lts, linux-hardened or linux-zen? Why would they want linux-headers on their system? I think people using dkms should take care of installing the headers they need. All these are mentioned as optional dependencies when installing dkms.

commented on 2020-02-01 19:45 (UTC)

This package is missing a dependency to linux-headers.

mokkurkalve commented on 2020-01-12 11:29 (UTC)

Versions of this driver after r918.73f0a88 still completely knocks out my system as described below. r918.73f0a88 still works fine.

iyanmv commented on 2020-01-10 16:02 (UTC)

This package now forces to use the branch v5.6.4.2 (the one that works better for me), which is the default one in the remote repository although they still mention branch v5.3.4 as the stable one. If you have any issues, please leave a comment, and also tried to change the branch in the source array. For example, change it to:


Read the to learn how to set your interface in monitor mode (and other things).

Important: Use ip and iw instead of ifconfig and iwconfig

iyanmv commented on 2020-01-07 22:13 (UTC)

@ayuksel this is rtl88xxau not rtl8814au

ayuksel commented on 2020-01-04 02:56 (UTC)

I am not sure how to log it or necessarily prove it, but I am on Manjaro with kernel 5.3. I am using the netgear A7000 with rtl8814au, and I am not having an issue with detection but for some reason the connection keeps randomly dropping on a very consistent basis. I had tried with this ubuntu and it had turned out fine with kernel 5.0, but now on Manjaro it is not working at all. Also, when the connection does drop my network manager still says I'm connected to the network, but it won't load anything and the traffic for both upload/download drop to 0.

trulex commented on 2019-11-19 20:02 (UTC)


mokkurkalve commented on 2019-11-18 11:11 (UTC)

I have adapter Asus USB-AC56 (RTL8812AU). I use NetworkManager with IWD backend. Currently I've landed on using commit r918.73f0a88 for this driver, with the addition of cherrypicking commit to turn off the enormous flow of debug messages that spammed my logs and rendered them utterly useless. This setup is working very well for me. I've also tried using the currently latest commit in the repo. But somewhere between r918.73f0a88 and r965.a8ec357 there's snuck in a commit that hangs my system; can't use shell, can't reboot by software, and I wouldn't know how to start debugging that with an unuseable system.

vinayyadav3016 commented on 2019-11-14 19:23 (UTC)

For those, whom network card stopped working after latest AUR package update to v5.6.2 or v5.6.1.

By reverting to v.5.3.4, my device has stated working again both 2.4G and 5G. OS:Arch Linux Kernel:4.19.84-1-lts Device: TP-Link AC600 T2U Plus

iyanmv commented on 2019-11-04 22:02 (UTC) (edited on 2019-11-04 22:06 (UTC) by iyanmv)

I have updated the PKGBUILD just to push pkgver to last commit. Most of errors that are reported here are because of using an old commit from upstream. Also, be aware that in the current branch (v5.6.4.1) setting monitor with the iw or iwconfig makes frame injection unstable, so better use airmon-ng start <interface> to avoid issues.

If you still have problems, try loading the module with USB Mode 3.0 by doing:

rmmod 88XXau
modprobe 88XXau rtw_switch_usb_mode:1

iyanmv commented on 2019-10-28 07:12 (UTC)

@devon bug reports here will not help, please report it upstream.

devon commented on 2019-10-26 22:42 (UTC) (edited on 2019-10-26 22:53 (UTC) by devon)

Hello, on 5.3.7 kernel, the connection started only for few seconds with poor signal and then go down, see the log below.

[ 1490.743836] WARNING: CPU: 6 PID: 2369 at net/wireless/sme.c:756 __cfg80211_connect_result.cold+0x32/0x7f [cfg80211] [ 1490.743837] Modules linked in: 88XXau(OE) ccm rt2800usb rt2x00usb rt2800lib rt2x00lib mac80211 libarc4 8021q garp mrp stp llc 8812au(OE) cfg80211 rfkill fuse ax25 nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) hwmon_vid intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm uvcvideo iTCO_wdt mxm_wmi iTCO_vendor_support drm_kms_helper irqbypass videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_usb_audio videobuf2_common intel_cstate snd_usbmidi_lib intel_uncore videodev snd_rawmidi snd_hda_intel snd_seq_device joydev input_leds mc drm mousedev snd_hda_codec i2c_i801 agpgart snd_hda_core snd_hwdep lpc_ich ipmi_devintf snd_pcm ipmi_msghandler r8169 snd_timer syscopyarea snd realtek sysfillrect sysimgblt soundcore libphy i7core_edac fb_sys_fops i5500_temp wmi asus_atk0110 evdev mac_hid acpi_cpufreq vboxpci(OE) virtio_net net_failover failover virtio_ring virtio vboxnetflt(OE) vboxnetadp(OE) nfsd vboxdrv(OE) auth_rpcgss nfs_acl loop lockd sg grace sunrpc crypto_user ip_tables x_tables [ 1490.743910] ext4 crc16 mbcache jbd2 sr_mod cdrom sd_mod hid_generic usbhid hid uhci_hcd ahci libahci libata xhci_pci xhci_hcd scsi_mod ehci_pci ehci_hcd raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq md_mod xfs libcrc32c crc32c_generic crc32c_intel [ 1490.743939] CPU: 6 PID: 2369 Comm: kworker/u32:0 Tainted: P W IOE 5.3.7-arch1-1-ARCH #1 [ 1490.743941] Hardware name: System manufacturer System Product Name/P6T, BIOS 1408 09/21/2010 [ 1490.743967] Workqueue: cfg80211 cfg80211_event_work [cfg80211] [ 1490.744005] RIP: 0010:__cfg80211_connect_result.cold+0x32/0x7f [cfg80211] [ 1490.744008] Code: 95 32 b9 f2 0f 0b e9 d8 90 fd ff 48 c7 c7 38 2d 37 c2 e8 82 32 b9 f2 0f 0b e9 e1 90 fd ff 48 c7 c7 38 2d 37 c2 e8 6f 32 b9 f2 <0f> 0b e9 3e 8f fd ff 48 c7 c7 38 2d 37 c2 e8 5c 32 b9 f2 0f 0b e9 [ 1490.744010] RSP: 0018:ffffb20502edfdb0 EFLAGS: 00010246 [ 1490.744013] RAX: 0000000000000024 RBX: ffff926b32960a18 RCX: 0000000000000000 [ 1490.744015] RDX: 0000000000000000 RSI: ffff926b67997708 RDI: 00000000ffffffff [ 1490.744017] RBP: ffffb20502edfe00 R08: 00000000000004d7 R09: 0000000000000001 [ 1490.744019] R10: 0000000000000000 R11: 0000000000000001 R12: ffff926ace962800 [ 1490.744021] R13: 0000000000000000 R14: ffffb20502edfdb0 R15: dead000000000100 [ 1490.744024] FS: 0000000000000000(0000) GS:ffff926b67980000(0000) knlGS:0000000000000000 [ 1490.744026] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1490.744028] CR2: 00005583c65871f0 CR3: 00000001c3e0a000 CR4: 00000000000006e0 [ 1490.744030] Call Trace: [ 1490.744042] ? __switch_to_asm+0x40/0x70 [ 1490.744046] ? __switch_to_asm+0x40/0x70 [ 1490.744075] ? cfg80211_process_wdev_events+0x139/0x1a0 [cfg80211] [ 1490.744103] cfg80211_process_wdev_events+0x139/0x1a0 [cfg80211] [ 1490.744134] cfg80211_process_rdev_events+0x32/0x70 [cfg80211] [ 1490.744159] cfg80211_event_work+0x1a/0x20 [cfg80211] [ 1490.744164] process_one_work+0x1d1/0x3a0 [ 1490.744168] worker_thread+0x4a/0x3d0 [ 1490.744173] kthread+0xfb/0x130 [ 1490.744176] ? process_one_work+0x3a0/0x3a0 [ 1490.744179] ? kthread_park+0x80/0x80 [ 1490.744184] ret_from_fork+0x35/0x40 [ 1490.744189] ---[ end trace 2bfe10d94a42b053 ]---

mokkurkalve commented on 2019-10-17 22:37 (UTC)

@Martinsos: Yes it is indeed very strange. But somehow you got very old sources, the commit is from 29 July 2018 in fact. I have no idea how this happened to you......

Martinsos commented on 2019-10-17 21:46 (UTC)

@mokkurkalve I have to admit I don't know much about PKGBUILD and cvs packages, but I am getting that if I installed it some time ago, it might not be pulling new source files from the git if I manage it through AUR helper since package itself does not change? But in my case, I installed it for the very first time right now! Anyway, thanks for help, this is probably not the place to teach me about the PKGBUILD, I will have to investigate it myself :). Thanks!

will_wisp commented on 2019-10-17 19:58 (UTC) (edited on 2019-10-17 22:45 (UTC) by will_wisp)

@mokkurkalve: The problem were the sources, indeed. That and that I use a AUR helper, so that I did not realize that the sources were out of date. Thanks for your help! I think I will add a pacman installation/update hook...

[Edit: An alias in the .bashrc was easier...]

mokkurkalve commented on 2019-10-16 00:20 (UTC)

@Martinsos: I had no problem compiling this. But I see that your sources are r61.1c72e11 while mine are r854.25c0645 (I BTW just installed this driver). Have you tried what was described just below your post; to make sure to have the latest sources from the GitHub repo for dkms to compile? @will_wisp: What version of the sources do you have? You both presumably should have the latest sources from the repo this package utilises:

will_wisp commented on 2019-10-15 21:33 (UTC)

With the newest version of gcc I am not able to make a dkms install. Will there be an update soon upstream in this package (= is this kind of behavior expected from time to time)? Or do you think there is a problem with the new gcc?

Martinsos commented on 2019-10-15 20:32 (UTC)

I am trying to get the alfa-awus036ach wifi adapter/dongle to work, which uses 8812 chipset. I tried using rtl8812au-dkms-git, and got it installed and loaded, but could not get dongle to show via ip link. I then arrived here, but can not get the package installed, I get error message:

Error! Bad return status for module build on kernel: 5.3.6-arch1-1-ARCH (x86_64) Consult /var/lib/dkms/rtl88xxau/r61.1c72e11/build/make.log for more information.

I took a look at make.log, and there are some compiler warnings, notably:

cc1: some warnings being treated as errors make[2]: [scripts/ /var/lib/dkms/rtl88xxau/r61.1c72e11/build/os_dep/linux/os_intfs.o] Error 1 In file included from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/include/drv_types.h:35, from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/os_dep/linux/mlme_linux.c:24: /var/lib/dkms/rtl88xxau/r61.1c72e11/build/include/wifi.h:1009: warning: "IEEE80211_MAX_AMPDU_BUF" redefined 1009 | #define IEEE80211_MAX_AMPDU_BUF 0x40 | In file included from ./include/net/cfg80211.h:21, from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/include/osdep_service_linux.h:94, from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/include/osdep_service.h:41, from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/include/drv_types.h:32, from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/os_dep/linux/mlme_linux.c:24: ./include/linux/ieee80211.h:1441: note: this is the location of the previous definition 1441 | #define IEEE80211_MAX_AMPDU_BUF 0x100 | make[1]: [Makefile:1626: module/var/lib/dkms/rtl88xxau/r61.1c72e11/build] Error 2 make[1]: Leaving directory '/usr/lib/modules/5.3.6-arch1-1-ARCH/build' make: *** [Makefile:1264: modules] Error 2

zebulon commented on 2019-10-15 09:30 (UTC) (edited on 2019-10-15 09:36 (UTC) by zebulon)

@iyanmv: just to precise, if you use a helper to reinstall, it may then trigger the download of the latest Git update again (if the PKGBUILD points to the latest sources like this one, and not a specific snapshot). Just be sure that your helper cache is empty (using e.g. yay -Scc). On the other hand the dkms package does not redownload any sources, they are statically installed by the PKGBUILD.

iyanmv commented on 2019-10-15 06:32 (UTC)

@zebulon exactly! This is a cvs PKGBUILD, so you won't receive any updates if you use any helper (such as yay). To get the last changes from upstream you should run makepkg. I will increase pkgver/pkgrel if there are some changes on the PKGBUILD itself according to VCS guidelines.

zebulon commented on 2019-10-15 06:27 (UTC)

Apologies for stating the obvious, but had this case before as a maintainer. Can everyone having issues with 5.3.1 make sure they have updated the sources the package uses? DKMS does not that, it only recompiles using the installed sources, it does not re-download the Github sources. To do so you can simply force a reinstalling of this package, which will indeed download teh Git sources again. Of course if your adapter does not work, you may do so by reinstalling an older kernel or try an alternate adapter.

mokkurkalve commented on 2019-10-14 12:20 (UTC)

My adapter Asus USB-AC56 (rtl8812au) seems to work fine here & now with kernel linux 5.3.5.arch1-1. What is curious is that I had to set Management Frame Protection (802.11w) from "supported" to "disabled" on the AP before I could associate adapter with AP. (And it was set to "supported", not "mandatory".) Anybody understands this? (The AP is Asus RT-AC68U with asuswrt-merlin 384.13 firmware.)

Nudin commented on 2019-10-12 21:18 (UTC)

Used this without problems until to the upgrade to kernel 5.3, after that it didn't got an interface, upgraded to newest version now I do see the interface but still get no scan results. All other drivers don't work as well…

Gatenkaas commented on 2019-10-07 10:25 (UTC)

Driver had some recent updates and works again for me now, thanks. (TP-Link T9UH v1)

iyanmv commented on 2019-10-01 19:41 (UTC)

@mrpanda so probably it's an issue with recent kernels. Have a look at this open issue upstream, subscribe to it just in case someone figure it out, and wwait till they fix it (kernel or driver). I'm sorry but I can't help here, I just maintain the PKGBUILD.

mrpanda commented on 2019-10-01 17:39 (UTC)

@iyanmv Yes it has compatible chipset. My point was that I was using this driver till kernel 5.3.1 update so I was expected to see some error during installation that's it.

iyanmv commented on 2019-10-01 06:43 (UTC)

@mrpanda why should it work this driver for you or any others from AUR? Are you sure your Qoltec uses a compatible chipset? Of course, you will be able to install any of them, but that's not the point, right?

mrpanda commented on 2019-09-30 22:27 (UTC)

none of the drivers in AUR support my Qoltec 57010 hardware rtl8811au no installation problems , but it seems that it has no power , the indicator is dead.

aris commented on 2019-09-30 04:44 (UTC)

@Gatenkaas The driver works for me on kernel 5.3.1, and I'm using TP-Link T9UH. However, this driver is nowhere close to the performance I'd get with the package rtl8814au-dkms-git. The signal strength is about 30% less and the upload speed is at least 80% slower. Sadly, the rtl8814au-dkms-git driver has stopped working after I upgraded to 5.3.1. Otherwise, I wouldn't be using the aircrack driver.

jpegxguy commented on 2019-09-23 16:48 (UTC) (edited on 2019-09-23 16:48 (UTC) by jpegxguy)

@Gatenkaas File any bug reports (Search before creating a new issue) in the upstream github. They can fix it there.

Gatenkaas commented on 2019-09-23 16:04 (UTC)

None of the current drivers in AUR for kernel 5.3 seem to support my tp-link T9UH v1 anymore [8814au]. No building problems at all - but the device has no power (lights). However lsusb shows the device, but modprobe hangs. No problems on kernel 5.2.

iyanmv commented on 2019-09-22 10:26 (UTC)

I have deleted the hardcoded branch in the sources array as suggested by @jpegxguy. v5.6.4.1 is currently the active branch so I'll keep it. If you have any problems, please try a different branch and check issues in the upstream repo.

jpegxguy commented on 2019-09-20 22:12 (UTC) (edited on 2019-09-20 22:13 (UTC) by jpegxguy)

@capoeira I disagree with that philosophy, but you can certainly go by it.

I mean, Linux 3.10 would work fine, but I wouldn't use it for my PC. It's old, less features and bugfixes.

The driver you chose is maintained and contains none of the work that aircrack have put into it for unification and to support all the chips e.t.c.

capoeira commented on 2019-09-20 20:51 (UTC)

@jpegguy thanks, but seams to work nicely for me. "If it aint broke, don't fix it"

jpegxguy commented on 2019-09-20 19:35 (UTC) (edited on 2019-09-20 19:35 (UTC) by jpegxguy)

@capoeira Try removing the branch selection from the sources array

jpegxguy commented on 2019-09-20 19:33 (UTC) (edited on 2019-09-20 19:34 (UTC) by jpegxguy)

They have changed the upstream branch. Save yourself the trouble, don't hardcode the branch in the sources array. Just use it like this:


capoeira commented on 2019-09-20 10:46 (UTC)

not working anymore for my TP-LINK Archer T4U. the other driver works

ckoba commented on 2019-09-13 07:00 (UTC)

I've reworked this slightly to support building on any platform (tested on x86_64 and aarch64).

The patch is at ... if the patch is acceptable to the maintainer, please merge.

jpegxguy commented on 2019-07-11 17:19 (UTC)

@peterpan4, It can be handled in the PKGBUILD conditionally with an ARCH variable or something. But indeed I've basically been using your way up until now

peterpan4 commented on 2019-06-29 00:25 (UTC) (edited on 2019-07-11 19:52 (UTC) by peterpan4)

Here is how I build this package under Arch Linux ARM disabling the randomized MAC address. Not sure if the process can be streamlined somehow.

tar xzfv rtl88xxau-aircrack-dkms-git.tar.gz
cd rtl88xxau-aircrack-dkms-git
makepkg -Aos  # fetch sources and deps without installing

vim src/rtl88xxau*/Makefile  # change the following lines:

vim src/rtl88xxau/core/rtw_ieee80211.c  # change this line:

makepkg -Aeif  # compile and install without re-downloading the source

iyanmv commented on 2019-05-27 21:56 (UTC)

There is a new branch (v5.6.4):

But still a lot of work to do... I'll keep an eye on it!

iyanmv commented on 2019-04-22 22:29 (UTC) (edited on 2019-04-22 22:30 (UTC) by iyanmv)

Upstream they have changed the default branch to v5.3.4. I'll edit PKGBUILD so it uses that from now on. If you have any issues, please leave a comment. You can use previous branch by editing line 18 in the PKGBUILD.

matthjes commented on 2019-04-09 18:08 (UTC)

Sorry, this is not the correct driver, my mistake. I finally found out that the ID is 0bda:b812, which, according to this site ( means that the chipset is RTL8812bu.

iyanmv commented on 2019-04-08 12:14 (UTC)

@matthjes try first to use the branch I suggest, it is still more active in the repo. Be sure that you are using this driver and not the previous one you installed. If it fails, then try the other branch.

Also, be sure to connect your card to a USB 3 port. My card, for example, also fails if I connect it to a USB 2 port.

matthjes commented on 2019-04-08 06:02 (UTC)

@iyanmv Hm, interesting. I've first used this package: As I was experiencing problems with my adapter, I uninstalled this package and installed the one from aircrack. This did not help, so I followed the advice from jgegxguy and used yay -G to download the package, then changed the branch and installed this version, without luck. It seems like I'm still using the other driver, which is strange. I have to look into this.

iyanmv commented on 2019-04-07 19:53 (UTC)

@matthjes Are you sure you are using this PKGBUILD? In the logs I read "rtl88x2bu v5.3.1_27678.20180430_COEX20180427-5959" :S

jpegxguy commented on 2019-04-07 16:03 (UTC)

@matthjes Try using branch 5.3.4 as well. You can do this by changing #branch=v5.2.20 to #branch=v5.3.4 in the sources matrix of the PKGBUILD

That said, it does sound like upstream issue. You'll get better help here

matthjes commented on 2019-04-07 15:33 (UTC)

I have the following problem: I can install the driver without problems, my USB wifi adapter gets recognized and I can establish a connection. However, after some minutes the adapter disappears. With dmesg I can see the following enries:

WARN rtw_halmac_poweron: Power state abnormal, try to recover...OK ERROR _halmac_reg_write_16: I/O FAIL! ERROR [HALMAC][ERR]bcn valid!! [17589.156758] RTW: ERROR [HALMAC][ERR]dl rsvd page!! [17589.156758] RTW: ERROR [HALMAC][ERR]send fw pkt!! [17589.659026] RTW: ERROR download_fw: download firmware FAIL! status=0x66

Here is the output:

jpegxguy commented on 2019-04-04 21:32 (UTC)

@pollito if you use the package you'll get updates. If you install with the method from the git repo you won't.

pollito commented on 2019-04-04 20:31 (UTC) (edited on 2019-04-04 20:59 (UTC) by pollito)

@zebulon Yes i already install the dkms and kernel headers, But whats the name of the module to modprobe? Thank... My wireless adapter is (rtl8811au). Update: nevermind i install from source and works ;)

jpegxguy commented on 2019-04-04 18:05 (UTC)

@iyanmv it builds fine on aarch64 as far as I remember. I used it in my board. I guess it's fine if your do the $CARCH thing. I don't know if we need the options set.

iyanmv commented on 2019-04-04 15:23 (UTC)

I've change ARCH from any to x86_64. @zebulon I'll have a look at what you say about using $CARCH because I also have no experience.

jpegxguy commented on 2019-04-04 15:03 (UTC)


zebulon commented on 2019-04-04 14:15 (UTC)

@jpegxguy: no idea, I have no arm device to check. I am only the messenger and would only advise those who need support to report further here.

jpegxguy commented on 2019-04-04 12:13 (UTC)

@zebulon I think Armbian uses the aircrack git without the rPI config option. Does this fail to build under arm?

zebulon commented on 2019-04-04 08:49 (UTC) (edited on 2019-04-04 08:52 (UTC) by zebulon)

@iyanmv: as commented by solstice in (see pinned comment), this PKGBUILD actually only works for x86_64, due to the fact that Makefile in the repository has these presets:




Hence, we should have arch=('x86_64') and not 'any' in the PKGBUILD. That said, it is possible to make it modular using $CARCH detection during build, but I have no experience using it.

zebulon commented on 2019-04-04 08:34 (UTC)

@pollito: you will need to provide further information: has the module compiled correctly (you need dkms in addition to the headers)? If yes, does it load succesfully (using modprobe)? You will find the procedure to check every step from the wiki page at:

pollito commented on 2019-04-04 06:56 (UTC)

Hi, im trying to install driver for rtl8811au and i dont know the exact steps to make the usb adapter works, i already install the headers and this driver and still not works.

zebulon commented on 2019-03-11 09:24 (UTC) (edited on 2019-03-11 09:49 (UTC) by zebulon)

@iyanmv: looks great, thanks for your work.

iyanmv commented on 2019-03-07 17:18 (UTC)

@zebulon @noraj: I've changed the pkgver() function to use the one provided in the wiki, so if in any moment they decide to use a tag upstream that will be used. Also modified pinned comment.

zebulon commented on 2019-03-06 08:20 (UTC)

@iyanmv: in your pinned comment about the possibility to use the 5.3.4 branch, the correct line to edit is 22, not 10. This is the 'source' variable which needs adjustment. The 'url' is just documentation and has no incidence on the downloaded branch.

churro commented on 2019-02-18 19:35 (UTC)

indeeed it didn't work, however I've found several repos already. and

zebulon commented on 2019-02-18 09:10 (UTC)

@churro: as jpegxguy wrote, there is no risk with trying. This driver uses dkms and uninstalling will be a clean process. That said, I think you would miss the hal files for your adapter (see the content of the hal directory in the Github sources). This repo has hal files for 8812, 8814 and 8821au. The hal files for 8822bu can only be found in the repo jpegxguy has mentioned.

jpegxguy commented on 2019-02-17 14:39 (UTC) (edited on 2019-02-17 14:39 (UTC) by jpegxguy)

@churro If you're referring to the AC1200 Dual-Band USB 3.0 Wifi Adapter (PCI ID 0bda:b812) it seems that its driver is rtl88x2bu, latest version found in this repository (follow the link in the README if a new version is ever available)

But you can try this one anyway and then uninstall if it doesn't work. It won't harm anything.

churro commented on 2019-02-17 05:45 (UTC)

Would this work with the b812?

iyanmv commented on 2019-02-14 17:09 (UTC) (edited on 2019-02-14 17:09 (UTC) by iyanmv)

@noraj versioning makes sense, I will change it during a study break. Regarding the optdepends, I agree with @zebulon, dkms is enough. Other arch based distros user's should worry about modifying accordingly the PKGBUILD to be compatible with their respective repos, but AUR is for Arch, so optdepends should reflect Arch repos.

zebulon commented on 2019-02-14 12:40 (UTC) (edited on 2019-02-14 12:45 (UTC) by zebulon)

@noraj: regarding versioning, I think this is a good point. The wiki privides some guidance there: Even better than hardcoding the version number is to use the last fallback routine pkgver() { cd "$pkgname" ( set -o pipefail git describe --long 2>/dev/null | sed 's/([^-]*-g)/r\1/;s/-/./g' || printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" ) }

On the other hand, optdepends is not required: there is already a dkms dependency, which has the linux-headers optdepends. It is unadvised and unnecessary to repeat them, since they are inherited from dkms.

noraj commented on 2019-02-14 09:48 (UTC) (edited on 2019-02-14 09:48 (UTC) by noraj)

In pkgver() what about printf '%s.r%s.g%s' '' "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" instead of printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)" ? So the DKMS module will be versioned like this rtl88xxau/ instead of rtl88xxau/r600.983ec8c.

Also what about putting the linux headers as optdeps ?

optdepends=('linux-headers: build modules against the Arch kernel'
            'linux-lts-headers: build modules against the LTS kernel'
            'linux-zen-headers: build modules against the ZEN kernel'
            'linux-hardened-headers: build modules against the HARDENED kernel')

Because those headers are required, but since different arch based distro use other linux packages or use different version we should just put them as opt so people don't forget that linux header are required.

jpegxguy commented on 2019-02-11 01:08 (UTC)

I don't know the guidelines but maybe we shouldn't specify the branch at all so that it propagates to the package if/when the default branch becomes v5.3.4 or some other branch.

jpegxguy commented on 2019-02-11 00:55 (UTC)

@iyanmv Tags are looking good

iyanmv commented on 2019-02-10 22:49 (UTC)

@jpegxguy I changed the tags. Do you think they are ok now?

@polyzen: Oh yes, thanks! I fixed that.

polyzen commented on 2019-02-10 22:38 (UTC)

This package is not actually using the v5.2.20 branch as only the URL was changed. See:

jpegxguy commented on 2019-02-10 21:00 (UTC)

I think the rtl type entries in the tags should be modified to have au appended. people who won't search using 8812au, will search using rtl8812au. Also 8812 is missing the au (second entry)

jpegxguy commented on 2019-02-01 17:43 (UTC) (edited on 2019-02-01 17:46 (UTC) by jpegxguy)

Neither changing CONFIG_DISABLE_REGD_C nor trying the other package rtl8812au-dkms-git solved the issue. Even before the aircrack days, I used the 4.x version driver with package name rtl8821au-dkms-git. Only that one worked.

iyanmv commented on 2019-02-01 07:45 (UTC) (edited on 2019-02-01 13:05 (UTC) by iyanmv)

@jpegxguy @zebulon: there is a relevant line in the Makefile file that you may try to change. Try to change CONFIG_DISABLE_REGD_C=y -> CONFIG_DISABLE_REGD_C=n

@zebulon: regarding the USB2 thing, there is also the line CONFIG_USB2_EXTERNAL_POWER = n a little bit below in the same file.

zebulon commented on 2019-02-01 05:17 (UTC)

@jpegxguy: Have you the same issue with the rtl8812au-dkms-git package (gordboy's repo)? I only have this problem with aircrack's, although they both have codebase. And what is your adapter? I will look at issues on Github and see if something similar has been already reported.

jpegxguy commented on 2019-01-31 20:32 (UTC)

@zebulon. That's exactly my issue with v5.2.20, and why I used v5.3.4. The second time, I could see my neighbors 5 Ghz network, but not mine. v5.3.4 works every time. You're thinking of reporting upstream?

zebulon commented on 2019-01-31 18:39 (UTC)

I have a strange issue. I have an rtl8812au adapter (Edimax AC1200 EW-7822UAC). When using the rtl8812au-dkms-git ( from gordboy) I can see both 2.4 and 5GHz networks. However, with your aircrack-ng, I only see the 2.4GHz networks. If I use the aircrack-ng 5.3.4 branch, on the other hand, I can see the 5GHz networks. I know I should report this issue upstream to aircrack, but if anyone has an idea, I would be glad to hear it.

zebulon commented on 2019-01-31 14:58 (UTC)

@iyanmv: ok, thanks for the info. I thought pacman would complain with a conflict but maybe this is normal behaviour to prioritise replacement then. Good it works anyhow! Another thing: my rtl8812au driver makes my adapter work in USB 2 mode, while your makes it work in USB 3 mode. That said, it sucks more power from my USB hub and makes another USB receiver on the same hub (a logitech universal for keyboard/mouse) work badly almost no range. There is nothing you can do but this is interesting. Will need to move my adapters to various ports probably...

iyanmv commented on 2019-01-31 09:24 (UTC) (edited on 2019-01-31 12:29 (UTC) by iyanmv)

Mmm... the thing is that first time I try your solution (just with the replaces array), and in my case I got the new package installed without deleting the old one. Using both replaces and conflicts arrays, I force pacman to first uninstall the old one. Does this make sense? I also saw some official packages using both arrays when there is a renaming. See, for example, this:

By the way, thanks for updating the wiki :)

zebulon commented on 2019-01-31 09:03 (UTC) (edited on 2019-01-31 09:03 (UTC) by zebulon)

I have updated the wiki page and added it to the driver list.

Another note: I do not think you should have rtl8812au-aircrack-dkms-git in both conflicts and replaces, but only in replaces. conflicts would make an upgrade for those with rtl8812au-aircrack-dkms-git fail.

iyanmv commented on 2019-01-30 17:59 (UTC)

@zebulon: Ok, thanks, just change it. Regarding the v5.3.4, in my case injection does not work, so till they fix those issues or they change to the v5.3.9 base, I will leave the old branch. I will edit my pinned comment with the instructions to try the other branch.

jpegxguy commented on 2019-01-30 14:06 (UTC) (edited on 2019-01-30 14:06 (UTC) by jpegxguy)

Alright! Time to vote for this package, people! It covers all the others nicely

zebulon commented on 2019-01-30 12:14 (UTC) (edited on 2019-01-31 08:55 (UTC) by zebulon)

Great. Just some thoughts: in the description, you wrote 88XX cards, I think it should be 88XXau (USB adapters only) since there are other 88xx non USB or with bluetooth adapters, which use different drivers. Also, you may want to add conflicts with rtl8821au-dkms-git and rtl8814au-dkms-git since this version covers all of these adapters. Finallz, for those who want to try 5.3.4, they can simply edit line 22 and check out the 5.3.4 branch. There is no sha256 sum check, thus no difficulty (not tested yet though...)

jpegxguy commented on 2019-01-30 03:41 (UTC) (edited on 2019-01-30 03:43 (UTC) by jpegxguy)

My suggestion: You should put the full names in the description or the tags (like 8812au, 8814au e.t.c.) so that this package comes up in the results. It does come up if I omit the "au", but judging from the Ubuntu forum posts and other discussions online, most people will search for it with the 8812au keyword for example. Let them see this beautiful package as well. Good work, that repo. They've really worked on this driver.

iyanmv commented on 2019-01-29 21:55 (UTC)

Hi @jpegxguy! Thanks for the feedback. Good to know that branch v5.3.4 works better for you. I'm still trying to understand the most important differences between them before making a decision to change the PKGBUILD. I will keep an eye to more comments and this issue in the repo

jpegxguy commented on 2019-01-29 21:39 (UTC) (edited on 2019-01-30 03:44 (UTC) by jpegxguy)

I must say the 5.3.4 branch works much better for me. The normal 5.2.20 has issues finding my SSID. That said, I did see a stack trace in dmesg. It might be NetworkManager's fault though. I don't know if that's generally the case or just this branch.

My device: D-Link DWA-171 rev A1.

iyanmv commented on 2019-01-29 19:59 (UTC)

@zebulon: Ok, perfect (I missed that detail in the wiki hehe). So correct me if I am wrong: I create a new package with the name rtl88xxau-aircrack-dkms-git in my case), I use replaces with this one, and then I request to merge comments of this one with the new, right?

zebulon commented on 2019-01-29 19:52 (UTC) (edited on 2019-01-29 19:53 (UTC) by zebulon)

@iyanmv: PKGBUILD rules state only lower case for names (see, so rtl88xxau-dkms-git. Now for the module name, you are free to keep 88XXau as in the original source. Thanks again for the work!

Edit: for the renaming part, you can use replaces= the old name to allow smooth transition.

iyanmv commented on 2019-01-29 19:48 (UTC)

@zebulon: Small detail: Do you suggest renaming to rtl88xxau-dkms-git or rtl88XXau-dkms-git?

iyanmv commented on 2019-01-29 19:34 (UTC)

@zebulon: I agree about the renaming thing. I will try to do it. Regarding the 5.3 vs 5.2 thing, I will need more time to try and test. And thanks for the info, I will contact him when I do that, sure.

zebulon commented on 2019-01-29 14:48 (UTC)

@iyanmv: personally this is not a problem. However user SeeLook has reported on the rtl8812au-dkms-git PKGBUILD page that he got better results with an rtl8814au adapter under 5.3.4 than 5.2 ("wakes up faster after suspend and led blinks") but of course this is up to you since I cannot test adapters other than my 8812au (and I do not use injection). You may want to contact him to see the specifics of his findings and decide from there. That said a PKGBUILD would easily be adapted to use either branch of the repository (the more important is to fix the ko module name to RTL88XX, etc.)

That said, what do you think about renaming the package to rtl88xxau-dkms-git? That would reflect the fact the driver supports several chipsets, and then we could add it as a choice in the Wifi page in the Wiki.

iyanmv commented on 2019-01-29 01:01 (UTC)

At the end, I couldn't go to sleep without giving it a try. For the moment, I will leave it in branch v5.2.20. Please, let me know if it works for you. I tried it with my Alpha AWUS036ACH and everything seems to work just fine, even the injection.

iyanmv commented on 2019-01-28 23:07 (UTC)

@zebulon: Hi! Yes, I saw you are maintaining the rtl8812au-dkms-git one. Unfortunately, injection does not work for me with that driver. Regarding the version, to be honest I still don't know. I need to understand the differences first and try them before taking a decision. Branch 5.2.20 looks more active than 5.3.4, isn't it.

I hope to have some free time tomorrow evening to try and update it ;)

zebulon commented on 2019-01-28 21:11 (UTC)

@iyanmv: thanks for taking care of this. As I wrote below, I maintain the "official" driver versions for every chipset.Do you intend to package 5.3.4 version?

iyanmv commented on 2019-01-28 11:45 (UTC)

My orphan request was accepted. I will try to update and fix the PKGBUILD in the following days.

zebulon commented on 2019-01-28 08:53 (UTC) (edited on 2019-01-28 10:52 (UTC) by zebulon)

It looks this package has not been maintained for almost a year (but let's thank the original maintainer). I am maintaining in parallel rtl8812/14/21-dkms-git packages with "official" Realtek drivers, but would like to offer the aircrack 5.3.4 which looks properly maintained on Github by the excellent aircrack-ng team. It would also offer some cutting edge features to the users of the legacy ones. Since the aircrack 5.3.4 supports many drivers, how about an rtl88xxau-dkms-git AUR package? I could adopt this package, and if I am allowed rename it and use replaces="rtl8812au-aircrack-dkms-git" to have an rtl88xxau 5.3.4 driver.

jpegxguy commented on 2019-01-17 17:53 (UTC)

This PKGBUILD is out of date in other ways as well. there are newer branches now and the module is named 88XXau.ko AFAIK for example.

erkexzcx commented on 2019-01-04 16:21 (UTC)

'make' KVER=4.20.0-arch1-1-ARCH KSRC=/lib/modules/4.20.0-arch1-1-ARCH/build... error: command failed to execute correctly :: Running post-transaction hooks... (1/2) Install DKMS modules ==> dkms install rtl8812au/r500.67e27a1 -k 4.20.0-arch1-1-ARCH Error! Build of 8812au.ko failed for: 4.20.0-arch1-1-ARCH (x86_64) Consult the make.log in the build directory /var/lib/dkms/rtl8812au/r500.67e27a1/build/ for more information.

iyanmv commented on 2018-11-30 20:36 (UTC)

Forget my last comment. Everything works fine with @alxbl suggestion. I guess a reboot was needed.

iyanmv commented on 2018-11-28 15:45 (UTC)

I could install the driver using @alxbl patch. However, I cannot inject packets. Anyone facing some problem?

alxbl commented on 2018-11-23 13:42 (UTC)

The newer versions of GCC consider the cast mentioned by elimpfor as incompatible, and the -Werror flag makes it error out. I've made a quick patch that adds -Wno-error=<...> for the relevant warning. It's a hacky workaround until whenever upstream deals with the warning the way they find appropriate. Here's the patch in case anyone else benefits from it:

diff --git a/Makefile b/Makefile
index c3057cd..89bfae9 100755
--- a/Makefile
+++ b/Makefile
@@ -3,6 +3,7 @@ EXTRA_CFLAGS += -O1
 EXTRA_CFLAGS += -Wextra
+EXTRA_CFLAGS += -Wno-error=incompatible-pointer-types
 #EXTRA_CFLAGS += -Werror
 #EXTRA_CFLAGS += -pedantic
 #EXTRA_CFLAGS += -Wshadow -Wpointer-arith -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes

I've also modified my local PKGBUILD to apply this patch automatically in case anyone is interested in that.

ncoder-2 commented on 2018-11-14 20:13 (UTC)

Seems broken on kernel 4.19.1:

/var/lib/dkms/rtl8812au/r325.5e69fe4/build/os_dep/linux/os_intfs.c:1197:22: error: initialization of ‘u16 ()(struct net_device , struct sk_buff , struct net_device , u16 ()(struct net_device , struct sk_buff , struct net_device ))’ {aka ‘short unsigned int ()(struct net_device , struct sk_buff , struct net_device , short unsigned int ()(struct net_device , struct sk_buff , struct net_device ))’} from incompatible pointer type ‘u16 ()(struct net_device , struct sk_buff , void , u16 ()(struct net_device , struct sk_buff , struct net_device ))’ {aka ‘short unsigned int ()(struct net_device , struct sk_buff , void , short unsigned int ()(struct net_device , struct sk_buff , struct net_device ))’} [-Werror=incompatible-pointer-types]
.ndo_select_queue = rtw_select_queue, ^~~~~~~~~~~~~~~~ /var/lib/dkms/rtl8812au/r325.5e69fe4/build/os_dep/linux/os_intfs.c:1197:22: note: (near initialization for ‘rtw_netdev_ops.ndo_select_queue’)

erkexzcx commented on 2018-08-19 22:15 (UTC) (edited on 2018-09-06 17:37 (UTC) by erkexzcx)

Getting random disconnections when using this driver for wifi connection with AWUS1900 alfa adapter. Use this driver instead to fix this issue: rtl8814au-dkms-git. EDIT: this aircrack driver works perfectly fine and no idea why it stopped working. Now it works fantastically and has lower ping.

erkexzcx commented on 2018-08-05 22:08 (UTC) (edited on 2018-08-05 22:31 (UTC) by erkexzcx)

Sharing is caring - this is the same, but updated PKGBUILD to support all ARM devices and RTL8814 as well: Enjoy!

fantomas commented on 2018-06-01 20:37 (UTC)

for armv7h

fantomas commented on 2018-06-01 12:52 (UTC)

is it possible to adapt for the Raspberry Pi? thanks in advance

TrackMasterSteve commented on 2018-04-21 15:24 (UTC)

Does this support rtl8814 as well as rtl8812?

ncoder-2 commented on 2018-04-08 16:58 (UTC)

Oh and one more thing, any chance you could make a package with 'make RTL8814=1' as that driver also supports the RTL8814 chipset if compiled with RTL8814=1. Thanks!

ncoder-2 commented on 2018-04-08 16:52 (UTC)

Hi! Thanks for the package! Can you add a conflicts=('rtl8812au-dkms-git' 'rtl8812au-inject-dkms-git') in your PKGBUILD?