Cisco Valet Connector AM10 in Ubuntu 11.04

[ohmysql]

I'm using Ubuntu 11.04. I'm trying to get a Cisco Valet Connector AM10 to work. It's one of those ZeroCD USB devices that is both storage and modem.

Using this link:

http://linuxwireless.org/en/users/Dr...ght=%28am10%29

I filled out usb_modeswitch like this:

# Configuration for the usb_modeswitch package, a mode switching tool for
# USB devices providing multiple states or modes
#
# This file is evaluated by the wrapper script "usb_modeswitch_dispatcher"
# in /usr/sbin
# To enable an option, set it to "1", "yes" or "true" (case doesn't matter)
# Everything else counts as "disable"


# Disable automatic mode switching globally (e.g. to access the original
# install storage)

DisableSwitching=0


# Enable logging (results in a extensive report file in /var/log, named
# "usb_modeswitch_<interface-name>" (and probably others)

EnableLogging=0

# DAS edit 2011-07-20

# Cisco Valet Connector AM10
#
# Contributor: ohmysql (quite the n00b so please help if you see errors)

# No. 1
DefaultVendor= 0x1307
DefaultProduct= 0x0169
TargetVendor= 0x13b1
TargetProduct= 0x0031
#MessageEndpoint=0×01
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"

And here's what I get when I run:

sudo usb_modeswitch -c /etc/usb_modeswitch.conf

Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
Found devices in default mode, class or configuration (1)
Accessing device 006 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Error: message endpoint not given or found. Aborting.

HELP!

[chili555]

I know very little about usb_modeswitch, but I noticed your post went 15 hours without a peep, so maybe you'll accept a suggestion from an amateur. The error message is:

Error: message endpoint not given or found. Aborting.

However, 'message endpoint' is commented out in your .conf file:

<snip>
# No. 1
DefaultVendor= 0x1307
DefaultProduct= 0x0169
TargetVendor= 0x13b1
TargetProduct= 0x0031
#MessageEndpoint=0×01
MessageContent="5553424312345678c00000008000069f03 0000000000000000000000000000"

Does the behavior improve if you remove the hash?

[ohmysql]

I know very little about usb_modeswitch, but I noticed your post went 15 hours without a peep, so maybe you'll accept a suggestion from an amateur. The error message is:However, 'message endpoint' is commented out in your .conf fileoes the behavior improve if you remove the hash?

Hello,

Thanks for the reply. No, I've tried removing the hash and changing the value to a few things found on the internet - 01, 05 and it still says it can't find the endpoint.

Thanks for the suggestion - I've been googling trying to figure out where the end point of USB devices is listed. If only I had windows so I could plug this in and spy on how it works there.

Maybe that would help.

David

[chili555]

Dr. Chili is not one to curse, but....curses, now I have to learn about usb_modeswitch. I thought I had a clean getaway.

DefaultVendor= 0x1307
DefaultProduct= 0x0169
TargetVendor= 0x13b1
TargetProduct= 0x0031

Where did these numbers come from? How does it relate to:

sudo lsusb -v

Feel free to redact the not-a-Cisco parts.

[ohmysql]

Dr. Chili is not one to curse, but....curses, now I have to learn about usb_modeswitch. I thought I had a clean getaway.Where did these numbers come from? How does it relate to:

sudo lsusb -v

Feel free to redact the not-a-Cisco parts.

Chili, you're a lot classier than I am. I've been cursing since I purchased this thing.

More than anything, what you can do to help is just be someone to bounce ideas off. I mean if you Google something and find different things than me, that's even better.

Yeah, I've been trying to learn usb_modeswitch - I don't find it easy.

To answer your question, I got those target numbers from here:

http://linuxwireless.org/en/users/Dr...ght=%28am10%29

Here are the AM10 parts of that code. Note for some reason, there appears to be two devices?

 lsusb

Bus 001 Device 005: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Bus 001 Device 003: ID 1307:0169 Transcend Information, Inc. 

ubuntu:~$ sudo lsusb -v

Bus 001 Device 005: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1307 Transcend Information, Inc.
  idProduct          0x1169 TS2GJF210 JetFlash 210 2GB
  bcdDevice            1.00
  iManufacturer           1 Cisco Systems, Inc.
  iProduct                5 Cisco AM10 AM10
  iSerial                 3 000000000000D9
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               98mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      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     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               8
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)

Bus 001 Device 003: ID 1307:0169 Transcend Information, Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x1307 Transcend Information, Inc.
  idProduct          0x0169 
  bcdDevice            1.00
  iManufacturer           1 Cisco Systems, Inc.
  iProduct                4 Cisco AM10 USB Hub
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower               98mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval               8
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             3
  wHubCharacteristic 0x0004
    Ganged power switching
    Compound device
    Ganged overcurrent protection
    TT think time 8 FS bits
  bPwrOn2PwrGood       50 * 2 milli seconds
  bHubContrCurrent     49 milli Ampere
  DeviceRemovable    0x0a
  PortPwrCtrlMask    0xff
 Hub Port Status:
   Port 1: 0000.0503 highspeed power enable connect
   Port 2: 0000.0100 power
   Port 3: 0000.0100 power
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         0 Full speed (or root) hub
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

