ZTE MF636 3G modem sometimes is not connecting in Lucid

[GeorgeVita]

PC: Asus EeePC 1000H (and P4 older desktop)
Modem: ZTE MF636
O.S.: Karmic Koala Desktop i386, Alpha 2, Alpha 3, daily builds of 29-July, daily updates, newer kernels up to daily build

Final: Linux KK729 2.6.31-999-generic #200908031000 SMP Mon Aug 3 09:44:18 UTC 2009 i686 GNU/Linux
Tested with Network Manager: 0.7.1-0ubuntu1 and 0.7.1.git.5.272c6a626-0ubuntu1~nm1

ZTE MF636 3G modem appears as ZeroCD drive (19d2:2000) in original (as bought) mode. When connected to my EeePC 1000H (also checked to an older Pendium4 desktop) running any version of Karmic (Alpha 2, 3, updated till today) firstly appears as the CD-drive.

When ejecting it the 'real modem mode' appears (19d2:0031 at lsusb) and some /dev/ttyUSBx ports are created (shown into dmesg output). After a while the ZeroCD re-appears and some malfunctioning is happening.

With kernel versions up to kernel 2.6.31-4.22 the system got totally frozen (no mouse, no clock, no keyboard).
Using newer (rc5) versions of kernel (daily builds till today's 3-Aug) the behavior is better and the system is operating (except some small delays in keyboard entry using terminal possibly when negotiating with the modem).

Trying to 'investigate' the problem I noticed that the /dev/ttyUSBx ports created are looping (created, partially removed, recreated etc.) as shown in the attached dmesg which includes everything from boot till the physical removal of the modem.

**********
In brief the actions seemed to be performed by the system are:

Modem attached, USB SCSI CD-ROM found, sr0 created.
'sudo eject sr0'
sr0 ejected, new device scanned, usbserial (or option) creates ttyUSB0-1-2
MMC Storage detected
USB SCSI C-ROM detected again
sdb removable disk attached (card reader of the modem?)
ttyUSB0-1 disconnected
[ 330.925586] option: option_instat_callback: error -108
ttyUSB2 disconnected
option driver creates some more ports ttyUSB3-4-5
sr1 scsi CD-ROM attached

ttyUSB5-4 disconnected
[ 336.292793] option: option_instat_callback: error -108
ttyUSB3 disconnected

and all above again (creating ttyUSB6-7-8, disconnecting ttyUSB8,7 error -108, ...)
**********

Notes:
- most times after 'purging' network manager the system did not get frozen (tested with kernels up to 2.6.31-4.22) and could connect fine using wvdial. Full iso images are downloaded in this manner (10-12 hours connected) so there is no problem with my modem/provider or Karmic update (generally).
- tested also PPA version of Network Manager with approximately same results

As this is my first 'bug' report, please help me be more accurate annd ask me provide any more information.

For reference I supply the following links with more historical data:
http://ubuntuforums.org/showthread.php?t=1202430
my posts at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/373821
http://www.acomelectronics.com/GeorgeVita/ZTEonUBUNTU.html

Regards,
George

[GeorgeVita (8-launchpad-mhnyma-com)]

Additional info: New clean installation of Ubuntu 9.10 daily build of 4-Aug with same problem.

g@KKaug4:~$ uname -a
Linux KKaug4 2.6.31-5-generic #24-Ubuntu SMP Sat Aug 1 12:48:18 UTC 2009 i686 GNU/Linux

Below is the part of dmesg after removing network-manager (sudo apt-get purge network-manager).
Actions done: modem attached, CD drive ejected (sudo eject sr0), ttyUSB0-1-2 created, everything on system OK, after a while the modem removed.

[ 1189.776217] usb 1-2: new high speed USB device using ehci_hcd and address 6
[ 1189.921734] usb 1-2: configuration #1 chosen from 1 choice
[ 1189.926304] scsi4 : SCSI emulation for USB Mass Storage devices
[ 1189.926975] usb-storage: device found at 6
[ 1189.926986] usb-storage: waiting for device to settle before scanning
[ 1194.925828] usb-storage: device scan complete
[ 1194.927732] scsi 4:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 2
[ 1194.972152] sr0: scsi-1 drive
[ 1194.974213] sr 4:0:0:0: Attached scsi CD-ROM sr0
[ 1194.977280] sr 4:0:0:0: Attached scsi generic sg1 type 5
[ 1208.212993] ISO 9660 Extensions: Microsoft Joliet Level 1
[ 1208.216241] ISOFS: changing to secondary root
[ 1209.909770] usb 1-2: USB disconnect, address 6
[ 1214.776201] usb 1-2: new high speed USB device using ehci_hcd and address 7
[ 1214.911614] usb 1-2: configuration #1 chosen from 1 choice
[ 1214.914114] option 1-2:1.0: GSM modem (1-port) converter detected
[ 1214.914366] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[ 1214.914664] option 1-2:1.1: GSM modem (1-port) converter detected
[ 1214.914866] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[ 1214.915398] scsi5 : SCSI emulation for USB Mass Storage devices
[ 1214.916206] option 1-2:1.3: GSM modem (1-port) converter detected
[ 1214.916623] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
[ 1214.916918] usb-storage: device found at 7
[ 1214.916932] usb-storage: waiting for device to settle before scanning
[ 1219.917140] usb-storage: device scan complete
[ 1219.918285] scsi 5:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
[ 1219.919159] scsi 5:0:0:1: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 2
[ 1219.922607] sd 5:0:0:0: Attached scsi generic sg1 type 0
[ 1219.950195] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[ 1219.952653] sr0: scsi-1 drive
[ 1219.952970] sr 5:0:0:1: Attached scsi CD-ROM sr0
[ 1219.955016] sr 5:0:0:1: Attached scsi generic sg2 type 5
[ 1233.004231] ISO 9660 Extensions: Microsoft Joliet Level 1
[ 1233.005659] ISOFS: changing to secondary root
[ 1255.293852] usb 1-2: USB disconnect, address 7
[ 1255.293964] option: option_instat_callback: error -108
[ 1255.294425] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 1255.294504] option 1-2:1.0: device disconnected
[ 1255.294923] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 1255.294995] option 1-2:1.1: device disconnected
[ 1255.298981] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 1255.299085] option 1-2:1.3: device disconnected
[ 1255.349627] scsi 5:0:0:1: rejecting I/O to dead device

