Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

TP-Link wireless usb (zd1211)

26 views
Skip to first unread message

Nuno Magalhães

unread,
Apr 19, 2009, 1:50:08 PM4/19/09
to
Greets,

i'm trying to setup wireless through a USB adapter. I haven't quite
managed it although it seems its firmware is supported. This is what
i've tried so far:

It's a TP-Link TL-WN322G, i've installed these packages:
wireless-tools wpasupplicant wicd iw lshw lsusb

I've modprobed zd1211rw into /etc/modules, it now has:
loop
sbp2
/etc/modules
...and i probed it to try and activate it.

There's /lib/firmware/zd1211 with a bunch of files

# lsusb
Bus 001 Device 003: ID 15ca:00c3 Textech International Ltd. Mini Optical Mouse
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 007: ID 0ace:1215 ZyDAS WLA-54L WiFi
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hu

# lshw -C network
 *-network
       info on my eth1 (eth0 is firewire)
 *-network DISABLED
      description: Wireless interface
      physical id: 1
      logical name: wlan0
      serial: <MAC-adress here>
      capabilities: ethernet physical wireless
      configuration: broadcast=yes multicast=yes wireless=IEEE 802.1

I've tried this in /etc/network/interfaces:
allow-hotplug wlan0
iface wlan0 inet dhcp
       essid "my ssid here"
       mode Managed #also tried Auto
       freq 7
       key s:mykeyhere

Also tried wireless-{essid,...}, nothing works:

# ifup wlan0
Error for wireless request "Set Encode" (8B2A) :
   SET failed on device wlan0 ; Invalid argument.
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
SIOCSIFFLAGS: Connection timed out
SIOCSIFFLAGS: Connection timed out
wmaster0: unknown hardware address type 801

..then it tries do get IP but obviously fails

The driver is there - i think -, the usb device is found... but it
gets no wireless. Somehow it's disabled... I use WPA in my LAN but
this laptop's going to another LAN (not sure about the config). Is
there a way to configure it through ifconfig? Or, better yet, some GUI
i can use?

On reboot a usb device was consecutively found on address 2, 3, 4, 5...
# dmesg |grep usb
(...)
[ 5.656066] usb 2-1: new full speed USB device using uhci_hcd and address 2
[ 20.768028] usb 2-1: device descriptor read/64, error -110
[ 35.984024] usb 2-1: device descriptor read/64, error -110
[ 36.200031] usb 2-1: new full speed USB device using uhci_hcd and address 3
[ 51.312030] usb 2-1: device descriptor read/64, error -110
[ 66.528030] usb 2-1: device descriptor read/64, error -110
[ 66.744031] usb 2-1: new full speed USB device using uhci_hcd and address 4
[ 77.152029] usb 2-1: device not accepting address 4, error -110
[ 77.264025] usb 2-1: new full speed USB device using uhci_hcd and address 5
[ 87.672024] usb 2-1: device not accepting address 5, error -11
(...)

Wicd finds no wireless networks. Now lsusb hangs and lshw only shows eth1

Any suggestions?
TIA,
Nuno Magalhães

--
() ascii ribbon campaign - against html e-mail
/\ ascii-rubanda kampajno - kontraŭ html-a retpoŝto


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Nuno Magalhães

unread,
Apr 19, 2009, 6:40:09 PM4/19/09
to
I've also tried this[1], to no avail. lsusb does list the device, but
it's still disabled as far as lshw goes...

Suggestions?

[1] http://www.linuxquestions.org/questions/linux-hardware-18/how-to-get-sagem-xg760n-usb-wlan-zydas-zd1211-working-in-debian-5.0-718991/?s=93edc99c0121f4b606a936c7e83a92f8#post3513198

Nuno Magalhães

unread,
Apr 21, 2009, 1:30:15 PM4/21/09
to
2009/4/21 Dimitris <tsa...@gmail.com>:
> The TPLink zd1211 stick has a strange RF chip and it is not detected
> correctly in the debian's kernel (2.6.26). In 2.6.29 it works
> perfectly, try installing that kernel

Thank you very much :) it Just Works™ now. Except for the connecting
part, but that's msot likely my screwing up configurations.

Thanks agian,

0 new messages