Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
From what I can tell, the AC600 uses an MT7610U chipset, which worked with Linux back in 2016.
This is not listed in the Debian/Stretch package firmware-misc-nonfree.
According to https://askubuntu.com/questions/9722.../972334#972334 , the device is obsolete.
Has anyone else had any luck with a device driver? Recommended alternatives?
The Debian Wiki's only certified recommendation is a generation old.
I bought I bought a TP-link AC1300 couple of days ago, which (according to the documentaion) also uses the rtl8812AU driver. "make" worked without error. "make install" worked without error. "dkms install -m rtl8812AU_8821AU_linux -v 1.0" run from root worked without error. iwconfig does not report any wireless device.
??
I am running Debian Stretch, not Ubuntu. That shouldn't make any difference.
Quote:
Originally Posted by Quakeboy02
you might try the rtl8812AU driver. I have a A6100 which I think is the same as a AC600 and this driver works for me.
I am running Debian Stretch, not Ubuntu. That shouldn't make any difference.
It shouldn't make any difference. I'm running Debian on the one I installed it on. Did you run "modprobe rtl8812au? Do you have network manager installed and running? Did you follow the network manager instructions for finding the available wireless servers and connecting to yours?
root@harold:~# lsusb
Bus 003 Device 003: ID 0483:91d1 STMicroelectronics Sensor Hub
Bus 003 Device 002: ID 8087:8001 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 056a:00ec Wacom Co., Ltd
Bus 001 Device 003: ID 5986:029d Acer, Inc
Bus 001 Device 002: ID 04f3:0254 Elan Microelectronics Corp.
Bus 001 Device 006: ID 2357:0115
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@harold:~# usb-devices
[21455.523241] asix 1-2:1.0 eth0: unregister 'asix' usb-0000:00:14.0-2, ASIX AX88772B USB 2.0 Ethernet
[21521.088017] usb 1-2: new high-speed USB device number 6 using xhci_hcd
[21521.228493] usb 1-2: New USB device found, idVendor=2357, idProduct=0115
[21521.228495] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[21521.228496] usb 1-2: Product: 802.11ac NIC
[21521.228497] usb 1-2: Manufacturer: Realtek
[21521.228498] usb 1-2: SerialNumber: 123456
[22820.937552] usb 1-1: new high-speed USB device number 7 using xhci_hcd
[22821.080207] usb 1-1: New USB device found, idVendor=18a5, idProduct=0302
[22821.080209] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[22821.080210] usb 1-1: SerialNumber: 13061851009089
root@harold:# ip-link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noque state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
Network manager is running (works fine with ethernet connection)
Quote:
Originally Posted by ferrari
This is a USB device correct? If so, what is reported by the following command when the device is plugged in?
Code:
usb-devices
Also, you can observe the kernel output in terminal window
Code:
dmesg -w
(Re)plug the the device and capture the output generated.
I bought I bought a TP-link AC1300 couple of days ago, which (according to the documentaion) also uses the rtl8812AU driver. "make" worked without error. "make install" worked without error. "dkms install -m rtl8812AU_8821AU_linux -v 1.0" run from root worked without error. iwconfig does not report any wireless device.
??
It's not clear to me if you managed to complete this driver build successfully, or perhaps it didn't include your particular chipset? You should be able to determine that using 'modinfo' eg assuming module name is '8812au'...
In the git I mentioned, the driver is "rtl8812au", not "8812au". Take a look at /lib/modules/4.9.0-7-amd64 and see what's actually there. IOW, what .ko file do you have? If none, then something didn't work in the install.
I downloaded "Archer T4U v2Archer T4UH v2Archer T4UHP v1_EUUS_Linux_beta" directly from the www.tp-link.com . The "make" resulted in 8812au.ko . That is what I copied into the /lib/modules/4.9.0-7-amd64/kernel/drivers/net/wireless directory.
NOTE The previous install attempt did use the download from git-hub. IIRC that driver was named rtl8812au.ko . Same problem: driver not recognized by modprobe.
The instructions provided by tp-link for Linux in that download did not use dkms.
Quote:
Originally Posted by Quakeboy02
In the git I mentioned, the driver is "rtl8812au", not "8812au". Take a look at /lib/modules/4.9.0-7-amd64 and see what's actually there. IOW, what .ko file do you have? If none, then something didn't work in the install.
If 'usb-devices' and 'ip link' don't show that a driver is loaded and a wireless network device node is present respectively (as per post #6) then forget trying to configure a network connection. A working driver needs to be present first.
But the command "depmod" reports that the driver is present.
Quote:
Originally Posted by ferrari
If 'usb-devices' and 'ip link' don't show that a driver is loaded and a wireless network device node is present respectively (as per post #6) then forget trying to configure a network connection. A working driver needs to be present first.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.