With network...

[GeorgeVita (8-launchpad-mhnyma-com)]

Many tests done and the system behavior is very bad when network manager and modem manager running, after ejecting the created CDROM. Partially freeze on terminal, cannot open a new terminal or complete freeze of the system. I can understand 'no connection' but 'loosing' the system is a real 'bug'.

After a clean install of Ubuntu 9.10 Alpha 4 my best way to connect with ZTE MF636 modem:

0- boot without the modem, wait for the system to load
1- stop network manager
2- check that wvdial is not running (no process)
3- find process number of modem-manager
4- kill modem-manager
5- attach modem
6- check lsusb: 19d2:2000 (CDROM)
7- wait and eject CDROM created (sr0)
8- check again lsusb: 19d2:0031 (modem)
9- check creation of /dev/ttyUSB0-1-2
a- connect using wvdial and port /dev/ttyUSB2
b- checked that the connection done: valid IP, DNS

******* code

g@KKa4:~$ sudo /etc/init.d/NetworkManager stop
[sudo] password for g:
 * Stopping network connection manager NetworkManager [ OK ]
g@KKa4:~$ ps -A | grep wvdial
g@KKa4:~$ ps -A | grep modem
 1494 ? 00:00:00 modem-manager
g@KKa4:~$ sudo kill 1494
g@KKa4:~$ ps -A | grep modem
g@KKa4:~$ lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 19d2:2000 ONDA Communication S.p.A.
Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC WebCam / CNF7129
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
g@KKa4:~$ sudo eject sr0
g@KKa4:~$ lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 19d2:0031 ONDA Communication S.p.A.
Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC WebCam / CNF7129
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
g@KKa4:~$ dmesg | grep ttyUSB
[ 224.005998] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[ 224.008440] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[ 224.009049] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
g@KKa4:~$ sudo wvdial 2
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT&F
AT&F
OK
--> Sending: AT+CGDCONT=1,"IP","gint.b-online.gr"
AT+CGDCONT=1,"IP","gint.b-online.gr"
OK
--> Modem initialized.
--> Sending: ATDT*99***1#
--> Waiting for carrier.
CONNECT
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Fri Aug 14 14:58:32 2009
--> Pid of pppd: 2420
--> Using interface ppp0
--> local IP address 212.152.101.199
--> remote IP address 10.64.64.64
--> primary DNS address 212.152.70.6
--> secondary DNS address 212.152.70.7

******* /code

Trying to get debug log from modem manager all system got frozen (totally).
I am still in progress to find a way to get this log....

[GeorgeVita (8-launchpad-mhnyma-com)]

I believe that the problem is at network manager and/or modem manager because when running (nm+mm or nm stopped mm running), after ejecting the initially created CD-ROM (sr0) some seconds later (when it re-appears) the system partially freezes:

new terminal window opens but you cannot type anything
existed terminal windows are frozen totaly (you cannot close them except 'force close')
CTRL+ALT+F2 don't work
Shut down or reboot NEVER finalize, I need to press power button continuesly to do a 'hard' power off

After booting again (without the modem) terminal has already lost its history (up arrow)

modem: ZTE MF636 (Greece ?)
pc: EeePC 1000H
os: Linux KKa4 2.6.31-020631rc7-generic #020631rc7 SMP Sat Aug 22 09:51:01 UTC 2009 i686 GNU/Linux
nm: 0.8~a~git.20090820t182117.cb60390-0ubuntu2
mm: 0.2.git.20090821t194148.180ad40-0ubuntu2~nmt1
above versions are from 'trunk', listed with: 'sudo aptitude show package-name'
tested also with 'typical alpha4' versions

Below is the SUCCESSFUL connection method:
**********
g@KKa4:~$ sudo /etc/init.d/NetworkManager stop
[sudo] password for g:
 * Stopping network connection manager NetworkManager [ OK ]
g@KKa4:~$ ps -A | grep modem
 2508 ? 00:00:00 modem-manager
g@KKa4:~$ sudo kill 2508
g@KKa4:~$ ps -A | grep modem
g@KKa4:~$ # ------> MODEM ATTACHED NOW, WAIT 20sec
g@KKa4:~$ dmesg | grep CD-ROM
[ 150.920937] scsi 2:0:0:0: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 2
[ 150.948117] Uniform CD-ROM driver Revision: 3.20
[ 150.949905] sr 2:0:0:0: Attached scsi CD-ROM sr0
g@KKa4:~$ sudo eject sr0
g@KKa4:~$ # -------> WAIT 10sec
g@KKa4:~$ lsusb | grep 19d2
Bus 001 Device 004: ID 19d2:0031 ONDA Communication S.p.A.
g@KKa4:~$ dmesg | grep ttyU
[ 183.957799] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[ 183.958218] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[ 183.958681] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
g@KKa4:~$ pppd ttyUSB2 nodetach defaultroute noipdefault lock usepeerdns connect 'chat "" "at" "" "at" "OK" "at&f" "OK" "atz" "OK" "at+cgdcont=1,'IP','gint.b-online.gr'" OK "atdt*99***1#" CONNECT' user web password web
Serial connection established.
Using interface ppp0
Connect: ppp0 <--> /dev/ttyUSB2
CHAP authentication succeeded
CHAP authentication succeeded
Could not determine remote IP address: defaulting to 10.64.64.64
Cannot determine ethernet address for proxy ARP
local IP address 212.152.103.76
remote IP address 10.64.64.64
primary DNS address 212.152.70.6
secondary DNS address 212.152.70.7
**********

Actions done:
0. boot without modem, wait for the system to fully load
1. STOP network manager
2. KILL modem manager
3. modem attached
4. ZeroCD ejected
5. check: 'real modem state' (lsusb), ttyUSBx creation (dmesg)
6. connected via pppd command (chat included)
7. all terminal copied and pasted here (using above connection)

