Tp Link Tl-wn822n Driver

[Ling Kliment]

helloi buy a 300 Mbps High Gain Wireless USB adapter, Model TL - WN822N from TP LINK. i tray to find drivers for it and i found here -link.us/support/download/?model=TL-WN822N&version=V3 a driver for OS X 10.8 and it doesn't work. The installation doesn't go until the end. So i wood like to now if someone now's a driver for os x 10.9 (i suppose that will fix the problem).

My old tl wn821n v3 usb stick adapter started doing the same thing about thursday last week. I thought it was just getting old. It would max out at just under 4 mbs and then start to decrease til the Led light froze or went off completely. After a bit it would start up again. Any heavy downloading would make it do it again and again. It would work for bit then drop down til it lost connection then reconnect.

I tried the drivers but there is only 2012 win 8 beta drivers for it. Tried uninstalling it and reinstalling it. Tried other usb ports. I use an old pc so i got a couple of bsods i thought must be linked to it and looked at the minidump analysis. Nothing i could understand. So in the end i tried a new fresh win 10 install on another drive. The new win 10 install wouldn't recognize it even with the drivers put in. It sees it as an Atheros adapter. It seems to working. Need to try it on a heavy download. Network speed is low though. Will try an ookla speed run test..

Well you have to fart with it but my old pc is a dinosaur. So getting back to 4 mbs is good enough. have to test it on a big fast download which means finding a downloader to download something at that speed.

There is no official driver for Windows 10 laptop of 823N V3, Instead, it can be installed automatically by the system. thus it is hard toguarantee the performance and stability. We will do some troubleshooting first and check whether it will work.

I use torrents for alsorts, you can monitor download speed at the torrent speed the downloader operates on. That's how you can see it looks like it's being throttled back as it reaches certains speeds at verying times. It's not static so it happens at random times and at random speeds. Of course that could be due to the torrent and seeds but that didn't matter as so much that once it started to happen it would throttle back slowly down to zero. Once zero was reached it would freeze ( Led light stuck on and would require to be pulled and reinserted. ) or turn off completely. Most times that meant it had shut down then windows 10 would pick it back up again.

It's on my old pc in the garage but close to where the router is in the house. The walls are thin and though it's not top signal strength it's constant at 70 to 90 signal strength. Since the last reply to you it started to throttle back when i put it under load. I had an old phone so i connected that and no throttle back issues or disconnection. All i can figure is that it's an old adapter that can't handle heavy loads any more. I somehow wrecked the atheros driver for it in my win 10 and it wouldn't recognize it anymore but would still pick it up, so i was able to connect via just automatic network profile set to private. Still got throttle back and disconnection issues.

I was using win 7 til 2 weeks ago then decided to switch back to win 10. I should never have made the jump. Win 10 1903 wrecked my constant and has given me nothing but problems. Once the adapter started acting like this then switching back to win 7 copy didn't matter. I have usb 3 issues so thought it was possibly a consequence of that but i don't think so. I did come across a forum where they said to reload the motherboard drivers to help with the usb 3 problems. It didn't matter as it did the same on the other usb ports anyway.

Ok, so with a TL-WN821N v4 with Windows 10 version 1909, I've done what was explained above, asking to Windows to stop installing drivers by itself, trying to uninstall the driver using the Device Manager, disconnecting the TP LINK, ect. and it didn't work because the last Windows versions don't allow you to unistall drivers using the Device Manager. So I went directly to delete the driver in the system32 using right clic on your device on the Device Manager, Properties, Drivers and Details on drivers. I found two drivers that were used for this device the C:\Windows\System32\drivers\vwifibus.sys from Windows and the C:\Windows\System32\drivers\rtwlanu_oldIC.sys from Realtek. Modifing my access in order to delete the last driver correctly (modified the owner : "TrustInstaller" to "Yourself" and change the permissions of 'Yourself' on this file) (make sure you keep a copy on your desktop or somewhere) I managed to delete the Realtek driver in order to force install the TP-Link driver for Windows 8.1. and now, finally it's working !

However, with subsequent updates when my copy of MacOS Catalina reached around v10.15 it started throwing a message from time to time mentioning that the drivers would stop being compatible with the system soon.

