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.019134
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 .. 11 12 13 14 15 16 17 18 19 20 21 22 Next › Last »

jpegxguy commented on 2019-04-07 16:03 (UTC)

@matthjes Try using branch 5.3.4 as well. You can do this by changing #branch=v5.2.20 to #branch=v5.3.4 in the sources matrix of the PKGBUILD

That said, it does sound like upstream issue. You'll get better help here https://github.com/aircrack-ng/rtl8812au/issues

matthjes commented on 2019-04-07 15:33 (UTC)

I have the following problem: I can install the driver without problems, my USB wifi adapter gets recognized and I can establish a connection. However, after some minutes the adapter disappears. With dmesg I can see the following enries:

WARN rtw_halmac_poweron: Power state abnormal, try to recover...OK ERROR _halmac_reg_write_16: I/O FAIL! ERROR [HALMAC][ERR]bcn valid!! [17589.156758] RTW: ERROR [HALMAC][ERR]dl rsvd page!! [17589.156758] RTW: ERROR [HALMAC][ERR]send fw pkt!! [17589.659026] RTW: ERROR download_fw: download firmware FAIL! status=0x66

Here is the output: https://drive.google.com/open?id=1H4idVZTbaOkAEMWgPfNTE0bES4ZGcR_O

jpegxguy commented on 2019-04-04 21:32 (UTC)

@pollito if you use the package you'll get updates. If you install with the method from the git repo you won't.

pollito commented on 2019-04-04 20:31 (UTC) (edited on 2019-04-04 20:59 (UTC) by pollito)

@zebulon Yes i already install the dkms and kernel headers, But whats the name of the module to modprobe? Thank... My wireless adapter is (rtl8811au). Update: nevermind i install from source and works ;)

jpegxguy commented on 2019-04-04 18:05 (UTC)

@iyanmv it builds fine on aarch64 as far as I remember. I used it in my board. I guess it's fine if your do the $CARCH thing. I don't know if we need the options set.

iyanmv commented on 2019-04-04 15:23 (UTC)

I've change ARCH from any to x86_64. @zebulon I'll have a look at what you say about using $CARCH because I also have no experience.

jpegxguy commented on 2019-04-04 15:03 (UTC)

@zebulon https://github.com/armbian/build/issues/1275

zebulon commented on 2019-04-04 14:15 (UTC)

@jpegxguy: no idea, I have no arm device to check. I am only the messenger and would only advise those who need support to report further here.

jpegxguy commented on 2019-04-04 12:13 (UTC)

@zebulon I think Armbian uses the aircrack git without the rPI config option. Does this fail to build under arm?

zebulon commented on 2019-04-04 08:49 (UTC) (edited on 2019-04-04 08:52 (UTC) by zebulon)

@iyanmv: as commented by solstice in https://aur.archlinux.org/packages/rtl8821au-dkms-git/ (see pinned comment), this PKGBUILD actually only works for x86_64, due to the fact that Makefile in the repository has these presets:

CONFIG_PLATFORM_I386_PC = y

CONFIG_PLATFORM_ARM_RPI = n

CONFIG_PLATFORM_ARM64_RPI = n

Hence, we should have arch=('x86_64') and not 'any' in the PKGBUILD. That said, it is possible to make it modular using $CARCH detection during build, but I have no experience using it.