Additionally I attach the 'problematic' dmesg (MF636_onlyMM_dmesg.txt).
In that test, nm was stopped, mm killed, mm started as --debug, modem attached. Copied from terminal using mouse. Keyboard was not functional via terminal window.

In next post I will send the 'debug...

[GeorgeVita (8-launchpad-mhnyma-com)]

Feel free to ask me do any test you need!
Regards,
George

[beudbeud (beudbeud)]

i have a same bug but with a HUAWEI E180

lsub

Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 005: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270 HSDPA/HSUPA Modem
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 04d9:048e Holtek Semiconductor, Inc.
Bus 005 Device 002: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0c45:63e0 Microdia Sonix Integrated Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[Sergiu Bivol (sergiu-bivol)]

Using Karmic Beta I get freezes and kernel Oops pretty frequently (>20 times/day).
NetworkManager does not write DNS information to /etc/resolv.conf in 50% of attempts.
ModemManager has obscene timeouts set for ZTE modems before connecting, and tries to connect to interfaces that have nothing to do with data transfer. Oh, it also brings the modem in an unusable state pretty often, making sure that wvdial won't help me.

And because it's Linux - either get used to these "features", or switch to Windows. That's how it works.

[Id2ndR (id2ndr)]

I can confirm the behavire describe by Sergiu Bivol.

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi Sergiu Bivol and Id2ndR .
At this time (2.6.31-12-generic) system gets frozen/stuck etc. with both ZTE MF636 and Huawei E169.
Today a lot of updates change the beta 'stability' to full floating...

For the MF636 the 'workaround' is simpler than windows:
- boot without modem
- sudo stop network-manager
- sudo killall modem-manager
- check that nothing of above is running: ps -A | grep -i manager
- use any other way to connect (wvdial, pppd commaaaaand, etc)
- do your work and check again after next update (hope needed).

Regards,
George

[GeorgeVita (8-launchpad-mhnyma-com)]

Sorry, I forgot to write that CDROM must be ejected (right click icon or use sudo eject sr...)
to get 'real modem' mode (lsusb must show 19d2:0031 and the /dev/ttyUSB0-1-2 created).
G

[Hardik Dalwadi (hardik-dalwadi)]

I am seeing the same problem with Huawei EC 1260 with Karmic + Beta + Latest updates. This is happening after upgrading Kernel from "2.6.31-11-generic #36" To " 2.6.31-14-generic #48".

Observation:
It was working fine with " 2.6.31-11-generic #36" kernel + Network Mangaer + Modem Manager. There was some random crash from Modem Manager. I have already filed bug against it [0]. But after upgrading to " 2.6.31-14-generic #48". It's detect Huawei EC 1260 as usb-storage. Now NM is not dialling modem at all, I can see disconnect in available list of connection but it's not working at all. But i am able to dial modem with wvdial without any problem.

[0] https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/452489

My triage shows that this is happening because there was fix from upstream kernel update [1] to 2.6.31-12.39 Kernel Source Tree. That fix was for "* USB: usb-storage fails to attach to Huawei Datacard cdrom device." I think that is the problem behind the crash.

[1] http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_2.6.31-14.48/changelog

[Robbob (rob-kirkbride)]

I can confirm the same behaviour on beta today (with all updates installed).

Any help I can provide in fixing the problem?

[jakartadean (jakartadean)]

I'm having a similar problem with a new Qanta HDSPA modem (vendor=0x0408) on a new 9.10RC install. The modem is recognized as a storage device, but does not trigger a link to the CD-ROM. I can remove the usb-storage module and insert the usbserial module, which creates /dev/ttyUSB0, but that's as far as I've got so far.

Is there a page or wiki compiling various 3G experiences with karmic? It seems that a lot of people are having trouble with 3G dongles with this kernel, although it was supposed to make things easier.

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi jakartadean,
you can start reading: https://wiki.ubuntu.com/NetworkManager/Hardware/3G
then create a new thread at ubuntuforums.org to discuss it and finally report a new 'bug report' at Launchpad.
Regards,
George

[Suyog (suyog)]

I can confirm that this issue is still present in 9.10 final release. I am also using Huawei EC 1260.
Seamless connectivity experience in Jaunty is broken in 9.10 now. Let me know if there is any workaround.
Such bug should have been fixed before final release.

[ovoskeuiks (ovoskeuiks)]

Same problem with MF636 on an Compaq 6710b
am using wvdial at the moment to connect

[z3non (tom-uttenthaler)]

I can confirm, that this is a regression. It was working in 9.04 (with some tricks, I had usb-modeswitch installed). In 9.10 it is broken now (tried it on fresh installed Alpha1 and Upgraded 9.10 final).

After the usb-modeswitch the daemon log shows:
Nov 5 15:51:12 localhost modem-manager: (ttyUSB1) opening serial device...
Nov 5 15:51:12 localhost modem-manager: (ttyUSB1): probe requested by plugin 'ZTE'
Nov 5 15:51:12 localhost modem-manager: (ttyUSB0) opening serial device...
Nov 5 15:51:12 localhost modem-manager: (ttyUSB0): probe requested by plugin 'ZTE'
Nov 5 15:51:12 localhost modem-manager: (ttyUSB2) opening serial device...
Nov 5 15:51:12 localhost modem-manager: (ttyUSB2): probe requested by plugin 'ZTE'
Nov 5 15:54:33 localhost modem-manager: Got failure code 100: Unknown error
Nov 5 15:57:55 localhost modem-manager: Got failure code 100: Unknown error

and the Modem never shows up in the nm-applet. Without the modeswitch there is not activity of modem-manager at all. Using Huawei modem works without problems

[z3non (tom-uttenthaler)]

I have to correct my previous comment.

The ZTE MF636 is recognized, but only after 13 minutes of waiting ...

I produced another log in debug mode (sudo kill -SIGUSR1 `pgrep modem-manager`) - see attachment.

The modem only works, when the modeswitch is performed before (I use usb-modeswitch, should be possible with normal eject too). IMHO this should be done by the modem-manager, otherwise I don't recognize the purpose of it.

[Jonathan Harker (jonathanharker)]

