Help - Search - Members - Calendar
Full Version: Usb "retail Plus" Wifi
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
Antikx
I'm slowly working towards stuffing wifi into my C1000, so...
Grabbed a cheap USB wifi stick.
product link

Trying to get it working under R198.
Any help would be appreciated.
The sticker on it says: PANWL22038
The green light comes on when I plug it in.
dmesg doesn't say much:
CODE
usb 1-2: new full speed USB device using pxa27x-ohc1 and address 2
usb 1-2: configuration #1 chosen from one choice

I'm guessing I have to edit a file and add this device info? Sorry, I haven't done this in a while, so please excuse my ignorance.

Capn_Fish
Can you see what chipset it uses (if it's clear)? That would probably be a good place to start.
speculatrix
what does "lsusb" report, whether on x86 or zaurus?
Antikx
Ahhh... That's the command I was trying to remember.

On the Zaurus it doesn't say much: ZyDAS
on a Linux PC it says the same thing for lsusb
but on a PC "dmesg" says:
CODE
[148756.704000] usb 4-4: new high speed USB device using ehci_hcd and address 18
[148756.836000] usb 4-4: configuration #1 chosen from 1 choice
[148757.512000] usb 4-4: reset high speed USB device using ehci_hcd and address 18
[148757.796000] zd1211rw 4-4:1.0: firmware version 4725
[148757.840000] zd1211rw 4-4:1.0: zd1211b chip 0ace:1215 v4810 high 00-02-72 AL2230_RF pa0 g--NS
[148757.844000] zd1211rw 4-4:1.0: eth2
[148757.844000] usbcore: registered new interface driver zd1211rw
Antikx
I found this site, which talks about getting them working under Slackware:
http://www.linuxquestions.org/questions/sl...ackware-494224/
It points to the source being available here:
http://zd1211.wiki.sourceforge.net/
I would be happy to buy one of these and ship it to them if someone would help me get it going.
Capn_Fish...you want to bite? (no pun intended) smile.gif
Capn_Fish
I'll try.
Capn_Fish
Am I just being thick, or is there no download link for the driver?

EDIT:

QUOTE
Requirements

* Linux 2.6.18-rc1 or newer, with the ieee80211, ieee80211softmac, and firmware_class modules (CONFIG_IEEE80211, CONFIG_IEEE80211_SOFTMAC, CONFIG_FW_LOADER)
o There is no backwards compatibility with older kernels
* Device firmware (see above)


It appears you need a 2.6.18 or newer kernel to get the driver. sad.gif

EDIT2: I can try building the other driver listed, the one without support, if you'd like.
Antikx
I guess we are at 2.6.16, hey? hmmm... too bad.
It's better then nothing, so ya, if you wouldn't mind giving it a shot.
Thanks man.
undrwater
There are instructions here: linky

Indicates 2.4 kernel.

I think finding the 2.4 version might be difficult.
undrwater
Driver compiled for cacko kernel 2.4.20 here. Scroll down a bit.
Capn_Fish
Maybe pester InSearchOf to make sure the module is in the upcoming release, as well...

EDIT: Sorry, I got sidetracked building this new web browser. I'll work on the module afterwards, if that's OK.
Antikx
QUOTE(Capn_Fish @ Nov 29 2007, 03:14 PM) *
Maybe pester InSearchOf to make sure the module is in the upcoming release, as well...

EDIT: Sorry, I got sidetracked building this new web browser. I'll work on the module afterwards, if that's OK.


Good idea.

and yes, when ever you are ready. no prob. thanks. wink.gif
Capn_Fish
OK, see how this works. There were a bunch of errors about stuff not being defined (kernel config issues, I guess), so I'm not too hopeful.
Antikx
Thanks Capn'Fish and underwater.
I'll plug away at this for a few days
Antikx
OK
I copied the KO file to: /lib/modules/2.6.16/kernel/drivers/usb/net/
I rebooted, iinserted the usb wifi
checked dmesg and lsusb, but nothing had changed
typed this:
CODE
modprobe zd1211b

and got this:
CODE
FATAL: Error inserting zd1211b (/lib/modules/2.6.16/kernel/drivers/usb/net/zd1211b.ko): Invalid module format

checked dmmesg and it said this:
CODE
zd1211b: module has no symbols (stripped?)

any suggestions? am I doing something wrong?
Capn_Fish
I did strip it, mostly out of habit. I'll try again tomorrow.
Antikx
smile.gif OK, thanks.
Capn_Fish
Here's the new module, a.k.a. the same module not stripped smile.gif.
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. sad.gif

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. sad.gif Not that that response was aimed at me.
Antikx
smile.gif and sad.gif
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! smile.gif)
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 smile.gif
Antikx
hmmm... looks like I might need a better soldering kit and less coffee.

