USB internet dongle with chipset rtl8812au not working in Fedora 32/

On my Fedora 32 installation I can’t get my USB Internet dongle driver to be recognized. I was trying to go through some of the previous version troubleshooting to hopefully find and updated drive but everytime I try to make the driver after downloading the driver from github it comes up missing

/lib/modules/5.6.6-300.fc32.x86_64/build: No such file or directory.

Is there the module for that kernel number not available yet?I have tried to find a matching file through numerous searches but they lead me no where. I would really like to break the tether of the ethernet cord here. The dongle works fine on my windows side of my PC so i don’t think that is the issue.

Open to anything as I have spent the last 4 hours download different libs and updates and just can’t seem to find this last one. Tried both information for the 8812au.ko and the 88x2bu.ko drivers and ran into the same roadblock on both of them.

USB type info:

Bus 002 Device 002: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter

Thank You for any Support

Did you try this already?

Thanks.

I tried that route figuring if I could get it to the 5.3.4 version that I could update the dkms to the 5.6.6 version. It failed missing the 5.6.6 module that I had posted.

The repo also has branches for newer kernels. Did you happen to also try the 5.7. or 5.6.4.2 (i.e. default) branches?

I didn’t find other branches. Any chance you could point the clueless new guy in the right direction?

Sure.
I’m assuming you cloned the repository using the command from the HowTo? That means that you cloned the v5.3.4 branch (-b v5.3.4).

In your terminal, navigate into the rtl8812au directory & use git branch -a to have a look at the available branches (the -a means git will list both local and remote branches, instead of just local):

ce@kat ~/rtl8812au % git branch -a
* v5.3.4
  remotes/origin/EXPERIMENTAL
  remotes/origin/HEAD -> origin/v5.6.4.2
  remotes/origin/v4.3.21
  remotes/origin/v5.1.5
  remotes/origin/v5.2.20
  remotes/origin/v5.2.9
  remotes/origin/v5.3.4
  remotes/origin/v5.6.4
  remotes/origin/v5.6.4.2
  remotes/origin/v5.7.0

The * marks the branch you’re currently on, the ones without a prefix are local branches, the ones with remotes/... in front are those that the remote repository has. The HEAD entry shows you which one is the remote’s default branch (and thus also the one you would have got locally if you didn’t specify the -b v5.3.4 during cloning).

You can switch to any of those branches by using the git checkout command:

ce@kat ~/rtl8812au % git checkout v5.7.0
Branch 'v5.7.0' set up to track remote branch 'v5.7.0' from 'origin'.
Switched to a new branch 'v5.7.0'
ce@kat ~/rtl8812au % git branch -a      
  v5.3.4
* v5.7.0
  remotes/origin/EXPERIMENTAL
  remotes/origin/HEAD -> origin/v5.6.4.2
  remotes/origin/v4.3.21
  remotes/origin/v5.1.5
  remotes/origin/v5.2.20
  remotes/origin/v5.2.9
  remotes/origin/v5.3.4
  remotes/origin/v5.6.4
  remotes/origin/v5.6.4.2
  remotes/origin/v5.7.0

As you can see, we now have both the v5.3.4 and the v5.7.0 branches locally, and have switched to the v5.7.0 branch. If you check the README.md file, you’ll see that it now talks about 5.7.0, so we know this did what it was supposed to.

You can also look at the repo’s GitHub page - it shows you how many branches there are, if you click on the 9 branches you will get the same list as above.