Using latest updated Karmic i386 on my HP Mini 5101, ZTE MF636 detects ok, unmounts ok using the below rule, and shows up ok as the new devices /dev/ttyUSB0 /dev/ttyUSB1 and /dev/ttyUSB2. However the modem still does not appear in network manager.

SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="2000", RUN+="/usr/bin/eject %k", OPTIONS+="last_rule"

[Suyog (suyog)]

This is still issue , only workaround is
1) After plugging in USB modem, eject cd drive, USB mass storage which come up for USB modem.
2) install gnome-ppp and use it to dial.

[Suyog (suyog)]

Good news ! After running update manager today and installing all updates, issue seem to have been resolved.
I dont know which update exactly fixed this. :-)
i can confirm that now cd drive, sd storage services work well and also Mobile broadband. no need to do anything else.

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi Suyog, updates fixed bug#446146 which refers to most 3g modems including Huawei.

This bug#408555 refers to ZTE MF636 where the problem still exist on 9.10 +updates!

[Sam Azer (samazer)]

My MF636 was also disconnecting after about 10 minutes consistently but is now working reliably. Checking /var/log/dpkg it seems that many packages were updated recently including udev and libgudev.

In my case I insert the modem, eject the USB drive, wait a few seconds then run sudo wvdial to establish a connection. Performance is the same as when running under WinXP.

My thanks to all the unsung heroes who are responsible for 9.10 - it's GREAT!!

[Sam Azer (samazer)]

(My modem just disappeared again. Not sure what triggers the problem or why; have removed knetworkmanager and modem-manager again.)

[vedavata (vedavrata)]

i have the same problem with network-manager on Acer 3002 + CDMA-modem Huawei EC321...

[MisterW (ian-warrilow)]

Don't know if I can help here, but I have been doing some tests to see if my modem ( ZTE MF627 ) will work on 9.10 BEFORE I upgrade my Netbook from 9.04.

The story so far:-
I initially tried the 9.10 Live CD on the netbook and had the problem whereby the modem disconnects after about 7 minutes. Not wanting to mess up my working netbook, I then set about running 9.10 in a virtual machine ( on my desktop ) with all updates applied and still got the disconnects. I even tried the latest versions from https://launchpad.net/~network-manager/+archive/trunk, no difference!.
So then I started to investigate the forums for more information about the problem and it seems as though the consensus is that its something to do with the Unsolicited messages from the ZTE modems. Ah, I thought, on my netbook I actually use the application that came on the dongle ( yes a Linux version of the Windows software from 3 UK ) to manage the connection, rather than Network Manager since it gives me SMS facilities,and other useful stuff.
So I installed that on my 9.10 system and it couldn't see the dongle, yes that reminded me on 9.04 I had to stop NM managing the modem by changing nm-probe-modem-capabilites rules to comment out probing the option driver, so how do I do that on 9.10 I thought!. I obviously needed somehow to stop the new modem-manager probing it, eventually I just tried removing modem-manager ( with synaptic ) and sure enough my 3UK software now worked and could see the modem, and guess what , no more disconnects!!!
Ok, so I now did a bit more testing and discovered that without modem-manager installed the modem doesn't disconnect but install modem-manager and withing a few minutes, with the modem just idle, then i get a usb disconnect.
I have attached syslog output to show both the log with modem-manager installed and the one without.
I hope this may help and if there is anything else useful I can do then please let me know. Meanwhile I've downloaded the source for modem-manager and will investigate further...

[muratsever (mseverr)]

Hi i am a new user and i installed Ubuntu 9.10on my Asus EEEPc 1000H, everything works fine except my ZTE MF636 3G usb modem, i read entry #3 by GeorgeVita but i could not get my modem to work, here is what i get:

1. I could not stop NetworkManager,
2. I could not kill modem-manager
3. My usb modem seen as it should be:
    Bus 001 Device 004: ID 19d2:0031 ONDA Communication S.p.A.
4. dmesg | grep ttyUSB seems ok:
[ 2881.923530] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[ 2881.923756] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[ 2881.924053] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2

5. i could not wvdial,

6. Finally my ubuntu is:
murat@murat-laptop:~$ uname -a
Linux murat-laptop 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009 i686 GNU/Linux
murat@murat-laptop:~$

Any help would be appreciated, thanks in advance...

The code is.............................:
----------------------------------------------
sudo /etc/init.d/NetworkManager stop
sudo: /etc/init.d/NetworkManager: command not found
murat@murat-laptop:~$ ps -A | grep wvdial
murat@murat-laptop:~$ ps -A | grep modem-manager
 2100 ? 00:00:00 modem-manager
murat@murat-laptop:~$ sudo kill 2100
murat@murat-laptop:~$ ps -A | grep modem-manager
 2117 ? 00:00:00 modem-manager
murat@murat-laptop:~$ sudo kill 2117
murat@murat-laptop:~$ ps -A | grep modem-manager
 2122 ? 00:00:00 modem-manager
murat@murat-laptop:~$ sudo kill 2122
murat@murat-laptop:~$ ps -A | grep modem-manager
 2127 ? 00:00:00 modem-manager
murat@murat-laptop:~$ sudo kill 2127
murat@murat-laptop:~$ ps -A | grep modem-manager
 2132 ? 00:00:00 modem-manager
murat@murat-laptop:~$ sudo kill 2132
murat@murat-laptop:~$ ps -A | grep modem-manager
 2137 ? 00:00:00 modem-manager
murat@murat-laptop:~$ murat@murat-laptop:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 19d2:0031 ONDA Communication S.p.A.
Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC WebCam / CNF7129
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0b05:b700 ASUSTek Computer, Inc. Broadcom Bluetooth 2.1
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
murat@murat-laptop:~$ dmesg | grep ttyUSB
[ 2881.923530] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[ 2881.923756] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[ 2881.924053] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
murat@murat-laptop:~$ sudo wvdial 2
sudo: wvdial: command not found
murat@murat-laptop:~$ uname -a
Linux murat-laptop 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009 i686 GNU/Linux
murat@murat-laptop:~$

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi muratsever,
as your modem is identified correctly (0x0031) check IF you can have a 'steady' existance of ttyUSB0, 1 & 2 :

