Bug 16368 - Linksys WUSB 600N rev 2. not detected
Summary: Linksys WUSB 600N rev 2. not detected
Status: CLOSED INVALID
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 high
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-12 13:38 UTC by Gaetan Cambier
Modified: 2010-07-12 15:19 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.33.X
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Dmesg after reboot (48.89 KB, application/octet-stream)
2010-07-12 14:21 UTC, Gaetan Cambier
Details

Description Gaetan Cambier 2010-07-12 13:38:44 UTC
in the changelog of the kernel 2.6.33, i have found :

- rt2x00: Add USB ID for Linksys WUSB 600N rev 2.

but my wireless key is not detected :s

lsusb -vvv

Bus 002 Device 002: ID 1737:0079 Linksys WUSB600N Wireless-N USB Network Adapter with Dual-Band ver. 2
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1737 Linksys
  idProduct          0x0079 WUSB600N Wireless-N USB Network Adapter with Dual-Band ver. 2
  bcdDevice            1.01
  iManufacturer           1 Linksys
  iProduct                2 
  iSerial                 3 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           67
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              450mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           7
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              5 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)
Comment 1 John W. Linville 2010-07-12 13:58:43 UTC
We will need to see the output from dmesg shortly after booting and inserting your USB device.
Comment 2 Gaetan Cambier 2010-07-12 14:21:16 UTC
i have reboot the computer,

after the reboot i have unplug and plug the wireless usb
see dmesg.log for detail.

tkx for the quick reponse
Comment 3 Gaetan Cambier 2010-07-12 14:21:48 UTC
Created attachment 27072 [details]
Dmesg after reboot
Comment 4 John W. Linville 2010-07-12 15:19:14 UTC
OK...that device is in a group of devices that have subsequently been listed as "unknown" status.  That is, they are suspected to be able to work with the rt2800usb driver, but their actual status has not been verified.  Support for that group of devices can be turned-off at build configuration, and the Fedora kernels do just that.

If you would like to rebuild your kernel (or build an upstream one) with CONFIG_RT2800USB_UNKNOWN enabled then the status for your specific device might be changed if you report success with it.  If you would like to try that, please post the results (especially positive ones) to linux-wireless@vger.kernel.org.

In any case, what you are observing is not actually a but, but the results of a choice made by Fedora.

Note You need to log in before you can comment on or make changes to this bug.