USB_ModeSwitch

Hi,

Since I still have some problems cross-compiling usb_modeswitch with Kernel 2.4.34 (library -l usb not found...) for my embedded platform, I thought I could probably try it out on my Fedora FC9 first.

Compiled on FC9 was OK with some minor changes.

I have a MBD-100HU USB Modem and here are the USB IDs.
Mass Storage = vendor=0x1c9e product=0x1001
Modem = vendor=0x1c9e product=0x6061

and here's the steps that I tried.

[root@localhost usb_modeswitch-0.9.3]# ./usb_modeswitch -v 0x1c9e -p 0x1001 -V 0x1c9e -P 0x6061 -C 0xff -d 1

* usb_modeswitch: tool for controlling "flip flop" mode USB devices
* Version 0.9.3 (C) Josua Dietze 2007
* Works with libusb 0.1.12 and probably other versions

Looking for target device
OK, target device not found. Action required
Looking for default device
Ok, found default device
Looking for target class
OK, device not found in target class mode. Action required
Prepare switching, accessing device
Looking for active default driver to detach it
OK, driver found ("usb-storage")
OK, Driver "usb-storage" successfully detached
-> See /proc/bus/usb/devices (or call lsusb) for changes. Bye

[root@localhost usb_modeswitch-0.9.3]# /sbin/lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 004: ID 1c9e:1001
Bus 004 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


The storage was detached but when I did "lsusb", I still saw the storage product ID (0x1001) instead of modem product ID (0x6061).

I am not sure if MessageEndpoint and MessageContent are required. How do I get the numbers? How do I "debug" this?

Thank you.
-V

Firstly, I strongly recommend the latest beta version (0.9.4beta2). It will soon become the new release with few changes because it is more reliable in overcoming udev related switching problems.

Secondly, I rather recommend to use an entry in the "/etc/usb_modeswitch.conf" file rather than using the more expert-oriented command line parameters. The functions are the same, but the more verbose option names are somewhat self-explaining.

For example, the TargetClass parameter is so far only necessary with devices that DON'T change their IDs after switching. Yours does, so skip the "-C" parameter.
Also the parameter "-d" in it's long form is "DetachStorageOnly"; so this will be the only action required and thus no command "message" needs to be sent.

As for the target ID parameters, these are really optional with the latest versions.

Thanks Josh. I downloaded the latest 0.9.4 and the new usb_modeswitch.conf and now my MBD-100HU works on my fedora 9 laptop.

Aleksandar Samardzic has actually "cracked" the Modem in the latest usb_modeswitch.conf file (the last table in the file - Alcatel OT-X020).

Hmm... I wondered why the option "DetachStroageOnly" is not required and how and where to get the MessageEndpoint and MessageContent?

Thanks.

Actually, Aleksandar searched for advice on the Linux-USB mailing list. I asked him to provide a sniffer log and thus we were able to get his device working.

Are you saying the Alcatel OT-X020 is a branding for the MBD-100HU ?

If so, I'll include that in the docs, to help people find stuff

Well, at least the IDs (both Default and Target) match the Alcatel OT-X020's. And the Windows application for this (MBD) USB modem states MBD-100HU. The actual Name/Brand on the USB Modem cover is "NUTON 3.5G".

I guess they are from the same Vendor/Manufacturer. I found these links on Google.

Alcatel:
http://mobile.softpedia.com/phonePictures/2490

Nuton:
http://www.myccs.com/display-product.php?id=2992

For anyone else in Japan, this is also the Emobile D11LC. Looks nothing like the Alcatel or the Nuton (http://japan.cnet.com/story_media/20376 ... -d11lc.jpg), but the product and vendor IDs match.

The same exact conf will also work for this model (HT-WM66).

Here's the link - http://www.rodeotrade.com/pdf_datasheet ... ts_id=1493