Problems with ti_usb_3410_5052 kernel module.

[Matt Wiseman]

On Tue, 2009-07-28 at 06:36 +0200, Nils Kassube wrote:
> I don't know if that "weird autoloading script" is really needed. Can 
> you tell us the USB-ID for the device? You can find it out with the
> 
> lsusb
> 
> command in a terminal while the device is plugged in.
> 
> 
> Nils
> 
> 
##From LSUSB
Bus 005 Device 008: ID 06e0:f111 Multi-Tech Systems, Inc. 

##From LSUSB -v
Bus 005 Device 008: ID 06e0:f111 Multi-Tech Systems, Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x06e0 Multi-Tech Systems, Inc.
  idProduct          0xf111 
  bcdDevice            1.01
  iManufacturer           1 
  iProduct                2 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
cannot read device status, Operation not permitted (1)