[SOLVED] How to compile device drivers for usb wireless internet adaptor TP-LINK ARCHER T9UH
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
On lsusb not listing your adapter, I thought it doesn't list it at all, but you now detailed that only the "human friendly" description is missing. This is just cosmetic and not a real issue.
Slackware, AFAIK, doesn't provide you with a tool to update the USB IDs database found in /usr/share/hwdata/usb.ids
You can do it manually from: http://www.linux-usb.org/usb-ids.html
HowTo:
Code:
cd /usr/share/hwdata/
mv usb.ids usb.ids.old
wget http://www.linux-usb.org/usb.ids
cd /
Then run lsusb again to check if the new DB contains details about your adapter.
yeah, you don't need to worry about lsusb being blank, it just means that device is not in its database so it can't print a pretty name
as I suspected and alluded to.
I should have looked it up to save some worry.
make clean
git checkout v5.2.20
make && sudo make install
alternatively, install dkms that @abga linked, and run the dkms-install.sh
mah, just peeked , that seems hard coded to rtl8812au
we can fix that if the driver works and you want to add dkms
/!\ I compiled with current against 4.4.14 kernel source
bc didn't seem to matter
( but you should probably install it anyway, it can be handy )
@Faultygaia
I had difficulties understanding what Firerat was testing in the latest posts, considering that he/she's failing to build what I suggested in #16
The positive side effect of this latest development, is that I tested the instructions I presented in #16 and can confirm they are working, module is built and can be loaded, at least on a Slackware 14.2 using the 4.4.190 kernel (only test system I had ATM).
After I built & installed DKMS from SlackBuilds, I ran the following:
Code:
/kit# uname -r
4.4.190-smp
/kit#git clone https://github.com/nazar-pc/RTL8814AU.git
/kit#cd RTL8814AU/
/kit/RTL8814AU# ./dkms-install.sh
About to run dkms install steps...
Creating symlink /var/lib/dkms/rtl8814au/4.3.21/source ->
/usr/src/rtl8814au-4.3.21
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
'make'.....................................................................................................
cleaning build area...
DKMS: build completed.
rtl8814au.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.4.190-smp/updates/dkms/
depmod.....
DKMS: install completed.
Finished running dkms install steps.
/kit/RTL8814AU# ls -al /lib/modules/4.4.190-smp/updates/dkms/
total 1332
drwxr-xr-x 2 root root 4096 Sep 23 21:36 ./
drwxr-xr-x 3 root root 4096 Sep 23 21:36 ../
-rw-r--r-- 1 root root 1355280 Sep 23 21:36 rtl8814au.ko
/kit/RTL8814AU# modinfo rtl8814au
filename: /lib/modules/4.4.190-smp/updates/dkms/rtl8814au.ko
version: v4.3.21_17997.20160531
author: Realtek Semiconductor Corp.
description: Realtek Wireless Lan Driver
license: GPL
....
/kit/RTL8814AU#modprobe rtl8814au
#dmesg:
[ 1137.823724] rtl8814au: loading out-of-tree module taints kernel.
[ 1137.833096] RTL871X: module init start
[ 1137.833109] RTL871X: rtl8814au v4.3.21_17997.20160531
[ 1137.833242] usbcore: registered new interface driver rtl8814au
[ 1137.833249] RTL871X: module init ret=0
/kit/RTL8814AU# ./dkms-remove.sh
About to run dkms removal steps...
-------- Uninstall Beginning --------
Module: rtl8814au
Version: 4.3.21
Kernel: 4.4.190-smp (i686)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
rtl8814au.ko:
- Uninstallation
- Deleting from: /lib/modules/4.4.190-smp/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 4.3.21
completely from the DKMS tree.
------------------------------
Done.
Finished running dkms removal steps.
To give an update on the situation, I tried the method with DKMS shown on post number 16 that @abga posted, it compiled fine and everything but I decided to start up wpa_supplicant to see if I could edit any settings and see if anything was working and all that was in the .conf was
"ctrl_interface=/var/run/wpa_supplicant"
"ctrl_interface_group=root"
I have been logged in as root the whole time btw.
Also I ran dmesg after that and whenever I plugged in the usb It would spit out "Driver 'rtl8814au' is already registered, aborting."
I know that this is abrupt but im not going to be able to do anymore testing until tomorrow morning,
so I will try what @firerat said in post #20 and what @abga said in post #21 then.
But thanks for the help as always!!
To give an update on the situation, I tried the method with DKMS shown on post number 16 that @abga posted, it compiled fine and everything but I decided to start up wpa_supplicant to see if I could edit any settings and see if anything was working and all that was in the .conf was
"ctrl_interface=/var/run/wpa_supplicant"
"ctrl_interface_group=root"
I have been logged in as root the whole time btw.
Also I ran dmesg after that and whenever I plugged in the usb It would spit out "Driver 'rtl8814au' is already registered, aborting."
I know that this is abrupt but im not going to be able to do anymore testing until tomorrow morning,
so I will try what @firerat said in post #20 and what @abga said in post #21 then.
But thanks for the help as always!!
My post #21 is just a confirmation (testing) for what I suggested in #16
Have you checked if you got a working wifi interface - wlan0 after loading the driver I suggested in #16 ?
Code:
/usr/sbin/iw dev
If positive, you can also do a test - tune the Wifi card to your ESSID - change "ESSID" to reflect the real one (keep the quotes)
A simple way to add your ESSID & Password to wpa_supplicant.conf you might find useful:
Code:
/usr/sbin/wpa_passphrase ESSID PASSWORD | tee -a /etc/wpa_supplicant.conf
P.S.
Do clean the system from your previous (previous to my post #16) attempts to get a working driver as Firerat suggested in the previous post. I didn't mention this because I didn't consider it necessary - I mean, it's obvious you need to clean the other drivers before you attempt installing a new one.
Last edited by abga; 09-23-2019 at 08:47 PM.
Reason: P.S.
Thanks but the make of that driver crashes with same error
Faultygaia down below got.
I thought you had a working version but no led
when I saw the v5.2.20 in the git and it compiled on 4.4.14 I assumed we were getting somewhere.
down below?
Ah, I configure for top down reading... ( oldest first )
"Previous Post" fits either way
A good habit as is use of gender natural pronouns.
I first tried ponce's driver, when I make'd it I got no errors but nothing changed on the machine so I went with Firerat's first answer with aircrack. Midway through make'ing it I got and error and it stopped, so I went with the second answer and it make'ed and install'ed perfectly.
Im current not at my house so im unable to test connecting to any wireless networks but when I do iwconfig now I get wlan0 (which I didn't get before). When I do lsusb though it still doesn't recognize the actual usb device, it just has a blank spot. Should I be worried about this? Thanks!!
when I saw the v5.2.20 in the git and it compiled on 4.4.14 I assumed we were getting somewhere.
down below?
Ah, I configure for top down reading... ( oldest first )
"Previous Post" fits either way
A good habit as is use of gender natural pronouns.
I tried the driver in the link you suggested but
make crashed with an error so I returned to the
5.2.20 driver.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.