[zml]

modeSwitchByCfgFile 530 cmd = usb_modeswitch -v 0x2001 -p 0xa80b -I -W -c /tmp/3G/2001_a80b_0 &
Start find usb_modeswitch

Reading config file: /tmp/3G/2001_a80b_0

* usb_modeswitch: handle USB devices with multiple modes
* Version 1.1.9 (C) Josua Dietze 2011
* Based on libusb0 (0.1.12 and above)

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x2001
DefaultProduct= 0xa80b
TargetVendor= not set
TargetProduct= not set
TargetClass= not set
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0usb 1-1: USB disconnect, address 4

SonyMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="555342431048748500000000000003f0010100000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode disabled

MessageContent is 555342431048748500000000000003f0010100000000000000000000000000
MessageContent over
Note: target parameter missing; success check limited
Looking for default devices ...
searching devices, found USB ID 2001:a80b
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 1d6b:0002
Found devices in default mode, class or configuration (1)
Accessing device 004 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: D-Link,Inc
Product: D-Link DWM-156
Serial No.: 532274401106080
-------------------------
Looking for active driver ...
No driver found. Either detached before or never attached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01
Device is gone, skipping any further commands

Checking for mode switch (max. 20 times, once per second) ...
usb 1-1: new high speed USB device using ar7240-ehci and address 5
usb 1-1: configuration #1 chosen from 1 choice
Start find usb_modeswitch
(For a better success check provide target IDs or class)
Original device vanished after switching

Mode switch most likely succeeded. Bye.

[Josh]

Thank you very much for this information.

To add this to the data package, I would need to know the target ID, (the USB ID that is shown by the "lsusb" command after the mode switching). Can you provide that too, please?

[zml]

Thank you very much for this information.

To add this to the data package, I would need to know the target ID, (the USB ID that is shown by the "lsusb" command after the mode switching). Can you provide that too, please?

The target ID is (2001,7d00)

Josh,do you know the "eject" tool ?

My kernel version is 2.6.31, now I can't use it .

Could you help me ?

[Josh]

Thanks for the additional info!

If you say you "can't use" the eject tool, does that mean you get errors? If so, what kind of errors? And what exactly do you want to do with the tool?

Maybe you can post a log?

[zml]

Thanks for the additional info!

If you say you "can't use" the eject tool, does that mean you get errors? If so, what kind of errors? And what exactly do you want to do with the tool?

Maybe you can post a log?

when opening the device, it returned error -1.

Because some modem must use the tool to switch , such as MU351, E303 and so on,
so I wanna get it work.

To use the eject tool, I added usb-storage.ko, scsi_mod.ko, cdrom.ko, sr_mod.ko.
And the four ko was insmod one by one, the sr_mod.ko added some important block device infomation to the kobj_map, you know it .

But later , I didn't know what happened on USB device, the sr_mod.ko was removed , so the open function couldn't work and return error -1.

Do you know what I said ?

[Josh]

You can send the SCSI "Eject" command with usb_modeswitch also. Maybe this will work:

MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"

The first is "Allow Medium Removal"; only some modems need it but it is never wrong.

Oh, and sometimes timing is very important - not too soon and not too late after plugging ...

[zml]

You can send the SCSI "Eject" command with usb_modeswitch also. Maybe this will work:

MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"

The first is "Allow Medium Removal"; only some modems need it but it is never wrong.

Oh, and sometimes timing is very important - not too soon and not too late after plugging ...

What will happen if too late after plugging? And is it important that there is no Target vid and pid?

I find some devices with vid 12d1 and pid 1446, there are 2 cmds to switch them: 55534243123456780000000000000011062000000100000000000000000000 && 55534243000000000000000000000011060000000100000000000000000000.
But if switched by the wrong cmd, it can't dial successfully.

[zml]

You can send the SCSI "Eject" command with usb_modeswitch also. Maybe this will work:

MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"

The first is "Allow Medium Removal"; only some modems need it but it is never wrong.

Oh, and sometimes timing is very important - not too soon and not too late after plugging ...

It's a pity that the SCSI "Eject" command also can't work ,
maybe the drivers we used occured error, could you tell me the drivers that we should use?

[Josh]

Can you see what's going on when plugging in by calling the "dmesg" tool repeatedly?
Some modems have a badly behaving pseudo CD-ROM ...

As I said, timing may be crucial.

Also, make sure that there is not already an active usb_modeswitch installation that treats the modems automatically.

[jzinedine]

Can you see what's going on when plugging in by calling the "dmesg" tool repeatedly?
Some modems have a badly behaving pseudo CD-ROM ...

As I said, timing may be crucial.

Also, make sure that there is not already an active usb_modeswitch installation that treats the modems automatically.

Hi Guys,

I have problem with this d-link 3G modem with the same Vendor Id and Product Id (DefaultVendor= 0x2001 DefaultProduct=0xa80b ).
Randomly when the modem works, it will disconnect and disappear from lsusb list.

The problem will not occur in Windows.

Appreciate any help or hints.

Best,
Jani

[LOM]

Hi Guys,

I have problem with this d-link 3G modem with the same Vendor Id and Product Id (DefaultVendor= 0x2001 DefaultProduct=0xa80b ).
Randomly when the modem works, it will disconnect and disappear from lsusb list.

The problem will not occur in Windows.

Appreciate any help or hints.

Best,
Jani

This is not a usb_modeswitch problem, usb_modeswitch does only switch the dongle into modem mode and will then exit - it has done all what it should do.
If the dongle disappears completely from the USB bus, then it is a hardware problem or a usb core/subsystem problem in the kernel you are using.