[chili555]

I think there are two devices; the flash drive part has the (Windows) software that drives the wireless device. As I understand usb_modeswitch, it's objective is to hop over the flash drive part and just use the wireless device with Linux drivers. I am confident that those smarter than me will hop in here and correct me. I will be grateful for the assistance.

You have:

# No. 1
DefaultVendor= 0x1307
DefaultProduct= 0x0169
TargetVendor= 0x13b1
TargetProduct= 0x0031
#MessageEndpoint=0×01
MessageContent="5553424312345678c00000008000069f03 0000000000000000000000000000"

I'm guessing the Default pieces correspond to:

ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB

The first experiment I'd suggest is to change the Default parts to 0x1307 and 0x1169.

The Target parts you have as 0x13b1 and 0x0031. That doesn't correspond to anything that I see in lsusb.

ID 1307:0169 Transcend Information, Inc.

I'd change the Target parts to 0x1307 and 0x0169.

I'd then run the command again:

sudo usb_modeswitch -c /etc/usb_modeswitch.conf

Look for clues as to what's happening under the hood and let's see what it says. If we're both lucky and smart today, it will work.

If we're not, then my next experiment would be to reverse what I suggested and try again.

[ohmysql]

I think there are two devices; the flash drive part has the (Windows) software that drives the wireless device. As I understand usb_modeswitch, it's objective is to hop over the flash drive part and just use the wireless device with Linux drivers. I am confident that those smarter than me will hop in here and correct me. I will be grateful for the assistance.

You have:I'm guessing the Default pieces correspond to:The first experiment I'd suggest is to change the Default parts to 0x1307 and 0x1169.

The Target parts you have as 0x13b1 and 0x0031. That doesn't correspond to anything that I see in lsusb. I'd change the Target parts to 0x1307 and 0x0169.

I'd then run the command again:

sudo usb_modeswitch -c /etc/usb_modeswitch.conf

Look for clues as to what's happening under the hood and let's see what it says. If we're both lucky and smart today, it will work.

If we're not, then my next experiment would be to reverse what I suggested and try again.

W00t! Ok, we are one step closer. Thank you so much for the ideas. Here's the code that worked:

DefaultVendor= 0x1307
DefaultProduct= 0x1169
TargetVendor= 0x13b1
#0x1307
TargetProduct= 0x0031
#0x0169
#MessageEndpoint=0×05
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"

If you put in any other values for default vendor it doesn't work, and it doesn't seem to care much what you put for TargetVendor, (though that may prove to be quite important later...).

Here's the response it gives:

Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
 Found devices in default mode, class or configuration (1)
Accessing device 005 on bus 001 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x82 (in)
Using endpoints 0x01 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached

Then it hangs there forever. BUT Linux doesn't claim there's a USB storage device plugged in there anymore. Well, at least my home menu doesn't have it listed on the side anymore. But, here are the contents of lsusb:

Bus 002 Device 003: ID 045e:007d Microsoft Corp. Notebook Optical Mouse
Bus 002 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Bus 001 Device 003: ID 1307:0169 Transcend Information, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

So, nothing has changed there.

I've been following this tutorial.

http://standy.blog.ugm.ac.id/2010/02...u-jaunty-9-04/

The next step he says (assuming this device is acting like a modem) is to:

Next, you must modprobe your modem as usbserial into kernel … (different method with other ubuntu version) with “sudo gedit /boot/grub/menu.lst” in terminal.

Compare, add and edit yours to be like this :

menu.lst is blank, so I'm not quite sure what to do. Does that mean to add something in /etc/modules?

I think I'm one step closer.

[chili555]

I don't think you have a modem; I think you have an ordinary wireless device that connectes to the signal from your wireless router, yes? No? I think our next step is to figure out the correct driver and load it and see if we can bring it to life. It is late here, so I will attack this tomorrow. I suggest you Google for 1307:0169. Early hints suggest the Ralink RT3072 chipset, but I am not yet persuaded.

[ohmysql]

Check out this thread:

http://www.draisberghof.de/usb_modes...r=asc&start=15

Wow... they've put a lot of work in and not necessarily gotten very far.

[chili555]

They've gotten as far as any I've been able to find on the web; that is, as far as you and not very far at all...sadly. My search for a wireless driver for 1307:0169 comes up pretty sparse; mostly coming back to valiant but fruitless attempts to get usb_modeswitch going.

What is in the flash storage part? Does it automount to your desktop if you insert it and just wait for it? Is it a Windows .exe? Maybe we can unravel it and see what driver it thinks it wants from the .inf file.

We could compile RT3072 and add the device ID to it and see what happens. We could make history!