Package Details: rtl8812au-dkms-git 5.13.6.r46.gcbe2fd6-1

Git Clone URL: https://aur.archlinux.org/rtl8812au-dkms-git.git (read-only, click to copy)
Package Base: rtl8812au-dkms-git
Description: rtl8812AU chipset driver with firmware v5.13.6
Upstream URL: https://github.com/morrownr/8812au-20210820
Licenses: GPL2
Conflicts: rtl8812au
Submitter: thelinuxguy
Maintainer: zebulon (zebulon)
Last Packager: zebulon
Votes: 76
Popularity: 0.120728
First Submitted: 2015-06-08 13:04 (UTC)
Last Updated: 2024-05-23 13:07 (UTC)

Dependencies (3)

Required by (0)

Sources (2)

Pinned Comments

zebulon commented on 2019-10-01 06:19 (UTC)

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

Latest Comments

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

zebulon commented on 2018-04-11 08:30 (UTC)

@accensi: my first attempt was not a success. I changed the module name in dkms.conf only, but then there was no module to load. I may need to do further changes in the Makefile themselves. I have to be careful not to break this.

zebulon commented on 2018-04-10 08:25 (UTC)

@accensi: this is a good suggestion, I will do this for the other rtl drivers too.

accensi commented on 2018-04-10 00:58 (UTC)

dkms.conf sets module name as BUILT_MODULE_NAME="8812au"

Not a significant point, but you could change that to 'rtl8812au' just to be like other rtl modules and make it easier to find or grep in modules tree.

Thanks

zebulon commented on 2018-04-03 08:27 (UTC)

Just pushed a minor revision: bc is now a depends.

<deleted-account> commented on 2018-03-25 10:57 (UTC)

The dkms module fails to build during a kernel update if bc (makedepends) is not installed, please move that to depends

nikita2206 commented on 2018-02-24 11:04 (UTC) (edited on 2018-02-24 11:12 (UTC) by nikita2206)

Hey, I'm having an odd situation after kernel upgrade. Now that I'm on 4.15.5-1, I can't build this driver. The error I get is here: https://gist.github.com/nikita2206/47af51eacb937f4993a142f425329b67

I obviously have tried installing libelf but that has no effect at all (the error remains the same), plus it was already installed anyway.

Is there something obvious that I miss? That CONFIG_UNWINDER_ORC issue seems to be not very googleable, a few people who had a similar problem seem to have either ignored it or solved it by installing libelf-dev.

I've tried restarting/updating my machine, removing-reinstalling rtl8812au-dkms-git package, to no avail.

EDIT: apparently, reinstalling base-devel fixed it. I may have had a slight disk failure recently, I guess it's not so slight after all...

capoeira commented on 2018-02-23 18:37 (UTC) (edited on 2018-02-23 18:37 (UTC) by capoeira)

@gordboy

wow. 4.13? even LTS is 4.14 allready. doubt that only beginners are using 4.14 and 4.15. anyways. 5Ghz is working fine now that I chose a UNII-1 channel in my router. that is on 4.14 (LTS) and 4.15. I'm using connman btw. regarding analysing the channels: I use LinSSID. It will show a nice graph of the used channels. But since it seams that I am the only one using 5Ghz here, I should be fine with any channel.

gordboy commented on 2018-02-20 19:18 (UTC)

@capoeira

A few notes and observations.

First off, kernel 4.15 is very new and not all userland apps and services have been updated to be in sync with the new crda/regdomain/cfg80211 regime. In particular, network-manager is known to be in flux.

I supplied files in the regdb folder for those bold adventurers who wish to experiment with the new 4.15 kernel. The instructions are at the bottom of the page:

https://github.com/zebulon2/rtl8812au-driver-5.2.20

which is a direct clone of my git repo at:

https://github.com/gordboy/rtl8812au

In order to use kernel 4.15 you need the proper regdb files. Either from your distro, or from the repos above.

Second of all, probably the best way to see which wireless APs are visible is "wavemon". It is very robust and has few dependencies. Desktop applets are liable to lag behind kernel innovations, and give misleading results.

What worked for me was "wicd", in terms of desktop stuff. "network-manager" still has issues with kernel 4.15.

But what worked even better for me was not using kernel 4.15, and going back to 4.13.

Until everything is in sync, blindly upgrading to the latest shiny new kernel, is a mistake many hapless newcomers make.