kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Sean McNamara, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Changed in: linux (Ubuntu)
       Status: Triaged => Incomplete

** Attachment removed: "Screenshot of the 'Wireless Network Drivers' window."
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/408165/+attachment/913561/+files/Screenshot-Wireless%20Network%20Drivers.png

** Attachment removed: "Screenshot of working WUSB600Nv2 with NDISWRAPPER"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/408165/+attachment/913535/+files/Screenshot.png

** Attachment removed: "dmesg"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/408165/+attachment/1090873/+files/dmesg.txt

** Attachment removed: "wireshark results"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/408165/+attachment/1098319/+files/Wireshark_results_no_media_scan.zip

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/408165

Title:
  Linksys By Cisco WUSB600N v2 Doesn't Work

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I have a  "Linksys By Cisco" brand WUSB600N v2. Its USB ID is
  1737:0079 Rev. 0101

  When the USB adapter is hotplugged (or even coldplugged) the USB bus
  recognizes that "something" has been plugged in, but no additional
  modules are loaded at all. The output of `lsmod' before and after hot
  insertion is identical. So no modules claim they support this card.

  The original of this model, WUSB600N, is supposedly an
  rt2870-compatible chip. I am not sure whether "v2" is an entirely
  different chipset, or whether it's just rt2870 with a quirk. I tried
  manually adding the USB ID to the rt2870sta source code and rebuilding
  the driver, but doing so gave me a kernel oops within that module. So
  apparently the fix to get it supported isn't as simple as adding that
  one line. But at least rt2870 seems to be partially aware of the chip
  -- right after the oops I ran `ifconfig' and the interface was up and
  I could get its MAC address (and it was correct). But since the module
  oopsed, I was unable to send any commands to the wireless interface
  via NetworkManager, iwconfig, etc.

  I'm not sure how fervently upstream tries to support manufacturers who
  buy the rt2870 chipset and put it in their own product. If Ralink is
  nice enough to patch their drivers for the quirks of other vendors'
  products (such as Linksys) then it's just a matter of waiting. But if
  the action is in Linksys' court, I'm not sure they would help us at
  all. I think we will need a volunteer kernel hacker to take a look at
  it and see if the fix is reasonably easy.

  Since these wireless USB adapters are relatively inexpensive, I am
  willing to donate one to a single competent individual who believes
  he/she can get this working well. All I ask in return is that you get
  it working, and return it to me when you are done with it (shipping at
  my expense)... unless of course you break it, which is understandable.
  Fragile little device.

  NB: I've tested this thoroughly on both Jaunty and Karmic. In Karmic,
  we have the rt2800usb driver as part of the open source rt2x00 project
  (now entering mainline); but the new set of rt2* drivers still fail to
  automatically probe this card. I applied my patch to the rt2870sta
  driver downloaded from Ralink's website and built that on Jaunty, but
  did not test my naive patch against the Karmic kernel sources, as I
  expected the same result.

  UPDATE: I think the future of Ralink chipsets on Linux is the rt2x00
  project, as they are moving at a faster pace than rt2870sta and they
  are integrated into mainline. Their wifi drivers are first class
  citizens, with a behavior just like you'd expect from, say, iwlwifi:
  NetworkManager can use them; WPA2 works without a custom supplicant;
  no proprietary daemons; etc. Not sure how much code rt2x00 shares with
  rt2870sta (if any), but hopefully this project will pick up support
  for 1737:0079 soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/408165/+subscriptions