Automatic Activation, Hotplug and UDEV, Configuration
Post Reply
Y.J. Cao
Posts: 4
Joined: 03 Jul 2011, 12:55

no Find ttyUSB* after usb-modeswitch report switch succeed

Post by Y.J. Cao » 03 Jul 2011, 15:34

I am trouble in using usb_modeswitch.
I can't find the ttyUSB* in /dev when the usb_modeswitch report:
***************************************************************************************************************************
Reading config file: ../19d2:0026

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

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x19d2
DefaultProduct= 0x0026
TargetVendor= 0x19d2
TargetProduct= 0x0152
TargetClass= not set
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
MessageEndpoint= not set
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint= not set
Interface=0x00

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

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

Looking for target devices ...
searching devices, found USB ID 19d2:0026
found matching vendor ID
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0002
No devices in target mode or class found
Looking for default devices ...
searching devices, found USB ID 19d2:0026
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0002
Found devices in default mode, class or configuration (1)
Accessing device 006 on bus 002 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using endpoints 0x09 (out) and 0x89 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached

SCSI inquiry data (for identification)
-------------------------
Vendor String: ZTE Corp
Model String: USB Storage
Revision String: 2.31
-------------------------

USB description data (for identification)
-------------------------
Manufacturer: Qualcomm, Incorporated
Product: USB ZTE Storage
Serial No.: AC580_CT_C010001
-------------------------
Setting up communication with interface 0 ...
Using endpoint 0x09 for message sending ...
Trying to send message 1 to endpoint 0x09 ...
OK, message successfully sent
Reading the response to message 1 (CSW) ...
OK, response successfully read (13 bytes).
Trying to send message 2 to endpoint 0x09 ...
OK, message successfully sent
Reading the response to message 2 (CSW) ...
OK, response successfully read (13 bytes).
Resetting response endpoint 0x89
Resetting message endpoint 0x09

Checking for mode switch (max. 20 times, once per second) ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
USB error: could not claim interface 0: No such device
USB error: could not release intf 0: No such device
Original device can't be accessed anymore. Good.
Searching for target devices ...
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 001 on 001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 001 on 001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 007 on 002
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 001
searching devices, found USB ID 19d2:0152
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0002

Found target device, now opening

Found target device 007 on bus 002

Target device description data
-------------------------
Manufacturer: ZTE, Incorporated
Product: ZTE EVDO Technologies MSM
Serial No.: not provided
-------------------------
Found correct target device

Mode switch succeeded. Bye.

/**************************************************************************************************

I am sure the device info is correct, and the usbserial.ko is insmod in the kernel.
Besides if i input the command mdev -s there are three device nodes come out :usbdev1.1 c 189 0 usbdev2.1 c 189 123 usbdev c 189 165.
however, even these nodes come out, the dail script still don't work corretly.

thanks if giving same advices!


Y.J. Cao

Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 03 Jul 2011, 17:01

Are you calling usb_modeswitch manually?

If you want the driver to be loaded, the automatical way must work first. And don't use "usbserial". See the main doc page.

Annother possibility ist that this is rather a CDC device. In that case, the "cdc_acm" driver would be loaded automatically after switching in any case. You might want to check if you have it, just to be on the safe side.


Y.J. Cao
Posts: 4
Joined: 03 Jul 2011, 12:55

Post by Y.J. Cao » 04 Jul 2011, 16:06

Josh wrote:Are you calling usb_modeswitch manually?

If you want the driver to be loaded, the automatical way must work first. And don't use "usbserial". See the main doc page.

Annother possibility ist that this is rather a CDC device. In that case, the "cdc_acm" driver would be loaded automatically after switching in any case. You might want to check if you have it, just to be on the safe side.
thanks!

Post Reply