Usb "retail Plus" Wifi Options

[Capn_Fish]

I did strip it, mostly out of habit. I'll try again tomorrow.

[Antikx]

OK, thanks.

[Capn_Fish]

Here's the new module, a.k.a. the same module not stripped .

Attached File(s)

 zd1211b_new.tar.gz ( 126.07K ) Number of downloads: 9

 

[Antikx]

I think we are getting warmer here!
when I plug it in, dmesg now says this:

CODE

usb 1-2: configuration #1 chosen from 1 choice

_____     ____    _    ____
|__  /   _|  _ \  / \  / ___|
  / / | | | | | |/ _ \ \___ \
/ /| |_| | |_| / ___ \ ___) |
/____\__, |____/_/   \_\____/
     |___/
ZD1211B - version 2.22.0.0-development
vendor_id = 0ace
product_id = 1215
USB 1.1 Host
Release Ver = 4810
EEPORM Ver = 4810
Finsih download Firmware. Ready to reboot
PA type: 0
PHYNEWLayout = 1
Airoha AL2230S_RF
OverWrite CR47 = 0x1C
zd1205_config: EEP(HWFeature)=0x580
AllowedChannel = 000107ff
Region:16
usbcore: registered new driver zd1211b

EDIT:
Next I did a:

CODE

modprobe -v zd1211b

then typed:

CODE

ifconfig eth0 up

It now just blinks on and off, now.

I guess I need to figure out how to get it to find my AP next.
Any advice, please?

[Capn_Fish]

Cool! I had little hope that it would work.

The usual

CODE

iwconfig mode managed essid YOURSSID key WEPKEY power 1
dhcpcd INTERFACE

ought to do it, unless you're using WPA, in which case you need to use WPA_Supplicant

CODE

wpa_supplicant -Dzd1211b -iINTERFACE /etc/wpa_supplicant.conf

The above line may be wrong, as I'm doing it off the top of my head.

[Antikx]

I've been trying that and it just keeps blinking. Tried it on two AP's.
hmmm...
any other advice?

I've signed up for their driver mail list so I'll tell them exactly what we have done and they should be able to help.

EDIT, here's the mail I sent to the list:
Hello,

First off, thanks for the work put into this driver. I'm sure it wasn't a walk in the park.

As per the Subject line I'm trying to get a USB Wifi device working on the Sharp Zaurus (a Linux sub-sub-laptop).

I started a thread on the OESF forum, if you want to read it first: http://www.oesf.org/forum/index.php?showtopic=25125

Someone who has the kernel source and a compile environment was kind enough to compile the driver for me.
I'm running a 2.6.16 kernel with the pdaXrom R198 distro. Because it no 2.6.18 or better he had to compile the one that was not supported.

I've installed the kernel module and according to dmesg it looks like it loads OK:

CODE

usb 1-2: configuration #1 chosen from 1 choice

_____     ____    _    ____
|__  /   _|  _ \  / \  / ___|
  / / | | | | | |/ _ \ \___ \
/ /| |_| | |_| / ___ \ ___) |
/____\__, |____/_/   \_\____/
     |___/
ZD1211B - version 2.22.0.0-development
vendor_id = 0ace
product_id = 1215
USB 1.1 Host
Release Ver = 4810
EEPORM Ver = 4810
Finsih download Firmware. Ready to reboot
PA type: 0
PHYNEWLayout = 1
Airoha AL2230S_RF
OverWrite CR47 = 0x1C
zd1205_config: EEP(HWFeature)=0x580
AllowedChannel = 000107ff
Region:16
usbcore: registered new driver zd1211b

I've typed the following, but it still just keeps blinking and never connects to the AP:

CODE

modprobe -v zd1211b
ifconfig eth0 up
iwconfig eth0 rate 2000kb
iwconfig eth0 channel 11
iwconfig eth0 essid linksys
iwpriv eth0 set_mac_mode 3
iwconfig eth0 mode 2

