TECOM WL5061DP usb wireless problem [SOLVED]

[salixcylic]

Hello:

I've got an TECOM WL5061DP usb wireless receiver (you can see it here: http://img03.taobaocdn.com/bao/uploaded ... 091028.jpg ) but it doesn't work.
If I execute the command iwconfig it is not detected. The command lsusb tells me:

Code: Select all

Bus 002 Device 002: ID 0572:2002 Conexant System (Rockwell), Inc. SoftGate 802.11 Adapter

Ok, some time for "googling" and I've found in http://cateee.net/lkddb/web-lkddb/P54_USB.html that ID 0572:2002 uses Prism54 chipset and module p54usb is included in kernel 2.6.24 or above. Salix 13.1.1 has kernel 2.6.33-4 (uname -r) so it should have p54usb module. Lets try the command modinfo p54usb:

Code: Select all

filename:       /lib/modules/2.6.32-24-generic/kernel/drivers/net/wireless/p54/p54usb.ko
firmware:       isl3887usb
firmware:       isl3886usb
alias:          prism54usb
license:        GPL
description:    Prism54 USB wireless driver
author:         Michael Wu <flamingice@sourmilk.net>

...etc (more lines ommited)

If I check the dmesg I found:

Code: Select all

usb 2-1: New USB device found, idVendor=0572, idProduct=2002
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1: Product: USB device
usb 2-1: Manufacturer: Conexant
usb 2-1: reset full speed USB device using uhci_hcd and address 2
usb 2-1: firmware: requesting isl3887usb
usb 2-1: (p54usb) cannot load firmware isl3887usb (-2)!
usb 2-1: firmware: requesting isl3887usb_bare
p54usb: probe of 2-1:1.0 failed with error -2
usbcore: registered new interface driver p54usb

why modinfo p54usb tells me "firmware: isl3887usb" and dmesg tells me "cannot load firmware isl3887usb"? ¿¿??

Any help would be most welcome.

Sorry for my bad English.

[thenktor]

That's because you need to get the requested firmware somewhere else. Salix already has firmwares included in /lib/firmware/ but apparently the requested one is missing.

EDIT: Look at http://wireless.kernel.org/en/users/Dri ... 4#firmware

[salixcylic]

Thanks for the link!
I've downloaded the isl3887usb firmware for 2.6.29 kernels and above ( http://daemonizer.de/prism54/prism54-fw ... 0.lm87.arm )
Then I've unplugged the wireless receiver, copied the file to /lib/firmware, renamed it ( 2.13.24.0.lm87.arm ) to isl3887usb, and finally plugged the receiver again. Then dmesg tells me:

Code: Select all

usb 2-1: new full speed USB device using uhci_hcd and address 3
usb 2-1: New USB device found, idVendor=0572, idProduct=2002
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1: Product: USB device
usb 2-1: Manufacturer: Conexant
usb 2-1: reset full speed USB device using uhci_hcd and address 3
usb 2-1: firmware: requesting isl3887usb
phy1: p54 detected a LM87 firmware
p54: rx_mtu reduced from 3240 to 2384
phy1: FW rev 2.13.24.0 - Softmac protocol 5.9
phy1: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES
phy1: hwaddr 00:03:c9:ae:e5:ab, MAC:isl3887 RF:Frisbee
phy1: Selected rate control algorithm 'minstrel'
Registered led device: p54-phy1::assoc
Registered led device: p54-phy1::tx
Registered led device: p54-phy1::rx
Registered led device: p54-phy1::radio
usb 2-1: is registered as 'phy1'
udev: renamed network interface wlan0 to wlan1
ADDRCONF(NETDEV_UP): wlan1: link is not ready

Ok, no more "cannot load firmware isl3887usb". Then a iwconfig:

Code: Select all

lo        no wireless extensions.

eth0      no wireless extensions.

wlan1     IEEE 802.11bg  Mode:Managed  Access Point: Not-Associated   
          Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

Great!
Now I execute iwlist scan:

Code: Select all

wlan1     Scan completed :
          Cell 01 - Address: 00:02:CF:55:7D:93
                    Channel:9
                    Frequency:2.452 GHz (Channel 9)
                    Quality=70/70  Signal level=-129 dBm  
                    Encryption key:on
                    ESSID:"WLAN_B6"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000033b2b98d1c0
                    Extra: Last beacon: 249ms ago
                    IE: Unknown: 0007574C414E5F4236
                    IE: Unknown: 010582848B962C
                    IE: Unknown: 030109
                    IE: Unknown: 2A0100
                    IE: Unknown: 32080C1218243048606C

Then iwconfig wlan1 essid WLAN_B6 key s:xxxxxxxxxxxxx (where xx... is the password) Ok, now dhclient wlan1:

Code: Select all

bash: dhclient: command not found

Lets try with dhcpcd wlan1:

Code: Select all

dhcpcd: version 5.2.2 starting
dhcpcd: wlan1: waiting for carrier
dhcpcd: timed out
dhcpcd: allowing 8 seconds for IPv4LL timeout
dhcpcd: timed out

What's wrong?

[salixcylic]

I'm learning a lot about wireless commands with this device, but not enought to run it on Salix
An experiment: I've used the receiver at home's friend with another PC, another distro and another wifi-network following the same steps but dhclient command and it works, so the receiver is right.
I've returned home and using wicd it can see the network but if I try to connect it stop in the step "Validating autentication" and send me an error message: "Fail connection: incorrect password" I know the password is OK.
I've been "googling" and I know that Slackware don´t uses dhclient but I don´t know if I can install it. What is the difference between dhclient and dhcpd?
I've found also info about edit file /etc/rc.d/rc.inet1.conf. Will this help?

[gapan]

I would first try with an unencrypted network. If that works, it's probably something with the encryption.

