19d2:2000 ZTE HSDPA Modem MF627 MF628 not recognized by network-manager in Ubuntu 13.04

[LJ]

Hello,

I just had to notice that my ZTE HDPA USB Modem is no longer working in Ubuntu 13.04 - but in 12.04 it worked.
lsusb lists the device as
"ID 19d2:2000 ZTE WCMA Technologies MSM MF627/MF628 HSDPA/HSUPA"
but the internal flash memory as well as the modem itself are not recognized by nautilus or the network-manager respectively.
Older workaround I found anywhere here with killing modem-manager does not work.

Ubuntu release 13.04 3.8.0-19
usb-modeswitch 1.2.3+repack0-1ubuntu3
modemmanager 0.6.0.0.really-0ubuntu5

WORKAROUND: 1. I added the modules (not sure if this is really necessary)
usbserial
option
in /etc/modules
2.picked up the matching config file (e.g. "19d2:2000" - this is the device ID) from /usr/share/usb_modeswitch/configPack.tar.gz and added the line "ReleaseDelay=3000". Then saved the file at /etc/usb_modeswitch.d
3. finally I created a file named "usb-storage.conf" in /etc/modprobe.d" and copied in these lines:
# Increase the default delay to avoid conflict with usb_modeswitch

options usb-storage delay_use=3

4. Connected the usb-modem, waited about 10-15 seconds until the internal SD-card was mounted and the the modem recognized by the modem-manager.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[pixolex (pixolex)]

I think I've found something.

The USB PEN works when connected to USB 2.0 port and don't work when connected to USB 3.0 port.

USB 2.0 port (WORKS):
[Seg Abr 29 22:59:16 2013] usb 1-1: new high-speed USB device number 6 using ehci-pci
[Seg Abr 29 22:59:16 2013] usb 1-1: New USB device found, idVendor=19d2, idProduct=2000
[Seg Abr 29 22:59:16 2013] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[Seg Abr 29 22:59:16 2013] usb 1-1: Product: ZTE WCDMA Technologies MSM
[Seg Abr 29 22:59:16 2013] usb 1-1: Manufacturer: ZTE,Incorporated
[Seg Abr 29 22:59:16 2013] usb 1-1: SerialNumber: P673A4ZTED000000
[Seg Abr 29 22:59:16 2013] scsi15 : usb-storage 1-1:1.0
[Seg Abr 29 22:59:17 2013] scsi 15:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 2
[Seg Abr 29 22:59:17 2013] sr0: scsi-1 drive
[Seg Abr 29 22:59:17 2013] sr 15:0:0:0: Attached scsi CD-ROM sr0
[Seg Abr 29 22:59:17 2013] sr 15:0:0:0: Attached scsi generic sg1 type 5
[Seg Abr 29 22:59:23 2013] usb 1-1: USB disconnect, device number 6
[Seg Abr 29 22:59:28 2013] usb 1-1: new high-speed USB device number 7 using ehci-pci
[Seg Abr 29 22:59:28 2013] usb 1-1: New USB device found, idVendor=19d2, idProduct=0031
[Seg Abr 29 22:59:28 2013] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[Seg Abr 29 22:59:28 2013] usb 1-1: Product: ZTE WCDMA Technologies MSM
[Seg Abr 29 22:59:28 2013] usb 1-1: Manufacturer: ZTE,Incorporated
[Seg Abr 29 22:59:28 2013] usb 1-1: SerialNumber: P673A4ZTED000000
[Seg Abr 29 22:59:28 2013] option 1-1:1.0: GSM modem (1-port) converter detected
[Seg Abr 29 22:59:28 2013] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[Seg Abr 29 22:59:28 2013] option 1-1:1.1: GSM modem (1-port) converter detected
[Seg Abr 29 22:59:28 2013] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[Seg Abr 29 22:59:28 2013] scsi16 : usb-storage 1-1:1.2
[Seg Abr 29 22:59:28 2013] option 1-1:1.3: GSM modem (1-port) converter detected
[Seg Abr 29 22:59:28 2013] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[Seg Abr 29 22:59:29 2013] scsi 16:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
[Seg Abr 29 22:59:29 2013] sd 16:0:0:0: Attached scsi generic sg1 type 0
[Seg Abr 29 22:59:29 2013] sd 16:0:0:0: [sdb] Attached SCSI removable disk

