Arch Linux User Repository

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

a patch to make it work for rpi and may be other ARM device:

--- PKGBUILD.old    2019-03-15 20:08:05.345042676 +0100
+++ PKGBUILD    2019-03-15 20:04:24.390294977 +0100
@@ -32,4 +32,10 @@
         sed -e "s/@_PKGBASE@/${_pkgbase}-dkms/" \
                         -e "s/@PKGVER@/${pkgver}/" \
                         -i "${pkgdir}"/usr/src/${_pkgbase}-${pkgver}/dkms.conf
+
+   # patch Makefile for RPI
+   sed -i '/^CONFIG_PLATFORM_I386_PC/s/y/n/' ${pkgdir}/usr/src/${_pkgbase}-${pkgver}/Makefile
+   sed -i '/^CONFIG_PLATFORM_ARM_RPI/s/n/y/' ${pkgdir}/usr/src/${_pkgbase}-${pkgver}/Makefile
+   # disable debug code with __DATE__ macro (TODO: proper fix ?)
+   sed -i '/__DATE__/s/^/\/\//' ${pkgdir}/usr/src/${_pkgbase}-${pkgver}/core/rtw_debug.c
 }

Note: I am seeing the interface of the usb wifi key marketed as DEEPOW dongle (from amazon) changing MAC address at every boot even though I have not set up anything like that in netctl, here.

I don't know if it's a hardware problem or driver problem. However, it's the same with rtl88xxau-aircrack-dkms-git driver

@zebulon I temporarily moved those files out from my /usr/src/rtl8821au-5.1.5.r78.gecd3494 directory (where pacman says they were installed) - is that what you meant? I can't tell if there's another step where they're "installed" from here, since I would expect this directory is only used for building source code, but I can't seem to find any step beyond this.

In any case, rebooting after moving those files didn't seem to affect anything. I'm connected to the network just fine, and I don't see anything suspicious in the system logs.

@jschuster: interesting. The main difference (other than the driver itself) is that I package also ifcfg-wlan0, runwpa and wlan0dhcp files. As far as I am awaree, they come from the Ubuntu world, and I am not even sure they even interfere with netctl in Arch. Could you please check what happens if you move/delete those files from your system?

The aircrack-ng version does not entirely work for me (although I have a workaround). On startup, I have a netctl profile called "home" that should bring up the network, but when I use the aircrack-ng driver, it fails with "WPA association/authentication failed for interface 'wlan0'". This driver (rtl8821au-dkms-git) does not have the same problem: the netctl profile brings up the network without any problems.

In the aircrack-ng case, I can eventually get the network up and running with the following workaround, though I don't yet know why this works: 1. sudo ip link set wlan0 up 2. sudo netctl start home (step 2 fails because it sees that the interface is already up, but the workaround doesn't work without it) 3. sudo ip link set wlan0 down 4. sudo netctl start home

For some reason that sequence of commands eventually brings the network up, so my guess is that there's something that the "ip" tool is doing to initialize my adapter that the aircrack-ng driver is not.

For what it's worth, the USB ID for my adapter is 0bda:0811. The product itself is the NET-DYN AC600 USB Wi-Fi Adpater: https://netdynwifi.com/product/ac600-usb-wi-fi-adapter/ .

I can run some tests if anyone would like more information, but unfortunately I don't have much time to investigate this myself.

@HiImTye: thanks for reporting. I think I am close to deprecating this package.

@solstice: thanks for the patch. Due to the future deprecation of this package, can you please report to rtl88xxau-aircrack-dkms-git? Also, this patch would need some work to make it modular for x86_64/arm (using $CARCH detection).

the rtl88xxau package works great for me. thanks for maintaining this old one, it was the one that (previously) was the most reliable :)

a patch to make it work for rpi and may be other ARM device:

--- PKGBUILD.old    2019-03-15 20:08:05.345042676 +0100
+++ PKGBUILD    2019-03-15 20:04:24.390294977 +0100
@@ -32,4 +32,10 @@
         sed -e "s/@_PKGBASE@/${_pkgbase}-dkms/" \
                         -e "s/@PKGVER@/${pkgver}/" \
                         -i "${pkgdir}"/usr/src/${_pkgbase}-${pkgver}/dkms.conf
+
+   # patch Makefile for RPI
+   sed -i '/^CONFIG_PLATFORM_I386_PC/s/y/n/' ${pkgdir}/usr/src/${_pkgbase}-${pkgver}/Makefile
+   sed -i '/^CONFIG_PLATFORM_ARM_RPI/s/n/y/' ${pkgdir}/usr/src/${_pkgbase}-${pkgver}/Makefile
+   # disable debug code with __DATE__ macro (TODO: proper fix ?)
+   sed -i '/__DATE__/s/^/\/\//' ${pkgdir}/usr/src/${_pkgbase}-${pkgver}/core/rtw_debug.c
 }

Note: I am seeing the interface of the usb wifi key marketed as DEEPOW dongle (from amazon) changing MAC address at every boot even though I have not set up anything like that in netctl, here.

I don't know if it's a hardware problem or driver problem. However, it's the same with rtl88xxau-aircrack-dkms-git driver

aircrack works great for me.

I have added a patch for linux kernel 5. Please try, but as explained, I am considering deprecating and recommend the aircrack-ng version (for which there is a PKGBUILD in AUR.)

I think I should deprecate this PKGBUILD. The driver has the same base than the aircrack-ng (astsam/rtl8812au) but the aircrack-ng version is much better maintained. And there is a PKGBUILD for it: https://aur.archlinux.org/packages/rtl88xxau-aircrack-dkms-git. Can I suggest that all users of this driver switch to the rtl88xxau-aircrack-dkms-git and check it works with no issue? If this is the case then I do not see any reason to maintain it.

@archixx: Thanks for the notice. Will look into it. Indeed the aircrack-ng is up to date, and thus I recommend to use the PKGBUILD available: https://aur.archlinux.org/packages/rtl88xxau-aircrack-dkms-git.