EDIT: coincidently, he mentions the exact same WiFi adapter. smile.gif
Drake01
QUOTE(Antikx @ Dec 13 2007, 02:06 PM) *
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
QUOTE(Drake01 @ Dec 13 2007, 05:36 PM) *
QUOTE(Antikx @ Dec 13 2007, 02:06 PM) *
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.

Capn_Fish
I'd need to recompile the driver, but I lack the kernel sources to compile with for 2.4.18 or 2.4.20. Modules are very kernel-version dependent.
Antikx
Does anyone have the kernel sources that Captain Fish can use to compile the driver so that it will work under pdaXrom Beta3 ... please?
Capn_Fish
I'd definitely like the pdaXrom 2.4.18 and 2.4.22 kernel sources.

EDIT: I mean 2.4.18 and 2.4.20
Antikx
I just talked to InSearchOf and he is going to see if he can get it to us.
Capn_Fish
Great news!
Antikx
Sorry if I'm getting this mixed up, but Beta3/pdaXii13 uses 2.4.20, but you need 2.4.18 kernel sources for compiling drivers and 2.4.20 for compiling applications. Is that right?
eviLjazz
For kernel 2.4.20 you could use my unified Sharp/Tetsu/Cacko/pdaXrom kernel branch: http://www.katastrophos.net/zaurus/kernels/v55/

http://www.katastrophos.net/zaurus/kernels....20-v55.tar.bz2

The archive contains all sources and a README with all necessary instructions to either compile it automatically via script or manually.

If you need help I think I have some free time at the weekend.

AFAIK the 2.4.18 sources + patches are in the pdaXrom build kit which is somewhere on the ibiblio server...
eviLjazz
http://distro.ibiblio.org/pub/linux/distri...2.04.06.tar.bz2

Seems like they download the kernel from Sharp and then patch it with the kernel patches included in the archive...
Capn_Fish
QUOTE(Antikx @ Jan 3 2008, 02:45 PM) *
Sorry if I'm getting this mixed up, but Beta3/pdaXii13 uses 2.4.20, but you need 2.4.18 kernel sources for compiling drivers and 2.4.20 for compiling applications. Is that right?

I'd just like 2.4.18 and 2.4.20. I'd only need 2.4.20 to build against for pdaXii13, but I think modules have been requested for Cxx0 series that would use the 2.4.18 kernel.
Antikx
I'm starting to stress test this driver. So far so good.

InSearchOf/Capn_Fish, how is compiling this driver for pdaXrom/Beta3 coming. Can I help?
Capn_Fish
I still don't have sources, and am currently too preoccupied with other matters to find the patches and patch the vanilla kernel myself.

EDIT: Antikx: Thinking of going back to beta3/pdaXii13?
Antikx
No, probably not.
I sent cycle_55 one of the usb wifi adaptors and since he uses beta3 I was hoping he could use it.
cycle_55
QUOTE(Antikx @ Jan 30 2008, 02:03 PM) *
No, probably not.
I sent cycle_55 one of the usb wifi adaptors and since he uses beta3 I was hoping he could use it.


I am at the present time not using it in the Z but in my wife's fit-pc with Ubuntu 7.10 and it works quite well. At some point i do want a usb wifi adapter for the Z and would be willing to pay someone to mess with the driver for me. Thanks Antikx for the adapter.

cycle_55
utx
You cannot use ZD1211B based dongles as they are. They need more power than Zaurus is able to provide.

You have three changes:

1) Use powered hub

2) Modify you Zaurus to provide 500mA power on USB (it means change of one resistor).

3) Modify your dongle to run at 3.3V and use 3.3V from pin 11 of IOPORT connector.
utx
QUOTE(utx @ Mar 25 2008, 04:41 PM) *
You cannot use ZD1211B based dongles as they are. They need more power than Zaurus is able to provide.

3) Modify your dongle to run at 3.3V and use 3.3V from pin 11 of IOPORT connector.


I just tried it with my dongle. After removal of the linear voltage stabilizer from the dongle, the whole dongle runs at 3.3V and eats only 66% of the power than before.

But connecting it to 3.3V from pin 11 of IOPORT causes immediate crash of the Zaurus (one has to remove battery for a while to get it working again). It seems the current limitation circuit take action.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2015 Invision Power Services, Inc.