- dmesg
- wait 20 seconds
- dmesg
- wait 20 seconds
- dmesg

If there are no 'ttyUSB2 disconnected...' then try to 'setup a new broadband connection':

- right click network manager icon
- edit connections
- mobile broadband
- add
- ...

If you want to try other methods to connect like wvdial, gnome-ppp etc (you need to install them first from Synaptic Package Manager or Ubuntu Software Center) AND if you have the 'looping' creation/disconnection of ttyUSB2 you can stop network manager and kill modem manager using the procedure of comment#9 which works with beta/rc/final version of Ubuntu 9.10 (comment#3 was for earlier alphas testing versions):

- boot without modem
- from terminal run: sudo stop network-manager
- from terminal run: sudo killall modem-manager
- check that no network/modem managers are running (from terminal): ps -A | grep -i manager
- use any other way to connect (wvdial, pppd commaaaaand, etc)

Note that wvdial, gnome-ppp and some other 'alternatives' are not included into standard distribution and must be installed separately. Most of those solutions require configuration files.

MF636 and wvdial (Ubuntu 8.10): http://ubuntuforums.org/showpost.php?p=6511814&postcount=2
MF636 on pre-released versions of 9.10: http://ubuntuforums.org/showthread.php?t=1202430

Regards,
George

[muratsever (mseverr)]

Hello again,
Thank you George for your quick reply:)

This is what i got after the last try, but despite everything seems ok, i cannot surf in Firefox:(

murat@murat-laptop:~$ sudo wvdial 2
--> WvDial: Internet dialer version 1.60
--> Warning: section [Dialer 2] does not exist in wvdial.conf.
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT&F &D2 &C1
AT&F &D2 &C1
OK
--> Sending: ATS7=60 S30=0 S0=0
ATS7=60 S30=0 S0=0
OK
--> Sending: AT+CGDCONT=1,"IP","internet"
AT+CGDCONT=1,"IP","internet"
OK
--> Modem initialized.
--> Sending: ATDT*99***1#
--> Waiting for carrier.
ATDT*99***1#
CONNECT
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Sat Dec 5 02:07:18 2009
--> Pid of pppd: 2129
--> Using interface ppp0
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�
--> local IP address 213.211.17.220
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�
--> remote IP address 10.64.64.64
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�
--> primary DNS address 192.168.18.11
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�
--> secondary DNS address 195.175.39.39
--> pppd: h[06]� h[08]� �[08]� �[08]� �[08]�

My wvdial.conf file reads:
-------------------------

[Dialer Defaults]
Modem = /dev/ttyUSB2
Modem Type = Analog Modem
ISDN = 0
Baud = 460800
Dial Attempts = 1
Username = user
Password = pass
Init1 = ATZ
Init2 = AT&F &D2 &C1
Init3 = ATS7=60 S30=0 S0=0
Init4 = AT+CGDCONT=1,"IP","internet"
Phone = *99***1#
Stupid Mode = 1

But after i changed the line Phone = *99***1# to Phone = *99#, modem again started successfully but no connection via firefox:( and i got this:

murat@murat-laptop:~$ sudo wvdial 2
--> WvDial: Internet dialer version 1.60
--> Warning: section [Dialer 2] does not exist in wvdial.conf.
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT&F &D2 &C1
AT&F &D2 &C1
OK
--> Sending: ATS7=60 S30=0 S0=0
ATS7=60 S30=0 S0=0
OK
--> Sending: AT+CGDCONT=1,"IP","internet"
AT+CGDCONT=1,"IP","internet"
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
ATDT*99#
CONNECT
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Sat Dec 5 02:35:59 2009
--> Pid of pppd: 2439
--> Using interface ppp0
--> pppd: �.q
--> pppd: �.q
--> pppd: �.q
--> pppd: �.q
--> pppd: �.q
--> pppd: �.q
--> pppd: �.q
--> local IP address 213.211.3.27
--> pppd: �.q
--> remote IP address 10.64.64.64
--> pppd: �.q
--> primary DNS address 192.168.18.11
--> pppd: �.q
--> secondary DNS address 195.175.39.39
--> pppd: �.q

Regards...

[muratsever (mseverr)]

GOOD NEWS:

I have changed nothing but removed the definition for mobile broadband from network manager, tried again to connect by wvdial while network manager still running, and i send this message via my ZTE MF636 3G usb modem, carrier AVEA, Turkey...

Thank you very very much George:)

Regards...

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi muratsever,
always happy to see more people connected ...!

In your wvdial example you must connect using: sudo wvdial
(parameter 2 not needed because you do not have a specific [Dialler 2] paragraph within wvdial.conf)

Using wvdial firefox starts running in 'offline mode' and can become 'online' again with ALT-F W
Newer versions (3.5+) start always 'online'.

Regards,
George

[GeorgeVita (8-launchpad-mhnyma-com)]

Finally I got a connection without 'trims' or modifications, just WAITed some minutes (3-5') till my broadband connection appeared to network manager icon.

System info:
------------
pc: asus eeepc 1000h
os: Lucid Lynx alpha1 + updates (14-Dec) kernel 2.6.32-8-generic #12
3g: ZTE MF636 19d2:2000 (when attached) 19d2:0031 (when connected)

Notes:
------
1. my system runs from installation on SDHC card (maybe slower)
2. wifi and bluetooth were enabled

Results:
--------
Although looping creation/disconnection of ttyUSB0-1-2 happens (as in previous comments) the connection made. I realized that port numbering (ttyUSBx) is stable (0-1-2) as below:

[ 193.944529] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 193.944615] option 1-3:1.0: device disconnected
[ 205.929604] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 205.929696] option 1-3:1.1: device disconnected
[ 205.929866] option: option_instat_callback: error -108
[ 205.930216] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 205.930328] option 1-3:1.3: device disconnected
[ 206.040127] usb 1-3: reset high speed USB device using ehci_hcd and address 6
[ 206.174960] option 1-3:1.3: GSM modem (1-port) converter detected
[ 206.175864] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0
[ 206.176308] option 1-3:1.1: GSM modem (1-port) converter detected
[ 206.180126] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1
[ 206.180345] option 1-3:1.0: GSM modem (1-port) converter detected
[ 206.182341] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2

