[ilix]

VID: 0x1a8d
PID: 0x1000 => 0x1002

I was not able to make it switch with a single command from the sniff log. However the following sequence makes it switch reliably.

Code: Select all

echo "sleep 5"
sleep 5
usb_modeswitch -v 0x1a8d -p 0x1000 -m 0x05 -M 555342435886b2851200000080000603000000020000000000000000000000 -n 1 -r 0x82;
echo "sleep 1"
sleep 1
usb_modeswitch -v 0x1a8d -p 0x1000 -m 0x05 -M 55534243f814b9851200000080000603000000020000000000000000000000 -n 1 -r 0x82;
echo "sleep 1"
sleep 1
usb_modeswitch -v 0x1a8d -p 0x1000 -m 0x05 -M 5553424308a0e2851200000080000600000000020000000000000000000000 -n 1 -r 0x82;

echo "sleep 10"
sleep 10
usb_modeswitch -v 0x1a8d -p 0x1000 -m 0x05 -M 555342435886b2851200000080000603000000020000000000000000000000 -n 1 -r 0x82;
echo "sleep 1"
sleep 1
usb_modeswitch -v 0x1a8d -p 0x1000 -m 0x05 -M 55534243f814b9851200000080000603000000020000000000000000000000 -n 1 -r 0x82;
echo "sleep 1"
sleep 1
usb_modeswitch -v 0x1a8d -p 0x1000 -m 0x05 -M 5553424308a0e2851200000080000600000000020000000000000000000000 -n 1 -r 0x82;

[bln_george]

Dears,
sleep 1 means sleep 1 second or ...?
please advice!
Thanks
George

[CrazyTerabyte]

Hey, I got a Bandrich Bandluxe C120 device. I could switch it using a much simpler script. I just need to send two commands:

Code: Select all

usb_modeswitch -v 0x1a8d -p 0x1000 -V 0x1a8d -P 0x1002 -m 0x05 -r 0x82 -M 55534243109298820000000000000600000000000000000000000000000000
usb_modeswitch -v 0x1a8d -p 0x1000 -V 0x1a8d -P 0x1002 -m 0x05 -r 0x82 -M 555342439034a0820000000000000600000000000000000000000000000000

I found these commands by using SniffUsb 2.0 under Windows. The log was huge, but I found that the most important portion just sends these two commands a few repeated times.

I would attach the relevant portion of the log (around 45K uncompressed), but it seems that this forum does not support attachments.


Anyway, I used this sed script to extract only the outbound messages sent to endpoint 0x05:

Code: Select all

#!/bin/sed -nf

/PipeHandle.*=.*\[endpoint 0x00000005\]/,/UrbLink/ {
	/[0-9a-fA-F]\+:[ 0-9a-fA-F]\+/p
}

Then, a bit of text manipulation in Vim, followed by "uniq" command, and I found that only those two messages were sent.


Edit: I found that this *only* works after usb_storage has detected the device. If, for example, I blacklist usb_storage, or prevent it from attaching itself to the device, then the two USB messages above don't work.

Edit: I've posted on my blog very detailed instructions of possible solutions of how to make this device work as a modem, including one solution that does not require a device switch at all.
http://my.opera.com/CrazyTerabyte/blog/ ... velox-plug

[efa]

I own a WIND MSI U90 netbook + WIND itelco ITM22 modem, that is a BandRich BandLuxe C120 modem rebranded.
The modem connected to a Notebook Fujitsu/Siemens work well on WinXP and Linux Ubuntu 9.04 using usb_modeswitch on /dev/ttyUSB1 and wvdial (or gnome-ppp).
The same modem connected to the WIND MSI U90, work on WinXP, but strangely does not work with Ubuntu 9.04 !!

Here what happen:
immediately after connecting 'dmesg' show:

Code: Select all

Aug 14 13:32:41 01ATO1600 kernel: [19807.204132] usb 3-1: new full speed USB device using uhci_hcd and address 10
Aug 14 13:32:41 01ATO1600 kernel: [19807.369937] usb 3-1: configuration #1 chosen from 1 choice
Aug 14 13:32:41 01ATO1600 kernel: [19807.389144] scsi13 : SCSI emulation for USB Mass Storage devices

and 'lsusb' show:
Bus 003 Device 010: ID 1a8d:1000

then I used the 6 messages 'usb_modeswitch' script and the switch happen.
Actually 'lsusb' show:
Bus 003 Device 012: ID 1a8d:1002

but 'dmesg' show that the modem continue to reset and remount in a cyclic manner:
/dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2, /dev/ttyUSB3
and then restart.
Follow the first messages in 'dmesg' after successfull switch, but the log continue increasing indefinitely until I disconnect the modem.

