View original (French)

Wi-Fi Card Detection Issue TL-WN722N

PIXLDealer Posted messages 34 Status Member -  
PIXLDealer Posted messages 34 Status Member -
Hello everyone,

So I'm going to explain my current problem.

I have a Raspberry Pi 2 and since it doesn't have Wi-Fi, I bought a TL-WL722N Wi-Fi card.
However, I thought it would be a simple plug & play, but no. It is not detected, the LED does not light up. I tried changing the port, but it doesn't care, it won't turn on. At first, I thought it was a design error, but it works perfectly fine once the drivers are installed on my two PCs running Windows 10.
I then tried to install the drivers from the TP-LINK site but once downloaded and unzipped, I don't know what to do with them... It is also not detected on my other computer running Kali Linux.

After searching extensively on the Internet, I found no solution...

Here's what my RPi displays after an lsusb (with the card plugged in):

pi@raspberrypi:~ $ lsusb

Bus 001 Device 005: ID 2357:010c
Bus 001 Device 004: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Then without the card:

pi@raspberrypi:~ $ lsusb

Bus 001 Device 004: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

For more info, I did an ifconfig with and without the card, and the result is the same:

pi@raspberrypi:~ $ ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:f8:ea:b5
inet addr:192.168.1.54 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::98fb:9f38:153f:6013/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9944 errors:0 dropped:0 overruns:0 frame:0
TX packets:707 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:465282 (454.3 KiB) TX bytes:94762 (92.5 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:200 errors:0 dropped:0 overruns:0 frame:0
TX packets:200 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:16656 (16.2 KiB) TX bytes:16656 (16.2 KiB)

To be sure it wasn't detected, I ran an "ifconfig wlan0 up" and the command returned this:

pi@raspberrypi:~ $ ifconfig wlan0 up
wlan0: ERROR while getting interface flags: No such device

I tested with another Wi-Fi card which returned this:

pi@raspberrypi:~ $ lsusb
Bus 001 Device 008: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 007: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@raspberrypi:~ $ ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:f8:ea:b5
inet addr:192.168.1.54 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::98fb:9f38:153f:6013/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27264 errors:0 dropped:0 overruns:0 frame:0
TX packets:1945 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1280875 (1.2 MiB) TX bytes:253303 (247.3 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:200 errors:0 dropped:0 overruns:0 frame:0
TX packets:200 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:16656 (16.2 KiB) TX bytes:16656 (16.2 KiB)

wlan0 Link encap:Ethernet HWaddr 74:da:38:6a:f8:fe
inet6 addr: fe80::7b11:c8f8:26c7:929/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

This shows that my RPi works perfectly with other Wi-Fi cards, but I don't understand why it doesn't work with my TP-LINK.

Please help me find out how to install these drivers and get this card working! :)

Thank you for your help,

4 answers

  1.
    zipe31 Posted messages 34620 Registration date   Status Contributor Last intervention   6 502
     
    Hello,

    First, try to install the package firmware-atheros : 
    sudo aptitude update
    sudo aptitude install firmware-atheros

    Once installed, reboot your Raspberry (dongle connected) and test (lsub, ifconfig).

    --
    _______________________________ ☯ Zen my nuggets ☮ ______________________________
    Do something for the environment, close your windows and adopt a penguin… 🐧
    0
    1. PIXLDealer Posted messages 34 Status Member 11
       
      The package was already installed, no results even after the reboot...
      But I think it's normal, the drivers need to be installed; on my Windows computer, the dongle was not recognized until I installed the drivers with the installation CD.
      The commands 
      lsusb
      and 
      ifconfig
      returned the same result 

      pi@raspberrypi:~ $ lsusb
      Bus 001 Device 005: ID 2357:010c
      Bus 001 Device 004: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
      Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
      Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
      Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

       pi@raspberrypi:~ $ ifconfig
      eth0 Link encap:Ethernet HWaddr b8:27:eb:f8:ea:b5
       inet addr:192.168.1.54 Bcast:192.168.1.255 Mask:255.255.255.0
       inet6 addr: fe80::98fb:9f38:153f:6013/64 Scope:Link
       UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
       RX packets:631 errors:0 dropped:0 overruns:0 frame:0
       TX packets:99 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:1000
       RX bytes:33655 (32.8 KiB) TX bytes:15978 (15.6 KiB)

      lo Link encap:Local Loopback
       inet addr:127.0.0.1 Mask:255.0.0.0
       inet6 addr: ::1/128 Scope:Host
       UP LOOPBACK RUNNING MTU:65536 Metric:1
       RX packets:200 errors:0 dropped:0 overruns:0 frame:0
       TX packets:200 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:1
       RX bytes:16656 (16.2 KiB) TX bytes:16656 (16.2 KiB)
      0
    2. zipe31 Posted messages 34620 Registration date   Status Contributor Last intervention   6 502 > PIXLDealer Posted messages 34 Status Member
       
      Unplug your key, wait a few seconds, then plug it back in and show the result of the command 
      dmesg | tail -20
      .
      0
    3. PIXLDealer Posted messages 34 Status Member 11
       
      Here it is: 
       
      pi@raspberrypi:~ $ dmesg | tail -20
      [ 15.103336] Adding 102396k swap on /var/swap. Priority:-1 extents:4 across:1 92508k SSFS
      [ 16.699380] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
      [ 16.703663] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E 1
      [ 17.489329] random: nonblocking pool is initialized
      [ 27.088824] Bluetooth: Core ver 2.21
      [ 27.088975] NET: Registered protocol family 31
      [ 27.088992] Bluetooth: HCI device and connection manager initialized
      [ 27.089034] Bluetooth: HCI socket layer initialized
      [ 27.089057] Bluetooth: L2CAP socket layer initialized
      [ 27.089108] Bluetooth: SCO socket layer initialized
      [ 27.168303] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
      [ 27.168350] Bluetooth: BNEP filters: protocol multicast
      [ 27.168398] Bluetooth: BNEP socket layer initialized
      [ 3106.147411] usb 1-1.5: USB disconnect, device number 5
      [ 3129.680623] usb 1-1.5: new high-speed USB device number 6 using dwc_otg
      [ 3129.781696] usb 1-1.5: New USB device found, idVendor=2357, idProduct=010c
      [ 3129.781728] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber =3
      [ 3129.781745] usb 1-1.5: Product: 802.11n NIC
      [ 3129.781761] usb 1-1.5: Manufacturer: Realtek
      [ 3129.781776] usb 1-1.5: SerialNumber: 00E04C0001
      0
    4. zipe31 Posted messages 34620 Registration date   Status Contributor Last intervention   6 502 > PIXLDealer Posted messages 34 Status Member
        
      [ 3129.680623] usb 1-1.5: nouvel appareil USB haute vitesse numéro 6 utilisant dwc_otg
      [ 3129.781696] usb 1-1.5: Nouvel appareil USB trouvé, idVendor=2357, idProduct=010c
      [ 3129.781728] usb 1-1.5: Nouvelles chaînes d'appareil USB : Mfr=1, Product=2, SerialNumber=3
      [ 3129.781745] usb 1-1.5: Produit: 802.11n NIC
      [ 3129.781761] usb 1-1.5: Fabricant: Realtek
      [ 3129.781776] usb 1-1.5: Numéro de série : 00E04C0001

      The key is recognized, that's already something.

      In the meantime, I found this.
      To test...
      0
    5. PIXLDealer Posted messages 34 Status Member 11 > zipe31 Posted messages 34620 Registration date   Status Contributor Last intervention  
       
      Thank you for your help, it's already a step forward.
      However, I don't know how to install it. I launched the script 
      sudo ./installer
      while being in the right directory, but it returns (I switched to super user thinking that it would be easier regarding permissions) 
       
      root@raspberrypi:/tlwn722n-linux-install# ./install.sh

      Installing firmware...

      Changing to directory "compat-drivers-source"...
      Trying to select the ath9k_htc driver to be compiled...
      Processing new driver-select request...
      Backing up makefile: Makefile.bk
      Backup exists: Makefile.bk
      Backup exists: Makefile.bk
      Backup exists: Makefile.bk
      Backup exists: Makefile.bk
      Backing up makefile: drivers/net/wireless/Makefile.bk
      Backing up makefile: drivers/net/wireless/ath/Makefile.bk
      Backing up makefile: net/wireless/Makefile.bk
      Backing up makefile: drivers/ssb/Makefile.bk
      Backing up makefile: drivers/bcma/Makefile.bk
      Backing up makefile: drivers/misc/eeprom/Makefile.bk
      Backup exists: Makefile.bk
      Compiling modules...
      ./scripts/gen-compat-autoconf.sh /tlwn722n-linux-install/compat-drivers-source/.config /tlwn722n-linux-install/compat-drivers-source/config.mk > include/linux/compat_autoconf.h
      make -C /lib/modules/4.4.50-v7+/build M=/tlwn722n-linux-install/compat-drivers-source modules
      make[1]: *** /lib/modules/4.4.50-v7+/build: No such file or directory. Stop.
      Makefile:90: recipe for target 'modules' failed
      make: *** [modules] Error 2
      There was a problem compiling the package.


      I downloaded the package with <code> git clone https://github.com/ebirbe/tlwn722n-linux-install


      What do you think?
      0
  2. UnGnU Posted messages 1468 Status Contributor 158
     
    Hi,

    To test: http://barntek.net/simplemachinesforum/index.php?topic=190.0

    Adding the repositories is probably not necessary. Just check that the packages "wireless-tools" and "usbutils" are in the default repositories and install them if needed.

    --
    A penguin on the ice.
    0
    1. PIXLDealer Posted messages 34 Status Member 11
       
      Thank you for your response,

      I tried but my card is still not detected...

      I sent an email to TP-Link support, let's see what they reply...
      0
    2. jns55
       
      I sent an email to TP-Link support, we'll see what they reply...

      If they respond to you...
      0
  3. PIXLDealer Posted messages 34 Status Member 11
     
    Here is the email from TP-LINK:

    Hello,
    Linux being an open system with many distributions, we cannot guarantee that the driver we provide will work with your Linux distribution.
    Given the specificity of the Linux system, we are sorry that we cannot provide further guidance on the installation, other than the guide included in the archive containing the driver, and we recommend consulting the forums dedicated to your distribution to seek help from its community.

    Best regards,
    Technical Support

    Then I tried a bunch of things but the result is always the same.
    I plan to try downgrading to a Raspbian version from January 2015.
    I will keep you updated.
    0
  4. PIXLDealer Posted messages 34 Status Member 11
     
    After many tutorials, help from you, forums in English, Spanish, and even Russian, I still don't have the solution.

    Thanks to those who helped me, my Raspberry will find another key.

    One piece of advice:
    Don't buy a dongle from Tp-Link if you're on Linux.
    0