Extra info:
-----------
Attached is the dmesg I got doing the following actions:
0. boot without modem, wait for the system to fully load
1. sudo dmesg -c # (to clear initial lines)
2. modem attached
3. click on network manager every 20 seconds till the pre-configured mobile broadband connection appear as selection
4. dmesg > Desktop/LLa1_dmesg.txt
5. try & suceed connection via network manager

Regards,
George

[Marius B. Kotsbak (mariusko)]

Saving the following content to "/usr/share/hal/fdi/information/20thirdparty/20-zte-mf626.fdi" and then reinsert the modem seems to solve the problem for me (this should be included by default):

<!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<!-- ZTE MF626 HSDPA USB Modem -->
<match <email address hidden>:usb.vendor_id" int="0x19d2">
<match <email address hidden>:usb.product_id" int="0x0031">
<match <email address hidden>:usb.interface.number" int="3">
<append key="modem.command_sets" type="strlist">GSM-07.07</append>
<append key="modem.command_sets" type="strlist">GSM-07.05</append>
<append key="info.capabilities" type="strlist">modem</append>
</match>
</match>
</match>
</device>
</deviceinfo>

[Jeremy Foshee (jeremyfoshee)]

GeorgeVita,
      For the sake of completeness, and so that I have all the necessary debug information from this machine for the engineers, would you mind running apport-collect -p linux 408555 so that we can get the other logs necessary to fully troubleshoot this issue from our end?

Thanks in advance,

-JFo

[GeorgeVita (8-launchpad-mhnyma-com)]

AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: g 1532 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1043831a,00100004'
   Controls : 12
   Simple ctrls : 7
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=e631ceb2-691b-4141-9f80-b5703113e697
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: ASUSTeK Computer INC. 1000H
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-18-generic root=UUID=ca2372a6-4b33-4bb9-97a7-c7796bdea359 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-18-generic N/A
 linux-firmware 1.26
Uname: Linux 2.6.31-18-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1548): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1548): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1647): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1675): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1951): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 07/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000H
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2102:bd07/21/2009:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000H
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi Jeremy Foshee,
please note that I ran 'apport-collect -p linux 408555' on the EeePC 1000H but the problem exists also on any PC.

The procedure I used to send the 'apport-collect' data was:

- Boot without the modem
- modem attached, CD-ROM icon appear, right click it and 'eject' drive
(modem changed from 19d2:2000 to 19d2:0031)
- network manager did not 'see' the modem
- dmesg show a looping creation (or 'attachment') of ttyUSBx ports and then disconnection

To 'send' the report I had to connect with the same modem (MF636):
- modem removed
- sudo stop network-manager
- sudo killall modem-manager
- sudo pppd ttyUSB2 nodetach defaultroute noipdefault lock usepeerdns connect 'chat "" "at" "" "at" "OK"...
- from new terminal window: apport-collect -p linux 408555
and finally I followed directions to send it.

Regards,
George

[GeorgeVita (8-launchpad-mhnyma-com)]

(!) no edit at launchpad comments!

The correct is:

To 'send' the report I had to connect with the same modem (MF636):
- modem removed
- sudo stop network-manager
- sudo killall modem-manager

- modem attached
- CD-ROM icon appear, right click it and 'eject' drive
- dmesg shows a 'stable' ttyUSB0-1-2 creation

- sudo pppd ttyUSB2 nodetach defaultroute noipdefault lock usepeerdns connect 'chat "" "at" "" "at" "OK"...
- from new terminal window: apport-collect -p linux 408555
and finally I followed directions to send it.

Regards,
George

[Sergiu Bivol (sergiu-bivol)]

The state of ZTE MF636 in Kubuntu Lucid:
- the virtual CD-ROM is automatically ejected;
- the modem works fine with KNetworkManager;
- at random intervals (usually > 1 hour), the modem stops responding, and it's light turns off;
- replugging the modem makes it work again;
- modem-manager takes a long time to recognize the modem (~20 seconds after inserting it). Kppp connects instantly to ttyUSB2.
- the serial interface of the device is recognized as /dev/ttyUSB2, but after several reconnects - as ttyUSB3, 4, 5...

[Id2ndR (id2ndr)]

I've got a similar modem : ONDA Communication S.p.A. ZTE MF627/MF628/MF628+ HSDPA.
The current state in Lucid is :
- it doesn't eject automaticaly but doing it with a right click allow the modem to be used by network-manager
- I can't connect because de sim code is not used by modemmanager (bug #509738)

[Surbhi Palande (csurbhi)]

This seems like a bug in the modem-manager. Need to assess if this works in Lucid.

[Alexander Sack (asac)]

Id2ndR, can you confirm if the modem auto ejects in kubuntu for you (try a livecd maybe), but not in ubuntu (both lucid?)?

[Surbhi Palande (csurbhi)]

Have closed the bug for linux as the freezes/lock-ups should no longer be an issue. The rest of it seems like a bug in the modem manager.

[Marius B. Kotsbak (mariusko)]

Sure. The modem works with wvdial, it is just that it is doesn't appear in the network manager any longer in karmic.

[Id2ndR (id2ndr)]

@Alexander Sack: I don't imagine how this can be related to the desktop environment but I'll try kubuntu and report the results. I think this can be linked to an udev rules and my hardware that is not exactly the same (mine is a ZTE model K3565-Z).

[Id2ndR (id2ndr)]

I just tried with kubuntu lucid daily and it works just like in gnome.

[GeorgeVita (8-launchpad-mhnyma-com)]

Just for reference, I tested my ZTE MF636 on my EeePC 1000H running LL LiveUSB (gnome desktop daily live of 8-Feb). Same behavior as with KK (looping attachment/disconnection of ttyUSBx).

My procedure:
- boot daily liveUSB (8-Feb .iso i386 desktop)
- from terminal: 'sudo dmesg -c'
- modem attached
- green led, led off (modem switched), green led, blue led (3g found)
- lsusb shows exact type/model (0031 MF636)
- from terminal: 'sudo dmesg > Desktop/LL_MF636_attached'

