1

I'm using archer T2U v3 in my 14.04 and 16.04 system flawlessly as the driver was directly provided by TP-Link from their website https://www.tp-link.com/en/support/download/archer-t2u/#Driver (Kernel version 2.6.18~5.0) enter image description here According to their PDF link https://static.tp-link.com/2018/201812/20181207/Installation%20Guide%20for%20Linux.pdf I just had to use make command to compile their driver and load it by sudo insmod 88x2bu.ko.

Recently I upgraded my system and found that direct make command don't work from Ubuntu 18.04 onward as it says make should be installed first.

So I researched and have already gone through these links like TP-Link AC600 Archer T2U Nano driver for Ubuntu 18.04 or Need rtl8814au driver for kernel 5.3 on Ubuntu 19.10 where I'll have to execute these commands

sudo apt install git dkms 
git clone https://github.com/aircrack-ng/rtl8812au.git 
cd rtl8812au 
sudo make dkms_install

but there is a problem as I cannot access internet directly even by usb tethering due to some problem so my question is can I some how install those packages like dkms git build-essential from another working machine to this machine? Can I install those packages in offline mode?

Thanks in advance

A. Bhowmick
  • 29

1 Answers1

7

I did this a few years ago. It's an iterative process. Requirements: A USB key; A working Ubuntu system, (call it hq), and the target system (tgt). You can use a non-Ubuntu hq, but downloading the .deb files to the USB key is up to you.

  1. On hq, use apt-get --download-only install on your list of packages.
  2. On hq copy the .deb files you downloaded in Step 1 to the USB key.
  3. sudo eject the USB key, and move it to tgt.
  4. On tgt, cd to the USB key, and sudo dpkg -i *.deb 2>err.log to try to install the packages. Some (many, all) may fail due to "dependencies". The error messages will be saved in err.log.
  5. On tgt, cd back to $HOME, sudo eject the USB key, and move it back to hq.
  6. On hq, inspect err.log, extract the package names, add them to your list of packages, and go back to Step 1.
  7. Eventually, 3 or 4 iterations, err.log will have no errors, and you are done! After 10+ iterations, with continuing errors, you have entered "dependency hell", and must rethink/redesign your process.

When program/Package A needs to use Program/Package B for something, A is dependent on B. These "dependencies" are what the above is resolving.

waltinator
  • 37,856