Hide Forgot
Description of problem: usb modeswitch does not work for ZTE 3565-Z UMTS USB Modem. Version-Release number of selected component (if applicable): usb_modeswitch-1.1.2-3.fc13.i686 How reproducible: Insert Modem and wait for switch. It does not happen. If i disable usb_modeswitch and eject from nautilus it works like expected. This is from the logfile if it does not work: Apr 28 10:14:49 kernel: usb 1-4: new high speed USB device using ehci_hcd and address 5 Apr 28 10:14:49 kernel: usb 1-4: New USB device found, idVendor=19d2, idProduct=2000 Apr 28 10:14:49 kernel: usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=3 Apr 28 10:14:49 kernel: usb 1-4: Product: ZTE CDMA Technologies MSM Apr 28 10:14:49 kernel: usb 1-4: Manufacturer: ZTE,Incorporated Apr 28 10:14:49 kernel: usb 1-4: SerialNumber: P673A2VDF_MS Apr 28 10:14:49 kernel: scsi3 : usb-storage 1-4:1.0 Apr 28 10:14:49 usb_modeswitch: switching 19d2:2000 (ZTE,Incorporated: ZTE CDMA Technologies MSM) Steps to Reproduce: 1. insert modem 2. wait for modem to become available 3. nothing happens Actual results: modem not switched Expected results: modem switched Additional info:
Did it work with earlier versions of usb_modeswitch ?
It worked in the f13 alpha phase. Not sure when it stopped working, because i only use it now and then when i am in the train.
Found the problem. The MessageContent for the ZTE 3565-Z is wrong. This is working for me: DefaultVendor= 0x19d2 DefaultProduct= 0x2000 TargetVendor= 0x19d2 TargetProductList="0063" CheckSuccess=20 MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
You could try the following variant of the ZTE entry, if you have version 1.1.3 which is in Fedora Update: --------------- DefaultVendor= 0x19d2 DefaultProduct= 0x2000 TargetVendor= 0x19d2 TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0063,0064,0108,0128" MessageContent="5553424312345678000000000000061e000000000000000000000000000000" MessageContent2="5553424312345679000000000000061b000000020000000000000000000000" MessageContent3="55534243123456702000000080000c85010101180101010101000000000000" NeedResponse=1 CheckSuccess=20 --------------- To the best of my knowledge, this combination will handle really all "19d2:2000" devices. It is used in the latest upstream release of the data package, "20100817". Josua Dietze
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug can be closed. The sequence suggested in comment #4 is working with all of the quirky ZTE devices. All newer Fedora releases have it included. "Upstream"
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.