Welcome!

Please read this important information about Spectre and Meltdown vulnerabilities.
Please read this important information about MX sources lists.

News
  • MX Linux on social media: here
  • Mepis support still here
Current releases
  • MX-17.1 Final release info here
  • antiX-17 release info here
New users
  • Please read this first, and don't forget to add system and hardware information to posts!
  • Read Forum Rules

TP-Link TL-WN822N wifi dongle on MX-17

Message
Author
User avatar
tascoast
Forum Guide
Forum Guide
Posts: 1020
Joined: Sat Aug 06, 2011 4:58 am

Re: TP-Link TL-WN822N wifi dongle on MX-17

#11 Postby tascoast » Tue Dec 12, 2017 6:09 am

sunrat wrote:Update - I just installed MX17RC1 and got this working and it initialised at boot (once at least) and works with NetworkManager this time.
Basically the same steps:
- build and install the driver with dkms
- blacklist rtl8xxxu by creating a blacklist file in /etc/modprobe.d/
- reboot
- configure with password in NM
- profit!

I'm posting from it now.
@tascoast I don't know why yours wouldn't work the same. It shows the rtl8192eu being used already. Maybe try blacklisting the other driver anyway. Or maybe it's because of the wlan2 issue mentioned above and NM is attempting to configure a different interface. Lotsa luck! Works ok once you get it working. What version of the dongle do you have, by the way? This one is V4.0 and my old reliable Atheros one is V2.

A magnifying glass tells me that I have a V4.0, according to the box sticker.
I shall experiment further once I get settled. Simply blacklisting rtl8xxxu in Network Assistant removes any wifi detection from NM, but I'll follow your approach once I study it a bit.
Cheers
Mick
Lenovo ThinkCentre A58 4GBRAM, MX-16 RC1/MX14.04/MX-15.01/antiX16(64-bit)-Aspire One D255E 1.66GHz, 512KB cache, 1GB RAM-MX-15.01/W10

sunrat
Forum Novice
Forum  Novice
Posts: 61
Joined: Mon Mar 28, 2016 9:54 pm

Re: TP-Link TL-WN822N wifi dongle on MX-17

#12 Postby sunrat » Thu Dec 21, 2017 6:27 pm

One user at Debian User Forums reported they solved this issue by disabling MAC address randomisation in NetworkManager. Just adding

Code: Select all

[device]    wifi.scan-rand-mac-address=no

to the /etc/NetworkManager/NetworkManager.conf file

http://forums.debian.net/viewtopic.php? ... 87#p661687
https://bugs.launchpad.net/ubuntu/+sour ... ug/1681513


Return to “Hardware /Configuration”

Who is online

Users browsing this forum: No registered users and 2 guests