I runt 'lsmod' and I can see 'usbserial' used by 'option' module, but I cannot understand how to stabilize the modem port number.

I also updated the BIOS of MSI U90 to the last version as they claim an 'hot plug recognision fix', but no luck.

Itelco/Wind Connection Manager and current BandLuxeC120 Connection Manager for Windows does not allow to manually force the USB device to be a modem (disabling the onboard Flash drive with Win32 driver).

I also tried to use 'wvdial' on /dev/ttyUSB4, but it can initialize the modem in a moment, start configuring it, then before it can dial, the modem disappear, and 'wvdial' goes in error with 'modem not responding'.

Sad to say, but as now I had to boot in WinXP to connect, very bad!
Please help me.

Code: Select all

Aug 14 13:46:26 01ATO1600 kernel: [20632.280194] usb 3-1: USB disconnect, address 11
Aug 14 13:46:31 01ATO1600 kernel: [20637.636086] usb 3-1: new full speed USB device using uhci_hcd and address 12
Aug 14 13:46:31 01ATO1600 kernel: [20637.798203] usb 3-1: configuration #1 chosen from 1 choice
Aug 14 13:46:31 01ATO1600 kernel: [20637.803550] scsi16 : SCSI emulation for USB Mass Storage devices

Aug 14 13:46:31 01ATO1600 kernel: [20637.821523] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 14 13:46:31 01ATO1600 kernel: [20637.821689] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB0
Aug 14 13:46:31 01ATO1600 kernel: [20637.840569] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 14 13:46:31 01ATO1600 kernel: [20637.840733] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB1
Aug 14 13:46:36 01ATO1600 kernel: [20642.809630] scsi 16:0:0:0: CD-ROM            BandLuxe CDROM            1.01 PQ: 0 ANSI: 4
Aug 14 13:46:36 01ATO1600 kernel: [20642.852481] sr1: scsi3-mmc drive: 0x/0x caddy
Aug 14 13:46:36 01ATO1600 kernel: [20642.853012] sr 16:0:0:0: Attached scsi generic sg2 type 5
Aug 14 13:46:36 01ATO1600 kernel: [20642.978537] sr: Sense Key : No Sense [current] 
Aug 14 13:46:36 01ATO1600 kernel: [20642.978551] sr: Add. Sense: No additional sense information
Aug 14 13:46:37 01ATO1600 kernel: [20643.381502] sr: Sense Key : No Sense [current] 
Aug 14 13:46:37 01ATO1600 kernel: [20643.381512] sr: Add. Sense: No additional sense information
Aug 14 13:46:39 01ATO1600 kernel: [20645.163157] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Aug 14 13:46:39 01ATO1600 kernel: [20645.163220] option 3-1:1.1: device disconnected
Aug 14 13:46:39 01ATO1600 kernel: [20645.163467] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Aug 14 13:46:39 01ATO1600 kernel: [20645.163507] option 3-1:1.2: device disconnected
Aug 14 13:46:39 01ATO1600 kernel: [20645.272143] usb 3-1: reset full speed USB device using uhci_hcd and address 12

