Realtek 8812AU USB WiFi Driver for 802.11ac

[rcrsn51]

Project withdrawn.

[ardvark]

2. This module requires that wpa_supplicant switch its internal "driver" from wext to nl80211. So you need a WiFi connection program that is not locked into wext. PeasyWiFi can do this by modifying its config file.

I have built drivers for slacko_570_PAE-k3.10.32 and tahrpup_602_PAE-k3.14.20. The PETs are too large to post on the forum. If anyone wants these packages, please post a request.

Hi...

How would one go about modifying the config file? Also, I wouldn't mind having the .pet for Tahr on hand in case I run across this adapter.

Thanks!

[rcrsn51]

[deleted]

[ardvark]

When you get the adapter and are able to run some actual tests, I will upload it somewhere.

That's fine. Not sure when (or if) that would be, though. My installs of Puppy for other folks is quite rare.

Regards...

[rcrsn51]

bump

[gychang]

[Updated 2017-04-09] This is the next-generation AC600 driver for devices like the Edimax EW-7811UTC. AC600 claims to be up to 3X faster than N-mode, assuming that you have an AC600 router. In an N-mode network, I have not found this device to be any better than standard drivers like 8192cu. YMMV.

The 8812au driver is not present in any current mainstream kernel. However, there is a modified vendor driver from here that compiles in many Puppies. I have built a selection of PETs and packaged them in a single tarball.

Code: Select all

8812au_fatdog64_710_gnab-k4.4.35.pet
8812au_precise_571_gnab-k3.9.11.pet
8812au_slacko_630_gnab-k3.14.55.pet
8812au_slacko64_gnab-k4.1.11.pet
8812au_tahr_605_gnab-k3.14.56.pet
8812au_tahr64_gnab-k3.14.54.pet

Download it from here. Click the green DOWNLOAD box.

Extract the package and run the PET for your system.

Be aware that these drivers are kernel-specific. They will NOT run in alternate Puppies like no-PAE.

-----------------------------

thanks!, works great on tahrpup64!

[gychang]

changed to 6.0.6 and following the instruction does not recognize the wifi. Anyone have a similar experience?

shall I change the 3.14.79 kernel running on 6.0.6 via quickpet ?, any fix for this?

[rcrsn51]

Your WiFi driver and Puppy version MUST have matching kernels. Puppy builders have a bad habit of switching kernels without considering the implications.

Here is a method.

1. Go here for instructions on changing kernels.

2. Go here and get the Slacko64 k4.1.11 kernel. It will also work in Tahr64.

3. Change kernels.

4. Install the 8812au_slacko64_gnab-k4.1.11.pet from above.

[gychang]

Your WiFi driver and Puppy version MUST have matching kernels. Puppy builders have a bad habit of switching kernels without considering the implications.

Here is a method.

1. Go here for instructions on changing kernels.

2. Go here and get the Slacko64 k4.1.11 kernel. It will also work in Tahr64.

3. Change kernels.

4. Install the 8812au_slacko64_gnab-k4.1.11.pet from above.

thanks for detailed instructions, I noticed there is kernel_sources-4.1.11-tahr64_2.sfs in quickpup, is this not the correct one rather than Slacko64 k4.1.11 you mention in 2?

[gychang]

Your WiFi driver and Puppy version MUST have matching kernels. Puppy builders have a bad habit of switching kernels without considering the implications.

Here is a method.

1. Go here for instructions on changing kernels.

2. Go here and get the Slacko64 k4.1.11 kernel. It will also work in Tahr64.

3. Change kernels.

4. Install the 8812au_slacko64_gnab-k4.1.11.pet from above.

thanks for detailed instructions, I noticed there is kernel_sources-4.1.11-tahr64_2.sfs in quickpup, is this not the correct one rather than Slacko64 k4.1.11 you mention in 2?

Wow, thanks rcrsn51, I was able to change the kernel and install the "slacko wifi driver" to get it all working. Detailed instructions I appreciate very much.

[gychang]

Your WiFi driver and Puppy version MUST have matching kernels. Puppy builders have a bad habit of switching kernels without considering the implications.

Here is a method.

1. Go here for instructions on changing kernels.

2. Go here and get the Slacko64 k4.1.11 kernel. It will also work in Tahr64.

3. Change kernels.

4. Install the 8812au_slacko64_gnab-k4.1.11.pet from above.

thanks for detailed instructions, I noticed there is kernel_sources-4.1.11-tahr64_2.sfs in quickpup, is this not the correct one rather than Slacko64 k4.1.11 you mention in 2?

Wow, thanks rcrsn51, I was able to change the kernel and install the "slacko wifi driver" to get it all working. Detailed instructions I appreciate very much.

as a followup on this issue, I have been using this for several weeks and noticed significant problem with connecting on boot, nearly half of the time I can not seem to autoconnect, when it does connect, speed is slow... On Peppermint OS, flies without any difficulty. moderately disappointing...

[rcrsn51]

@gychang: I own an 8812au adapter but I don't use it much, so it's hard for me to comment. But I have made some changes.

1. I have built a new version of the driver from a different github project. Download it here

2. I have built it against the huge xenial64 k4.9.13 kernel. Get it from the usual place and do a kernel-switch.

3. WiFi connection works through a tool called wpa_supplicant. It has two modes - the legacy "wext" and the modern "nl80211". It looks to me like this driver prefers the latter.

I don't know how the regular Puppy connection managers select one over the other. But PeasyWiFi lets you explicitly pick nl80211 in its Config.

Code: Select all

export DRIVER=nl80211

I have attached the 64bit version of PWF below.

[Edit] I ran a few tests and this "dieder" driver looks better than the previous "gnab" version when run with nl80211.

-----------------------

[gychang]

@gychang: I own an 8812au adapter but I don't use it much, so it's hard for me to comment. But I have made some changes.

1. I have built a new version of the driver from a different github project. Download it here

2. I have built it against the huge xenial64 k4.9.13 kernel. Get it from the usual place and do a kernel-switch.

3. WiFi connection works through a tool called wpa_supplicant. It has two modes - the legacy "wext" and the modern "nl80211". It looks to me like this driver prefers the latter.

I don't know how the regular Puppy connection managers select one over the other. But PeasyWiFi lets you explicitly pick nl80211 in its Config.

Code: Select all

export DRIVER=nl80211

I have attached the 64bit version of PWF below.

[Edit] I ran a few tests and this "dieder" driver looks better than the previous "gnab" version when run with nl80211.

-----------------------

I had followed your original instructions above and have difficulty following your steps here.

2. I have built it against the huge xenial64 k4.9.13 kernel. Get it from the usual place and do a kernel-switch.

my kernel is 4.1.11 now. How do I get from the "usual place"? etc.

[gychang]

@gychang: I own an 8812au adapter but I don't use it much, so it's hard for me to comment. But I have made some changes.

1. I have built a new version of the driver from a different github project. Download it here

2. I have built it against the huge xenial64 k4.9.13 kernel. Get it from the usual place and do a kernel-switch.

3. WiFi connection works through a tool called wpa_supplicant. It has two modes - the legacy "wext" and the modern "nl80211". It looks to me like this driver prefers the latter.

I don't know how the regular Puppy connection managers select one over the other. But PeasyWiFi lets you explicitly pick nl80211 in its Config.

Code: Select all

export DRIVER=nl80211

I have attached the 64bit version of PWF below.

[Edit] I ran a few tests and this "dieder" driver looks better than the previous "gnab" version when run with nl80211.

-----------------------

I am having difficulty following 2. Can u explain for puppy novice like me? thanks

[rcrsn51]

You are going to change the kernel, just like you did above on May 5.

[gychang]

You are going to change the kernel, just like you did above on May 5.

I managed to change kernel, reboot, use the peasywifi manager and change to nl80211 and configure. Now it connects on reboot instantly much improved, but noticed the speed is little better than "n" but not "ac" protocol. (55 mbps vs 110mbps). Overall much better than before.

[rcrsn51]

Are you connecting to an AC-mode router? Are you using the 5 Ghz access point? How do you know for sure?

Are you saying that your Peppermint OS setup runs at closer to AC-mode speeds?

How are you measuring speeds?

[gychang]

Are you connecting to an AC-mode router? Are you using the 5 Ghz access point? How do you know for sure?

Are you saying that your Peppermint OS setup runs at closer to AC-mode speeds?

How are you measuring speeds?

u r right, I was connected to 2.4Ghz, put in the correct SSID for 5Ghz and now getting the AC speed. thanks. all solved.

[rcrsn51]

Excellent.

[netfrog77]

Hi rcrsn51,

Have you created a pet of this driver for Slacko64 6.3.0 ?

Thanks