Attached is the dmesg output (file LL_MF636_attached).

Regards,
George

[Marius B. Kotsbak (mariusko)]

It works ok in daily builds of Lucid live cd.

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi,
just tested my MF636 on EeePC 1000H with LL daily-live of 18-Mar-2010, which connected but needs a reboot after removing/attaching modem to connect again. No more looping creation/disconnection on ttyUSBx, and no terminal freeze.

kernel: 2.6.32-16-generic #25-Ubuntu
modemmanager: 0.3-0ubuntu2
network-manager: 0.8-0ubuntu2

Procedure #1:
- boot with the modem attached
- system loads ('test Ubuntu'), click on network-manager icon, click on 'new broadband ...' to setup and connect
(if 'new broadband ...' did not appear, wait some seconds and try again)
- connect, browse, all OK, disconnect
- remove modem
- wait some seconds
- attach modem
- wait, click on network manager icon, 'mobile broadband connection option' is NOT there!
- wait, retry above, NO mobile broadband connection.
- shut down, remove LiveUSB, attach LiveUSB, boot and retry works OK.

Procedure #2
- boot without the modem
- wait for the system to load ('test Ubuntu')
- attach modem
- click on network-manager icon to see if a 'broadband connection' option exists
>>> I had to wait around 2 minutes for this option to appear
- connect, browse, all OK, disconnect
- remove modem
- wait some seconds
- attach modem
- wait, click on network manager icon, 'mobile broadband connection option' is NOT there!
- wait, retry above, NO mobile broadband connection.
- shut down, remove LiveUSB, attach LiveUSB, boot and retry works OK.

Feel free to ask any more test for further analysis (please describe full procedure).

Regards,
George

[Marius B. Kotsbak (mariusko)]

GeorgeVita, I tested this with Lucid beta 1 now, and could not reproduce your problem. I both disconnected modem using the network manager menu and just removed modem while connected. In both cases I was able to connect again, although it sometimes as your write takes some time for the modem to appear in the menu. I have though not tested booting with the modem attached.

Can you test this again in beta 1? Have you enabled PIN code check on the SIM card? I just tested without that (disable by inserting the SIM card in a phone). Can you take a look at /var/log/daemon.log and post here the relevant output from NetworkManager and modemmanager while it fails?

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi Marius Kotsbak, as the beta 2 will be released after 3 days, I think it is better to use LL beta 2 to test it and report back.
Also note that SIM PIN is always disabled.
Regards,
George

[Marius B. Kotsbak (mariusko)]

Ok. Waiting for your test result when that is released then (btw. also worked with yesterdays daily kubuntu netbook remix).

Also the micro SD card reader on device was now automatically mounted (in addition to the modem manual drive) :)

[GeorgeVita (8-launchpad-mhnyma-com)]

I just tested every combination with the same results.

Modem: ZTE MF636 IMEI: 3628470211xxxxx
PC: EeePC 1000H
OS Tested: LL desktop beta 2, LL netbook remix beta 2, LL kubuntu netbook daily live 20100406.1
>>> all running as LiveUSB

For Ubuntu LL beta 2 (desktop and netbook) the behavior is exactly as comment #64

Using Kubuntu netbook daily live 20100406.1 I did not managed to connect (the modem appeared once as attached peripheral but then disappeared). Using Kubuntu LiveUSB the system was slower so other reasons could existed resulting to less tests.

At this time I cannot test an installation of LL beta 2.

Regards,
George

[Marius B. Kotsbak (mariusko)]

Can you post your /var/log/daemon.log now? Installation or Live version should be the same.
Is the modem working before you connect (i.e. it is not blinking red)?
Is the modem/sim card working with other OS (Windows)

[GeorgeVita (8-launchpad-mhnyma-com)]

