Hi,
Does anyone have any contacts inside ZyDAS who are involved with ZD1211
drivers and/or their Linux code?
Alternatively, has anyone received a response when emailing the
addresses listed on their website? If so, where has the response come from?
At the Linux Wireless Summit we
Hi,
Since yesterday, zd1211rw has become far more usable:
1. Monitor mode works.
2. Connectivity with WEP-encrypted networks through iwconfig works.
3. Connectivity with WPA-encrypted networks through wpa_supplicant
works, as long as you apply this kernel patch:
Remco wrote:
If you mean the 'reference_lock.patch', yes. If I'm not mistaken the
spinlock/unlock functions take the address of the lock, not the lock itself.
Correct, was just curious because I hadn't run into it.
Anyway, I passed your report onto Johannes Berg who set about
implementing
Remco wrote:
Apr 21 16:05:39 my-pc kernel: EIP is at
ieee80211softmac_auth_queue+0x15d/0x185 [ieee80211softmac]
Please do the following:
# cd /usr/src/linux (or whereever)
# rm net/ieee80211/softmac/ieee80211softmac_auth.o
# make CONFIG_DEBUG_INFO=y \
Unplugging and replugging the device is enough to
get things working again.
Not here, sorry, I wish that it was true...
But the problem is definitely just a disconnection (no kernel crash or
anything like that?)
---
Using Tomcat but
Greg KH wrote:
Also, I couldn't think of a better
name for the vendor id, if you can, please do (this device says it is a
ZyDAS device, yet another vendor id, yeah, fun...)
I'm not sure we'll keep with the vendor name #defines - I think Ulrich
pulled them from the vendor driver originally? We
Remco wrote:
Are you saying that softmac does the association on behalf of wpa_supplicant ?
Yes - wpa_supplicant doesn't really have much say in the process. All it
does is use WE to request association, and transmit and receive data
frames, as well as set the encryption parameters once
Guennadi Liakhovetski wrote:
ifconfig eth1 up
iwlist scan
iwconfig eth1 essid ...
You don't have to explicitly scan, but the trick is to only set an essid
after bringing the interface up.
ugly... Can we improve it?
It's on my todo list. It's not a driver bug, it needs to be fixed in the
Hi Bryan,
Bryan Rittmeyer wrote:
Thanks for zd1211rw. Here's a patch to add one of the TEW-429UB IDs
since it is basically working in Monitor mode:
Could you please send the chip ID string of your hardware alongside this
patch for archival purposes?
Also, if you could resubmit the other
Bryan Rittmeyer wrote:
usb 1-2.1.3: firmware device id 0x4330 and actual device id 0x4802 differ,
continuing anyway
zd1211rw 1-2.1.3:1.0: firmware version 4605
zd1211rw 1-2.1.3:1.0: zd1211 chip 157e:300b v4802 high 00-14-d1 AL2230_RF
pa0 g--
Thanks, added to my tree.
I will leave the kismet
Ulrich Kunitz wrote:
the clearing is definitely not in the performance-critical path
and is definitely faster then 10 milliseconds. On most
architectures is not even a function call. What I want to prevent
is the usage of structures, after they have cleared. A cleaned
structure will result in
Some comments on r79:
1. In recent kernels, all urbs are guaranteed to be killed before
disconnect() is invoked. This change was made to remove the number of
races like this. The only danger is of urbs which might resubmit
themselves in their callback handler (they must handle kill
Matthieu CASTET wrote:
I manage to associate to an AP, but when I ping the packet are sent tree
times :
- when I ping from the client to the AP, the AP see 3 ping request on sent
3 ping reply.
- when I ping from the AP to the client, the client see 1 ping request.
So it seem the packet
Matthieu CASTET wrote:
I check the intel driver and they seem to use radiotap only when
CONFIG_IEEE80211_RADIOTAP is defined.
But it seems CONFIG_IEEE80211_RADIOTAP is never defined in the 2.6.17.
Indeed - it is only the out-of-tree version which enables radiotap by
default. I didn't realise
Guennadi Liakhovetski wrote:
Is it known and just not implemented yet or is it just my dongle? With
the old driver the LED on my dongle blinked cheerfully during transfers
and just from time to time for fun:-) Now with rw it stays quiet:-(
That's correct. The vendor driver simply blinks the
Anes Lihovac wrote:
iwconfig eth1 key restricted [1] myWEPSecret
I'm increasingly shocked at the amount of people using shared key
authentication. Thankfully I fixed softmac's shared key auth anyway, you
need this patch:
Hi,
zd1211rw was merged into Linus' kernel tree just before 2.6.18-rc1 was
released.
We're still developing in external git repo's but having an early
version included in the mainline kernel should be beneficial for wider
development and testing.
Daniel
Using Tomcat but need to do more?
Harald Dunkel wrote:
iwconfig says:
wlan0 802.11g zd1211 ESSID:
Mode:Managed Frequency:2.412 GHz Access Point: Invalid
Bit Rate=1 Mb/s
Encryption key:------XX Security mode:open
Link Quality:0 Signal level:0 Noise
Harald Dunkel wrote:
Hi Daniel,
Sorry, of course I should have included more information
about the network configuration. Here is the entry in
/etc/network/interfaces:
Please drop the distro configuration and try using normal
ifconfig/iwconfig commands on the command line.
Daniel
Guennadi Liakhovetski wrote:
I am using the driver for my regular internet access, and the connection
seems to be unstable. Could we, perhaps, get some diagnostics from the
driver / softmac layer? Currently as the connection breaks there are no
messages... Would be extremely useful for
Hi,
The signal strength measurement code in zd1211rw doesn't seem to work at
the moment - the values it reads seem to be fairly inaccurate.
How well does signal strength measuring work for you users of the
vendor/community-maintained driver? There are clearly some drawbacks
with their code,
Guennadi Liakhovetski wrote:
You mean these 2 options:
# CONFIG_IEEE80211_DEBUG is not set
# CONFIG_IEEE80211_SOFTMAC_DEBUG is not set
No, I mean CONFIG_ZD1211RW_DEBUG
? The problem with them is - they are called full debugging, which
usually means noisy all the time up to unuseable
Hi,
I think I have an explanation for the unresolved zd1211rw failure
reports (rello, remco, a couple of others) that are floating around.
With zd1211rw, my ZD1211B device cannot connect to my network when
encryption is enabled. Well, it can associate, but data tx/rx does not
work. The vendor
Mattia Dongili wrote:
I'm trying out zd1211rw in mainline and I'm having some problems.
As soon as I plug the dongle and udev loads the firmware the leds are
shutting down and I can't subsequently use the wi-fi lan.
We don't do anything with the LED yet, so thats normal.
Does the vendor
Grr.. I can't get my ZD1211B connecting to unencrypted networks and
don't have any logs showing it ever worked. I must have made a mistake
in my earlier analysis (left the ethernet cable in or something!) -- I
am no longer sure that this is a bug related to packets encrypted in
software.
Mattia Dongili wrote:
I just tried, I get the same error as with r80 (failed intr_urb):
[ 186.648000]
[ 186.652000] _ _
[ 186.656000] |__ / _| _ \ / \ / ___|
[ 186.664000] / / | | | | | |/ _ \ \___ \
[ 186.668000] / /| |_| | |_| / ___ \ ___) |
[
Mattia Dongili wrote:
That would be great, but I can't see any patch attached :)
Index: linux/drivers/usb/core/urb.c
===
--- linux.orig/drivers/usb/core/urb.c
+++ linux/drivers/usb/core/urb.c
@@ -224,8 +224,10 @@ int
Mattia Dongili wrote:
Doh, I can't see any difference in the logs.
I'm pretty sure I booted the modified kernel,
strings usbcore.ko | grep -i 'too small'
confirms it.
Ok, that patch didn't cover all possibilities, just the most likely
ones. The EINVAL might come from later in the call
Remco wrote:
I have/had all the described problems with a ZD1211. With linux-2.6.18-rc1 /
wpa_supplicant 0.4.8 (no patches) things seem to have improved a bit.
What follows is just user experience, I just hope there's something useful in
it.
OK, yours seems to be different problem then.
For those who were having problems with monitor mode on zd1211rw, where
ethereal was only showing malformed packets (radiotap header parsing
bug): this is fixed in wireshark, the new ethereal.
Daniel
-
Take Surveys. Earn
Hi,
The changes made here are going to be partially reverted in zd1211rw:
http://zd1211.ath.cx/changeset/17
My ZyXEL G220F will not initialize unless this code is in place. More
specifically, WS11Ur and WS11Ub must be uploaded. Fortunately, the messy
routine (download the whole firmware,
Version 1.2 now available at http://zd1211.ath.cx/get-firmware
It includes the new firmware shipped in the most recent vendor driver.
This adds large packet support, I guess it might change other things too
but that is unclear.
I am planning to add large packet support soonish, otherwise
The snapshot to be generated in a few hours time includes a fix where I
couldn't use my ZD1211B device at all, and a fix where I couldn't
transmit data on encrypted networks on my ZD1211B device. I wrote some
mails about this to the list last week, all these issues are fixed.
The second fix
gerryst wrote:
Hi everyone
I'm running a vanilla 2.6.18-rc2 on a Gentoo box with some Zydas chip WLAN
USB stick.
I had some problems with previous kernels and updated to give the rw driver
a try.
somehow the zd1211rw module can't be loaded. This is what dmesg says on
bootup:
Hi,
caleb wrote:
I have the same problem with wusbf54g. Somebody's got ideas how to fix these
functions?
This USB adapter is getting more popular.
Scannig works fine, but adapter cannot set rate properly and ap MAC
address.
According to the windows driver, this device is a ZD1211B. Have
Guennadi Liakhovetski wrote:
20:53:50: usb 1-1.4: handle_retry_failed_int() retry failed interrupt
20:54:43: usb 1-1.4: handle_retry_failed_int() retry failed interrupt
Is it just weak signal? But failed interrupt (URB?) is suspicious...
It's not a failed interrupt, it's an interrupt
Guennadi Liakhovetski wrote:
This time - yes, it was automatic. To the user it looks like there's no
connection for some time and then it is back. Sometimes it never
recovers on its own, but ifdown+ifup / disconnecting and reconnecting the
dongle get a connection back. I think, it is
Guennadi Liakhovetski wrote:
are you planning on submitting your improvements / bugfixes for 2.6.18 or
are they only going into the wireless tree for after-2.6.18?
Fixes are going into 2.6.18, improvements are going into
wireless-2.6.git to be merged into 2.6.19. We have been sending patches
Ulrich Kunitz wrote:
This is the address of the invalid code. It's a pity that they
don't write out a normal kernel oops, which would give us much
more information. Look into /proc/modules and /boot/System.map*
to check where it is. If it is in zd1211 you can uses
nm -n -g zd1211.ko to find
Martin Dummer wrote:
Hi,
I have a success message for the
Siemens Gigaset USB Stick 54
Thanks! Added to my tree.
Daniel
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly
Ulrich pointed out that trendware have released a new device (Trendware
Trendnet TEW-429UF)
http://www.trendware.com/products/TEW-429UF.htm
This device is based on ZD1211 and includes a hotspot finder, as well as
512mb (R/W) flash memory.
Another interesting point is that it is not advertised
arandamandi wrote:
Hi,i follow instruction for zd1211-rw
i have new kernel 2.6.18
my device is zyxel g-air 220
i have first edited usb.c on kernel sources and
add my usb id,then i configure network
with rate=54M (i'm on slackware current)
Drivers works,wpa too but there is a problem
rate
Elimar Riesebieter wrote:
Hi all,
I am running
zd1211rw 4-1:1.0: firmware version 4605
zd1211rw 4-1:1.0: zd1211 chip 6891:a727 v4330 high 00-14-7c RF2959_RF pa0 g---
IEEE 802.11b/g ESSID:BLO Nickname:zd1211
Mode:Managed Frequency:2.462 GHz Access Point: XX:XX:BB:LL:KK:00
Bit
Elimar Riesebieter wrote:
I have a wired interface eth0 and the wireless one which was
detected as eth1 but named as eth3. How do I fix the name of the
wireless stick to eth1? I've played with udev:
KERNEL==eth*, SYSFS{address}==AA:BB:CC:DD:EE:FF, NAME=eth1
or
KERNEL==eth*,
Matthieu CASTET wrote:
Daniel, Ulrich is it possible to know if the firmware is already loaded ?
I wanted to use zd_ioread16_locked(chip, version, FW_FIRMWARE_VER);, but
it need context that aren't available at firmware_upload time.
I don't know, and we generally don't get to know fine details
Christoph Biedl wrote:
My system is running Debian testing (etch) on kernel 2.6.18. In order to
have the firmware loader find the firmware, I had to issue some commands
first:
ln -s /usr/lib/hotplug/firmware /lib/firmware/zd1211
cd /lib/firmware/zd1211
ln -s zd1211-WS11Ub.fw zd1211b_ub
ln
Harald Dunkel wrote:
Doesn't this mean that iwconfig should wait till the softmac
stuff has been completed, either on the first or second run?
No.
It's not a great system but is going to be replaced in the nearish future.
Daniel
Hans Dingemans wrote:
Hello all,
This posting is for all who are having problems to get a zd1211b based usb
wifi device working on Mandriva 2006.
Problems that crossed my path:
1) Device does not connect to ap. Solution: use a recent driver version of
zd1211rw (look at
Santiago Capel wrote:
Hi, I've got a USB stick whose usbid is 083a:4505
Neat, we didn't know which product this ID referred to until now.
The make printed on the stick is: SMC Ez Connect(tm) g
The model is: SMCWUSB-G
IC: 4711A-WN4501H
FCC ID: RAXWN4501H
Description: 802.11g Wireless Lan
Matthieu CASTET wrote:
Hi,
any new about the hw encyption status ?
Not really, I have some emails to go through and more testing to do.
Feel free to take over, I'm low on time at the moment.
There was a patch for the RX path (and I asked questions about MIC
checking), but there no news on
eric magaoay wrote:
I have a question regarding the zd1211rw firmware. Is it supposed to be
included within the latest stock kernel (I'm using latest kernel
development version of Fedora Core 6 - soon to be release -
2.6.18-1.2798.fc6-xen) or does it require user/distribution download and
Matthieu CASTET wrote:
It is not really GPL as GPL ask to deliver the preferred form for
modification and I don't think Zydas write their firmware in hexa ;)
The GPL doesn't place restrictions on what can and can't be licensed.
The firmware *is* GPL, even though it is hex and is kinda silly.
Matthieu CASTET wrote:
Hi,
the EP_REGS_OUT endpoint on my device is interrupt not bulk [1].
This cause the problem described on
http://marc.theaimsgroup.com/?l=linux-usb-develm=116129264007056w=2 [2]
.
Why are we using bulk urb on an endpoint declared as interrupt ?
Should that be
eric magaoay wrote:
OK, I just installed Ubuntu 6.10 RC1 (edgy). zd1211rw/firmware are
included in the kernel (2.6.17-10-generic) and is fully functional
without having to download the firmware from http://www.deine-taler.de.
(thumbs up for Ubuntu)
They don't ship the firmware in the
Andreas Gick wrote:
Hello altogether,
after downloading the git-kernel-sources, I found the modules in the kernel
tree, but couldn't figure out, how to select them in order to build them. So
how do I accomplish this?
Use the search feature, type /ZD1211RWenter while in menuconfig. If it
Hi,
Igor Dragicevic wrote:
Hi Eric,
when I plug the device in, nothing happens. ;-)
sudo lsmod dosn't show any zd1211rw module loaded.
iwconfig doesn't show any wireless interfaces.
The G220 ID was only added very recently, it takes time for this to
propagate through the kernel
Andreas Gick wrote:
Hi everybody,
after successfully loading the zd1211rw module, I encounter problems
regarding the WEP-encryption. It fails with the message: SET failed on device
eth2; operation not supported. As I don't have any clue on how to solve this
issue I added the output of dmesg
Guennadi Liakhovetski wrote:
Yes, reverting that commit fixes the problem. I don't understand the
comment there saying that those packed attributes were unneeded... From a
quick view they DO seem to be needed - those are indeed structs mapped on
data blocks received from hardware. The
Tetsuya Yatagai wrote:
Success with in-kernel version (2.6.19-rc4) , snapshots firmware
(2006-11-02)
and wpa_supplicant (TKIP).
The brand and retail product name of your device
Planex GW-US54Mini
Thanks! Added.
Daniel
Hi,
With help from Johannes Berg, I've been working on reverse engineering
the firmware to try and understand the instruction format. Assuming we
can figure out all of the instructions, the end result is that we'll be
able to produce an open source firmware.
So far I've built up a partial
Guennadi Liakhovetski wrote:
Please restore your git tree to the working state.
Unless Ulrich objects I'll request that this gets reverted for 2.6.19.
We can always try again for 2.6.20.
Daniel
-
Take Surveys. Earn Cash.
walter harms wrote:
hi list,
i got hold of a second longshine lcs8131G3 for testing an noted something odd.
The second also gets attached to eth1.
The driver names itself with ethX as you can see in dmesg. If yours
appears later as wlan0 it means that your distro has renamed it soon
after it
Eric Goff wrote:
Some interesting tidbits from dmesg:
zd1211rw 2-6:1.0: firmware version 4605
zd1211rw 2-6:1.0: zd1211 chip 07b8:6001 v4330 high 00-12-0e AL2230_RF pa0 g--
zd1211rw 2-6:1.0: eth1
SoftMAC: empty ratesinfo?
SoftMAC: empty ratesinfo?
SoftMAC: empty ratesinfo?
SoftMAC: empty
Elimar Riesebieter wrote:
using latest wireless-dev makes kismet working with the bcm43xx
kismet source. But after quitting kismet, the device is still hold
on monitoring mode? This is using wpa2-psk. I have to restart the
network to get back to managed mode. iwconfig eth1 mode managed
didn't
unibrow wrote:
Oh, and the reason I think it uses the AL2230_RF transmitter is because
that's what dmesg | grep 'zd1211b\? chip' told me (zd1211rw 1-5:1.0:
zd1211b chip 0471:1236 v4810 high 00-12-bf AL2230_RF pa0 g--, to be
precise).
Thanks, added to my tree
Matthieu CASTET wrote:
I use a small program to dump the memory :
http://castet.matthieu.free.fr/tmp/debug_ctrl0.c
I compared the eeprom state before and after firmware load.
I notice only 0xffe9-0x changed.
Also 0xfff7-0x where like memory address (and of course
LOAD_VECT_SIZE =
matthieu castet wrote:
Daniel Drake wrote:
Matthieu CASTET wrote:
Thanks for looking into all that. This just started happening on one
of my devices (ZD1211B) - it cannot survive a rmmod/insmod cycle
without me having to unplug it. Same problem with the vendor driver.
Same for reboots
Henrik Hjelte wrote:
Brand: Linksys
Retail name:
Linksys Wireless-G USB Network Adapter with Wi-Fi Finder
Thanks, added to my tree
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay
Michel Salim wrote:
Is this an issue with the firmware version mismatch, or something else?
Something else. Please try without using network manager or any other
configuration agents. That way you get a good grasp of the point of failure.
Daniel
Jon Smirl wrote:
It looks to me like Ubuntu told the interface to initialize and then
told it to associate before the initialization was complete.
No - your trace clearly shows that it is setting security keys and
trying to associate *before* the interface is brought up.
Daniel
Hi,
The ZD1211 download page has been removed from Atheros.com, but ZyDAS
sent me a new driver release.
You can download it from:
http://dsd.object4.net/zd1211-vendor/releases/
Large packet support is now disabled by default due to the reboot/module
reload problems that the large packet
Harald Dunkel wrote:
Jon Smirl wrote:
The rate is not set automatically
iwconfig eth0 rate 54M
My configuration says to do
Harald and others,
Please read the zd1211rw driver home page. It would have saved some
people the effort of mailing the list over the last couple of weeks :)
Matthieu CASTET wrote:
BTW doing the reset in probe seems to work with new firmware :
http://castet.matthieu.free.fr/tmp/zd_reset.diff
What do you mean by 'new firmware'? Does this work on all of:
cold plugin
warm rmmod/insmod
warm reboot
Daniel
athoslnx wrote:
1)Airoha AL2230S_RF it is supported?
On which driver? Do you have one?
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
Jon Smirl wrote:
I just spent a while with Windows booted on the same hardware. With no
trouble at all I am able to achieve 19Mb/sec of useful file copy
throughput.
Matching the windows driver behaviour is hard, since we don't have the
source. A much more worthwhile test would be using the
Armando Romero wrote:
Obviously the kernel driver compiled in my 2.6.19-1, zd1211rw gives no
functionality to my 3COM 3CRUSB10075 .
Is there any pointer what I shall do to get it working with kernel driver?
It's probably a distro bug. Turn off your configuration utilities and
configure the
Armando Romero wrote:
I have tried zd1211rw from 2.6.19-1 and I did not get it working,
although the kernel has all other modules and configurations like 2.6.15
I am using now with extra driver.
If you were using ZD1211 hardware on 2.6.15 then you were using a
different driver so you cannot
Marijn Schouten wrote:
Hi list,
I tested the driver included with 2.6.19-gentoo-r2 kernel. It is a Zyxel
ZyAIR G-220 v2.
Thanks, added to my tree.
Daniel
-
Take Surveys. Earn Cash. Influence the Future of IT
Join
http://zd1211.ath.cx/get-firmware
This is the firmware from vendor driver 2_16_0_0.
Large packet support is now disabled (zd1211rw does not support this
anyway). The zd1211 firmware is now the same as v1.1 but the zd1211b
firmware is new: It is the same which is shipped in the 2.10.0.0 release
Here is my current grasp of the situation:
zd1211-firmware-1.2 is BROKEN and will cause this issue on most devices.
Don't use this firmware version.
Assuming a 'good' firmware such as v1.3, original ZD1211 devices work
just fine.
Bad firmware aside, ZD1211B devices are the ones which suffer
Romain Liévin wrote:
VID/PID is 050d/705C and the chip is a ZD1211B.
I used the zd1211rw driver provided with a vanilla kernel 2.6.19.1 running
on a dual Turion64 (x86_64 SMP with ACPI on).
Thanks for testing. This device has already been reported as working so
the ID addition is on its way
Shu Hung (Koala) wrote:
Hello,
I'm using Planex GW-US54GZL
http://www.planex.net/product/wireless/gw-us54gzl.htm adapter on my
Ubuntu Dapper (6.06LTS). Although I want to upgrade to Ubuntu 6.10 or
later, the adapter does not work on those. It seems that after you
rewrote the driver for
Jon Smirl wrote:
Do any of the zd1211 based devices do 802.11a? All of the ones I can
locate are 11b/g only.
http://zd1211.ath.cx/wiki/RfTypes
-
Take Surveys. Earn Cash. Influence the Future of IT
Join
Peter Lueg wrote:
we are using the NUB-8301 (zd1211 with AL7230B rf module) in a portable
device. In order to length the uptime we need to reduce the power
consumption. WLAN is the top power consumer it deems necessary to
implement powersave mode on the zd1211rw driver.
What is the status?
I'd like to get my hands on an AL2230S device and then add support for
it in zd1211rw. There seem to be a few around.
Is anyone willing to send me one? Reimbursement is possible. I am
currently US-based.
Thanks!
Daniel
-
I'm looking for an original ZD1211 device (i.e. non-ZD1211B). My last
one broke. It would make diagnosing these reboot/replug issues more
definite.
Does anyone have a current source for these, or is someone willing to
send me one? Reimbursement is possible.
Thanks,
Daniel
I haven't seen the replug issues in a while, but previously had them
quite a bit with my ZD1211B.
I'm running (near enough) 2.6.20-rc6 with the following patch added:
http://marc.theaimsgroup.com/?l=linux-netdevm=117003239100898q=raw
Earlier testing shows that the above patch alone wasn't
Ulrich Kunitz wrote:
I don't know. On the web page http://www.atheros.com/RD you still
can find the contact data of sales personnel.
My company inquired to both the Taiwan sales contact and the main
Atheros sales contact addresses about ordering a large stock of ZD1211
devices. They did not
Pekka Savola wrote:
Also, if I manually do 'ifconfig eth1 up' before ESSID is set, it'll
work without problem.
This is a distro bug - it should bring the interface up before using it.
Many drivers require the interface to be up before scanning is possible,
since for a lot of hardware,
Pekka Savola wrote:
I started with AP 1, then moved (with the WLAN interface enabled, only
30 meters) next to another AP 2. AP 1 is still heard with ~20/100
Link quality and ~15/100 Signal level.
The driver doesn't seem to switch to using the new AP. I'd expect
this to happen
Andy Green wrote:
I think in managed mode the firmware in the stick insists that valid
packets are marked up with either the AP or your MAC address, or some
similar strict regime.
I have also seen in monitor mode nearby transmissions on different
channels (!) turning up on another
Jon Smirl wrote:
If could be that these noise packets are being received in Managed
mode and the firmware is eliminating them.
Yes -- Andy Green pointed this out earlier today and he is entirely
correct. This behaviour is expected. I think in this case the filtering
is done in hardware, as
Hi,
A user came on IRC with a UW2453 ZD1211 device. This is the first
instance that I've seen one of these RF chips. Then later today there
was a mail to this list from someone else.
ZyDAS confirmed that currently their major models are UW2453 and
AL2230S, neither of which are supported by
Robert Schulz wrote:
what to do now?
What device is it (product name/manufacturer)? Which USB ID's?
I'm getting one of these sent to me, should be able to get it supported
in zd1211rw soon.
You can temporarily use the vendor driver (2.16.0.0) to get
connectivity. It won't work with the
Diego Sevilla Ruiz wrote:
Now I updated to Ubuntu Feisty and it doesn't work. The 2.6.20
kernel doesn't recognize the USB even when I load manually the zd1211rw
driver. I tried the different firmwares and also didn't work.
Please provide some actual information. Which device, which USB
Diego Sevilla Ruiz wrote:
Hi, Daniel:
I'm sorry, I was really tired after an evening of trying to
configure the card...
OK, here is the detailed data: I bought a SMC ez-connect g
wireless USB. (SMCWUSB-G) USB id: 083a:4505. I downloaded the community
driver r83 plus the
Hi Richard! Remember me?
Richard Hughes wrote:
SoftMAC: Scanning finished: scanned 11 channels starting with channel 1
SoftMAC: Queueing Authentication Request to 00:11:95:19:a7:4c
SoftMAC: Cannot associate without being authenticated, requested
authentication
SoftMAC: Sent Authentication
Hillier, Gernot wrote:
If there's nothing available yet: is this a huge task or something which a
more-or-less-kernel-newbie with an absolute lack of WLAN knowledge could dig
into in a reasonable time frame? Any pointers?
Up until recently, the biggest thing holding this functionality back
XtSI wrote:
Hi there,
I recently bougth a MSI WLAN Stick (US54SE). The reason was to exchange an
old DLINK DWL-120 11 MBit Interface that gave me an maximum of 2 MBit/s.
It is running on an EPIA M1 board with kernel 2.6.18-2.
Airoha AL2230S_RF
zd1211:Mixed Mode
The AL2230S is very new
Robert Schulz wrote:
Hi Daniel!
I could compile the ZD1211LnxDrv_2_16_0_0.tar.gz with 2.6.17-10 - find syslog
beneath.
Does not help me, since this module made my keyboard driver crash (as did the
zd1211-driver-r83) - not being able to type any more and shutdown hangs too.
Sorry, I
1 - 100 of 180 matches
Mail list logo
