From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: linux-wireless@vger.kernel.org,
Gertjan van Wingerde <gwingerde@gmail.com>
Subject: Linksys WUSB600N v2 with rt2x00 driver doesn't work
Date: Mon, 28 Mar 2011 09:56:20 +0300 [thread overview]
Message-ID: <4D903114.2090905@pardus.org.tr> (raw)
Hi,
The mentioned dongle's vendor&product id is added to the rt2800usb
driver with the following commit:
commit 5e31258945f60dff65952575625cac214a75893e
Author: Gertjan van Wingerde <gwingerde@gmail.com>
Date: Wed Dec 23 00:03:21 2009 +0100
rt2x00: Add USB ID for Linksys WUSB 600N rev 2.
This is a rt2870 based device.
Signed-off-by: Gertjan van Wingerde <gwingerde@gmail.com>
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
On 2.6.37.5 with compat-wireless 2.6.38.3, the driver gets loaded, the
interface wlan0 is created but no scan results is returned. These are
what logged in dmesg after plugging the device:
[336770.008134] usb 2-3: new high speed USB device using ehci_hcd and
address 6
[336770.154067] usb 2-3: New USB device found, idVendor=1737, idProduct=0079
[336770.154071] usb 2-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[336770.154075] usb 2-3: Product: Linksys WUSB600N Wireless-N USB
Network Adapter with Dual-Band ver. 2
[336770.154078] usb 2-3: Manufacturer: Linksys
[336770.156447] usbip 2-3:1.0: this device 2-3 is not in match_busid
table. skip!
[336770.171767] ieee80211 phy2: Selected rate control algorithm
'minstrel_ht'
[336770.172614] Registered led device: rt2800usb-phy2::radio
[336770.172653] Registered led device: rt2800usb-phy2::assoc
[336770.172734] Registered led device: rt2800usb-phy2::quality
[336770.900090] ADDRCONF(NETDEV_UP): wlan0: link is not ready
ozanDesktopI7x86_64 rt2x00 # ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 68:7F:74:F5:E8:1A
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
ozanDesktopI7x86_64 rt2x00 # rfkill list
2: phy2: Wireless LAN
Soft blocked: no
Hard blocked: no
reply other threads:[~2011-03-28 6:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D903114.2090905@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=gwingerde@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.