(I read that I can't changed the channel while in managed mode... why is that?)

if I try and run "dhcpd eth0", it blinks for a bit and then seems to down the eth0 device

If I look at dmesg after I've tried connecting to an AP it starts out by saying:

CODE

ADDRCONF(NETDEV_UP): eth0: link is not ready
Wait too long to start scanning

then is says a lot of:

CODE

ZD1211_TX_BUSY is locked over 5 seconds
jiffies = 1817302, lastSetBusy = 1815785, HZ=100

(the above two lines repeat many times with only the jiffies and lastSetBusy numbers changing)

then near the bottom I get (FYI, might have been around when I unplugged the device):

CODE

macp is NULL or macp.flags.ZD1211_RUNNING
Wait too long to start scanning
soc: WM8750 <-> pxa2xx-i2s info
soc: rate mask 0x6fe
soc: min ch 2 max ch 2
soc: min rate 8000 max 96000
ADDRCONF(NETDEV_UP): eth0: link is not ready
Call StartSTA(IBSS or AP)

[Capn_Fish]

That sounds like what happens with my ZT6688 (DM9601) wired USB ethernet adapter. I insert it, the module loads, and I can get eth0 up, but dhcpcd times out (just like you said). I have no idea what is going on with it. It worked OK once when I wired it directly to a spare router with a ~0.5m cable, but nothing after that. You could try standing right next to the AP (seeing as how distance seemed to be a factor in my case).

[kkazakov13]

Do you use powered USB hubs? Because ... I have an Asus WL-167G and under debian it showed in the logs, that the power is insufficient. But under beta3 - it just lights up and nothing more ... I don't have powered USB hub yet to try ...

[Capn_Fish]

Good point, I considered asking at some point, then forgot about it.

Unfortunately that can't be my issue. From some USB identification program, I have learned that my adapter should draw 150mA tops. Not that that response was aimed at me.

[Antikx]

and
Well kkazakov13... you called it.
It's cool that we now have a working driver on the Zaurus for a very cheap ($19) USB WiFi stick, but it's sad that it requires a powered USB hub.

Thanks guys!

My quest goes on... can anyone recommend a cheap (and small) USB WiFi device that doesn't require a powered hub?

[Capn_Fish]

You can still stick it in your Z. I seem to recall AlbertR's site says you just need to bypass a resistor and then you can use it on USB power alone.

EDIT: Glad to hear the driver works (note to self: don't strip modules! )

[kkazakov13]

Yes, we can use description from here - http://www.seicento.selfip.org/zelectronic...ower_boost.html

unfortunately, I removed everything, got to the mentioned resistor ... but it was TOO SMALL, I barely saw it ... can't risk soldering on it. I have a friend with soldering skills in another city, which I will beg to help me

[Antikx]

hmmm... looks like I might need a better soldering kit and less coffee.

EDIT: coincidently, he mentions the exact same WiFi adapter.

[Drake01]

hmmm... looks like I might need a better soldering kit and less coffee.

Didn't someone mention using a conductive "silver paint" to do something similar? Sounds like it would be a lot easier than trying to solder that.

I think I found the post I remembered. Apparently there was an issue with the conductivity of the "paint," but it might work for this application since the resistors would be in direct contact with each other and we're talking about much higher resistances than the 10 Ohms from pelrun's post.

[Antikx]

hmmm... looks like I might need a better soldering kit and less coffee.

Didn't someone mention using a conductive "silver paint" to do something similar? Sounds like it would be a lot easier than trying to solder that.

I think I found the post I remembered. Apparently there was an issue with the conductivity of the "paint," but it might work for this application since the resistors would be in direct contact with each other and we're talking about much higher resistances than the 10 Ohms from pelrun's post.

I have never heard of silver paint. I'll have to look into it. thanks.

Capn'Fish... would the driver that you compiled work under pdaXrom Beta3? I know you used the kernel sources from the 2.6.16 kernel, but I don't have enough experience to know how forgiving it will be when installed on a 2.4.x kernal system.