Arch Linux User Repository

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

@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:

https://wikidevi.com/wiki/Special:Ask?title=Special%3AAsk&q=%5B%5BChip1+model::RTL8812AU%5D%5D&po=%3FInterface%0D%0A%3FForm+factor=FF%0D%0A%3FInterface+connector+type=USB+conn.%0D%0A%3FFCC+ID%0D%0A%3FManuf%0D%0A%3FManuf+product+model=Manuf.+mdl%0D%0A%3FVendor+ID%0D%0A%3FDevice+ID%0D%0A%3FChip1+model%0D%0A%3FSupported+802dot11+protocols=PHY+modes%0D%0A%3FMIMO+config%0D%0A%3FOUI%0D%0A%3FEstimated+year+of+release=Est.+year&eq=yes&p%5Bformat%5D=broadtable&order%5B0%5D=ASC&sort_num=&order_num=ASC&p%5Blimit%5D=500&p%5Boffset%5D=&p%5Blink%5D=all&p%5Bsort%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bsearchlabel%5D=%E2%80%A6+further+results&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable

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.

Thanks Gordboy, I just incorporated the changes. @HarD: please reinstall the driver using the same PKGBUILD.

@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.

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.

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.

@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?

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.

@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.