Hi,
My Huawei E220 begins to be old and I went to SFR with my EEEPC to test other 3G USB modem. Currently SFR have more than ZTE K3565-Z ABCD.
I plugged it on my EEEPC, unfortunately it has not been recognized, below the error messages.
I use a Debian Squeeze:
- Kernel 2.6.32
- usb-modeswitch 1.1.2-3
- usb-modeswitch-data 20100418-1
The error messages :
Jun 8 13:44:16 lobon kernel: [ 478.816209] usb 1-3: new high speed USB device using ehci_hcd and address 10
Jun 8 13:44:17 lobon kernel: [ 478.962316] usb 1-3: New USB device found, idVendor=19d2, idProduct=2000
Jun 8 13:44:17 lobon kernel: [ 478.962329] usb 1-3: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Jun 8 13:44:17 lobon kernel: [ 478.962339] usb 1-3: Product: ZTE CDMA Technologies MSM
Jun 8 13:44:17 lobon kernel: [ 478.962346] usb 1-3: Manufacturer: ZTE, Incorporated
Jun 8 13:44:17 lobon kernel: [ 478.962633] usb 1-3: configuration #1 chosen from 1 choice
Jun 8 13:44:17 lobon kernel: [ 478.971673] scsi19 : SCSI emulation for USB Mass Storage devices
Jun 8 13:44:17 lobon kernel: [ 478.972629] usb-storage: device found at 10
Jun 8 13:44:17 lobon kernel: [ 478.972637] usb-storage: waiting for device to settle before scanning
Jun 8 13:44:22 lobon kernel: [ 483.973525] usb-storage: device scan complete
Jun 8 13:44:22 lobon kernel: [ 483.975627] scsi 19:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0
Jun 8 13:44:22 lobon kernel: [ 483.996092] sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
Jun 8 13:44:22 lobon kernel: [ 483.996424] sr 19:0:0:0: Attached scsi CD-ROM sr0
Jun 8 13:44:22 lobon kernel: [ 483.996633] sr 19:0:0:0: Attached scsi generic sg2 type 5
Jun 8 13:44:35 lobon kernel: [ 496.945465] sr0: CDROM (ioctl) error, command: Xdread, Read track info 52 01 00 00 00 01 00 00 08 00
Jun 8 13:44:35 lobon kernel: [ 496.945501] sr: Sense Key : Hardware Error [current]
Jun 8 13:44:35 lobon kernel: [ 496.945512] sr: Add. Sense: No additional sense information
Jun 8 13:45:09 lobon kernel: [ 531.421639] usb 1-3: USB disconnect, address 10
It bug before the modem is detected.
I do not know if there is a problem with usb-modeswitch, the kernel or the ZTE firmware ?
Regards.
Hi,
Thank you for your reply.
Normally I have no problem to test. But in the SFR store, I just tested the ZTE 3G USB dongle on my EeePC. As it was not recognized I did not buy.
I can not go back in the SFR store to test too often.
The USB device identifier is : idVendor=19d2, idProduct=2000
This identifier is known to USB_ModeSwitch :
/etc/usb_modeswitch.d/19d2:2000
But, I did not find this identifier in the kernel source of 2.6.32 or in the GIT of 2.6.35: /usr/src/linux/drivers/usb/serial/option.c
Is this identifier should not be known to the kernel?
If you think yes, I post a bug report to the kernel.
Regards.
Thank you for your reply.
Normally I have no problem to test. But in the SFR store, I just tested the ZTE 3G USB dongle on my EeePC. As it was not recognized I did not buy.
I can not go back in the SFR store to test too often.
The USB device identifier is : idVendor=19d2, idProduct=2000
This identifier is known to USB_ModeSwitch :
/etc/usb_modeswitch.d/19d2:2000
But, I did not find this identifier in the kernel source of 2.6.32 or in the GIT of 2.6.35: /usr/src/linux/drivers/usb/serial/option.c
Is this identifier should not be known to the kernel?
If you think yes, I post a bug report to the kernel.
Regards.
The 19d2:2000 does not have to be known to the "option" driver. It is the ID only for the storage mode; it will change after switching.
With kernels after 2.6.26, it's not essential to add new IDs to the "option" driver because they can be activated on the fly if the module is loaded. This is what usb_modeswitch does after mode switching.
If you are able to test again try to change the 19d2:2000 config file to the following content:
With kernels after 2.6.26, it's not essential to add new IDs to the "option" driver because they can be activated on the fly if the module is loaded. This is what usb_modeswitch does after mode switching.
If you are able to test again try to change the 19d2:2000 config file to the following content:
Code: Select all
########################################################
# ZTE models
DefaultVendor= 0x19d2
DefaultProduct= 0x2000
TargetVendor= 0x19d2
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063"
CheckSuccess=20
MessageContent="5553424312345678240000008000061b000000020000000000000000000000"
MessageContent2="55534243123456782400000080000685000000240000000000000000000000"
NeedResponse=1Hi,
I went back to the SFR store and I've tested the same ZTE 3G USB dongle.
I updated the kernel to 2.6.34. The ZTE 3G USB dongle has not been recognized, following tests
With the original "19d2:2000" file:
/var/log/usb_modeswitch_1-2:1.0 :
USB_ModeSwitch log from Wed Jun 16 13:46:46 CEST 2010
Using global config file: /etc/usb_modeswitch.conf
raw args from udev: /1-2:1.0
Bus ID for device not given by udev.
Trying to determine it from kernel name (1-2:1.0) ...
USB dir exists: /sys/bus/usb/devices/1-2
Warning: USB attribute "serial" not found.
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product ZTE CDMA Technologies MSM
serial
----------------
SCSI attributes not needed, moving on
/var/log/syslog:
Jun 16 13:46:46 lobon kernel: [ 49.480177] usb 1-2: new high speed USB device using ehci_hcd and address 4
Jun 16 13:46:46 lobon kernel: [ 49.625213] usb 1-2: New USB device found, idVendor=19d2, idProduct=2000
Jun 16 13:46:46 lobon kernel: [ 49.625227] usb 1-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Jun 16 13:46:46 lobon kernel: [ 49.625237] usb 1-2: Product: ZTE CDMA Technologies MSM
Jun 16 13:46:46 lobon kernel: [ 49.625244] usb 1-2: Manufacturer: ZTE, Incorporated
Jun 16 13:46:46 lobon kernel: [ 49.635318] scsi3 : usb-storage 1-2:1.0
Jun 16 13:46:47 lobon kernel: [ 50.639652] scsi 3:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0
Jun 16 13:46:47 lobon kernel: [ 50.762354] sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
Jun 16 13:46:47 lobon kernel: [ 50.762367] Uniform CD-ROM driver Revision: 3.20
Jun 16 13:46:47 lobon kernel: [ 50.764813] sr 3:0:0:0: Attached scsi CD-ROM sr0
Jun 16 13:46:47 lobon kernel: [ 50.832846] sd 1:0:0:0: Attached scsi generic sg0 type 0
Jun 16 13:46:47 lobon kernel: [ 50.837474] sd 2:0:0:0: Attached scsi generic sg1 type 0
Jun 16 13:46:47 lobon kernel: [ 50.841140] sr 3:0:0:0: Attached scsi generic sg2 type 5
Jun 16 13:47:00 lobon kernel: [ 63.143157] sr0: CDROM (ioctl) error, command: Xdread, Read track info 52 01 00 00 00 01 00 00 08 00
Jun 16 13:47:00 lobon kernel: [ 63.143191] sr: Sense Key : Hardware Error [current]
Jun 16 13:47:00 lobon kernel: [ 63.143202] sr: Add. Sense: No additional sense information
Jun 16 13:47:26 lobon kernel: [ 89.576848] usb 1-2: USB disconnect, address 4
With your "19d2:2000" file:
/var/log/usb_modeswitch_1-2:1.0 :
USB_ModeSwitch log from Wed Jun 16 13:50:39 CEST 2010
Using global config file: /etc/usb_modeswitch.conf
raw args from udev: /1-2:1.0
Bus ID for device not given by udev.
Trying to determine it from kernel name (1-2:1.0) ...
USB dir exists: /sys/bus/usb/devices/1-2
Warning: USB attribute "serial" not found.
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product ZTE CDMA Technologies MSM
serial
----------------
SCSI attributes not needed, moving on
/var/log/syslog:
Jun 16 13:50:39 lobon kernel: [ 58.760179] usb 1-2: new high speed USB device using ehci_hcd and address 4
Jun 16 13:50:39 lobon kernel: [ 58.905374] usb 1-2: New USB device found, idVendor=19d2, idProduct=2000
Jun 16 13:50:39 lobon kernel: [ 58.905389] usb 1-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Jun 16 13:50:39 lobon kernel: [ 58.905399] usb 1-2: Product: ZTE CDMA Technologies MSM
Jun 16 13:50:39 lobon kernel: [ 58.905406] usb 1-2: Manufacturer: ZTE, Incorporated
Jun 16 13:50:39 lobon kernel: [ 58.916815] scsi3 : usb-storage 1-2:1.0
Jun 16 13:50:40 lobon kernel: [ 59.919557] scsi 3:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0
Jun 16 13:50:40 lobon kernel: [ 60.058393] sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
Jun 16 13:50:40 lobon kernel: [ 60.058406] Uniform CD-ROM driver Revision: 3.20
Jun 16 13:50:40 lobon kernel: [ 60.060793] sr 3:0:0:0: Attached scsi CD-ROM sr0
Jun 16 13:50:41 lobon kernel: [ 60.131951] sd 1:0:0:0: Attached scsi generic sg0 type 0
Jun 16 13:50:41 lobon kernel: [ 60.137214] sd 2:0:0:0: Attached scsi generic sg1 type 0
Jun 16 13:50:41 lobon kernel: [ 60.140874] sr 3:0:0:0: Attached scsi generic sg2 type 5
Jun 16 13:50:55 lobon kernel: [ 74.148207] sr0: CDROM (ioctl) error, command: Xdread, Read track info 52 01 00 00 00 01 00 00 08 00
Jun 16 13:50:55 lobon kernel: [ 74.148240] sr: Sense Key : Hardware Error [current]
Jun 16 13:50:55 lobon kernel: [ 74.148251] sr: Add. Sense: No additional sense information
Jun 16 13:52:30 lobon kernel: [ 169.206923] usb 1-2: USB disconnect, address 4
Regards.
I went back to the SFR store and I've tested the same ZTE 3G USB dongle.
I updated the kernel to 2.6.34. The ZTE 3G USB dongle has not been recognized, following tests
With the original "19d2:2000" file:
/var/log/usb_modeswitch_1-2:1.0 :
USB_ModeSwitch log from Wed Jun 16 13:46:46 CEST 2010
Using global config file: /etc/usb_modeswitch.conf
raw args from udev: /1-2:1.0
Bus ID for device not given by udev.
Trying to determine it from kernel name (1-2:1.0) ...
USB dir exists: /sys/bus/usb/devices/1-2
Warning: USB attribute "serial" not found.
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product ZTE CDMA Technologies MSM
serial
----------------
SCSI attributes not needed, moving on
/var/log/syslog:
Jun 16 13:46:46 lobon kernel: [ 49.480177] usb 1-2: new high speed USB device using ehci_hcd and address 4
Jun 16 13:46:46 lobon kernel: [ 49.625213] usb 1-2: New USB device found, idVendor=19d2, idProduct=2000
Jun 16 13:46:46 lobon kernel: [ 49.625227] usb 1-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Jun 16 13:46:46 lobon kernel: [ 49.625237] usb 1-2: Product: ZTE CDMA Technologies MSM
Jun 16 13:46:46 lobon kernel: [ 49.625244] usb 1-2: Manufacturer: ZTE, Incorporated
Jun 16 13:46:46 lobon kernel: [ 49.635318] scsi3 : usb-storage 1-2:1.0
Jun 16 13:46:47 lobon kernel: [ 50.639652] scsi 3:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0
Jun 16 13:46:47 lobon kernel: [ 50.762354] sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
Jun 16 13:46:47 lobon kernel: [ 50.762367] Uniform CD-ROM driver Revision: 3.20
Jun 16 13:46:47 lobon kernel: [ 50.764813] sr 3:0:0:0: Attached scsi CD-ROM sr0
Jun 16 13:46:47 lobon kernel: [ 50.832846] sd 1:0:0:0: Attached scsi generic sg0 type 0
Jun 16 13:46:47 lobon kernel: [ 50.837474] sd 2:0:0:0: Attached scsi generic sg1 type 0
Jun 16 13:46:47 lobon kernel: [ 50.841140] sr 3:0:0:0: Attached scsi generic sg2 type 5
Jun 16 13:47:00 lobon kernel: [ 63.143157] sr0: CDROM (ioctl) error, command: Xdread, Read track info 52 01 00 00 00 01 00 00 08 00
Jun 16 13:47:00 lobon kernel: [ 63.143191] sr: Sense Key : Hardware Error [current]
Jun 16 13:47:00 lobon kernel: [ 63.143202] sr: Add. Sense: No additional sense information
Jun 16 13:47:26 lobon kernel: [ 89.576848] usb 1-2: USB disconnect, address 4
With your "19d2:2000" file:
/var/log/usb_modeswitch_1-2:1.0 :
USB_ModeSwitch log from Wed Jun 16 13:50:39 CEST 2010
Using global config file: /etc/usb_modeswitch.conf
raw args from udev: /1-2:1.0
Bus ID for device not given by udev.
Trying to determine it from kernel name (1-2:1.0) ...
USB dir exists: /sys/bus/usb/devices/1-2
Warning: USB attribute "serial" not found.
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product ZTE CDMA Technologies MSM
serial
----------------
SCSI attributes not needed, moving on
/var/log/syslog:
Jun 16 13:50:39 lobon kernel: [ 58.760179] usb 1-2: new high speed USB device using ehci_hcd and address 4
Jun 16 13:50:39 lobon kernel: [ 58.905374] usb 1-2: New USB device found, idVendor=19d2, idProduct=2000
Jun 16 13:50:39 lobon kernel: [ 58.905389] usb 1-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Jun 16 13:50:39 lobon kernel: [ 58.905399] usb 1-2: Product: ZTE CDMA Technologies MSM
Jun 16 13:50:39 lobon kernel: [ 58.905406] usb 1-2: Manufacturer: ZTE, Incorporated
Jun 16 13:50:39 lobon kernel: [ 58.916815] scsi3 : usb-storage 1-2:1.0
Jun 16 13:50:40 lobon kernel: [ 59.919557] scsi 3:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0
Jun 16 13:50:40 lobon kernel: [ 60.058393] sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
Jun 16 13:50:40 lobon kernel: [ 60.058406] Uniform CD-ROM driver Revision: 3.20
Jun 16 13:50:40 lobon kernel: [ 60.060793] sr 3:0:0:0: Attached scsi CD-ROM sr0
Jun 16 13:50:41 lobon kernel: [ 60.131951] sd 1:0:0:0: Attached scsi generic sg0 type 0
Jun 16 13:50:41 lobon kernel: [ 60.137214] sd 2:0:0:0: Attached scsi generic sg1 type 0
Jun 16 13:50:41 lobon kernel: [ 60.140874] sr 3:0:0:0: Attached scsi generic sg2 type 5
Jun 16 13:50:55 lobon kernel: [ 74.148207] sr0: CDROM (ioctl) error, command: Xdread, Read track info 52 01 00 00 00 01 00 00 08 00
Jun 16 13:50:55 lobon kernel: [ 74.148240] sr: Sense Key : Hardware Error [current]
Jun 16 13:50:55 lobon kernel: [ 74.148251] sr: Add. Sense: No additional sense information
Jun 16 13:52:30 lobon kernel: [ 169.206923] usb 1-2: USB disconnect, address 4
Regards.
In that case, replace the first message with this:Works with many ZTE devices.
Code: Select all
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"Hi,
I test you new MessageContent, but the ZTE 3G USB dongle has not been recognized.
The "19d2:2000" file :
########################################################
# ZTE MF622 and probably others (WE NEED MORE ID INFO)
DefaultVendor= 0x19d2
DefaultProduct= 0x2000
TargetVendor= 0x19d2
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063"
CheckSuccess=20
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
/var/log/usb_modeswitch_1-2:1.0 :
USB_ModeSwitch log from Thu Jun 24 13:43:28 CEST 2010
Using global config file: /etc/usb_modeswitch.conf
raw args from udev: /1-2:1.0
Bus ID for device not given by udev.
Trying to determine it from kernel name (1-2:1.0) ...
USB dir exists: /sys/bus/usb/devices/1-2
Warning: USB attribute "serial" not found.
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product ZTE CDMA Technologies MSM
serial
----------------
SCSI attributes not needed, moving on
/var/log/syslog:
Jun 24 13:43:27 lobon kernel: [ 39.868192] usb 1-2: new high speed USB device using ehci_hcd and address 4
Jun 24 13:43:27 lobon kernel: [ 40.014240] usb 1-2: New USB device found, idVendor=19d2, idProduct=2000
Jun 24 13:43:27 lobon kernel: [ 40.014251] usb 1-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Jun 24 13:43:27 lobon kernel: [ 40.014261] usb 1-2: Product: ZTE CDMA Technologies MSM
Jun 24 13:43:27 lobon kernel: [ 40.014268] usb 1-2: Manufacturer: ZTE, Incorporated
Jun 24 13:43:27 lobon kernel: [ 40.024158] scsi3 : usb-storage 1-2:1.0
Jun 24 13:43:28 lobon kernel: [ 41.027671] scsi 3:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0
Jun 24 13:43:29 lobon kernel: [ 41.502132] sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
Jun 24 13:43:29 lobon kernel: [ 41.502146] Uniform CD-ROM driver Revision: 3.20
Jun 24 13:43:29 lobon kernel: [ 41.503960] sr 3:0:0:0: Attached scsi CD-ROM sr0
Jun 24 13:43:29 lobon kernel: [ 41.652556] sd 1:0:0:0: Attached scsi generic sg0 type 0
Jun 24 13:43:29 lobon kernel: [ 41.657135] sd 2:0:0:0: Attached scsi generic sg1 type 0
Jun 24 13:43:29 lobon kernel: [ 41.659782] sr 3:0:0:0: Attached scsi generic sg2 type 5
Jun 24 13:43:42 lobon kernel: [ 54.145448] sr0: CDROM (ioctl) error, command: Xdread, Read track info 52 01 00 00 00 01 00 00 08 00
Jun 24 13:43:42 lobon kernel: [ 54.145481] sr: Sense Key : Hardware Error [current]
Jun 24 13:43:42 lobon kernel: [ 54.145492] sr: Add. Sense: No additional sense information
Jun 24 13:44:50 lobon kernel: [ 122.585291] usb 1-2: USB disconnect, address 4
The same error messages, I wonder if there is not a bug in the firmware, or is it a kernel problem?
Do you think it comes from USB-ModeSwitch?
Regards.
I test you new MessageContent, but the ZTE 3G USB dongle has not been recognized.
The "19d2:2000" file :
########################################################
# ZTE MF622 and probably others (WE NEED MORE ID INFO)
DefaultVendor= 0x19d2
DefaultProduct= 0x2000
TargetVendor= 0x19d2
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063"
CheckSuccess=20
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
/var/log/usb_modeswitch_1-2:1.0 :
USB_ModeSwitch log from Thu Jun 24 13:43:28 CEST 2010
Using global config file: /etc/usb_modeswitch.conf
raw args from udev: /1-2:1.0
Bus ID for device not given by udev.
Trying to determine it from kernel name (1-2:1.0) ...
USB dir exists: /sys/bus/usb/devices/1-2
Warning: USB attribute "serial" not found.
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product ZTE CDMA Technologies MSM
serial
----------------
SCSI attributes not needed, moving on
/var/log/syslog:
Jun 24 13:43:27 lobon kernel: [ 39.868192] usb 1-2: new high speed USB device using ehci_hcd and address 4
Jun 24 13:43:27 lobon kernel: [ 40.014240] usb 1-2: New USB device found, idVendor=19d2, idProduct=2000
Jun 24 13:43:27 lobon kernel: [ 40.014251] usb 1-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Jun 24 13:43:27 lobon kernel: [ 40.014261] usb 1-2: Product: ZTE CDMA Technologies MSM
Jun 24 13:43:27 lobon kernel: [ 40.014268] usb 1-2: Manufacturer: ZTE, Incorporated
Jun 24 13:43:27 lobon kernel: [ 40.024158] scsi3 : usb-storage 1-2:1.0
Jun 24 13:43:28 lobon kernel: [ 41.027671] scsi 3:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0
Jun 24 13:43:29 lobon kernel: [ 41.502132] sr0: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
Jun 24 13:43:29 lobon kernel: [ 41.502146] Uniform CD-ROM driver Revision: 3.20
Jun 24 13:43:29 lobon kernel: [ 41.503960] sr 3:0:0:0: Attached scsi CD-ROM sr0
Jun 24 13:43:29 lobon kernel: [ 41.652556] sd 1:0:0:0: Attached scsi generic sg0 type 0
Jun 24 13:43:29 lobon kernel: [ 41.657135] sd 2:0:0:0: Attached scsi generic sg1 type 0
Jun 24 13:43:29 lobon kernel: [ 41.659782] sr 3:0:0:0: Attached scsi generic sg2 type 5
Jun 24 13:43:42 lobon kernel: [ 54.145448] sr0: CDROM (ioctl) error, command: Xdread, Read track info 52 01 00 00 00 01 00 00 08 00
Jun 24 13:43:42 lobon kernel: [ 54.145481] sr: Sense Key : Hardware Error [current]
Jun 24 13:43:42 lobon kernel: [ 54.145492] sr: Add. Sense: No additional sense information
Jun 24 13:44:50 lobon kernel: [ 122.585291] usb 1-2: USB disconnect, address 4
The same error messages, I wonder if there is not a bug in the firmware, or is it a kernel problem?
Do you think it comes from USB-ModeSwitch?
Regards.
Hmm, did that /var/log/usb_modeswitch_1-2:1.0 really stop there in the middle?
And do you have the "NeedResponse=1" setting in the "19d2:2000" file?
Anyway, try to add the following line to the configuration and see if that helps:
MessageContent2="55534243876543212000000080000c85010101180101010101000000000000"
And do you have the "NeedResponse=1" setting in the "19d2:2000" file?
Anyway, try to add the following line to the configuration and see if that helps:
MessageContent2="55534243876543212000000080000c85010101180101010101000000000000"
Hi,Josh wrote:Hmm, did that /var/log/usb_modeswitch_1-2:1.0 really stop there in the middle?
And do you have the "NeedResponse=1" setting in the "19d2:2000" file?
I used "NeedResponse=1" when you said, ie for this case:
MessageContent="5553424312345678240000008000061b000000020000000000000000000000"
MessageContent2="55534243123456782400000080000685000000240000000000000000000000"
NeedResponse=1
I should have to use every time?
- For what "MessageContent=" ?Josh wrote:Anyway, try to add the following line to the configuration and see if that helps:
MessageContent2="55534243876543212000000080000c85010101180101010101000000000000"
- Can I also put the line "NeedResponse=1" ?
Thank you for your help.
Regards.
I had the same issue with my Telstra MF626. I am using it in the embedded system.Josh wrote:I'm sorry, I must have missed your last post; so my answer is pretty late.
It's still not quite clear to me where your problem is. Do you get a proper log from usb_modeswitch ?
In that case please post it in full length here.
The CDROM read errors are common with those devices. Don't bother.
I also have ZTE MF626 and it works....
These two devices should be the same model , but Telstra MF626 just don't work.
I try almost all the MessageContent and still can not find out the right one for Telstra MF626.
Here are some log messages.
Version 0.9.5:
Looking for target devices
No target device found
Looking for default devices
Found default devices (1)
Prepare switching, accessing latest device
Looking for active default driver to detach it
No driver found. Device probably not initialized. Trying to continue ...
Setting up communication with device
Trying to send the message
Sending the message returned error -145, trying to continue ...
-> See /proc/bus/usb/devices (or call lsusb) for changes. Bye
---------------------------------------------------------------------------------------------------------
Version 1.0.6:
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
Found default devices (1)
Accessing device 003 on bus 001 ...
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
------stop here, no message come out
I traced the code and found that it stuck in the usb_bulk_write()
This function is located in the libusb-0.1.12
So, is there any kernel configuration I should set?
If one modem works and the other doesn't, the kernel has nothing to do with it. Nor has libusb in my opinion. The main suspect is the firmware on the device.
The error with version 0.9.5 may be caused by the missing storage driver. If you try usb_modeswitch repeatedly, always re-plug the stick before each run. You should see the message
OK, driver "usb-storage" detached
every time you run.
If you can, use the latest version of usb_modeswitch (1.1.3) together with the current data package.
The error with version 0.9.5 may be caused by the missing storage driver. If you try usb_modeswitch repeatedly, always re-plug the stick before each run. You should see the message
OK, driver "usb-storage" detached
every time you run.
If you can, use the latest version of usb_modeswitch (1.1.3) together with the current data package.
Yes, every time I posted the entire usb_modeswitch log.Josh wrote:I'm sorry, I must have missed your last post; so my answer is pretty late.
It's still not quite clear to me where your problem is. Do you get a proper log from usb_modeswitch ?
In that case please post it in full length here.
Regards.
Josh wrote:Hmm, did that /var/log/usb_modeswitch_1-2:1.0 really stop there in the middle?
And do you have the "NeedResponse=1" setting in the "19d2:2000" file?
Anyway, try to add the following line to the configuration and see if that helps:
MessageContent2="55534243876543212000000080000c85010101180101010101000000000000"
Hi,
My Huawei E220 is definitively dead, so I bought the ZTE which is supposed to work.
It allowed me to test why usb_modeswitch stop in the middle.
I also updated usb-modeswitch from 1.1.2-3 to 1.1.3-1, and usb-modeswitch-data from 20100418-1 to 20100623-1.
The usb-modeswitch Squeeze Debian package is dependent to tcl or tclsh packages without a version number.
In my Squeeze EeePC I have tcl8.3 which provided tclsh, and the "/lib/udev/usb_modeswitch" script doesn't work with tcl8.3.
After installing the tcl package which depends on the tcl8.4 package logs were filled :
USB_ModeSwitch log from Tue Jul 20 19:13:08 CEST 2010
Using global config file: /etc/usb_modeswitch.conf
raw args from udev: /1-2:1.0
Bus ID for device not given by udev.
Trying to determine it from kernel name (1-2:1.0) ...
USB dir exists: /sys/bus/usb/devices/1-2
Warning: USB attribute "serial" not found.
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product ZTE CDMA Technologies MSM
serial
----------------
SCSI attributes not needed, moving on
checking config: /etc/usb_modeswitch.d/19d2:2000
! matched, now switching
(running command: /usr/sbin/usb_modeswitch -I -W -c /etc/usb_modeswitch.d/19d2:2000)
verbose output of usb_modeswitch:
--------------------------------
usb_set_debug: Setting debugging level to 15 (on)
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_busses: Found 001
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 003 on 001
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 16 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
Reading config file: /etc/usb_modeswitch.d/19d2:2000
* usb-modeswitch: handle USB devices with multiple modes
* Version 1.1.3 (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
TargetClass= not set
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063,0064,0128"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
MessageEndpoint= not set
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint= not set
Interface=0x00
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Looking for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 19d2:2000
found matching vendor ID
searching devices, found USB ID eb1a:2761
searching devices, found USB ID 0951:1606
searching devices, found USB ID 1d6b:0002
No devices in target mode or class found
Looking for default devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 19d2:2000
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID eb1a:2761
searching devices, found USB ID 0951:1606
searching devices, found USB ID 1d6b:0002
Found devices in default mode or class (1)
Accessing device 004 on bus 001 ...
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: ZTE CDMA Technologies MSM
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to the message (CSW) ...
OK, response successfully read (13 bytes).
Resetting response endpoint 0x81
Resetting message endpoint 0x01
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.
fail:
--------------------------------
(end of usb_modeswitch output)
All done, exiting
The switch has not be done with the file "/etc/usb_modeswitch.d/19d2:2000" of package "usb-modeswitch-data" version 20100623-1, the file contains:
DefaultVendor= 0x19d2
DefaultProduct= 0x2000
TargetVendor= 0x19d2
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063,0064,0128"
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
NeedResponse=1
CheckSuccess=20
I test with the file of "usb-modeswitch-data" version 20100418-1
DefaultVendor= 0x19d2
DefaultProduct= 0x2000
TargetVendor= 0x19d2
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063"
CheckSuccess=20
MessageContent="55534243123456782000000080000c85010101180101010101000000000000"
And the switch went well :
USB_ModeSwitch log from Tue Jul 20 19:18:32 CEST 2010
Using global config file: /etc/usb_modeswitch.conf
raw args from udev: /1-2:1.0
Bus ID for device not given by udev.
Trying to determine it from kernel name (1-2:1.0) ...
USB dir exists: /sys/bus/usb/devices/1-2
Warning: USB attribute "serial" not found.
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product ZTE CDMA Technologies MSM
serial
----------------
SCSI attributes not needed, moving on
checking config: /etc/usb_modeswitch.d/19d2:2000
! matched, now switching
(running command: /usr/sbin/usb_modeswitch -I -W -c /etc/usb_modeswitch.d/19d2:2000)
verbose output of usb_modeswitch:
--------------------------------
usb_set_debug: Setting debugging level to 15 (on)
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_busses: Found 001
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 005 on 001
usb_os_find_devices: Found 003 on 001
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 16 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
Reading config file: /etc/usb_modeswitch.d/19d2:2000
* usb-modeswitch: handle USB devices with multiple modes
* Version 1.1.3 (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
TargetClass= not set
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
MessageEndpoint= not set
MessageContent="55534243123456782000000080000c85010101180101010101000000000000"
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Looking for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 19d2:2000
found matching vendor ID
searching devices, found USB ID eb1a:2761
searching devices, found USB ID 0951:1606
searching devices, found USB ID 1d6b:0002
No devices in target mode or class found
Looking for default devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 19d2:2000
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID eb1a:2761
searching devices, found USB ID 0951:1606
searching devices, found USB ID 1d6b:0002
Found devices in default mode or class (1)
Accessing device 005 on bus 001 ...
USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: ZTE CDMA Technologies MSM
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
USB error: could not clear/halt ep 0: No such file or directory
USB error: could not claim interface 0: No such device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 003 on 001
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 16 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
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 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 003 on 001
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 16 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
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 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 003 on 001
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 16 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
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 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 003 on 001
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 16 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
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 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 003 on 001
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 16 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
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 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 006 on 001
usb_os_find_devices: Found 003 on 001
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 16 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
USB error: error sending control message: Connection timed out
Error: could not get description string "manufacturer"
USB error: error sending control message: Connection timed out
Error: could not get description string "product"
USB error: error sending control message: Connection timed out
Error: could not get description string "serial number"
OK, message successfully sent
Resetting response endpoint 0x00
Error resetting endpoint: -2
Resetting message endpoint 0x01
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 ...
Original device can't be accessed anymore. Good.
Searching for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID eb1a:2761
searching devices, found USB ID 0951:1606
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID eb1a:2761
searching devices, found USB ID 0951:1606
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID eb1a:2761
searching devices, found USB ID 0951:1606
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID eb1a:2761
searching devices, found USB ID 0951:1606
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID eb1a:2761
searching devices, found USB ID 0951:1606
searching devices, found USB ID 1d6b:0002
Searching for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 19d2:0052
found matching vendor ID
found matching product ID from list
searching devices, found USB ID eb1a:2761
searching devices, found USB ID 0951:1606
searching devices, found USB ID 1d6b:0002
Found target device 006 on bus 001
Target device description data
-------------------------
Manufacturer:
Product:
Serial No.:
-------------------------
Found correct target device
Mode switch succeeded. Bye.
ok
0052--------------------------------
(end of usb_modeswitch output)
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Now checking for newly created serial devices ...
new serial devices found, driver has bound
Checking for AVOID_RESET_QUIRK attribute
AVOID_RESET_QUIRK activated
All done, exiting
Thank you for your time and your help.
Do you notify the Debian maintainer for dependence of tcl8.4?
I'm going to test your new version of usb-modeswitch-data
Regards.