Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
$ lsusb -d 0cf3:1006
Bus 002 Device 003: ID 0cf3:1006 Atheros Communications, Inc.
using kubuntu/ubuntu 9.10 and followed your instructions
installed linux-ckports-modules-2.6.31-14-generic
sudo modprobe -i zd1211rw
echo "0cf3 1006 FFFFFFFF FFFFFFFF 0 0 1" | sudo tee -a /sys/bus/usb/drivers/zd1211rw/new_id
Since I plugged the usb stick, dmesg showed
Code:
[ 130.152120] usb 2-3: new high speed USB device using ehci_hcd and address 3
[ 130.301235] usb 2-3: configuration #1 chosen from 1 choice
[ 170.199547] usbcore: registered new interface driver zd1211rw
[ 177.329270] usb 2-3: reset high speed USB device using ehci_hcd and address 3
[ 182.481239] usb 2-3: read over firmware interface failed: -110
[ 182.592291] usb 2-3: reset high speed USB device using ehci_hcd and address 3
[ 182.741076] zd1211rw: probe of 2-3:1.0 failed with error -110
[ 897.597060] CE: hpet increasing min_delta_ns to 15000 nsec
Running iwconfig doesn't show my new card. It does, however, show the old card that stopped working a month ago.
Yes, it looks like the driver was recognized and paired with the device. This device also requires extra firmware, which Ubuntu provides. zd1211rw - Linux Wireless
This is about the only reference I could find to "read over firmware..." It's the patch to the driver and includes that error output. Perhaps someone with more knowledge of code can better decipher the problem.
Code:
+/* Read data from device address space using "firmware interface" which does
+ * not require firmware to be loaded. */
+int zd_usb_read_fw(struct zd_usb *usb, zd_addr_t addr, u8 *data, u16 len)
+{
+ int r;
+ struct usb_device *udev = zd_usb_to_usbdev(usb);
+
+ r = usb_control_msg(udev, usb_rcvctrlpipe(udev, 0),
+ USB_REQ_FIRMWARE_READ_DATA, USB_DIR_IN | 0x40, addr, 0,
+ data, len, 5000);
+ if (r < 0) {
+ dev_err(&udev->dev,
+ "read over firmware interface failed: %d\n", r);
+ return r;
+ } else if (r != len) {
+ dev_err(&udev->dev,
+ "incomplete read over firmware interface: %d/%d\n",
+ r, len);
+ return -EIO;
+ }
+
+ return 0;
You may also be able to build the old zd1211 driver. All the info I could find on it is pretty out of date though. (Which makes sense, as it was discontinued and the community developed zd1211rw took over.) https://help.ubuntu.com/community/Wi...sterMode#ZyDAS ZD1211
Can it be recognized only because i did beforwards:
Code:
echo "0cf3 1006 FFFFFFFF FFFFFFFF 0 0 1" | sudo tee -a /sys/bus/usb/drivers/zd1211rw/new_id
?
I also found zd_usb_read_fw function myself (this lead me to -ETIMEDOUT), but does not give me a clue, what does it means, what really happens. Should I enable kernel debugging? Will it give more information in dmesg?
(In /boot/config-2.6.31-14-generic (presumably the config for my current 2.6.31-14-generic ubuntu kernel) there is CONFIG_DEBUG_KERNEL=y.)
The patch "[PATCH] zd1211rw: Defer firmware load until first ifup" was included in kernel v2.6.23-rc1, and it's naturally also in my kernel (tag 'Ubuntu-2.6.31-14.48' in Ubuntu kernel repo).
Thank you for all the help. A while ago I started discussion on linux-wireless mailing list (at kernel.org; search for 0cf3:1006 or WN422G in the archives) and they suggested
Quote:
If you take a look at the vendor's windows driver for TP-LINK WN422G *v2*,
it becomes obvious that the device does not use the ZyDAS zd1211/ Atheros
5007UG cipset, but has switched to the new Atheros AR9271 chipset
[...]
At this moment a new driver called ath9k_htc is under (early) development:
wireless.kernel.org/en/users/Drivers/ath9k_htc
I haven't checked the windows drivers yet, so can't confirm i have "v2". Anyway I won't be copying the list here any further, so i encourage anyone interested in my story (or just having similar device to digg the linux-wireless recent archives.
As to the ndiswrapper. I know it's not hard, I have already used it on different machine with different card. Maybe it's due to particular windows driver in use, but i see way too often oopses with 'ndis' somewhere in the stacktrace
A Newbie's Getting Started Guide to Linux
Learn the basics of the Linux operating systems. Get to know what it is all about, and familiarize yourself with the practical side. Basically, if you're a complete Linux newbie and looking for a quick and easy guide to get you started this is it. subscribe
Open Source Security Myths Dispelled Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization subscribe
InformationWeek InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology. subscribe
Wireless Internet Anything related to getting wireless set up in Linux. WLAN, WiFi, etc.
Submit Your Article
Latest Articles
Article Categories
Join Linux Forums Today
to digg the linux-wireless recent archives.
Linear Mode