Aug 14 13:46:39 01ATO1600 kernel: [20645.423546] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 14 13:46:39 01ATO1600 kernel: [20645.425275] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB0
Aug 14 13:46:39 01ATO1600 kernel: [20645.425388] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 14 13:46:39 01ATO1600 kernel: [20645.425631] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB1
Aug 14 13:46:39 01ATO1600 kernel: [20645.492517] sr: Sense Key : No Sense [current] 
Aug 14 13:46:39 01ATO1600 kernel: [20645.492531] sr: Add. Sense: No additional sense information
Aug 14 13:46:40 01ATO1600 kernel: [20646.163518] sr: Sense Key : No Sense [current] 
Aug 14 13:46:40 01ATO1600 kernel: [20646.163532] sr: Add. Sense: No additional sense information
Aug 14 13:46:40 01ATO1600 kernel: [20646.169526] sr: Sense Key : No Sense [current] 
Aug 14 13:46:40 01ATO1600 kernel: [20646.169539] sr: Add. Sense: No additional sense information
Aug 14 13:46:40 01ATO1600 kernel: [20646.176564] sr: Sense Key : No Sense [current] 
Aug 14 13:46:40 01ATO1600 kernel: [20646.176577] sr: Add. Sense: No additional sense information
Aug 14 13:46:40 01ATO1600 kernel: [20646.197510] sr: Sense Key : No Sense [current] 
Aug 14 13:46:40 01ATO1600 kernel: [20646.197524] sr: Add. Sense: No additional sense information
Aug 14 13:46:41 01ATO1600 kernel: [20647.160602] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Aug 14 13:46:41 01ATO1600 kernel: [20647.160643] option 3-1:1.1: device disconnected
Aug 14 13:46:41 01ATO1600 kernel: [20647.161537] option 3-1:1.2: device disconnected
Aug 14 13:46:41 01ATO1600 kernel: [20647.272094] usb 3-1: reset full speed USB device using uhci_hcd and address 12
Aug 14 13:46:41 01ATO1600 kernel: [20647.424561] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 14 13:46:41 01ATO1600 kernel: [20647.424824] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB1
Aug 14 13:46:41 01ATO1600 kernel: [20647.424906] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 14 13:46:41 01ATO1600 kernel: [20647.425086] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB2
Aug 14 13:46:43 01ATO1600 kernel: [20649.161734] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Aug 14 13:46:43 01ATO1600 kernel: [20649.161775] option 3-1:1.1: device disconnected
Aug 14 13:46:43 01ATO1600 kernel: [20649.162521] option 3-1:1.2: device disconnected
Aug 14 13:46:43 01ATO1600 kernel: [20649.272152] usb 3-1: reset full speed USB device using uhci_hcd and address 12
Aug 14 13:46:43 01ATO1600 kernel: [20649.423555] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 14 13:46:43 01ATO1600 kernel: [20649.423791] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB2
Aug 14 13:46:43 01ATO1600 kernel: [20649.423848] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 14 13:46:43 01ATO1600 kernel: [20649.423960] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB3
Aug 14 13:46:45 01ATO1600 kernel: [20651.161735] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
Aug 14 13:46:45 01ATO1600 kernel: [20651.161777] option 3-1:1.1: device disconnected
Aug 14 13:46:45 01ATO1600 kernel: [20651.162517] option 3-1:1.2: device disconnected
Aug 14 13:46:45 01ATO1600 kernel: [20651.272141] usb 3-1: reset full speed USB device using uhci_hcd and address 12
Aug 14 13:46:45 01ATO1600 kernel: [20651.423557] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 14 13:46:45 01ATO1600 kernel: [20651.425243] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB3
Aug 14 13:46:45 01ATO1600 kernel: [20651.425343] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 14 13:46:45 01ATO1600 kernel: [20651.426131] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB4
Aug 14 13:46:45 01ATO1600 kernel: [20651.754256] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Aug 14 13:46:47 01ATO1600 kernel: [20653.162167] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
Aug 14 13:46:47 01ATO1600 kernel: [20653.162544] option 3-1:1.1: device disconnected
Aug 14 13:46:47 01ATO1600 kernel: [20653.163548] option 3-1:1.2: device disconnected
Aug 14 13:46:47 01ATO1600 kernel: [20653.272169] usb 3-1: reset full speed USB device using uhci_hcd and address 12
Aug 14 13:46:47 01ATO1600 kernel: [20653.423556] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 14 13:46:47 01ATO1600 kernel: [20653.423827] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB0
Aug 14 13:46:47 01ATO1600 kernel: [20653.423907] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 14 13:46:47 01ATO1600 kernel: [20653.425959] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB4
Aug 14 13:46:47 01ATO1600 kernel: [20653.752844] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Aug 14 13:46:49 01ATO1600 kernel: [20655.161744] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
Aug 14 13:46:49 01ATO1600 kernel: [20655.161786] option 3-1:1.1: device disconnected
Aug 14 13:46:49 01ATO1600 kernel: [20655.162520] option 3-1:1.2: device disconnected
Aug 14 13:46:49 01ATO1600 kernel: [20655.276149] usb 3-1: reset full speed USB device using uhci_hcd and address 12
Aug 14 13:46:49 01ATO1600 kernel: [20655.427559] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 14 13:46:49 01ATO1600 kernel: [20655.429256] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB1
Aug 14 13:46:49 01ATO1600 kernel: [20655.429358] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 14 13:46:49 01ATO1600 kernel: [20655.430155] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB4
Aug 14 13:46:49 01ATO1600 kernel: [20655.752683] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Aug 14 13:46:51 01ATO1600 kernel: [20657.162181] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
Aug 14 13:46:51 01ATO1600 kernel: [20657.162246] option 3-1:1.1: device disconnected
Aug 14 13:46:51 01ATO1600 kernel: [20657.162717] option 3-1:1.2: device disconnected
Aug 14 13:46:51 01ATO1600 kernel: [20657.272152] usb 3-1: reset full speed USB device using uhci_hcd and address 12
Aug 14 13:46:51 01ATO1600 kernel: [20657.423556] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 14 13:46:51 01ATO1600 kernel: [20657.423830] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB2
Aug 14 13:46:51 01ATO1600 kernel: [20657.423912] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 14 13:46:51 01ATO1600 kernel: [20657.425956] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB4
Aug 14 13:46:51 01ATO1600 kernel: [20657.752878] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
Aug 14 13:46:53 01ATO1600 kernel: [20659.160743] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
Aug 14 13:46:53 01ATO1600 kernel: [20659.160786] option 3-1:1.1: device disconnected
Aug 14 13:46:53 01ATO1600 kernel: [20659.161528] option 3-1:1.2: device disconnected
Aug 14 13:46:53 01ATO1600 kernel: [20659.272150] usb 3-1: reset full speed USB device using uhci_hcd and address 12
Aug 14 13:46:53 01ATO1600 kernel: [20659.423558] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 14 13:46:53 01ATO1600 kernel: [20659.423798] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB3
Aug 14 13:46:53 01ATO1600 kernel: [20659.423856] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 14 13:46:53 01ATO1600 kernel: [20659.423973] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB4