[pwatk]

If your hardware works and your not having any joy with wicd then I would start by configuring the networking rc script /etc/rc.d/rc.inet1.conf. If your network uses WPA encryption you'll need to configure /etc/wpa_supplicant as well.

You can reset the device node for your wireless card to wlan0 by deleting /etc/udev/rules.d/70-persistent-net.rules and reloading udev (a reboot might be safer here).

More information about the Slackware networking scripts can be found here: Configuring your network in Slackware

I also agree with gapan. I don't think dhcp is your problem, I think it's the encryption your using.

[salixcylic]

You both are right: if I turn off the WEP encryption:

Code: Select all

iwlist wlan0 scan

Cell 02 - Address: E0:91:53:03:BE:5E
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=70/70  Signal level=-1 dBm  
                    Encryption key:off
                    ESSID:"WLAN_EE"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000000795be9f1d9
                    Extra: Last beacon: 649ms ago
                    IE: Unknown: 0007574C414E5F4545
                    IE: Unknown: 010482848B96
                    IE: Unknown: 030106
                    IE: Unknown: 0706455320010D14
                    IE: Unknown: 2A0100
                    IE: Unknown: 32080C1218243048606C
                    IE: Unknown: DD050010910400

...and now I use wicd it conects OK and gives me an IP but I can't surf the web: Firefox doesn't load any web sites.
If I execute an iwconfig:

Code: Select all

wlan0     IEEE 802.11bg  ESSID:"WLAN_EE"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: E0:91:53:03:BE:5E   
          Bit Rate=1 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-129 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

but the command ping http://www.google.es:

Code: Select all

PING www.l.google.com (66.249.92.104) 56(84) bytes of data.
64 bytes from 66.249.92.104: icmp_req=1 ttl=53 time=95.4 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available

....etc

And some minutes later, I lost the conection and wicd doesn't detect wifi networks anymore. I must unplugged the receiver and plug it again.
This is making me crazy. I don't understand why another distro can run the receiver OK and Salix not. Tomorrow I'll make more test with another lan and another distro, and I'll read the link about /etc/rc.d/rc.inet1.conf if neccesary.

Thank you for your colaboration.

[Shador]

Can you post the output of:

Code: Select all

dmesg | tail

[salixcylic]

Ok, this is dmesg | tail width WEP encryption on:

Code: Select all

Registered led device: p54-phy0::rx
Registered led device: p54-phy0::radio
usb 2-1: is registered as 'phy0'
usbcore: registered new interface driver p54usb
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): eth0: link is not ready

This is dmesg | tail width WEP encryption off:

Code: Select all

wlan0: direct probe to AP e0:91:53:03:be:5e (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP e0:91:53:03:be:5e (try 1)
wlan0: authenticated
wlan0: associate with AP e0:91:53:03:be:5e (try 1)
wlan0: RX AssocResp from e0:91:53:03:be:5e (capab=0x421 status=0 aid=2)
wlan0: associated
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
cfg80211: Calling CRDA for country: ES
wlan0: no IPv6 routers present
No probe response from AP e0:91:53:03:be:5e after 500ms, disconnecting.
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): eth0: link is not ready

So, you can see that width WEP on the receiver don't connect. Width WEP off, wicd connect and give me an IP but then disconnect again ( No probe response from AP e0:91:53:03:be:5e after 500ms, disconnecting.) Thats the reason because a ping command tells me sendmsg: No buffer space available.
Why?

If I try width a Zydas based receiver, dmesg tell me:

Code: Select all

zd1211rw 2-1:1.0: phy3
usbcore: registered new interface driver zd1211rw
udev: renamed network interface wlan0 to wlan1
usb 2-1: firmware: requesting zd1211/zd1211b_ub
usb 2-1: firmware: requesting zd1211/zd1211b_uphr
zd1211rw 2-1:1.0: firmware version 4725
zd1211rw 2-1:1.0: zd1211b chip 0ace:1215 v4810 full 00-16-44 AL2230_RF pa0 ---NS
cfg80211: Calling CRDA for country: US
ADDRCONF(NETDEV_UP): wlan1: link is not ready

Look this. The P54 based (wlan0) use cfg80211: Calling CRDA for country: ES and the Zydas (wlan1) cfg80211: Calling CRDA for country: US. ¿¿??

If I connect width Zydas and WEP off. dmesg | tail:

Code: Select all

ADDRCONF(NETDEV_UP): wlan1: link is not ready
wlan1: direct probe to AP e0:91:53:03:be:5e (try 1)
wlan1: direct probe responded
wlan1: authenticate with AP e0:91:53:03:be:5e (try 1)
wlan1: authenticated
wlan1: associate with AP e0:91:53:03:be:5e (try 1)
wlan1: RX AssocResp from e0:91:53:03:be:5e (capab=0x421 status=0 aid=5)
wlan1: associated
ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
wlan1: no IPv6 routers present

I cant see any difference except this:
p54 :wlan0: RX AssocResp from e0:91:53:03:be:5e (capab=0x421 status=0 aid=2)
Zydas: wlan1: RX AssocResp from e0:91:53:03:be:5e (capab=0x421 status=0 aid=5)

Do you see another difference?

This receiver (Zydas) works OK also width WEP encryption on.

[Shador]

One issue I noticed is that you're displayed pretty low signal strengths < -100dBm.
I'm having myself here approximately -70dBm and that's pretty much the minimum for me.
The relatively high values for the last received beacon and the low Bit Rate values also support that assumption.

Maybe you should get closer to the access point. It's no good idea to go to close either as that can negatively influence the signal quality too. 5-10m should be good I think with few obstacles.

Can you post the output of iwlist x scan and iwconfig x with the Zydas device?

Possibly the Windows driver used with ndiswrapper gives better results?