Hi Marius Kotsbak,
yes my SIM and modem are working well, SIM PIN check is always disabled, my modem MF636 does NOT blink in red. I did not ever noticed a red led (I am not sure if exists), possibly we have slightly different h/w versions (that is why I mentioned my IMEI# in comment #68).

At this test I did not manage to 'use' the modem. Never shown at network manager icon but /dev/ttyUSB0-1-2 were created. Looking at /var/log/daemon.log I show trials to /dev/ttyUSB1! A ZTE modem canNOT be used via /dev/ttyUSB1, the usable data port is the last created, in our case /dev/ttyUSB2.

When the system cannot connect via nm & mm (as above) I can connect ALL TIMES using:
sudo stop network-manager
sudo killall modem-manager
sudo wvdial (or pppd ...)
as described in many comments above and http://ubuntuforums.org/showthread.php?t=1202430)

Concluding: It is not a modem's problem (PIN, signal, etc) but possibly a f/w or h/w variation.
My opinion is that the problem is around modem-manager or a timing-problem using the LiveUSB.

I can be online for 2-3 hours more for any new test (more tests tomorrow).

Regards,
George

[GeorgeVita (8-launchpad-mhnyma-com)]

New try: I used a new possibly faster that the USB stick, an SDHC as the LiveUSB (LL desktop beta 2)

Boot without modem, try ubuntu, all defaults (english, etc), modem attached, found, connected, 2nd try connected, 3rd try NO ACTION (at nm/mm).

Attached /var/log/daemon.log shows timing which can be compared with the 'human actions' described below:

sudo dmesg -c (to clear previous long dmesg)

23:40 modem attached
23:42 found at nm icon, new broadband connection, connected
(>>> terminal was open, mouse pointer disappeared, pressing ESC pointer came back)
browsing, time changed via internet to -3 hours
20:46 disconnected, modem removed
20:48 modem attached, found, green led was on, connected GPRS (ok), browse
20:52 modem found/changed to 3G, browsing all fine
20:54 disconnected, modem removed
20:55 modem attached again
>>> never appeared at nm icon, daemon.log froze at 20:56:40
21:00 modem removed
21:01 modem attached again
>>> no activity to daemon.log

daemon.log and dmesg copied to desktop (liveUSB has a minimum default persistent area)

21:0x >>> use all times classics!
sudo stop network-manager
sudo killall modem-manager
sudo pppd .... (long commaaaaaand), connected, launchpad.net, wrote this message (now time shows 21:22, actual is 00:22)

files attached for further debugging.

Regards,
George

[GeorgeVita (8-launchpad-mhnyma-com)]

... and the assosiated dmesg (from first modem attachment till 'no activity' time=21:04)

[GeorgeVita (8-launchpad-mhnyma-com)]

Same behavior running LiveCD on 2x desktops:
problems using network-manager & modem-manager
connecting fine after stop nm, killall mm, pppd
G

[GeorgeVita (8-launchpad-mhnyma-com)]

LL installed from daily live of Apr-11
Boot with modem attached, did not appeared to nm icon ('triggered' as useless /dev.ttyUSB1)
Modem removed and attached again for 2nd and 3rd time, appeared at nm icon (found as /dev/ttyUSB0), connected fine.

Attached file daemon_LLapr11.log is the /var/log/daemon.log

Regards,
George

[Marius B. Kotsbak (mariusko)]

Well, my modem blinks red while booting/connecting to network.

And what I forgot to say is that I have done the trick I found in an forum from windows to disable the driver CD mode. It might be that this changes the timing of the network manager and the modem. You might want to test it to confirm that theory or as an workaround.

[Marius B. Kotsbak (mariusko)]

I have had some problems with this in Lucid. Sometimes it workss perfectly with autoconnecting, other times nothing happens, but works perfectly with wvdial.

[Sam Azer (samazer)]

Similar experience for me: The modem is detected automatically in 10.04 and the /dev/ttyUSB0,1 & 2 devices appear - but then no joy from the Network Manager in the KDE desktop (This time I did a fresh install of Kubuntu 10.04.) However: wvdial works great and the modem appears to be working well (there have been no disconnects the past couple of times I tried it.)

My deepest thanks and congratulations, as always, to all the great guys and gals who are putting this together - even with the new & remaining problems K/ubuntu is fabulous!

[el es (el-es-poczta)]

Hi,
Tested on Acer Aspire One A150 : MF636 with BT UK, yesterday's upgrade Karmic->Lucid:
- Booting without dongle :
  After inserting the dongle FIRST TIME AFTER BOOT : (timeline) (+next event duration) - times approximate
  - it gets recognized as CD ROM (BT AM), dmesg shows it is mass storage (+20s)
  - tries to mount the CD automatically, but dmesg shows it sees no media (+10s)
  - so it ejects CD (+10s)
  - then the dongle light goes off, (+10s), it turns on red (+5s) turns blue
  - dmesg shows mass storage device (MMC), and the usual 3 ttyUSB ports (+10s)
  - Network Manager recognizes the dongle, if was not configured, shows new option (behold, up to 2 minutes!)
  - (if connection configured) Network Manager shows twirling icon and connects (can take 30 seconds easily)
  - haven't done tests w/r/t stability of connection over long time though.
So from plugging in to getting internet connection it CAN take up to 4 minutes altogether.

When closed connection, unplugged the dongle, and plugged in again :
- it gets recognized as mass storage and dmesg is stuck on 'waiting for device to stabilize before scanning' (or so)
- gave up waiting after 2 minutes

If booting with dongle in the USB port :
- it gets recognized as mass storage and dmesg is stuck on 'waiting for device to stabilize before scanning' (or so)
- gave up waiting after 2 minutes

But after poweroff/start up (haven't tried reboot only) it works through the usual procedure, no problem until dongle unplugged.

(this is my boss's netbook, next time round it I will try to attach dmesg of both cases)

[el es (el-es-poczta)]

The above is with both Network Manager and Modem Manager installed (there is other option, namely Wader, but that one does not work good with Network Manager probably)

[el es (el-es-poczta)]

Due to the operating system wiped out and winxp installed, no further report will be available from me on this case, sorry.

[harvest316 (harvest316)]

I have the same experience as "el es" on a fresh Lucid install.

Happy to provide any assistance in analysing this.

[ZiNk (cserpentis)]

Same behavior.

[ZiNk (cserpentis)]

Also by default after plugging in and waiting ~80 seconds (time needed for the dongle to be recognized by system), "Enable Mobile Broadband" is unchecked in Network Manager, although broadband connections are available and it is possible to connect to them by clicking.
If I manually click the "Enable broadband connection" before connecting to a network, then connection is lost shortly to the modem and Network Manager no longer recognizes it, until reboot.
If the checkbox is left "as it is" and I simply connect to the desired network, then it is possible to unplug the dongle and then it will be recognized properly, when connected (takes ~80 seconds to start as well). Hope this info is of any use in tracking and fixing this bug.

[GeorgeVita (8-launchpad-mhnyma-com)]

Great News!

Updating firmware of my ZTE MF636 to V1.0.4B11 (from V1.0.2B01) using a win-application from my local 3G data provider fixed all problems regarding instability of /dev/ttyUSBx creation/removal.
Tested on Ubuntu 10.04 (2.6.32-29-generic #58)

Now I can use my ZET MF636 as expected!

Note: after update usb-devices terminal command shows the following data

T: Bus=01 Lev=01 Prnt=01 Port=05 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=19d2 ProdID=0031 Rev=00.00
S: Manufacturer=ZTE,Incorporated
S: Product=ZTE WCDMA Technologies MSM
S: SerialNumber=MF662_ZTED010000
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
I: If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option

MF662 appears in Serial# after firmware update (real model is MF636 bought before 3 years)

If any other user needs any more tests, just describe the procedure.

Regards,
George

[GeorgeVita (8-launchpad-mhnyma-com)]

MF636 modem tested and working fine with Ubuntu 11.04 daily-live (10-MAR-2011).
uname -a
Linux ubuntu 2.6.38-6-generic #34-Ubuntu SMP Tue Mar 8 14:09:10 UTC 2011 i686 i686 i386 GNU/Linux
G

[Mathieu Trudel-Lapierre (cyphermox)]

Closing as Fix Released: my ZTE MF636 also works fine in Natty, worked fine in Maverick, all without firmware updates. There's also a report that it can be helped with a firmware update, so you might want to test this too.