[Josh]

Please specify how exactly the switching is done on the netbook:

Do you use a udev rule entry? A manual script? A direct command line?

And to specify your setup, disable any udev rule and run "usb_modeswitch -W" on the freshly plugged device with your parameters. Then post the output.

[efa]

Please specify how exactly the switching is done on the netbook:

Do you use a udev rule entry? A manual script? A direct command line?

I wrote a shell script with the 6 command in post:
http://www.draisberghof.de/usb_modeswit ... ?p=186#186
then run from command line the script.

And to specify your setup, disable any udev rule and run "usb_modeswitch -W" on the freshly plugged device with your parameters. Then post the output.

I do not know nothing about udev, but I will try to read something and disable the autorule.

Sorry for late but I have to boot windows to connect to internet

[Josh]

In your setup, there is probably no need for the repetition in the script. It's likely your device is switched by a single call of usb_modeswitch. Sending it again might cause the modem to reset itself.

Did you try using only one line from the script? Or the two-line script from CrazyTerabyte?

[efa]

In your setup, there is probably no need for the repetition in the script. It's likely your device is switched by a single call of usb_modeswitch. Sending it again might cause the modem to reset itself.

Did you try using only one line from the script? Or the two-line script from CrazyTerabyte?

I had done all the detailed try on the other Notebook, and the two messages from Crazy do nothing.
On that I tried with command line step by step, sometimes with the first three messages of the script I got the switching, but to get a reliable switching I need the complete 6 messages sequence.
I will try again the step by step with this NetPC.
thanks for the hints

[efa]

Here what happen on the NetPC WIND MSI U90 with the 6 messages step by step and -W:

Code: Select all

connect the modem, no icon appear on desktop, no unit is mounted

$ lsusb
Bus 003 Device 010: ID 1a8d:1000

$ usb_modeswitch -W -v 0x1a8d -p 0x1000 -m 0x05 -M 555342435886b2851200000080000603000000020000000000000000000000 -n 1 -r 0x82

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

Taking all parameters from the command line

DefaultVendor=  0x1a8d
DefaultProduct= 0x1000
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint=0x05
MessageContent="555342435886b2851200000080000603000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint=0x82
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 008 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002

Looking for default devices ...
 Found default devices (1)
Accessing device 008 on bus 003 ...
Using endpoints 0x05 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
USB error: could not get bound driver: No data available
 No driver found. Either detached before or never attached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: BandLuxe
 Product String: CDROM           
Revision String: 1.01
-------------------------

Device description data (identification)
-------------------------
Manufacturer: BandRich, Inc.
     Product: USB Mass Storage
  Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x05 ...
 OK, message successfully sent
Reading the response to the message ...
 OK, response successfully read (18 bytes).
-> Run lsusb to note any changes. Bye.

$ lsusb
Bus 003 Device 010: ID 1a8d:1000

$ usb_modeswitch -W -v 0x1a8d -p 0x1000 -m 0x05 -M 55534243f814b9851200000080000603000000020000000000000000000000 -n 1 -r 0x82

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

Taking all parameters from the command line

DefaultVendor=  0x1a8d
DefaultProduct= 0x1000
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint=0x05
MessageContent="55534243f814b9851200000080000603000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint=0x82
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 008 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002

Looking for default devices ...
 Found default devices (1)
Accessing device 008 on bus 003 ...
Using endpoints 0x05 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
USB error: could not get bound driver: No data available
 No driver found. Either detached before or never attached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: BandLuxe
 Product String: CDROM           
Revision String: 1.01
-------------------------

Device description data (identification)
-------------------------
Manufacturer: BandRich, Inc.
     Product: USB Mass Storage
  Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x05 ...
 OK, message successfully sent
Reading the response to the message ...
 OK, response successfully read (18 bytes).
-> Run lsusb to note any changes. Bye.

