Arch Linux User Repository

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:

source=('rtl88xxau::git+https://github.com/aircrack-ng/rtl8812au.git#branch=v5.3.4'

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

Important: Use ip and iw instead of ifconfig and iwconfig

Why are you forcing the branch in the source array?

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
        fi
}

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

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.

@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.

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 ;)

With commit

https://github.com/aircrack-ng/rtl8812au/commit/482064bbd91658973e28a09bcc3359e24739f3a2

the workaround for iwd are no longer needed.

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

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

[General]
UseDefaultInterface=true

@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 :)