Author Message

<  Device Information  ~  ZTE MF627

PostPosted: Thu May 06, 2010 1:48 pm
Posts: 6Joined: Thu May 06, 2010 1:27 pm
Trying to get the ZTE MF627 working.

Here is the /var/log/usb_modeswitch_5-5:1.0 file:
http://pastebin.com/ZsZcrEZe

Here is a snippet of the /var/log/messages file:
http://pastebin.com/gSU0STh0

Here is a snippet of the /var/log/syslog file:
http://pastebin.com/Gjv7hD2h

Before I tried to use usb-modeswitch-1.1.2 I did this:
http://www.olafusimichael.com/2009/12/h ... linux.html
Quote:
In the terminal I simply entered
AT+ZOPRT=5
AT+ZCDRUN=8
This will change the default mode of the modem from the CD drive to the modem mode. But you will not be able to install the software that came preloaded into the device, so if you want to use it on a new windows system, you might have to run AT+ZCDRUN=9 to enable you install the MTN or any other proprietary software that came with the modem.


I'm not sure what AT+ZOPRT=5 did or changed and I don't know if this command has interfered with the operation of usb-modeswitch. I later on ran the AT+ZCDRUN=9 command but I don't know what the original value of AT+ZOPRT was.


Offline Profile
PostPosted: Thu May 06, 2010 6:24 pm
Site AdminPosts: 4839Joined: Sat Nov 03, 2007 12:30 am
The usb_modeswitch log is almost good. What's missing is your target product ID in the list; we have to add "0064" to the "TargetProductList" in /etc/usb_modeswitch.d/19d2:2000.

I will do that in the next data release due this weekend, but you can do it right away on your system.

Anyway, the "option" driver seems to have been bound somehow according to your syslogs; "ttyUSB0" and "ttyUSB1" are ready and should be usable.

The only thing not working from usb_modeswitch's side is the adding of the "gsmmodem" symlink, but this is just a convenience feature to easily find the connect port (with interrupt transfer).



Offline Profile
PostPosted: Mon May 10, 2010 2:20 pm
Posts: 6Joined: Thu May 06, 2010 1:27 pm
Josh wrote:
The usb_modeswitch log is almost good.

I'm confused :? Doesn't your program generate that logfile?? If it does, then why is the generated log file almost good, why not completely good??


Offline Profile
PostPosted: Mon May 10, 2010 3:51 pm
Site AdminPosts: 4839Joined: Sat Nov 03, 2007 12:30 am
My wording might have been a bit too offhand ...

What I meant to say is that the content of the log file indicates that most steps worked fine; just the last steps (success check and driver binding) failed because the target ID of your model is yet unknown to the configuration file.



Offline Profile
PostPosted: Tue May 11, 2010 4:01 am
Posts: 6Joined: Thu May 06, 2010 1:27 pm
Josh wrote:
just the last steps (success check and driver binding) failed because the target ID of your model is yet unknown to the configuration file.


How do I go about discovering what the target ID of my model USB modem should be? Do I use Windows and SniffUSB?


Offline Profile
PostPosted: Tue May 11, 2010 11:19 am
Site AdminPosts: 4839Joined: Sat Nov 03, 2007 12:30 am
That's easy; it's in the "syslog" that you posted:

May 6 20:53:53 zeek klogd: usb 5-5: New USB device found, idVendor=19d2, idProduct=0064

The switching worked, so the device reconnects with the new ID afterwards. Just add the "0064" as described in my earlier post.



Offline Profile
PostPosted: Mon May 31, 2010 2:21 pm
Posts: 5Joined: Mon May 31, 2010 1:13 pm
try to use this device in CentOS 5.5
Quote:
Bus 001 Device 008: ID 19d2:2000 ONDA Communication S.p.A. ZTE MF627/MF628/MF628+ HSDPA
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x19d2 ONDA Communication S.p.A.
idProduct 0x2000 ZTE MF627/MF628/MF628+ HSDPA
bcdDevice 0.00
iManufacturer 2 ZTE, Incorporated
iProduct 1 ZTE CDMA Technologies MSM
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 5 SFF-8070i
bInterfaceProtocol 80
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 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
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

after starting usb_modeswitch execution stops at the line:
Quote:
Looking for default devices ...
Found devices in default mode or class (1)
Accessing device 008 on bus 001 ...
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
No driver found. Either detached before or never attached

and nothing else happens.

Start with strace in stopping time wrote:
Quote:
ioctl(5, USBDEVFS_CLAIMINTERFACE, 0xbf967074) = 0
ioctl(5, USBDEVFS_CLEAR_HALT, 0xbf967058) = 0
ioctl(5, USBDEVFS_SUBMITURB, 0x91d7928) = 0
clock_gettime(CLOCK_MONOTONIC, {19973, 942691492}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLOUT}], 2, 60000) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {20033, 938842191}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLOUT}], 2, 60000) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {20093, 934653908}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLOUT}], 2, 60000) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {20153, 931108606}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLOUT}], 2, 60000) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {20213, 928052826}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLOUT}], 2, 60000) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {20273, 924263845}) = 0
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLOUT}], 2, 60000) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {20333, 922585269}) = 0

device is recognized by the kernel as follows:
Quote:
May 31 18:53:50 localhost kernel: usb 1-2: new high speed USB device using ehci_hcd and address 5
May 31 18:53:50 localhost kernel: usb 1-2: configuration #1 chosen from 1 choice
May 31 18:53:50 localhost kernel: scsi3 : SCSI emulation for USB Mass Storage devices
May 31 18:53:55 localhost kernel: Vendor: ZTE Model: USB SCSI CD-ROM Rev: 2.31
May 31 18:53:55 localhost kernel: Type: CD-ROM ANSI SCSI revision: 00
May 31 18:53:55 localhost kernel: scsi 3:0:0:0: Attached scsi generic sg1 type 5
May 31 18:53:55 localhost kernel: sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
May 31 18:53:55 localhost kernel: Uniform CD-ROM driver Revision: 3.20

