Re: [zd1211-devs] Experiences with an unsupported device (USB 0cde:001a)
On Dec 21, 2007 6:22 AM, Daniel Drake <[EMAIL PROTECTED]> wrote: > 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="", the one I'm trying to connect to shows > > up properly), but I can't associate. wavemon shows 0 for RX and all > > signal levels. > > It's not clear what's going wrong, there does not seem to be any > response to the association request. As the next step you could try the > vendor driver, or you could run another wireless device in monitor mode > and watch the traffic. Is the association request from the device > "hitting the air"? Is the access point sending an association response > to the device? Hi, The tests before I performed on my school's open wireless network. I'm now at home, where we have a WEP-secured network. In this case the network isn't even appearing in a scan; I just get: eth2 Scan completed : Cell 01 - Address: 00:0F:3D:37:FB:02 ESSID:"" Protocol:IEEE 802.11bg Mode:Master Frequency:2.437 GHz (Channel 6) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 9 Mb/s; 11 Mb/s 6 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality=100/100 Signal level=58/100 Extra: Last beacon: 259ms ago The access point address and channel are correct, but the ESSID is blank there. Also, how would one put another device into monitor mode? It'd have to be something I can use from a livecd... Thanks, Bryan Donlan - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Experiences with an unsupported device (USB 0cde:001a)
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="", the one I'm trying to connect to shows > up properly), but I can't associate. wavemon shows 0 for RX and all > signal levels. It's not clear what's going wrong, there does not seem to be any response to the association request. As the next step you could try the vendor driver, or you could run another wireless device in monitor mode and watch the traffic. Is the association request from the device "hitting the air"? Is the access point sending an association response to the device? Daniel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] Experiences with an unsupported device (USB 0cde:001a)
On Dec 19, 2007 3:43 PM, Bryan Donlan <[EMAIL PROTECTED]> wrote: > Hi all, > > I've recently come across a device which seems to have a zd1211 chip, > but whose USB ID (0cde:001a) was not in the current driver. After > adding the USB ID to the ubuntu 2.6.22-14 kernel and insmodding > zd1211rw.ko, I was able to get the driver to perform a scan, but it > would not associate to a network. [snip] 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="", the one I'm trying to connect to shows up properly), but I can't associate. wavemon shows 0 for RX and all signal levels. Commands used to try to associate: ifconfig eth2 up iwconfig eth2 essid tempest dhclient eth2 I'm using the 1.4 firmware tarball. [ 888.736593] usb 2-1: new high speed USB device using ehci_hcd and address 3 [ 888.855043] usb 2-1: configuration #1 chosen from 1 choice [ 888.855934] usb 2-1: print_id() 0cde:001a v4810 high [ 888.958294] usb 2-1: reset high speed USB device using ehci_hcd and address 3 [ 889.069195] zd1211rw 2-1:1.0: zd_netdev_alloc() netdev->flags 0x1002 [ 889.069660] zd1211rw 2-1:1.0: zd_netdev_alloc() netdev->features 0x [ 889.070018] zd1211rw 2-1:1.0: zd_chip_read_mac_addr_fw() [ 889.073256] zd1211rw 2-1:1.0: probe() successful [ 889.073714] zd1211rw 2-1:1.0: eth1 [ 889.075905] net eth2: device_rename: sysfs_create_symlink failed (-17) [ 898.106180] zd1211rw 2-1:1.0: zd_usb_init_hw() [ 898.106191] usb 2-1: request_fw_file() fw name zd1211/zd1211_ub [ 898.110525] usb 2-1: firmware version 0x4330 and device bootcode version 0x4810 differ [ 898.110534] usb 2-1: request_fw_file() fw name zd1211/zd1211_ur [ 898.117385] usb 2-1: upload_code() transfer size 3584 [ 898.123153] usb 2-1: upload_code() firmware confirm return value 0x01 [ 898.123162] usb 2-1: upload_code() transfer size 3720 [ 898.132792] usb 2-1: upload_code() firmware confirm return value 0x01 [ 898.132827] usb 2-1: request_fw_file() fw name zd1211/zd1211_uphr [ 898.137934] usb 2-1: upload_code() transfer size 4096 [ 898.145168] usb 2-1: upload_code() transfer size 1024 [ 898.147412] usb 2-1: upload_code() firmware confirm return value 0x01 [ 898.147291] zd1211rw 2-1:1.0: zd_usb_enable_int() [ 898.147666] zd1211rw 2-1:1.0: zd_usb_enable_int() submit urb db805180 [ 898.148048] zd1211rw 2-1:1.0: zd_chip_init_hw() [ 898.150280] zd1211rw 2-1:1.0: dump_cr() CR_AFTER_PNP 0x [ 898.152525] zd1211rw 2-1:1.0: dump_cr() CR_GPI_EN 0x [ 898.154284] zd1211rw 2-1:1.0: dump_cr() CR_INTERRUPT 0x [ 898.156348] zd1211rw 2-1:1.0: read_fw_regs_offset() fw_regs_base: 0xf7d4 [ 898.159279] zd1211rw 2-1:1.0: read_pod() E2P_POD 0x0184 [ 898.159288] zd1211rw 2-1:1.0: read_pod() RF AL2230_RF 0x4 PA type 0x0 patch CCK 1 patch CR157 0 patch 6M 0 new PHY 0 link LED2 tx led 1 [ 898.159292] zd1211rw 2-1:1.0: hw_init() [ 898.159296] zd1211rw 2-1:1.0: zd1211_hw_reset_phy() [ 898.161274] zd1211rw 2-1:1.0: zd_chip_lock_phy_regs() CR_REG1: 0x00 -> 0x00 [ 898.166270] zd1211rw 2-1:1.0: zd_chip_unlock_phy_regs() CR_REG1: 0x00 -> 0x80 [ 898.171442] zd1211rw 2-1:1.0: zd1211_hw_init_hmac() [ 898.169271] zd1211rw 2-1:1.0: get_aw_pt_bi() aw 0 pt 0 bi 0 [ 898.169290] zd1211rw 2-1:1.0: set_aw_pt_bi() aw 0 pt 99 bi 100 [ 898.171279] zd1211rw 2-1:1.0: zd_chip_lock_phy_regs() CR_REG1: 0xa0 -> 0x20 [ 898.173394] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x003f790 bits 24 [ 898.178793] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x001 bits 24 [ 898.180788] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x00d bits 24 [ 898.182787] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x00b3331 bits 24 [ 898.184793] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x003b812 bits 24 [ 898.186782] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x000fff3 bits 24 [ 898.188784] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x824 bits 24 [ 898.190783] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0xda4 bits 24 [ 898.192782] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x00f4dc5 bits 24 [ 898.194780] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x00805b6 bits 24 [ 898.196788] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x0011687 bits 24 [ 898.198781] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x688 bits 24 [ 898.200781] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x00403b9 bits 24 [ 898.202780] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x000dbba bits 24 [ 898.204780] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x99b bits 24 [ 898.206778] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x00bdffc bits 24 [ 898.208780] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x00d bits 24 [ 898.210779] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x000500f bits 24 [ 898.213028] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x000d00f bits 24 [ 898.213903] zd1211rw 2-1:1.0: zd_usb_rfwrite() value 0x0004c0f bits 24 [ 898.21677
[zd1211-devs] Experiences with an unsupported device (USB 0cde:001a)
Hi all, I've recently come across a device which seems to have a zd1211 chip, but whose USB ID (0cde:001a) was not in the current driver. After adding the USB ID to the ubuntu 2.6.22-14 kernel and insmodding zd1211rw.ko, I was able to get the driver to perform a scan, but it would not associate to a network. dmesg output: [ 169.884000] usb 1-2: reset high speed USB device using ehci_hcd and address 2 [ 170.152000] usb 1-2: firmware version 0x4330 and device bootcode version 0x4810 differ [ 170.26] zd1211rw 1-2:1.0: firmware version 4605 [ 170.304000] zd1211rw 1-2:1.0: zd1211 chip 0cde:001a v4810 high 00-60-b3 AL2230_RF pa0 g---S [ 170.304000] zd1211rw 1-2:1.0: eth0 [ 170.304000] usbcore: registered new interface driver zd1211rw [ 215.328000] SoftMAC: Open Authentication completed with 00:0f:24:11:19:f0 lsusb -vv: Bus 001 Device 003: ID 0cde:001a Z-Com Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize064 idVendor 0x0cde Z-Com idProduct 0x001a bcdDevice 48.10 iManufacturer 16 ZyDAS iProduct 32 USB Device iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Unfortunately, I do not know the vendor name of the device; it's something I'm borrowing from a friend. It is labelled with: FCC ID: M4Y-XG-760N MODEL: XG-760N S/N: 32050157041400667 MAC: 0060B3106D77 I'll be trying this with the latest kernel.org tree next. - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
