On Thu, 2009-07-23 at 08:46 +0200, Holger Schurig wrote: > > Web search for 1286:1fab doesn't find anything useful other > > than recommendations to use ndiswrapper. > > It might be some 802.11n (marketing speak "Top Dog") thingy ??? That's very unlikely. ZEW2502 is advertised as 802.11b/g and it's dirt cheap ($20). Besides, its ID 1286:1fab suggests that it's probably a predecessor of 1286:2001 that is supported by the kernel drivers. In case it matters, its FCC ID is T58331GU2006M1. Some sites say its chipset is "Marvell 88W8338 + 88W8010", see e.g. http://www.xpcgear.com/zew2502.html I modified both libertas drivers to support that ID. usb8xxx asks for usb8388.bin. After I installed that firmware, usb8xxx started panicking with so many messages that the interesting part scrolls from the screen. I could try to capture that with a serial console. It's clearly not the right way to react to bad hardware. As for libertas_tf_usb, it does something strange. It registers a phy that only supports monitor mode. No network device is registered. I can add it using iw. If I try to bring the interface up, the driver requests lbtf_usb.bin. Whether that file is present of not, ifconfig hangs, and all subsequent network commands on other terminals hang too. Apparently, error handling in libertas drivers needs some improvement, regardless of whether ZEW2502 is a potentially supported device. The device is supported by ndiswrapper with the x86_64 WinXP driver. Scanning works, but wpa_supplicant fails. That's just to verify that the device is functional. -- Regards, Pavel Roskin -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