$ lsusb
Bus 003 Device 010: ID 1a8d:1000

$ usb_modeswitch -W -v 0x1a8d -p 0x1000 -m 0x05 -M 5553424308a0e2851200000080000600000000020000000000000000000000 -n 1 -r 0x82

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

Taking all parameters from the command line

DefaultVendor=  0x1a8d
DefaultProduct= 0x1000
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint=0x05
MessageContent="5553424308a0e2851200000080000600000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint=0x82
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 008 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002

Looking for default devices ...
 Found default devices (1)
Accessing device 008 on bus 003 ...
Using endpoints 0x05 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
USB error: could not get bound driver: No data available
 No driver found. Either detached before or never attached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: BandLuxe
 Product String: CDROM           
Revision String: 1.01
-------------------------

Device description data (identification)
-------------------------
Manufacturer: BandRich, Inc.
     Product: USB Mass Storage
  Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x05 ...
 OK, message successfully sent
Reading the response to the message ...
 OK, response successfully read (13 bytes).
-> Run lsusb to note any changes. Bye.

$ lsusb
Bus 003 Device 010: ID 1a8d:1000

$ usb_modeswitch -W -v 0x1a8d -p 0x1000 -m 0x05 -M 555342435886b2851200000080000603000000020000000000000000000000 -n 1 -r 0x82

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

Taking all parameters from the command line

DefaultVendor=  0x1a8d
DefaultProduct= 0x1000
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint=0x05
MessageContent="555342435886b2851200000080000603000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint=0x82
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 008 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002

Looking for default devices ...
 Found default devices (1)
Accessing device 008 on bus 003 ...
Using endpoints 0x05 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
USB error: could not get bound driver: No data available
 No driver found. Either detached before or never attached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: BandLuxe
 Product String: CDROM           
Revision String: 1.01
-------------------------

Device description data (identification)
-------------------------
Manufacturer: BandRich, Inc.
     Product: USB Mass Storage
  Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x05 ...
 OK, message successfully sent
Reading the response to the message ...
 OK, response successfully read (18 bytes).
-> Run lsusb to note any changes. Bye.

$ lsusb
Bus 003 Device 010: ID 1a8d:1000

$ usb_modeswitch -W -v 0x1a8d -p 0x1000 -m 0x05 -M 55534243f814b9851200000080000603000000020000000000000000000000 -n 1 -r 0x82

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

Taking all parameters from the command line

DefaultVendor=  0x1a8d
DefaultProduct= 0x1000
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint=0x05
MessageContent="55534243f814b9851200000080000603000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint=0x82
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 008 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002

Looking for default devices ...
 Found default devices (1)
Accessing device 008 on bus 003 ...
Using endpoints 0x05 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
USB error: could not get bound driver: No data available
 No driver found. Either detached before or never attached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: BandLuxe
 Product String: CDROM           
Revision String: 1.01
-------------------------

Device description data (identification)
-------------------------
Manufacturer: BandRich, Inc.
     Product: USB Mass Storage
  Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x05 ...
 OK, message successfully sent
Reading the response to the message ...
 OK, response successfully read (18 bytes).
-> Run lsusb to note any changes. Bye.

$ lsusb
Bus 003 Device 010: ID 1a8d:1000

$ usb_modeswitch -W -v 0x1a8d -p 0x1000 -m 0x05 -M 5553424308a0e2851200000080000600000000020000000000000000000000 -n 1 -r 0x82

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

Taking all parameters from the command line

DefaultVendor=  0x1a8d
DefaultProduct= 0x1000
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint=0x05
MessageContent="5553424308a0e2851200000080000600000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint=0x82
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 008 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002

Looking for default devices ...
 Found default devices (1)
Accessing device 008 on bus 003 ...
Using endpoints 0x05 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
USB error: could not get bound driver: No data available
 No driver found. Either detached before or never attached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: BandLuxe
 Product String: CDROM           
Revision String: 1.01
-------------------------

Device description data (identification)
-------------------------
Manufacturer: BandRich, Inc.
     Product: USB Mass Storage
  Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x05 ...
 OK, message successfully sent
Reading the response to the message ...
 OK, response successfully read (13 bytes).
-> Run lsusb to note any changes. Bye.

$ lsusb
Bus 003 Device 010: ID 1a8d:1000

$ lsusb

$ lsusb
Bus 003 Device 012: ID 1a8d:1002 

As show only the 6th message do the switch.
At this time a new icon appear on the desktop and a new unit is mounted. Eject or not the unit does not help.
Same results, /dev/ttyUSB4 appear and suddently disappear, dmesg show the same log from /dev/ttyUSB0 to /dev/ttyUSB4

[Josh]

Hmm. Did you read CrazyTerabyte's blog entry linked above? Some firmware versions do have a timer function and can switch automatically. I suspect something like that interferes with your efforts.

If your Windows software contains the "Quick Startup" option mentioned in the blog, you could try activating it.

Only out of curiousity, you can try to use the ResetUSB option in your setup, either in the same command line as the switching command or on a separate line:

Code: Select all

usb_modeswitch -v 0x1a8d -p 0x1000 -R -M 55534243f814b9851200000080000603000000020000000000000000000000

or (after the switching line)

usb_modeswitch -v 0x1a8d -p 0x1000 -R

Note that the command line syntax has changed somewhat in 1.0.0 so for command line switches (on/off) you don't have to add "1" anymore.

Also, the endpoints are found by the program and don't have to be specified by the user.

Is there any change in behaviour if you skip the response reading (-n), as I did in the command above?

[efa]

Hmm. Did you read CrazyTerabyte's blog entry linked above? Some firmware versions do have a timer function and can switch automatically. I suspect something like that interferes with your efforts.

If your Windows software contains the "Quick Startup" option mentioned in the blog, you could try activating it.

I tried the 4 methods from Josh, noone work. No timer autoswitch.

My Firmare Version is: 405070_001_041
Apr 10 2008

I haven't the option Quick Startup in my software, that is
Version: 1.01.014 Build044
Oct 3 2008

Only out of curiousity, you can try to use the ResetUSB option in your setup, either in the same command line as the switching command or on a separate line:

Code: Select all

usb_modeswitch -v 0x1a8d -p 0x1000 -R -M 55534243f814b9851200000080000603000000020000000000000000000000

or (after the switching line)

usb_modeswitch -v 0x1a8d -p 0x1000 -R

Note that the command line syntax has changed somewhat in 1.0.0 so for command line switches (on/off) you don't have to add "1" anymore.

Also, the endpoints are found by the program and don't have to be specified by the user.

Is there any change in behaviour if you skip the response reading (-n), as I did in the command above?

I will try the reset hint.
In the meantime I updated usb_modeswitch to 1.04 and compiled myself with libusb.

[efa]

I updated to 1.0.5
The reset do a step ahead!
Here the complete log (this time switched with 3 messages only):

Code: Select all

Connect:
--------

# dmesg:

Aug 28 02:41:14 01ATO1600 kernel: [ 4516.920135] usb 3-1: new full speed USB device using uhci_hcd and address 15
Aug 28 02:41:14 01ATO1600 kernel: [ 4517.085938] usb 3-1: configuration #1 chosen from 1 choice
Aug 28 02:41:14 01ATO1600 kernel: [ 4517.103524] scsi18 : SCSI emulation for USB Mass Storage devices
Aug 28 02:41:15 01ATO1600 kernel: [ 4517.657225] usb 3-1: usbfs: process 14998 (usb_modeswitch) did not claim interface 0 before use
Aug 28 02:41:15 01ATO1600 kernel: [ 4517.698231] usb 3-1: usbfs: process 15004 (usb_modeswitch) did not claim interface 0 before use

# lsusb | grep 1a8d

Bus 003 Device 015: ID 1a8d:1000

# usb_modeswitch -W -v 0x1a8d -p 0x1000 -M 555342435886b2851200000080000603000000020000000000000000000000
Taking all parameters from the command line


 * usb_modeswitch: handle USB devices with multiple modes
 * Version 1.0.5 (C) Josua Dietze 2009
 * Based on libusb 0.1.12

DefaultVendor=  0x1a8d
DefaultProduct= 0x1000
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint= not set
MessageContent="555342435886b2851200000080000603000000020000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 015 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002

Looking for default devices ...
 Found default devices (1)
Accessing device 015 on bus 003 ...
Using endpoints 0x05 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
USB error: could not get bound driver: No data available
 No driver found. Either detached before or never attached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: �
   Model String: @P�����:
Revision String: ��i
-------------------------

Device description data (identification)
-------------------------
Manufacturer: BandRich, Inc.
     Product: USB Mass Storage
  Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x05 ...
 OK, message successfully sent
-> Run lsusb to note any changes. Bye.

# sleep 1

# lsusb | grep 1a8d
Bus 003 Device 015: ID 1a8d:1000  

# usb_modeswitch -W -v 0x1a8d -p 0x1000 -M 55534243f814b9851200000080000603000000020000000000000000000000
Taking all parameters from the command line


 * usb_modeswitch: handle USB devices with multiple modes
 * Version 1.0.5 (C) Josua Dietze 2009
 * Based on libusb 0.1.12

DefaultVendor=  0x1a8d
DefaultProduct= 0x1000
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint= not set
MessageContent="55534243f814b9851200000080000603000000020000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 015 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002

