Edgy: Multiple issues with ZyDAS, zd1211rw, Network Manager
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Apologies for a non-attributed and wide ranging bug report. I have a 3COM 3CRUSB10075 USB 54g wifi card. This uses the ZyDas 1211 chipset. I have multiple issues with it on i386 and PPC (major).
* On i386, it connects using WPA with network manager. It is listed by NM as having being "Unknown USB Vendor Specific Interface";
* On i386, it comes up as a 11Mb/s device. It can be changed to 54M using iwconfg and then gives 54M like performance (2.3 MB/s transfers).
* dmesg reports ?errors?:
zd1211rw 4-3:1.0: firmware version 4725
[17733109.772000] zd1211rw 4-3:1.0: zd1211b chip 0ace:1215 v4810 high
00-16-e0 AL2230_RF pa0 ---
[17733109.772000] zd1211rw 4-3:1.0: eth2
[17733109.932000] ADDRCONF(
[17733130.876000] SoftMAC: Open Authentication completed with
00:14:7c:ad:a8:54
[17733130.892000] ADDRCONF(
[17733131.092000] TKIP: replay detected: STA=00:
000000000001 received TSC 000000000001
[17733145.276000] eth2: no IPv6 routers present
[17734399.204000] TKIP: replay detected: STA=00:
000000000166 received TSC 000000000166
[17734399.740000] TKIP: replay detected: STA=00:
000000000470 received TSC 000000000470
I do not get these replay reports with either a RT2500 or Intel 2200BG.
* On PPC (Powerbook G4 via PCMCIA USB2 card or direct USB 1.1 ports), then the device will never connect to the AP using network manager, however the kernel is seeing the AP.
Nov 21 15:06:12 localhost kernel: [ 754.895674] SoftMAC: Open Authentication completed with 00:14:xx:xx:xx:xx
* Occassionally the device may be brought to live on PPC by removing NM and configuring manually:
ifconfig eth2 up
iwconfig essid FOO-WIFI eth2
iwlist scan eth2
wpa_supplicant -Dwext -i eth2 -c .......
dhclient2 eth2
After this, most times it only works one way (I can ssh off the box but not on); very rarely it works both ways and even more rarely, at 54M speeds (after manual rate setting).
Thanks for taking the time to report this bug.
Feisty have new driver, still have problems?