Technoethical FLOSS Wifi Dongles not working out of the box in Debian 9.
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
In Debian 9.4 Stable, I tried the non-free 'firmware-atheros' package. Both dongles see my SSID and try to connect but never do.
I then uninstalled 'firmware-atheros' and installed the free drivers called 'open-ath9k-htc-firmware_1.3-1_all.deb' from a Trisquel archive. Again, both dongles still see my SSID and I try to connect to it but a connection never gets established.
Bus 001 Device 009: ID 0cf3:1002 Atheros Communications, Inc. TP-Link TL-WN821N v2 / TL-WN822N v1 802.11n [Atheros AR9170]
Bus 001 Device 010: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
I will post the output for (sudo cat /var/log/syslog | grep -Ei 'net|wpa|dhc') in another post. It's incredibly long. Actually it seems to output personal info such as SSID, MAC addresses, etc. Can you provide an alternate line to input?
Last edited by linustalman; 06-04-2018 at 01:50 PM.
i forgot we're talking about a usb dongle, so we'll need output of
Code:
sudo lsusb
so far i can see no errors; we need to find some, or there's nothing to troubleshoot...
maybe also
Code:
ping -c5 8.8.8.8
ping -c5 google.com
is r8188eu your device?
Code:
sudo lsusb
Code:
Bus 002 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 001 Device 005: ID 0cf3:1002 Atheros Communications, Inc. TP-Link TL-WN821N v2 / TL-WN822N v1 802.11n [Atheros AR9170]
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The r8188eu is for my 'TP-Link TL-WN725N Wireless Nano USB Adapter'. That works with the firmware-realtek package.
I can't ping as the dongle I want to get working won't connect to my SSID.
Last edited by linustalman; 06-05-2018 at 02:08 PM.
i now see that in post #1 you mention 2 usb wifi adapters.
this is confusing.
we need to concentrate on one.
and obviously i assume that all output you provide reflects the problematic behavior. is that so? please clarify.
next we need the syslog output also.
how do you try to connect? network manager? does it see the device at all, or does it simply say there's no wifi?
if it sees the device, what happens when you try to connect to your hotspot?
i now see that in post #1 you mention 2 usb wifi adapters.
this is confusing.
we need to concentrate on one.
and obviously i assume that all output you provide reflects the problematic behavior. is that so? please clarify.
next we need the syslog output also.
how do you try to connect? network manager? does it see the device at all, or does it simply say there's no wifi?
if it sees the device, what happens when you try to connect to your hotspot?
I recently bought 2 wifi dongles from Technoethical (N300 Wireless USB Adapter & N150 Mini Wireless USB Adapter). Both detect my network but fail to connect. I am trying to get the N300 to work - the N150 is not a priority right now. From what I can tell, all the problematic output was for the N300 but I can repost any relevant requirements again if you want.
The wifi dongle that works and that I've had for a long while is the 'TP-Link TL-WN725N Wireless Nano USB Adapter'.
What syslog do I show?
I use NetworkManager Applet 1.4.4.
Last edited by linustalman; 06-07-2018 at 02:48 PM.
To clarify - these output are with only the N300 attached.
Code:
lsusb
Code:
Bus 002 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 007: ID 0cf3:1002 Atheros Communications, Inc. TP-Link TL-WN821N v2 / TL-WN822N v1 802.11n [Atheros AR9170]
Bus 001 Device 003: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Code:
sudo lsusb
Code:
Bus 002 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 007: ID 0cf3:1002 Atheros Communications, Inc. TP-Link TL-WN821N v2 / TL-WN822N v1 802.11n [Atheros AR9170]
Bus 001 Device 003: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
there's currently an identical problem on bunsenlabs forums.
lacking any real errors (in syslog maybe???) the advice is to go thoroughly check out what debian wiki has to say to that, and report back.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.