Well, with linux 4.17.2-1 this driver compiles, it sees the AP, but no way I can make it connect. It did work with the 4.16. kernels. (BTW. I got the Asus USB-AC56 adapter.) Does 4.17. kernels work for others with this driver?
Search Criteria
Package Details: rtl8812au-dkms-git 5.13.6.r46.gcbe2fd6-1
Package Actions
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.001979 |
First Submitted: | 2015-06-08 13:04 (UTC) |
Last Updated: | 2024-05-23 13:07 (UTC) |
Latest Comments
« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 32 Next › Last »
mokkurkalve commented on 2018-06-17 23:44 (UTC)
aufkrawall commented on 2018-06-02 14:41 (UTC)
Would it be possible that you create an AUR package also for this driver? https://github.com/whitebatman2/rtl8821CU
zebulon commented on 2018-05-16 05:19 (UTC)
@gordboy: not at all, many thanks for keeping it up to date. I have now pushed your update to my repository.
gordboy commented on 2018-05-15 23:48 (UTC) (edited on 2018-05-15 23:50 (UTC) by gordboy)
@zebulon
Sorry to be a pest but someone sent me a couple of extra USB IDs, which I added to my github repo. You might want to pull in those changes too, just for completeness.
It's a bit like buses, you wait for ages and then 2 or 3 come at once ... :)
They actually sent a spreadsheet with all known IDs so I carefully checked it and added the missing ones, in (hex) numerical order to make it easy to find and add new IDs.
The list is originally from here:
Also, Realtek have issued a new revision 5.2.20.1 but it has no new features for us (it adds more android support). So until they come up with something shiny and new, I am going to stick with the trusty 5.2.20.
zebulon commented on 2018-05-14 12:57 (UTC)
Thanks Gordboy, I just incorporated the changes. @HarD: please reinstall the driver using the same PKGBUILD.
gordboy commented on 2018-05-14 11:01 (UTC) (edited on 2018-05-14 11:03 (UTC) by gordboy)
@HarD
Added a couple of new USB IDs to the master source, including yours. Obviously I corrected your minor mistake of
/ Tenda - U12 /
instead of the correct
/* Tenda - U12 */
@zebulon
Please incorporate the new changes.
HarD commented on 2018-05-01 08:13 (UTC)
Hi, could you please add {USB_DEVICE(0x2604, 0x0012), .driver_info = RTL8812}, / Tenda - U12 / to usb_intf.c
for support this device. Thanks. It work i compiled.
gordboy commented on 2018-04-18 13:38 (UTC)
Not really. Modprobe aliases is for legacy namespaces, for the most part, as I understand it.
The only way I can think of is to change the source Makefile & dkms.conf, as described below.
But if you find another viable way, I'd like to hear it.
zebulon commented on 2018-04-14 17:24 (UTC)
@gordboy: Thank you very much for your input and advice. Like you I think that changing the name may bring more issues than advantages, so let's think about it further. Ideally we would like to name modules without changing the original code. Is it possible to create aliases with modprobe.conf?
gordboy commented on 2018-04-12 13:09 (UTC) (edited on 2018-04-12 13:16 (UTC) by gordboy)
I would not recommend changing the module name, as only the in-tree kernel modules have the rtl prefix, but if you really, really want to create problems later, for no good reason ...
$ diff Makefile ../rtl8812au/Makefile
369c369
< MODULE_NAME = rtl8812au
---
> MODULE_NAME = 8812au
391,393c391,393
< hal/$(RTL871X)/$(HCI_NAME)/$(MODULE_NAME)_led.o \
< hal/$(RTL871X)/$(HCI_NAME)/$(MODULE_NAME)_xmit.o \
< hal/$(RTL871X)/$(HCI_NAME)/$(MODULE_NAME)_recv.o
---
> hal/$(RTL871X)/$(HCI_NAME)/rtl$(MODULE_NAME)_led.o \
> hal/$(RTL871X)/$(HCI_NAME)/rtl$(MODULE_NAME)_xmit.o \
> hal/$(RTL871X)/$(HCI_NAME)/rtl$(MODULE_NAME)_recv.o
Needless to say I will not be making those changes any time soon. There is no real requirement to 'find all rtl drivers', as they are loaded on demand in any case.
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.