Cisco/Iinksys WUSB600N V2

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=6070

jesmith

03-05-2010 20:46:19

I have a WUSB600N V2 USB Wireless N device. lsusb shows

17370079 Linksys

But the device does not appear when I "iw list". No messages appear in the system logs, so it appears nothing is even trying to drive this device.

Kernel 2.6.27.8
compat-wireless April 26, 2010
iw 0.9.19

I've read that the rt3572sta driver from RALINK works for this device.

Do I have a chance of getting this to work with compat-wireless, or do I need to use the RALINK driver?

IvD

04-05-2010 18:48:39

You must enable the CONFIG_RT2800USB_UNKNOWN configuration option.

jesmith

04-05-2010 19:22:47

That helped! Now the device appears, however 'iw list' only shows the 2.4GHz channels. I updated to the latest rt2870.bin firmware from ralink's web site, and there are no errors in dmesg.

Any idea why I cannot see the 5Ghz channels? (The box this thing came in says "Dual-Band Wireless-N USB Adapter", so I presume it has a 5GHz radio in it!)

Thanks.

IvD

05-05-2010 10:11:56

Could you enable RT2X00_DEBUG and post the debug messages?
That way I can identify the RF chipset and see if that is a known 5GHz device.

jesmith

05-05-2010 14:06:36

Here is /var/log/messages. Does it write info anyplace else?

IvD

06-05-2010 09:26:49

Ok you are absolutely right.
Your device does support 5Ghz, but it wasn't know yet. I have just checked the Ralink sourcecode, and they do indicate it has 5Ghz support,
I'll fix this as soon as possible.

jesmith

06-05-2010 13:18:42

Excellent. I'd be thrilled to test it out for you.

-Joshua

IvD

06-05-2010 13:33:59

Well apparently your device wouldn't work on 2.4GHz channels either due to another bug.
Both issues have now been fixed, and has been send upstream. It should appear in compat-wireless soon.

jesmith

06-05-2010 13:38:52

Is there any way for me to know when it has been integrated?

IvD

06-05-2010 13:50:13

Not really, when iw shows the 5GHz channels it is merged. But that requires you to test the drivers every few days.

jesmith

06-05-2010 13:51:30

OK, thanks. I guess I have a new Monday-morning chore to do )

jesmith

07-05-2010 14:32:32

Your changes are in compat-wireless, but the device is still not working. I rebuilt (with CONFIG_RT2800USB_UNKNOWN=y ) and installed 2010-05-06. When I plugged the device in, I got this
[code1okakoay]
usb 1-1.4: new high speed USB device using ehci_hcd and address 5
usb 1-1.4: configuration #1 chosen from 1 choice
Generic kernel compatibility enabled based on linux-next next-20100113
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
(2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
(2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
phy0: Selected rate control algorithm 'minstrel'
BUG: unable to handle kernel NULL pointer dereference at 00000000
IP: [<00000000>]
*pde = 00000000
Oops: 0000 [#1] SMP
Modules linked in: arc4 ecb rt2800usb(+) rt2800lib rt2x00usb rt2x00lib led_class compat_firmware_class mac80211 cfg80211 rfkill_backport compat crc_ccitt snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss pcmcia pcmcia_core agpgart lp ppdev parport_pc parport pcspkr psmouse sg snd_hda_intel snd_pcm snd_timer snd_page_alloc snd_hwdep snd soundcore e1000e evdev fuse aufs squashfs sqlzma unlzma [last unloaded: pcmcia_core]

Pid: 5344, comm: modprobe Not tainted (2.6.27.8 #1)
EIP: 0060:[<00000000>] EFLAGS: 00010286 CPU: 2
EIP is at 0x0
EAX: f5abe000 EBX: f71d6890 ECX: 00000000 EDX: 00000000
ESI: f71d6800 EDI: f5ba0c00 EBP: f5abe000 ESP: f5219c54
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modprobe (pid: 5344, ti=f5218000 task=f72ddb00 task.ti=f5218000)
Stack: c067340f f5abe160 00000282 00000292 f794e480 00000000 00000000 00000000
00000000 00000000 00000000 00000000 000005dc f5abe000 f5ba0c00 ffffffff
00000010 c06738c9 00000000 00000000 ffffffff 00000000 c08eaa5c ffffffff
Call Trace:
[<c067340f>] rtnl_fill_ifinfo+0x2af/0x4a0
[<c06738c9>] rtmsg_ifinfo+0x69/0x100
[<c06739a4>] rtnetlink_event+0x44/0x60
[<c013ba50>] notifier_call_chain+0x30/0x60
[<c013baf7>] raw_notifier_call_chain+0x17/0x20
[<c066ad60>] register_netdevice+0x200/0x340
[<fa1aea4c>] ieee80211_setup_sdata+0x2c/0xf0 [mac80211]
[<fa1af1ae>] ieee80211_if_add+0x47e/0x860 [mac80211]
[<c070b001>] schedule_timeout+0x51/0xd0
[<c03ab109>] crypto_spawn_tfm+0x59/0xb0
[<fa0fe1aa>] crypto_ecb_init_tfm+0x1a/0x30 [ecb]
[<c01263db>] printk+0x1b/0x20
[<fa1b0984>] ieee80211_init_rate_ctrl_alg+0xd4/0x1e0 [mac80211]
[<fa1a2b32>] ieee80211_register_hw+0x322/0x3b0 [mac80211]
[<fa128c19>] rt2x00lib_probe_dev+0x2d9/0x390 [rt2x00lib]
[<fa0d9c83>] rt2x00usb_probe+0xb3/0x150 [rt2x00usb]
[<c05e8e67>] usb_match_one_id+0x27/0xb0
[<c05e9e1a>] usb_probe_interface+0x8a/0x130
[<c01b984f>] sysfs_create_link+0xf/0x20
[<c0435592>] driver_probe_device+0x82/0x180
[<c04356fc>] __driver_attach+0x6c/0x70
[<c0434d3b>] bus_for_each_dev+0x3b/0x60
[<c0435416>] driver_attach+0x16/0x20
[<c0435690>] __driver_attach+0x0/0x70
[<c0435271>] bus_add_driver+0x1a1/0x220
[<c04358fd>] driver_register+0x4d/0x120
[<c05e9451>] usb_register_driver+0x81/0x100
[<fa1331c0>] rt2800_config_erp+0x0/0x170 [rt2800lib]
[<f8d1c000>] rt2800usb_init+0x0/0x14 [rt2800usb]
[<c0101123>] _stext+0x33/0x160
[<c0146bb7>] sys_init_module+0x87/0x1b0
[<c01764d1>] sys_read+0x41/0x70
[<c0103262>] syscall_call+0x7/0xb
=======================
Code: Bad EIP value.
EIP: [<00000000>] 0x0 SS:ESP 0068:f5219c54
---[ end trace 1da517d62543f400 ]---
[/code1okakoay]

iw list does show the device, but it doesn't show the 5GHz band.

jesmith

13-05-2010 15:32:23

FYI As of 2010-05-12, the crash above is still happening, but the 5GHz band now appears!

Thanks for that fix.