init: failsafe main process (902) killed by TERM signal It produces a very long output, the log of the Linux kernel, but at the end it'll have some lines from ath9k_htc. Does the driver appear in inxi -N output after loading it with sudo modprobe ath9k_htc? Network: Card: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169ĪlbertP wrote:That's right, at least the ath9k_htc driver is present at you if it doesn't show an error. Network: Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169Ĭard-2: Atheros TP-Link TL-WN821N v3 802.11n 'Windows Wireless Drivers' is the same as ~ $ lsusbīus 001 Device 007: ID 0cf3:7015 Atheros Communications, Inc.

I am sure we can get it working without needing the Windows driver. TP-Link TL-WN821N v3 802.11n ĪlbertP wrote:Please uninstall the driver, reboot, and run lsusb again. Multi Flash Readerīus 005 Device 002: ID 03f0:4911 Hewlett-Packard PSC 2350īus 001 Device 006: ID 03f0:5907 Hewlett-PackardĪlbertP wrote:Was the TL-WN822N dongle plugged in when running lsusb? I only see a Ralink wifi chip, which isn't a TL-WN822N as it doesn't even support 802.11n or 300Mbps.īus 001 Device 004: ID 0cf3:7015 Atheros Communications, Inc. QuickCam 3000 Pro īus 002 Device 002: ID 058f:6366 Alcor Micro Corp. HighSpeed Hubīus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 001 Device 004: ID 148f:2573 Ralink Technology, Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubīus 001 Device 002: ID 0409:0058 NEC Corp.

Wn822n v2