I don't think we properly announced this on the list before, so here it is:
Thanks to Michael Wu, zd1211rw has been ported to the development d80211
Linux wireless stack. This sets a path for us to implement many missing
features (ad-hoc, master mode, etc).
Ulrich and myself are now developing
Marcus D. Hanwell wrote:
I didn't set the frequency, I had actually assumed it was the driver trying
to
set its own frequency to match that of the AP. Not sure where the frequency
request came from then - I just set the essid and key for it. I was trying to
use simple WEP.
Nope - those
Hi,
I received a UW2453 device thanks to Haoyu Cheng. The programming
procedure is more complicated than the other RF's, but I'm now online
with it through zd1211rw.
I found a number of strange things in ZyDAS's implementation which I
hope to get clarified soon. I also need to clean up the
Marcus D. Hanwell wrote:
Hi,
This is my first time trying out this driver, so please be gentle if I have
missed anything obvious. I checked what I could see to make sure no one had
gone through this already. I just got a USB wireless adapter with an
ADSL router and thought I would give
Julien Pinon wrote:
I tried it too with 2.6.20 vanillia kernel, with some problems
regarding transfer rate : without any settings others than ssid and
wep key, I had something like 9 Mbits/sec with vanillia kernel, while
I have 18 with dscape stack.
The mainline version does not
I've added AL2230S support to zd1211rw and it is working nicely.
Here are the patches needed for mainline Linux:
http://marc.theaimsgroup.com/?l=linux-netdevm=117364295601764q=raw
http://marc.theaimsgroup.com/?l=linux-netdevm=117364295516100q=raw
(you need both, applied in that order)
Due to
ocset wrote:
Hi
I am running SUSE 10.2 (32bit) with a 3COM 3CRUSB10075 card and I am having
a problem with getting the wireless setting to be applied at startup. When I
boot up the machine, the card gets recognised by the zd1211rw driver but the
ESSID and WEP key are always blank and have
Richard Hughes wrote:
64 bytes from 10.0.0.10: icmp_seq=358 ttl=64 time=11428 ms
64 bytes from 10.0.0.10: icmp_seq=359 ttl=64 time=11840 ms
64 bytes from 10.0.0.10: icmp_seq=360 ttl=64 time=11984 ms
64 bytes from 10.0.0.10: icmp_seq=361 ttl=64 time=12826 ms
64 bytes from 10.0.0.10:
Javier Gracia Castro wrote:
Hello everybody,
I am new at embedded systems and Linux. I have ported a 2.6.20 Linux
kernel to my AT91RM9200-EK board and a file system with uClibc. I
wanted to add a wireless extension to this board and I chose an USB
wi-fi device with zd1211 chipset. I
Interesting. Some more questions:
Are the ping times really high all the time, or is it just some/most of
the time?
One significant difference between the 2 drivers is that softmac
defaults to 11M or 24M (depending on your kernel version) and doesn't
change, whereas mac80211 defaults to 54M
Mayne wrote:
Fine for me. I'd suggest to move zd1211rw content to linuxwireless and to
move the remaining content to Sourceforge. I'll replace zd1211.ath.cx with
a simple static page after some time.
OK. I just moved it over.
It's your decision but I think we still need a wiki for the
Mayne wrote:
I'd suggest to move the content of the current wiki as HTML pages to the
Sourceforge servers. I can give you access to these pages. It's not a
wiki anymore but you can still change it then. Same for the vendor
driver and SVN, this can be moved to Sourceforge.
OK, but be warned
Gomathi sankar wrote:
I too need details about ZYDAS for a research in it. Help me please
The device specs are private, sorry. We will only distribute them to
people who make significant contributions to open source driver development.
You can try approaching Atheros to obtain/buy device
Javier Gracia Castro wrote:
Finally, I have enabled all these options not as modules, but built in
the kernel itself.
You can't build zd1211rw into the kernel at the moment. It tries to load
the firmware before the filesystem is available, which fails for obvious
reasons. You need to build
[EMAIL PROTECTED] wrote:
I have some problems:
- sometimes the device will not start. I have to reboot, and restart
the card under Windows, then reboot again.
sudo ifup eth2 gives no device existing in this case. rmmod and
modprobe do not help
You need to provide more info here. Error
Are you sure this is a WL138g? Google indicates this is a PCI card...
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just
Sebastian Siewior wrote:
It worked perfectly with 2.6.18-20 and stopped workin with 2.6.21. After
removing the check, it is working again. Are there some sticks actually
not working or is my stick just a false positive?
Yes, my own and quite a few others (it can't TX). At the very least, if
Glenn wrote:
The Gigafast WF748-CUI that I have fpr examlpe shows 500ma as required in
it's config descriptor.
In general, these values are often inaccurate. I also think that even if
there is any variation in these values between different ZD1211 devices,
the actual power usage will be the
Daniel Drake wrote:
Sebastian Siewior wrote:
It worked perfectly with 2.6.18-20 and stopped workin with 2.6.21. After
removing the check, it is working again. Are there some sticks actually
not working or is my stick just a false positive?
One possible explanation for the fact yours worked
Lucio Crusca wrote:
While dhclient is trying to get in touch with the AP, iwevent
says:
May 7 15:22:15 Acaja-Tour kernel: zd1211rw 3-5:1.0: zd_usb_enable_int()
May 7 15:22:15 Acaja-Tour kernel: zd1211rw 3-5:1.0: zd_usb_enable_int()
submit urb e86d1e40
May 7 15:22:15 Acaja-Tour kernel:
Lucio Crusca wrote:
Ok then. Why don't we put on the website a minimal script to bring up an
interface with zd1211rw? Seems to me that, if distro scripts cause a lot of
problems, we would make a lot of users happy...
Feel free to volunteer. Personally I'm more than happy with my distro's
Lucio Crusca wrote:
Alle 19:19, lunedì 7 maggio 2007, Lucio Crusca ha scritto:
# ifconfig eth5 up
SIOCSIFFLAGS: Connection timeout
but this should be the first thing to do before doing anything else. I'm
stuck. iwevent output is plain silence.
I've forgotten the relevant kern.log
May
Guy Gallagher wrote:
Details:
Brand/Name: Zyxel ZyAIR G200
USB ID: 0586:3407
chip ID: zd1211 chip 0586:3407 v4721 high 00-13-49 AL2230_RF pa0
g---
Added to my tree.
This means that we now support all known ZyXEL ZD1211 devices, and we
have also now reached
Ulle wrote:
Does anybody know, what this means?
The second one I can not bring to inject packets, the first works okay with
injection.
zd1211rw does not support injection so you must be using a modified driver.
Please try normal operation with a clean driver.
Also, use a newer kernel.
Björn Tappert wrote:
What makes me mad is that on this page (http://zd1211.ath.cx/) it says, my
card
is supported:
Read again -- the hardware listed there is *not* supported by zd1211rw.
Medion 98300 Laptop Integratedzd1211b * 0ace:1215 UW2453
I only added this entry
Uli Kunitz wrote:
So at the moment your only chance will be to recompile the zd1211rw
git branch of my wireless-dev git tree. Some additional information
can be found here: http://linuxwireless.org/en/users/Drivers/zd1211rw
This code is known not to work very well, hence me not pushing it
I ran some tests to compare the performance of the UW2453 and AL2230S RF
chips.
My tests were downloading a 36mb file over the internet from a fast host
(HTTP). When repeating the tests, I unloaded the module, replugged the
device, and loaded the module again inbetween each test. I made sure not
Further UW2453 testing:
My tests were downloading a 36mb file over the internet from a fast host
(HTTP). When repeating the tests, I unloaded the module, replugged the
device, and loaded the module again inbetween each test. I made sure not
to change the location or orientation of the device,
Zen Kato wrote:
Hi,
I compiled 'zd1211rw_2007-05-24' for buffalo WLI-U2-KG54L, but I have
the following
compie error.
Where did you find the link to this file? The snapshots are no longer
maintained (even despite them having today's date). Use the in kernel
version, 2.6.21 or newer.
Zen Kato wrote:
T: Bus=04 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 6 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=0411 ProdID=00da Rev=48.10
S: Manufacturer=Buffalo
S: Product= USB2.0 WLAN
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0
This release is almost entirely only changes to zydas own driver
architecture (debug support etc) and some fixes for hardware
encryption/decryption -- in other words, no fixes that we can move
directly into zd1211rw just yet.
Nevertheless, I'm sure people are interested, so here it is:
Jeff Sadowski wrote:
This driver will work on an ARM processor correct?
This driver works with wpa_supplicant right?
zd1211rw: yes, and yes. The driver is actively developed -- if you do
find problems you'll have 2 active developers reading the reports at the
very least.
Bear in mind that
Jeff Sadowski wrote:
ah I read it supported master. :-P
Why do they say it supports master on wikipedia
http://en.wikipedia.org/wiki/Comparison_of_Open_Source_Wireless_Drivers
It says No in the master column.
I bought the http://www.airlink101.com/products/awll3026.html
It was the only
Zen Kato wrote:
hi,
I installed kernel source(kernel-2.6.20-1.2316.fc5.src.rpm) and add
{ USB_DEVICE(0x0411, 0x00da), .driver_info = DEVICE_ZD1211B } into zd_usb.c,
then did $make.
Then replaced the original zd1211rw.ko
Tomas Gustavsson wrote:
Hi.
I can't say that I know that the patch work (I have never
created a patch before) but I did get my Phillips SNU5600
WIFI-usb adapter working after
adding it's USB-ID to zdusb.c.
Please provide the chip ID, see
Jeff Sadowski wrote:
I don't see a link to the driver and how to compile it on the main page.
Do I need to git it via git?
Is there a tarball out there someplace?
You forgot to specify which driver you are asking about. If you mean
zd1211rw, it's in the kernel (which is where you generally
Zen Kato wrote:
zd1211rw 5-4:1.0: zd_mac_init_hw() Regulatory Domain 0x49 is not supported.
Interesting. That domain isn't listed in the vendor driver or the 802.11
specs.
I've modified zd1211rw to behave more like the vendor driver in this
respect. Please try this driver version:
Zen Kato wrote:
Hi Daniel,
wlan0 came out, but the LED light of usb stick is now off.
It flashes upon activity, but doesn't do anything if there is none.
I can not ser ap(access point) and rate from iwconfig, never can do ping
also.
You can use iwevent to monitor authentication and
ScottZ wrote:
I'm still confused on how to get zd1211rw softmac and the AL2230S support
working.
Assuming your device behaves like mine, as opposed to Zen Kato's, you
have 4 options:
1. Use 2.6.22-rc3
2. Wait until the next reviewed 2.6.21 stable release comes out
3. Patch 2.6.21 with the
ping li wrote:
one under vendor based driver sayPlease do not
confuse this driver with the zd1211rw driver included
in Linux 2.6.18 and newer! . Download driver using
subversion:
If you're looking for the zd1211rw driver, you shouldn't be looking on
the vendor-based driver homepage.
Tom Hunter wrote:
I did check the ZD1211 chip markings and can confirm that they are
different (one lot are ZD1211 and the other are ZD122B) yet same USB ID.
OK, thanks. ZyDAS would like to know whether these devices were ordered
directly from Abocom, or if they were from the retail market.
David Santinoli wrote:
Hallo,
very recently I bought a Siemens Gigaset USB Stick 54, which has an
USB ID of 129b:1667.
I saw previous posts in this list mentioning a Siemens stick with the
exact same name but a different USB ID. Those adapters were reported as
working. Unfortunately,
RGRagosta wrote:
A. No wireless connectivity and NO wireless interface definition (eth2,
etc.)
2.6.18 is very old and only supported a few ZD1211 devices. Upgrade to
Linux 2.6.21.5 or newer.
B. Curious if I should consider the recently announced strange
module-driver
Romain Liévin wrote:
since kernel v2.6.21, my WiFi is not useable any longer. The driver is
telling me that AL2230S devices are not yet supported. But, I have a
simple AL2230 device. dmesg output is the following:
Upgrade to 2.6.21.5
Thanks,
Daniel
Jon Smirl wrote:
Using current git wireless-dev tree. I was in monitor mode and did a
iwlist scan.
Added to the mac80211issues page, thanks for the report.
http://www.linuxwireless.org/en/users/Drivers/zd1211rw/mac80211Issues
hikichi wrote:
Daniel Drake wrote:
:
1. Connect to your network using ZD1211
2. Generate as much network traffic as possible, i.e. start downloading
a large file from a local machine, or upload one, or even do both at the
same time
3. Run cat /proc/bus/usb/devices
4. If this doesn't
David Santinoli wrote:
Indeed, it works. It's been up for more than a day now, with decent
throughput (much higher than my previous Ralink-based USB adapter).
It seems that 129b:1667 can safely be added to the supported models'
database.
Please provide the chip ID, see
David Santinoli wrote:
zd1211b chip 129b:1667 v4810 high 00-01-e3 AL2230S_RF pa0 ---N-
Thanks, added to my tree.
Daniel
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2
Pierellozzo wrote:
Then something _strange_ happens and my USB device disconnects (I've
attached the log file). The system starts running much slower,
iwconfig/lsusb commands don't run on terminal, and (obviously) I cannot
access the network anymore. I have to reboot to have it working again.
Giuseppe Lippolis wrote:
so i execute
iwconfig eth1 essid
an then iwconfig
eth1 IEEE 802.11b/g ESSID: Nickname:zd1211
Mode:Managed Frequency:2.412 GHz Access Point: 00:0F:3D:A6:FA:DA
Bit Rate=1 Mb/s
Encryption key:off
Jim Colton wrote:
zd_chip_unlock_phy_regs() CR_REG1: 0x20 - 0xa0
Jul 11 13:31:35 river kernel: zd1211rw 1-1.1:1.0: bssinfo_change()
changes: 4
Jul 11 13:31:38 river kernel: usb 1-1.1: handle_retry_failed_int() retry
failed interrupt
Jul 11 13:31:38 river pumpd[4009]: got dhcp offer
Jul 11
Giuseppe Lippolis wrote:
00:37:02 kernel: [ 502.652000] SoftMAC: Sent Authentication Request to
00:0f:3d:a6:fa:da.
00:37:02 kernel: [ 502.656000] SoftMAC: Open Authentication completed with
00:0f:3d:a6:fa:da
00:37:02 kernel: [ 502.656000] zd1211rw 4-1:1.0: set_channel() channel 1
Juerg Haefliger wrote:
The problem I'm observing is that wireless events that I can see through
iwevent don't seem to make it into the driver. The following logs and
iwevents are generated during driver load and 'ifup wlan0' execution. The
output of iwconfig shows the state after things
Hi,
I have created and published a utility to manipulate ZD1211 device
memory. It runs in userspace using libusb. It will not operate when any
ZD1211 kernel drivers are loaded.
Right now it allows you to modify select parts of the EEPROM, and to
dump the EEPROM to a file.
You can easily
Hi Tom,
Atheros supposedly contacted Abocom about this to make sure that Abocom
stop using 07b8:6001 for ZD1211B devices (this has historically been a
ZD1211 ID).
We still don't have a way of determining whether a device is ZD1211 or
ZD1211B before firmware load time, except for USB ID, which
Giuseppe Lippolis wrote:
Hi daniel,
I had tried to use the vendor driver and it worked with zd1211b.
So i modify the line in the kernel:
{ USB_DEVICE(0x0cde, 0x001a), .driver_info = DEVICE_ZD1211B }
and it has worked fine also in monitor mode.
Great!
Please provide the chip ID so that
Nathan Meyers wrote:
I'm writing to contribute a new device ID for the zd1211rw driver.
Product: ZyXEL M-202 XtremeMIMO USB Adapter
USB IDs: 0586:340a
Chip ID: zd1211b chip 0586:340a v4810 high 00-13-49 AL2230_RF pa0 S
FCC ID: SI5WUB221Z
Driver code: { USB_DEVICE(0x0586, 0x340a),
Nathan Meyers wrote:
Daniel Drake wrote:
Thanks for the report. It's very interesting: MIMO is the technology
used to drive 802.11n (multiple simultaneous data throughput channels)
but the ZD1211 hardware does not support this (it only has a single
radio). The ZyXEL website doesn't really
Mayne wrote:
Anyways, anyone apart from me running zd1211 on a USB 1.1 system? So far
the two 1.1 systems I used both had problems with the stick (hiccups every
some minutes). I got a NEC-based USB 2.0 PCI card now (1033:0035,
Longshine 8033H, NEC 720100 chipset, EHCI/OHCI) that seems to
Hi Sam,
itrs lin wrote:
[ 612.284000] zd1211rw 4-2:1.0: zd1211b chip 2019:5303 v4810 high
00-90-cc AL2230_RF pa0 ---N
Thanks for the report. What is this device marketed/branded as?
Thanks,
Daniel
-
This SF.net email
Brian Perkins wrote:
fc7 insists on using the mac80211 driver. Elsewhere on the list I
read that this driver is know to have issues. Is it possible that
this is the problem?
Yes: the mac80211 driver does work sometimes but is also broken at other
times and I would definitely advise that
Simos Xenitellis wrote:
Product: Aztech WL230USB
USB ID : 0cde:001a (Z-Com)
Chip ID:
zd1211rw 3-2:1.0: zd1211 chip 0cde:001a v4810 high 00-60-b3 AL2230_RF
pa0 g---
zd1211rw 3-2:1.0: zd1211b chip 0cde:001a v4810 high 00-60-b3 AL2230_RF
pa0 g---
The ID is already on its way to be added to
Atheros sent me a new driver. The most significant change is a new
firmware version which fixes the disconnect problem when you run lsusb
or cat /proc/bus/usb/devices. Yay!
I will roll out new firmware for zd1211rw soon.
Su-Jong You wrote:
zd1211rw 1-1:1.0: zd1211b chip 0471:1237 v4810 high 00-12-bf AL2230_RF
pa0 g--N
I am on Ubuntu Feisty(7.04) i386. I just inserted my usbid(0471:1237)
into the linux image source code(2.6.20-16-generic) and recompiled it.
It has been working perfectly so far. I hope my
VinX wrote:
Why are present this IDs in your supported hardware list and in the
vanilla tree not?
The supported hardware list gets updated when we submit new IDs upstream
and not when they actually get into a released kernel. Your IDs will be
in 2.6.24-rc1 and onwards.
Daniel
Jeff Sadowski wrote:
Would it be possible to port the zd1211 driver to use the libusb interface?
To use as a network driver for network access? No, at least not under
Linux, because Linux has no way of accepting network data from userspace
(it can only come from kernel drivers).
Reason I
Jeff Sadowski wrote:
User space issue.
Could I not do the same thing as openvpn does to get a network node?
Maybe, that's an interesting idea, but I'm not at all familiar with that
stuff.
-
This SF.net email is
Shyjumon N. wrote:
I am trying to customize the zd1211rw driver for my ARM-11
board. On the target board i use the 2.6.18 kernel and I have done with
back porting of your new zd1211rw driver that I have downloaded from
http://dsd.object4.net/zd1211rw-strange-al2230s.tar.gz. I am
Hi Jun, sorry for the slow response.
Jun Sun wrote:
After a few debugging session, I finally found the the problem.
In the ieee80211_copy_snap() function in ieee80211_tx.c, the data pointer
lands on odd address. Later when ethertype is assigned, one byte is
chopped off. That is why 0x06 is
Hi,
Atheros provided a new vendor driver release.
http://dsd.object4.net/zd1211-vendor/releases/ZD1211LnxDrv_2_22_0_0.tar.gz
This driver is unsupported by me -- it probably doesn't compile on
recent kernels, as usual. If you need support, ask on the list and hope
that someone responds. Please
Andrey wrote:
I wonder if anyone has seen anything similar or knows of a solution.
Is zd1211rw expected to work with 200Mhz PCs? Is USB 1.1 well
supported? Am I out of luck with the 2.6.18.1 kernel?
USB 1.1 is not well tested, and while I wouldn't expect it to make a lot
of difference to the
Andrey wrote:
The adapter works well on Ubuntu 7.1, but I notice a large number of
errors in ifconfig output:
Nothing to worry about.
Daniel
-
This SF.net email is sponsored by: Microsoft
Defy all challenges.
David Santinoli wrote:
Dec 3 17:22:09 romilda kernel: zd1211rw 1-4:1.0: firmware version 4725
Dec 3 17:22:09 romilda kernel: zd1211rw 1-4:1.0: zd1211b chip 129b:1667
v4810 high 00-01-e3 AL2230S_RF pa0 ---N-
My kernel is a vanilla 2.6.23.9, and I'm using the zd1211rw driver that
comes
paracetamolo wrote:
Hello,
I bought a usb-rsma adapter:
http://www.wifi-link.com/product.php?action=productclass1_id=13class2_id=409class3_id=410product_id=994
that uses AL2230S, and has ID: 0ace:1215
Using Ubuntu with a custom kernel 2.6.23 the device shows up as I
connect it and it is
Bryan Donlan wrote:
I've retried using 2.6.23.12 (and this time I remembered to install
the firmware), but still no go. I've attached dmesg with SoftMAC and
zd1211rw debug on full. Again I'm able to scan for networks (although
some show as essid=hidden, the one I'm trying to connect to shows
My current host (object4.net) is going away. The vendor driver can now
be found here: http://www.reactivated.net/software/zd1211-vendor/
Daniel
-
This SF.net email is sponsored by: Microsoft
Defy all challenges.
Openschemes wrote:
I'm working with your ZDOFW disassembler. What type of input file is
it expecting? I have raw binary dumps of the ZD1211 (0xEE00) but the
output is minimal: Less that what I can determine disassembling by
hand.
Can you shed any light here? Thanks!
Please send
Giaramita Domenico wrote:
My issues is the following: when I set the use of WEP key on the AP and
I make mistakes on putting the wep key, the response of iwconfig command
still says to me the MAC adress of the AP; obviously the communication
is not possible because the wep-key was wrong.
Benoit PAPILLAULT wrote:
1. I did not receive junk packet so far with only enabling CR_SNIFFER_ON.
The reason we flip-flopped once or twice in the past is because
CR_SNIFFER_ON behaves wildly differently on different revisions of the
ZD1211 hardware.
Daniel
Benoit PAPILLAULT wrote:
Very good point. I have two hardware here : one is zd1211 and the other
is zd1211b. If I test with both, will it be ok?
IIRC, 2 of my ZD1211B devices behave differently.
Also, the reason that you lose performance is likely because the chip
will stop synchronizing its
101 - 180 of 180 matches
Mail list logo
