In short, I did not get it working. It's quite likely that I've just missed something.
Here is my report according to http://zd1211.ath.cx/wiki/UntestedWithRewrite * The brand and retail product name of your device Zyxel G-220 v2 * The USB IDs 0586:340f The chip ID string, which can be read by: # dmesg | egrep "zd1211b? chip" | zd1211rw 6-1:1.0: zd1211b chip 0586:340f v4810 high 00-13-49 AL2230_RF pa0 g-- * The FCC ID of your product, if it is is visible. 188G220V2 A friend of mine got that device, he lended it to me for some testing. It seems like | { USB_DEVICE(0x0586, 0x340f), .driver_info = DEVICE_ZD1211B }, for drivers/net/wireless/zd1211rw/zd_usb.c was the right choice. 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 -s zd1211-WS11UPhR.fw zd1211b_uphr [ found at http://antares.escomposlinux.org/?p=326 thanks! ] A bit astonishing: The built-in blue LED turns off as soon as the driver module is loaded. Some lines from syslog: | usb 6-1: new high speed USB device using ehci_hcd and address 8 | usb 6-1: configuration #1 chosen from 1 choice | usb 6-1: firmware device id 0x4330 and actual device id 0x4810 differ, continuing anyway | zd1211rw 6-1:1.0: firmware version 4605 | zd1211rw 6-1:1.0: zd1211b chip 0586:340f v4810 high 00-13-49 AL2230_RF pa0 g-- | zd1211rw 6-1:1.0: eth1 | usbcore: registered new driver zd1211rw To my big surprise the newly created device is actually eth2. Now I can scan the network and find my 11g access point. All ieee80211_crypt* modules were loaded. However, association is not possible and I get a lot of | SoftMAC: Authentication timed out with 00:14:bf:**:**:** The wpasupplicant configuration was taken from another wlan card with a different hardware where it works without any problems so it's hopefully correct. Basically it is iface eth2 inet dhcp wpa-driver wext wpa-ssid <my id> wpa-key-mgmt WPA-PSK wpa-psk <my psd> (This is Debian's /etc/network/interface style, a handcraftet wpa-supplicant.conf didn't help either) My wisdom ends here. What could I try next? Christoph
signature.asc
Description: Digital signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
