Package Details: rtl8812au-dkms-git 5.2.9.3.r50.g0acfa00-1

Git Clone URL: https://aur.archlinux.org/rtl8812au-dkms-git.git (read-only)
Package Base: rtl8812au-dkms-git
Description: rtl8812AU chipset driver with firmware v5.2.9
Upstream URL: https://github.com/zebulon2/rtl8812au-driver-5.2.9/tree/txpower
Licenses: GPL2
Conflicts: rtl8812au
Submitter: thelinuxguy
Maintainer: zebulon (zebulon)
Last Packager: zebulon
Votes: 34
Popularity: 3.038321
First Submitted: 2015-06-08 13:04
Last Updated: 2017-11-21 11:58

Latest Comments

gordboy commented on 2017-12-11 20:34

Hello again.

It's funny how the person that originally made the 5.2.9.3 code work, is somehow a troll. Only in archland eh?

Anyways, I may re-enter the fray, not because I have any great love of abusive arch users, but because it would be selfish of me to fix the driver for kernel 4.15 for myself, and then not share it.

Another reason for reconsidering is that Realtek have removed the source code from their FTP sites. We are now on our own, and I don't see any of you guys apart from fariouche actually fixing anything.

I was not being trollish or insulting to zebulon. On the contrary, I am the guy that made this package actually work. And the reason I pulled out, was because of yet another abusive arch user. I got sick of the day-in day-out abuse from inept people blaming others for their own inadequacies.

Not to labour the point too much, with the honourable exception of fariouche below, do any of you guys actually contribute code, or is it just take, take, take?

End rant.

fariouche commented on 2017-12-11 07:32

hello, for information, my github fork based on the rtl8812au driver verdion 5.2.9.3 is working with chipset 8821a. i've taken the 5.1.5 hal. the 5.2.9 driver has a lot of changes, but only because the realtek developper most likely changed and he think that he had to change all the function namings... and also removed device detection by a stupid static compilation flag to select the suported device.

anyway, for those that uses the ap mode with 8821a are strongly encourraged to switch to 5.2.9.3 as this driver fixes the wps security hole found recently.

please not that i did not test in station mode, only ap mode with hostapd

marakasmalan commented on 2017-12-08 20:13

Hi, what is the status? I have the rtl8812au chipset on a Edimax AC600 EW-7811UAC but this driver does nor work anymore?

uname -a

Linux base 4.14.4-1-ARCH #1 SMP PREEMPT Tue Dec 5 19:10:06 UTC 2017 x86_64 GNU/Linux

Anything I need to tweak?

Rgards and thanks for the work!

capoeira commented on 2017-11-26 16:26

don't feed trolls man. even less if it is a stalker (personal troll)

Anonymous comment on 2017-11-26 15:01

Hi guys

Just to let you know I can no longer maintain the 5.2.9 code for 8812au. My github account is now deleted. And I only created this account here as a temporary measure.

The reason being an extremely abusive, and clueless user. Obviously not all arch users are like that, but it does talk to a culture of entitlement combined with ignorance.

Best Wishes

zebulon commented on 2017-11-21 11:59

I just committed the new dkms.conf with multicore build support. Thanks donvla.

zebulon commented on 2017-11-21 11:42

@donvla: thanks a lot, I'll commit it as soon as I can.
Meanwhile, I have committed patches for kernel 4.14, which is necessary for users of testing or AUR kernels (such as -ck).

donvla commented on 2017-11-14 10:04

Here is a slightly modified dkms.conf whcih respects multicore build:

PACKAGE_NAME="@PKGBASE@"
PACKAGE_VERSION="@PKGVER@"
BUILT_MODULE_NAME="8812au"
PROCS_NUM=$(nproc)
[ $PROCS_NUM -gt 16 ] && PROCS_NUM=16
MAKE="'make' -j$PROCS_NUM KVER=${kernelver} KSRC=/lib/modules/${kernelver}/build"
CLEAN="'make' clean"
DEST_MODULE_LOCATION="/kernel/drivers/net/wireless"
AUTOINSTALL="yes"
REMAKE_INITRD=no

Terence commented on 2017-11-05 10:19

@zebulon Ok cool, I had the driver from gordboy running fine too and I'll test your updated package now. I read that too about the KRACK bug, I guess that makes it fixed at a lower level then.

zebulon commented on 2017-11-04 23:23

@Terence: thanks. I have had little time to test it but it seems to work fine on my machine, so I pushed the new PKGBUILD. Please let me know if there is any issue.
They say they fixed the KRACK bug. Good but I think we were not affected due to the wpa_supplicant update.

All comments