USB 3.0 port (don't work):
[Seg Abr 29 23:03:59 2013] usb 5-2: new high-speed USB device number 7 using xhci_hcd
[Seg Abr 29 23:03:59 2013] usb 5-2: New USB device found, idVendor=19d2, idProduct=2000
[Seg Abr 29 23:03:59 2013] usb 5-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[Seg Abr 29 23:03:59 2013] usb 5-2: Product: ZTE WCDMA Technologies MSM
[Seg Abr 29 23:03:59 2013] usb 5-2: Manufacturer: ZTE,Incorporated
[Seg Abr 29 23:03:59 2013] usb 5-2: SerialNumber: P673A4ZTED000000
[Seg Abr 29 23:04:00 2013] scsi17 : usb-storage 5-2:1.0
[Seg Abr 29 23:04:01 2013] scsi 17:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 2
[Seg Abr 29 23:04:01 2013] sr0: scsi-1 drive
[Seg Abr 29 23:04:01 2013] sr 17:0:0:0: Attached scsi CD-ROM sr0
[Seg Abr 29 23:04:01 2013] sr 17:0:0:0: Attached scsi generic sg1 type 5

The pen don't pass from the...

[pixolex (pixolex)]

Ops!

The good led flash sequence is (USB2.0 port): red, red and blue

The bad led flash sequence is (USB 3.0 port): red and blue

[pixolex (pixolex)]

I think this is a LINUX KERNEL problem not a MODEMMANAGER problem.

[LJ (the-mr-lj-88)]

thanks for your work, pixolex!
This behavior exactly matches my problem.
Please feel free to assign the bug to Linux kernel (I'm not sure how to do this - is Linux kernel bugs the right project??)
Thanks again
LJ

[pixolex (pixolex)]

I'm pretty sure that this is a linux kernel bug and not a modemmanager bug.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-raring/

[LJ (the-mr-lj-88)]

no change with 3.9.0-030900-generic #201304291257 SMP Mon Apr 29 16:58:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Apr 30 21:59:46 [ 357.376155] usb 3-2: new high-speed USB device number 4 using xhci_hcd
Apr 30 21:59:46 [ 357.394666] usb 3-2: New USB device found, idVendor=19d2, idProduct=2000
Apr 30 21:59:46 [ 357.394678] usb 3-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Apr 30 21:59:46 [ 357.394684] usb 3-2: Product: ZTE WCDMA Technologies MSM
Apr 30 21:59:46 [ 357.394689] usb 3-2: Manufacturer: ZTE,Incorporated
Apr 30 21:59:46 [ 357.394693] usb 3-2: SerialNumber: P671A21N1D010000
Apr 30 21:59:46 [ 357.397631] scsi8 : usb-storage 3-2:1.0
Apr 30 21:59:46 mtp-probe: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
Apr 30 21:59:46 mtp-probe: bus: 3, device: 4 was not an MTP device
Apr 30 21:59:47 [ 358.397989] scsi 8:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 2
Apr 30 21:59:47 [ 358.401399] sr0: scsi-1 drive
Apr 30 21:59:47 [ 358.401740] sr 8:0:0:0: Attached scsi CD-ROM sr0
Apr 30 21:59:47 [ 358.403116] sr 8:0:0:0: Attached scsi generic sg1 type 5
Apr 30 21:59:48 usb_modeswitch: switching device 19d2:2000 on 003/004
Apr 30 22:01:42 [ 473.188380] usb 3-2: USB disconnect, device number 4

[pixolex (pixolex)]

I've tried also the V3.9-raring kernel and the behaviour is the same.

[LJ (the-mr-lj-88)]

Also no change with the latest ubuntu-update to 3.8.20;
no change with v3.9.1-saucy

[LJ (the-mr-lj-88)]

no change with 3.8.0-22
also affects modem ZTE MF110

[LJ (the-mr-lj-88)]

is there any bug-fix in progress?

[LJ (the-mr-lj-88)]

based on bug #979697 and some others I tried the following and finally it worked:
1. I added the modules (not sure if this is really necessary)
usbserial
option
in /etc/modules
2.picked up the matching config file (e.g. "19d2:2000" - this is the device ID) from /usr/share/usb_modeswitch/configPack.tar.gz and added the line "ReleaseDelay=3000". Then saved the file at /etc/usb_modeswitch.d
3. finally I created a file named "usb-storage.conf" in /etc/modprobe.d" and copied in these lines:
# Increase the default delay to avoid conflict with usb_modeswitch

options usb-storage delay_use=3

4. Connected the usb-modem, waited about 10-15 seconds until the internal SD-card was mounted and the the modem recognized by the modem-manager

[penalvch (penalvch)]

LJ, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[Tapio Taipalus (tapio-p-taipalus)]

I can confirm the problem too in 13.10. I tried this with the latest development release 25.1.2014 as instructed, but the apport-collect command did not work (requiring apport-python or something to be installed and the installation did not work in the live session) nor did the modem work in the development release.

Also tried the workaround in the first post without success. So I guess I have to install 12.04 or something…

[penalvch (penalvch)]

Tapio Taipalus, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[LJ (the-mr-lj-88)]

meanwhile I upgraded to 13.10 to get a fix for touchscreen issue in xorg (just upgrade - no completely new install).
Sometimes I have to plug in the modem twice until it is recognized correctly, but then it normally works.

[Tapio Taipalus (tapio-p-taipalus)]

Thank you for you prompt reply. Sorry about the delay in my comment. I was actually expecting some email notification from activity on the thread.

Unfortunately, I don't have access to the hardware. Its at remote location (thus the 3G modem) and I was there just delivering new PC with updated OS and some support to get things going. They resort now on the old PC with Ubuntu 11.04 where this modem is working. I can't remember if it worked out of the box with that one or if it required some fiddling. So I can't do any testing with it any time soon...

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Eurobiz computer administration (m-admin-eurobiz-upb-de-deactivatedaccount)]

In current 14.04 only step 3 was necessary for a workaround, e.g. according to the bug description:

"
3. finally I created a file named "usb-storage.conf" in /etc/modprobe.d" and copied in these lines:
# Increase the default delay to avoid conflict with usb_modeswitch

options usb-storage delay_use=3
"

The new option SetStorageDelay in usb-modeswitch.conf did not work for me.

[penalvch (penalvch)]

Eurobiz computer administration, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs