Arch Linux User Repository

To all having an issue with this driver: please try https://aur.archlinux.org/packages/rtl88xxau-aircrack-dkms-git alternatively.

@gordboy: many thanks. I will update the PKGBUILD soon.

@zebulon

Spring clean now done.

New version of upstream repo available with fix for kernel 5.6, and some compiler warnings banished.

@rocky7x

The aircrack-ng driver in the pinned comments has other chipsets.

What about chipset 8821au? Version 5.6.4.2 works only with chipset 8812au (according to the github page).

Version 5.6.4.2 is now available. Thanks a lot to gordboy for his excellent work.

@ gordboy: thank you so much. Sorry for the delay in responding. I will work on it asap.

@zebulon

You can try out my new repo at

https://github.com/gordboy/rtl8812au-5.6.4.2

I've been using it for 5 days now and it seems fine.

Once kernel 5.4 actually arrives, I'll see about getting it into shape.

Driver update:

Realtek have issued a new driver (version 5.6.4.2) which addresses the issues discussed here with kernel 5.3.7.

I have tested it with kernel 5.3.11 and it seems to work OK with that. However it is not yet fit for kernel 5.4-rc7.

It may be that we have to say a fond farewell to driver 5.2.20.2 for all newer kernels, and move over to 5.6.4.X.

I will post here again when I have further news, and the new driver is all packaged and tidied up. In the meantime, use an older kernel, that is known to work. Toodle Pip.

Another idea to try, for people having trouble with the latest cutting-edge and untested kernels ... is simply not to run the latest cutting-edge and untested kernels.

Chasing the latest kernel for no actual good reason is guaranteed to end in tears. Far better off using a kernel that is known to work well, and stick with it.

Yet another idea to try, is to contribute constructively instead of demanding instant results.

See, what actually happens is this -

1. Realtek issue a hopelessly outdated driver
2. People (myself included) try to fix up the driver so it actually works
3. New kernels come out, which change the API
4. If broken GOTO 2
5. New compilers come out which change the compiler flags
6. If broken GOTO 2

repeat ad nauseam.

and in other threads, simultaneously

1. People complain that their dongle doesn't work
2. Other people ask for more details
3. It mostly turns out they were using the wrong driver for their chipset
4. It mostly turns out they have not installed the requisite headers
5. It mostly turns out they have several half-baked builds scattered all over

Let's not forget the 7 or 8 people who actually keep this whole ship afloat are inundated and overworked, and receive no payment.

Of course there are a couple of good citizen users, who provide proper upstream bug reports, and even ... (cue the fanfare) ... fixes to the source code.

The rest are SELECT AS APPROPRIATE Tourists/Hapless/Feckless/Inept/Malcontents.

This is purely my opinion, and I don't claim to represent anyone else.

Seriously people, please look at the etiquette article or have a bit of common sense. Firstly, there is no way to help without an error log and/or having any information about the device you are using. Secondly, we are not kernel hackers or driver maintainers. This page is for the PKGBUILD specifically. Of course, reporting problems about the driver itself is normal and useful, but do not expect us to fix issues specific to hardware itself, which should be reported upstream to Realtek or the aircrack page (from https://aur.archlinux.org/packages/rtl88xxau-aircrack-dkms-git) who maintain actively the latest version.

Neither aircrack nor this one driver work for me. I'm running linux-lts in the meantime.