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

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

indeeed it didn't work, however I've found several repos already. https://github.com/EntropicEffect/rtl8822bu and https://github.com/RinCat/RTL88x2BU-Linux-Driver

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

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

Would this work with the b812?

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

@noraj: regarding versioning, I think this is a good point. The wiki privides some guidance there: https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function. 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.

In pkgver() what about printf '%s.r%s.g%s' '5.2.20.2' "$(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/5.2.20.2.r600.983ec8c 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.

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.

@iyanmv Tags are looking good