What could be the problem?


Offline Profile
PostPosted: Mon May 31, 2010 6:55 pm
Site AdminPosts: 4839Joined: Sat Nov 03, 2007 12:30 am
Which version of usb_modeswitch are you using?

Did you run manually or did you activate the logging in /etc/usb_modeswitch.conf ?


Offline Profile
PostPosted: Tue Jun 01, 2010 4:40 am
Posts: 5Joined: Mon May 31, 2010 1:13 pm
usb_modeswitch version 1.1.2. (libusb 0.1.12)
Tried in different ways. Manual (usb_modeswitch -v 0x19d2 -p 0x2000 -M 55534243123456782400000080000C85000000240000000000000000000000 -R 1) and a configuration file. The same result.


Offline Profile
PostPosted: Tue Jun 01, 2010 8:19 am
Site AdminPosts: 4839Joined: Sat Nov 03, 2007 12:30 am
Why are you adding a "reset" to your command line?

Anyway, two things to do:

1. Change the file "/etc/usb_modeswitch.d/19d2:2000" to this:
Code:
DefaultVendor=  0x19d2
DefaultProduct= 0x2000

TargetVendor=   0x19d2
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063,0064"

CheckSuccess=20

MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
MessageContent2="55534243123456782000000080000c85010101180101010101000000000000"
2. Check that there are no other rules trying to handle 19d2:2000 in /lib/udev/rules.d

Also, switch on logging in /etc/usb_modeswitch.conf. Then plug your device again and after a while look into /var/log for a file named "usb_modeswitch_<something>.log".



Offline Profile
PostPosted: Tue Jun 01, 2010 8:24 am
Site AdminPosts: 4839Joined: Sat Nov 03, 2007 12:30 am
And one more thing: what is your kernel version ?


Offline Profile
PostPosted: Tue Jun 01, 2010 8:55 am
Posts: 5Joined: Mon May 31, 2010 1:13 pm
2.6.18-164.11.1.el5

Other models of modems (most models Huawei, ZTE MF100) are working without problems, problems only with MF627 (tested on different modems).


Offline Profile
PostPosted: Tue Jun 01, 2010 9:55 am
Posts: 5Joined: Mon May 31, 2010 1:13 pm
another attempt

usb_modeswitch -I -W -c /etc/usb_modeswitch.d/19d2:2000

Quote:
Reading config file: /etc/usb_modeswitch.d/19d2:2000

* usb-modeswitch: handle USB devices with multiple modes
* Version 1.1.2alpha (C) Josua Dietze 2010
* Based on libusb0 (0.1.12 and above)

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x19d2
DefaultProduct= 0x2000
TargetVendor= 0x19d2
TargetProduct= not set
TargetProductList=0001,0002,0015,0016,0017,0031,0037,0052,0055,0063,0064
TargetClass= not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
MessageEndpoint= not set
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
MessageContent2="55534243123456782000000080000c85010101180101010101000000000000"
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

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


Looking for target devices ...
searching devices, found USB ID 19d2:2000
found matching vendor ID
searching devices, found USB ID 0000:0000
searching devices, found USB ID 0000:0000
searching devices, found USB ID 0000:0000
searching devices, found USB ID 0000:0000
searching devices, found USB ID 22b8:5802
searching devices, found USB ID 0000:0000
searching devices, found USB ID 0519:0003
searching devices, found USB ID 1aad:0001
No devices in target mode or class found
Looking for default devices ...
searching devices, found USB ID 19d2:2000
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 0000:0000
searching devices, found USB ID 0000:0000
searching devices, found USB ID 0000:0000
searching devices, found USB ID 0000:0000
searching devices, found USB ID 22b8:5802
searching devices, found USB ID 0000:0000
searching devices, found USB ID 0519:0003
searching devices, found USB ID 1aad:0001
Found devices in default mode or class (1)
Accessing device 007 on bus 001 ...

USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: ZTE CDMA Technologies MSM
Serial No.: not provided
-------------------------
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 ...
Sending the message returned error -110. Trying to continue
Trying to send message 2 to endpoint 0x01 ...
Sending the message returned error -110. Trying to continue

Checking for mode switch (max. 20 times, once per second) ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Original device still present after the timeout

Mode switch most likely failed. Bye.


Offline Profile
PostPosted: Tue Jun 01, 2010 1:20 pm
Site AdminPosts: 4839Joined: Sat Nov 03, 2007 12:30 am
Not even the first command is reaching the device.

It is rather strange that the storage driver did not bind to the device. This may be necessary to initialize it properly.

Did you check for annother udev rule handling the device? Grep for "19d2" in /etc/udev/rules.d and in /lib/udev/rules.d; disable any rule for your IDs (except in 40-usb_modeswitch.rules, of course).



Offline Profile
PostPosted: Wed Jun 02, 2010 1:41 pm
Posts: 5Joined: Mon May 31, 2010 1:13 pm
No other rules do not use the device. It seems to me that the problem is that InterfaceSubClass = 05 (SFF-8070i). Other modems and other models ZTE have InterfaceSubClass = 06 (SCSI).
For myself yet solved the problem of sending in the HyperTerminal Windows command AT+ZCDRUN=8, then the modem is defined as 19d2: 0031 and works.


Offline Profile

Display posts from previous:  Sort by:

All times are UTC + 1 hour [ DST ]
Page 1 of 2
17 posts
Go to page 1, 2  Next
Users browsing this forum: Google [Bot] and 0 guests
Search for:
Post new topic  Reply to topic
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum