Package Details: rtl88xxau-aircrack-dkms-git r1298.b44d288-1

Git Clone URL: https://aur.archlinux.org/rtl88xxau-aircrack-dkms-git.git (read-only, click to copy)
Package Base: rtl88xxau-aircrack-dkms-git
Description: Aircrack-ng kernel module for Realtek 88XXau (USB adapters only) network cards (8811au, 8812au and 8821au chipsets) with monitor mode and injection support
Upstream URL: https://github.com/aircrack-ng/rtl8812au
Keywords: 8811au 8812au 8821au aircrack dkms driver injection rtl8811au rtl8812au rtl8821au rtl88xx wireless
Licenses: GPL-2.0-only
Conflicts: rtl8812au-aircrack-dkms-git, rtl8812au-dkms-git, rtl8812au-inject-dkms-git, rtl8814au-dkms-git, rtl8821au-dkms-git
Submitter: iyanmv
Maintainer: iyanmv
Last Packager: iyanmv
Votes: 45
Popularity: 0.014379
First Submitted: 2019-01-29 20:43 (UTC)
Last Updated: 2024-05-21 09:00 (UTC)

Dependencies (2)

Required by (0)

Sources (2)

Pinned Comments

iyanmv commented on 2020-01-10 16:02 (UTC)

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

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 22 Next › Last »

Martinsos commented on 2019-10-15 20:32 (UTC)

I am trying to get the alfa-awus036ach wifi adapter/dongle to work, which uses 8812 chipset. I tried using rtl8812au-dkms-git, and got it installed and loaded, but could not get dongle to show via ip link. I then arrived here, but can not get the package installed, I get error message:

Error! Bad return status for module build on kernel: 5.3.6-arch1-1-ARCH (x86_64) Consult /var/lib/dkms/rtl88xxau/r61.1c72e11/build/make.log for more information.

I took a look at make.log, and there are some compiler warnings, notably:

cc1: some warnings being treated as errors make[2]: [scripts/Makefile.build:280: /var/lib/dkms/rtl88xxau/r61.1c72e11/build/os_dep/linux/os_intfs.o] Error 1 In file included from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/include/drv_types.h:35, from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/os_dep/linux/mlme_linux.c:24: /var/lib/dkms/rtl88xxau/r61.1c72e11/build/include/wifi.h:1009: warning: "IEEE80211_MAX_AMPDU_BUF" redefined 1009 | #define IEEE80211_MAX_AMPDU_BUF 0x40 | In file included from ./include/net/cfg80211.h:21, from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/include/osdep_service_linux.h:94, from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/include/osdep_service.h:41, from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/include/drv_types.h:32, from /var/lib/dkms/rtl88xxau/r61.1c72e11/build/os_dep/linux/mlme_linux.c:24: ./include/linux/ieee80211.h:1441: note: this is the location of the previous definition 1441 | #define IEEE80211_MAX_AMPDU_BUF 0x100 | make[1]: [Makefile:1626: module/var/lib/dkms/rtl88xxau/r61.1c72e11/build] Error 2 make[1]: Leaving directory '/usr/lib/modules/5.3.6-arch1-1-ARCH/build' make: *** [Makefile:1264: modules] Error 2

zebulon commented on 2019-10-15 09:30 (UTC) (edited on 2019-10-15 09:36 (UTC) by zebulon)

@iyanmv: just to precise, if you use a helper to reinstall, it may then trigger the download of the latest Git update again (if the PKGBUILD points to the latest sources like this one, and not a specific snapshot). Just be sure that your helper cache is empty (using e.g. yay -Scc). On the other hand the dkms package does not redownload any sources, they are statically installed by the PKGBUILD.

iyanmv commented on 2019-10-15 06:32 (UTC)

@zebulon exactly! This is a cvs PKGBUILD, so you won't receive any updates if you use any helper (such as yay). To get the last changes from upstream you should run makepkg. I will increase pkgver/pkgrel if there are some changes on the PKGBUILD itself according to VCS guidelines.

zebulon commented on 2019-10-15 06:27 (UTC)

Apologies for stating the obvious, but had this case before as a maintainer. Can everyone having issues with 5.3.1 make sure they have updated the sources the package uses? DKMS does not that, it only recompiles using the installed sources, it does not re-download the Github sources. To do so you can simply force a reinstalling of this package, which will indeed download teh Git sources again. Of course if your adapter does not work, you may do so by reinstalling an older kernel or try an alternate adapter.

mokkurkalve commented on 2019-10-14 12:20 (UTC)

My adapter Asus USB-AC56 (rtl8812au) seems to work fine here & now with kernel linux 5.3.5.arch1-1. What is curious is that I had to set Management Frame Protection (802.11w) from "supported" to "disabled" on the AP before I could associate adapter with AP. (And it was set to "supported", not "mandatory".) Anybody understands this? (The AP is Asus RT-AC68U with asuswrt-merlin 384.13 firmware.)

Nudin commented on 2019-10-12 21:18 (UTC)

Used this without problems until to the upgrade to kernel 5.3, after that it didn't got an interface, upgraded to newest version now I do see the interface but still get no scan results. All other drivers don't work as well…

Gatenkaas commented on 2019-10-07 10:25 (UTC)

Driver had some recent updates and works again for me now, thanks. (TP-Link T9UH v1)

iyanmv commented on 2019-10-01 19:41 (UTC)

@mrpanda so probably it's an issue with recent kernels. Have a look at this open issue upstream, subscribe to it just in case someone figure it out, and wwait till they fix it (kernel or driver). I'm sorry but I can't help here, I just maintain the PKGBUILD.

mrpanda commented on 2019-10-01 17:39 (UTC)

@iyanmv Yes it has compatible chipset. My point was that I was using this driver till kernel 5.3.1 update so I was expected to see some error during installation that's it.

iyanmv commented on 2019-10-01 06:43 (UTC)

@mrpanda why should it work this driver for you or any others from AUR? Are you sure your Qoltec uses a compatible chipset? Of course, you will be able to install any of them, but that's not the point, right?