I checked the same link I've provided above but no updates were available, however with MacOS BigSur v11.0.1 (20B29) the drivers are no longer compatible and the adapter does not work at all.

Does anyone have a solution and does TP-Link intend to update the drivers for this system update?

Thanks for testing that, you may need to leave the SIP disabled if you need this adapter to work, while our developers are working with the chip manufactures that we will release new driver for it in the near future, please keep an eye on the official website and wait patiently, thanks you very much.

I'm sorry, I can't help you, as I am unfamiliar with W-LAN problems and never had to deal with them.

You have to wait for someone competent to take care of your problem.

Have you already scoured the forum and Archwiki?

You should always post your specs on a wifi help request first thing. Your manufacturers model number is irrelevant as they can change the wifi chip used inside without any notice. What is always required is your wifi's chip ID,.

Only install this driver if it corresponds to the chip ID returned from the inxi command. This model from tp-link has also used the RTL8192CU chip in the past (so be sure to check and provide your chip ID). You must install the correct driver corresponding to the chip ID from the AUR.

This is not a common term that can be easily misinterpreted by a search engine. Users incapable of inputing a suggestion into a search engine and performing a rudimentary search for themselves may be suffering from overinflated expectations and an underwhelming level of self motivation.

I already provided a very large amount of information for you on my last post. Are you not capable of searching for directions yourself. If not, perhaps Garuda is not for you, as we do not believe in spoon feeding users the answer for every question. Users are expected to do some research for themselves.

I did a research before and I spent a large amount of time . That's why i asked for help , but ok . I'll try to be a less spoon feeding user next time or probably use a beginner distro again . Thanks for replying to my problem !

how to install the driver on this system?

for this equipment?

this unit works for ubuntu

debian

arch

yes, he should work everywhere

but, for some reason, when I try to install the driver using standard methods like:

To compile and install a driver from source code in Puppy you will need to have the devx .sfs and kernel sources .sfs both loaded. These are separated off to make Puppy smaller since many users do not require these development add-ons for normal running. They will need to be the correct ones that correspond to the Puppy version being used.

Puppy runs as root and does not use the "sudo" command, but otherwise the commands would probably be the same (just leave the sudo bit off the front of the lines).

AFAIK, in order to compile your system has to have the devx and kernel sources SFSes loaded. Hopefully, you've read enough before starting to know that Puppys should be run as 'Frugal installs'. As such, they employ a 'merge-file-system' with enables the use of many/several file-systems without having to install them. From the Menu: Setup>SFS-Load or File-browse to an SFS, Right-Click and select SFS-load from the popup menu. When not in use, SFSes can be (optional) unloaded. Legacy installs can't use SFSes properly. [Ask how if you insist on a Legacy Install; but you're better off starting from scratch and doing a Frugal Install].

Thanks for answers(

Everything is so complicated with your operating system (

I used the version of os - ubuntu, the most recent one downloaded from the official site

BUT! I also tried all other editions, from the official site

nowhere "the classic way of installing drivers - did not help" (

I understand that this is a lightweight system ...

But, the most basic functions "how to install drivers" should work out of the box? : (

It's just that my "windows-10" experience tells me that this should be present in "user-friendly systems"!

Not so long ago I started to study Linux, I just mastered the "correct installation of drivers with commands":

make

make install

modprobe

suddenly, some distributions don't know how to install drivers for hardware like this

This is very painful!

I would like to be able to put a driver on the hardware without having a network in the operating system itself (((

- the main thing is that you have the files necessary for installation in advance

in the case of "windows-10" - exe file

and in the case of Linux ... - "source code?"

Linux distros are all different with their own advantages and disadvantages. Puppy is special in that it is small and lightweight, but one way that has been achieved is that the development packages have been split off, but adding them back in is easy, only takes a few moments, and they can be unloaded again afterwards if you wish. The vast majority of users do not compile and install drivers from source code. A windows exe file will be a package that has been compiled from source code in windows and is ready for installation in windows. The equivalent of this in Puppy would be a .PET package of the driver, which would be a package already compiled for the specific Puppy and ready for installation with a click. With some drivers, you may find that such a package is available somewhere, or if not, sometimes Puppy community people will do the compiling of the source code for you and provide the .pet package if you post a request with links to the source code and specify the Puppy version you are running.

3a8082e126