Looking for default devices ...
 Found default devices (1)
Accessing device 015 on bus 003 ...
Using endpoints 0x05 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
USB error: could not get bound driver: No data available
 No driver found. Either detached before or never attached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: �
   Model String: �*�����:
Revision String: ��i
-------------------------

Device description data (identification)
-------------------------
Manufacturer: BandRich, Inc.
     Product: USB Mass Storage
  Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x05 ...
 OK, message successfully sent
-> Run lsusb to note any changes. Bye.

# sleep 1

# lsusb | grep 1a8d
Bus 003 Device 015: ID 1a8d:1000  

# usb_modeswitch -W -v 0x1a8d -p 0x1000 -M 5553424308a0e2851200000080000600000000020000000000000000000000
Taking all parameters from the command line


 * usb_modeswitch: handle USB devices with multiple modes
 * Version 1.0.5 (C) Josua Dietze 2009
 * Based on libusb 0.1.12

DefaultVendor=  0x1a8d
DefaultProduct= 0x1000
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint= not set
MessageContent="5553424308a0e2851200000080000600000000020000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 015 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002

Looking for default devices ...
 Found default devices (1)
Accessing device 015 on bus 003 ...
Using endpoints 0x05 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
USB error: could not get bound driver: No data available
 No driver found. Either detached before or never attached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: (
   Model String: �C�����:
Revision String: ��i
-------------------------

Device description data (identification)
-------------------------
Manufacturer: BandRich, Inc.
     Product: USB Mass Storage
  Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x05 ...
 OK, message successfully sent
-> Run lsusb to note any changes. Bye.

# sleep 10

# lsusb | grep 1a8d

# sleep 1

# lsusb | grep 1a8d
Bus 003 Device 016: ID 1a8d:1002  

now ttyUSB ciclic appear and disapper:
--------------------------------------
# dmesg:

Aug 28 02:52:27 01ATO1600 kernel: [ 5189.765647] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
Aug 28 02:52:29 01ATO1600 kernel: [ 5191.174160] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
Aug 28 02:52:29 01ATO1600 kernel: [ 5191.174553] option 3-1:1.1: device disconnected
Aug 28 02:52:29 01ATO1600 kernel: [ 5191.175535] option 3-1:1.2: device disconnected
Aug 28 02:52:29 01ATO1600 kernel: [ 5191.284156] usb 3-1: reset full speed USB device using uhci_hcd and address 16
Aug 28 02:52:29 01ATO1600 kernel: [ 5191.435556] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 28 02:52:29 01ATO1600 kernel: [ 5191.437179] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB3
Aug 28 02:52:29 01ATO1600 kernel: [ 5191.437279] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 28 02:52:29 01ATO1600 kernel: [ 5191.438057] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB4
Aug 28 02:52:29 01ATO1600 kernel: [ 5191.765851] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Aug 28 02:52:31 01ATO1600 kernel: [ 5193.174169] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
Aug 28 02:52:31 01ATO1600 kernel: [ 5193.174550] option 3-1:1.1: device disconnected
Aug 28 02:52:31 01ATO1600 kernel: [ 5193.175548] option 3-1:1.2: device disconnected
Aug 28 02:52:31 01ATO1600 kernel: [ 5193.284155] usb 3-1: reset full speed USB device using uhci_hcd and address 16
Aug 28 02:52:31 01ATO1600 kernel: [ 5193.435556] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 28 02:52:31 01ATO1600 kernel: [ 5193.437181] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB0
Aug 28 02:52:31 01ATO1600 kernel: [ 5193.437283] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 28 02:52:31 01ATO1600 kernel: [ 5193.438059] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB4
Aug 28 02:52:31 01ATO1600 kernel: [ 5193.765455] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Aug 28 02:52:33 01ATO1600 kernel: [ 5195.174169] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
Aug 28 02:52:33 01ATO1600 kernel: [ 5195.174235] option 3-1:1.1: device disconnected
Aug 28 02:52:33 01ATO1600 kernel: [ 5195.174728] option 3-1:1.2: device disconnected
Aug 28 02:52:33 01ATO1600 kernel: [ 5195.284156] usb 3-1: reset full speed USB device using uhci_hcd and address 16
Aug 28 02:52:33 01ATO1600 kernel: [ 5195.435557] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 28 02:52:33 01ATO1600 kernel: [ 5195.437196] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB1
Aug 28 02:52:33 01ATO1600 kernel: [ 5195.437297] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 28 02:52:33 01ATO1600 kernel: [ 5195.437564] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB4

Send reset:
-----------
# usb_modeswitch -W -v 0x1a8d -p 0x1002 -R
Taking all parameters from the command line


 * usb_modeswitch: handle USB devices with multiple modes
 * Version 1.0.5 (C) Josua Dietze 2009
 * Based on libusb 0.1.12

DefaultVendor=  0x1a8d
DefaultProduct= 0x1002
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint= not set
MessageContent= not set
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 016 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 002

Looking for default devices ...
 Found default devices (1)
Accessing device 016 on bus 003 ...
Using endpoints 0x05 (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

Received inquiry data (detailed identification)
-------------------------
  Vendor String: BandLuxe
   Model String: CDROM           
Revision String: 1.01
-------------------------

Device description data (identification)
-------------------------
Manufacturer: BandRich, Inc.
     Product: BandLuxe  3.5G HSDPA Adapter
  Serial No.: 0359074011385517
-------------------------
Warning: no switching method given.
Resetting usb device .
 OK, device was reset
-> Run lsusb to note any changes. Bye.


Here /dev/ttyUSB* stabilize to a couple of port:
-----------------------------------------------

# dmesg
Aug 28 02:53:10 01ATO1600 kernel: [ 5232.572155] usb 3-1: reset full speed USB device using uhci_hcd and address 16
Aug 28 02:53:10 01ATO1600 kernel: [ 5232.723564] option 3-1:1.2: GSM modem (1-port) converter detected
Aug 28 02:53:10 01ATO1600 kernel: [ 5232.723804] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB0
Aug 28 02:53:10 01ATO1600 kernel: [ 5232.723859] option 3-1:1.1: GSM modem (1-port) converter detected
Aug 28 02:53:10 01ATO1600 kernel: [ 5232.723967] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB4
Aug 28 02:53:11 01ATO1600 kernel: [ 5233.767671] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Aug 28 02:53:13 01ATO1600 kernel: [ 5235.788795] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Aug 28 02:53:15 01ATO1600 kernel: [ 5237.668795] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3

# ls -l /dev/ttyU*
0 crw-rw---- 1 root dialout 188, 4 2009-08-28 02:53 /dev/ttyUSB4
0 crw-rw---- 1 root dialout 188, 0 2009-08-28 02:53 /dev/ttyUSB0

# ls -l /dev/ttyU*
0 crw-rw---- 1 root dialout 188, 4 2009-08-28 02:53 /dev/ttyUSB4
0 crw-rw---- 1 root dialout 188, 0 2009-08-28 02:53 /dev/ttyUSB0

But I cannot communicate with the modem using minicom

[Josh]

I'm not sure the "end state" you get is the one you want.

Some thoughts:

• in further logs, don't use the -W option; the verbose info is not helping much in your case and it bloats the output
• if you are working at the console, you don't need "sleep" commands. They do just nothing for a certain time which is only useful in automatic scripts
• you can also skip the SCSI inquiry with the -I option
• very suspicious: in the beginning of the log at 02:41:15 there is an indication that usb_modeswitch was already run. Do you have an udev rule to start it automatically?
• the storage device ws not initialized correctly; this might be due to the previous point
• did you try to give the reset option together with the switching command as I described in my previous post?

[efa]

[*]if you are working at the console, you don't need "sleep" commands. They do just nothing for a certain time which is only useful in automatic scripts

sure, the log is an edited text, reporting content of the script and its output interlieved

[*]very suspicious: in the beginning of the log at 02:41:15 there is an indication that usb_modeswitch was already run. Do you have an udev rule to start it automatically?
[*]the storage device was not initialized correctly; this might be due to the previous point

that messages in dmesg appear after (I dont remember):
- install a Vanilla Kernel 2.6.30, because seemed that have native support (but don't worked)
- compile/install usb_modeswitch 1.0.3. I do only a #make install of usb_modeswitch. Something related to 'Makefile.integrated'?
With Debian packaged 1.0.2 and official Ubuntu 2.6.28 there isn't.

[*]did you try to give the reset option together with the switching command as I described in my previous post?[/list][/quote]
no only following switching as separate command.
The problem is that sometimes is the 3th message that do the switch, somtimes is the 6th.

[efa]

[*]you can also skip the SCSI inquiry with the -I option

I tried, but the modem never switch with -I, so I do not use it.

Finally I tried to connet with PPP (wvdial) after the reset, using one of the ttyUSB port and work!
THANKS.
minicom still can't communicate with the modem (maybe because max speed is 115K?), but wvdial (at 400K) can.

[*]did you try to give the reset option together with the switching command as I described in you previous post?[/list]

no, but now that resetting after 6th message works I will do (togheter 3th or 6th message) only if you think is usefull for your application. Let me know.

Remain to me a curiosity: why on WIND MSI U90 netbook with Ubuntu 9.04 is required a reset after the switch, when on a Fujitsu/Siemens notebook with Ubuntu 9.04 is not required?