GNOME Bugzilla – Bug 680545
Add support for ZTE MF190J.
Last modified: 2014-12-11 22:15:42 UTC
I have a 3G BroadBand modem from the Portuguese TMN. Ref: http://tinyurl.com/7v6yvh9 Its modem type is ZTE MF190J. I want to use it in my Ubuntu 12.04 laptop. I have created a definition in the "Mobile Broadband". The definition is done by a wizard where I select "Portugal" and "TMN" and where I enter a PIN-code. Please see the picture. The pen indicates a green light, but still, I cannot access the internet. And the network-applet icon switches off. The config looks like this http://bildr.no/view/1170463 and http://bildr.no/view/1172725 One thing I noticed that Ubuntu first thinks that this USB-pin is a storage device (like a cdrom) and it mounts it to /media/ZTEMODEM. I have to "Eject" this mount point first, then Linux seemingly continues to load the driver. The light on the USB-pin turns red, then after 5 secs to green. The network applet says "Registered to your home network", then immediate after that "Modem network.. disconnected". Listing of: $ lsusb Bus 001 Device 004: ID 19d2:1542 ZTE WCDMA Technologies MSM ... usb-devices listing before Eject / umount $ usb-devices T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 7 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=19d2 ProdID=1542 Rev=00.01 S: Manufacturer=ZTE S: Product=MF190J S: SerialNumber=9BB27BAF013DFB85103C397DCB576195 <snip> C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage usb-devices listing after Eject / umount. § usb-devices T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 8 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=19d2 ProdID=1544 Rev=00.01 S: Manufacturer=ZTE S: Product=MF190J S: SerialNumber=9BB27BAF013DFB85103C397DCB576195D <snip> C: #Ifs= 7 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 0 Cls=00(>ifc ) Sub=08 Prot=00 Driver=(none) I: If#= 1 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm I: If#= 2 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 3 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm I: If#= 4 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I: If#= 5 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm I: If#= 6 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm I added these mode-switch commands to disable automounting. I think the "/usr/bin/eject" is the only line that has effect. $ sudo gedit /lib/udev/rules.d/zte_modem.rules # Mode-switch of TMN ZTE MF190J modem. ATTRS{idVendor}=="19d2",ATTRS{idProduct}=="1542",RUN+="/usr/bin/eject %k", OPTIONS+="last_rule" ATTRS{idVendor}=="19d2",ATTRS{idProduct}=="1542",RUN+="usb_modeswitch '%b/%k'" ATTRS{manufacturer}=="ZTE" Notice: ------- This 3G-modem works fine if I use "wvdial" or "gnome-ppp" commands directly. $ sudo wvdial More details here: http://ubuntuforums.org/showpost.php?p=11934679 Or using gnome-ppp: $ gnome-ppp First, I added my username to the "dialout" group so you can run the gnome-ppp as ordinary user (do not need sudo). This will avoid the "Cannot open device /dev/ttyACM*..." messages. This picture shows the configuration of gnome-ppp. http://bildr.no/view/1182904 See also this bug-report on Launhcpad.net: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/994651
A small update. This 3G-modem (ZTE MF190J) works well in Ubuntu 12.10 (Quantal Quetzal). Only one thing needs manual intervention. I have to unmount (eject) it manually from the file manager or Ubuntu-icon. After that it connects well. Step 2) of this thread shows how to prevent its auto-mount. http://ubuntuforums.org/showpost.php?p=11934679&postcount=16 Configuration with default values is sufficient and OK. http://bildr.no/view/1290763
Okay, then this report can be closed, as the eject must be done by e.g. usb-modeswitch.
Hello, I sent an issue to usb-modeswitch forum. Ref: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=1100&p=7109
A short update. The developers of USB-modeswitch gave me some data and the mode-switch now works correctly. But this also caused additional problems. The 3G-pen does not fire after reboot, and there is no selections for "Enable Mobile Broadband", or "TMN tmn Internet" in the networks menu. The desktop (or NM) correctly asks the PIN-code. Sometimes it helps to unplug/plugin the modem once, sometimes upto 5 times before it fires and turns red, then green and finally allows me to connect from the NM. Please take a look at this thread: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4&t=1100 I removed all the mode-switch changes, and I do manually eject/unmount it from the filer manager and it connects fine. ATM this solutions is just ok. Please help me to resolve this bug. I can do debugging and even coding. I'm in your command. Just instruct me ;-) This installation: $ cat /etc/os-release NAME="Ubuntu" VERSION="12.10, Quantal Quetzal" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu quantal (12.10)" VERSION_ID="12.10" $ uname -a Linux quantal64 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux $ NetworkManager --version 0.9.6.0 $ usb_modeswitch --version * usb_modeswitch: handle USB devices with multiple modes * Version 1.2.3 (C) Josua Dietze 2012 * Based on libusb0 (0.1.12 and above)
Please add debug logs for modem manager: https://wiki.ubuntu.com/DebuggingModemmanager
Created attachment 228380 [details] modem.log-0.txt
Created attachment 228381 [details] nm.log-0.txt
Created attachment 228382 [details] dmesg1.txt
Re-hi, Here are the first debug logs. The test-situation was this. 0) I activated the proposed mode-switch changes so both /etc/usb_modeswitch.d/19d2:1542 and /lib/udev/rules.d/40-usb_modes (from the NM-menu)witch.rules where right. 1) Then cold-started this laptop. The desktop appeared but the modem was totally dormant. No sign of life, no selections for modem in the NM-menu. 2) I activated the debugging methods explained by https://wiki.ubuntu.com/DebuggingModemmanager 3) Then re-connected the modem to the laptop. This time it reacted and I could connect (from the NM-menu) to the internet. Please see: nm.log-0.txt and modem.log-0.txt and dmesg1.txt (dmesg log). First listing of dmesg1.txt shows situation when the modem stays dormant. In the 2.nd attempt it connects. Now I will test the latest NM from PPA. Ref: https://launchpad.net/~network-manager/+archive/trunk I'll be back.
I have now updated this system with latest packages from ppa:network-manager. $ sudo add-apt-repository ppa:network-manager/trunk $ sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade Updating following packages: libnm-glib-vpn1 libnm-glib4 libnm-util2 libssl0.9.8:i386 modemmanager network-manager ... After reboot. Version of NM is: $ NetworkManager --version 0.9.7.0 Unfortunately the error is still present. I have to disconnect this 3G-pen (often) several times before it sparks to life.
Maybe the modem is not ready when MM starts talking to it?
I have added echo 5 >/sys/module/usb_storage/parameters/delay_use to /etc/rc.local file. $ cat /sys/module/usb_storage/parameters/delay_use 5 --- I made a fresh Ubuntu 12.10 (32bit) installation. The bug is still here. After reboot the modem is passive and there are no modem-entries in the NM-menu. I have to unplug/reconnect it. Also, I used Windows to disable the PIN-code. This have never been a problem in Ubuntu but I've disabled it now. This system has the latest updates from ppa:network-manager/trunk. $ NetworkManager --verion 0.9.7.0
Did delay_use=5 help anything?
After reboot it has no effect at all; the modem is dormant. It may help when I disconnect/unplug and reconnect the pen to the computer. It hardly never fails to start. It connects immediately. I had a period when I had to plugin it several times before it reacted. The delay_use=5 may have helped. Not sure.
I've got several reports of MF190 running properly with MM 1.x; see table at: http://www.freedesktop.org/wiki/Software/ModemManager/SupportedDevices/ Can you please retest this with MM 1.x and a recent enough usb_modeswitch?
Hey moma, flagging this one as obsolete. MF190 should be properly handled in MM >= 1.x, but if you can still reproduce the issues with the newer MM, please open a new bug in the new bugzilla in fd.o: https://bugs.freedesktop.org/enter_bug.cgi?product=ModemManager