ZTE MF627 USB 3G modem not detected by NM0.7

Bug #310025 reported by Jonathon Fernyhough
38
This bug affects 4 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Running Jaunty 2.6.28-3-generic.

network-manager:
Installed: 0.7~~svn20081018t105859-0ubuntu2

3G modem supplied by 3 UK. Detected (after updating USB ids) as
Bus 005 Device 007: ID 19d2:2000 ONDA Communication S.p.A.

Using the settings for the MF682+ with usb_modeswitch gets the dongle to be detected as ID 19d2:0031 and it shows up as the ZeroCD device and USB drive. UMTSmon detects the modem once switched. /dev/ttyUSB[0-2] are created.

An addition to the HAL device information is needed for network-manager to recognise the modem. Files are attached that work around the problem.

References:
http://www.draisberghof.de/usb_modeswitch/
http://blog.ufsoft.org/2007/11/30/zte-mf622-usb-modem-under-linux
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/259028
https://answers.launchpad.net/ubuntu/+source/network-manager/+question/48520
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/267727

Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :
Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :

Pertinent output of sudo lsusb -vvv

Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :

Output of lshal once modem has been mode-switched.

description: updated
Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :

Output of lsusb -vvv once modem has been switched.

Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :

After switching it is possible to get the modem detected by network-manager by adding information to a HAL FDI file. I created one called 20-wwan-quirk.fdi in /usr/share/hal/fdi/information/20thirdparty but it could probably be integrated into 10-modem.fdi.

The kernel detects three modems with usb addresses 1.0, 1.1, 1.3 and creates ttys for each (/dev/ttyUSB[0-2]).

However, no matter which interface is picked in 20-wwan-quirk (0,1,3) the modem fails to initialise. This sequence is the same for each ttyUSB0, ttyUSB1, ttyUSB2.

Finally, I can't chat or screen to any of the /dev/ttyUSB[0-2] - it hangs and does nothing.

Dec 21 12:50:06 t7200 NetworkManager: <info> Activation (ttyUSB1) starting connection '3'
Dec 21 12:50:06 t7200 NetworkManager: <info> (ttyUSB1): device state change: 3 -> 4
Dec 21 12:50:06 t7200 NetworkManager: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
Dec 21 12:50:06 t7200 NetworkManager: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
Dec 21 12:50:06 t7200 NetworkManager: <debug> [1229863806.250497] nm_serial_device_open(): (ttyUSB1) opening device...
Dec 21 12:50:06 t7200 NetworkManager: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
Dec 21 12:50:06 t7200 NetworkManager: <WARN> init_done(): Modem initialization failed
Dec 21 12:50:06 t7200 NetworkManager: <info> (ttyUSB1): device state change: 4 -> 9
Dec 21 12:50:06 t7200 NetworkManager: <debug> [1229863806.393000] nm_serial_device_close(): Closing device 'ttyUSB1'
Dec 21 12:50:06 t7200 NetworkManager: <info> Marking connection '3' invalid.
Dec 21 12:50:06 t7200 NetworkManager: <info> Activation (ttyUSB1) failed.
Dec 21 12:50:06 t7200 NetworkManager: <info> (ttyUSB1): device state change: 9 -> 3
Dec 21 12:50:06 t7200 NetworkManager: <info> (ttyUSB1): deactivating device (reason: 0).

Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :

OK - using the correct SIM card would help. I was testing with my mobile SIM rather than the Broadband SIM as the broadband SIM won't work in a 2G service area whereas my mobile SIM will (as I've just found out on the 3 website. Grr.).

Selecting interface 3 in 20-wwan-quirk now leaves the modem searching for a network (which for me it will never find as I'm not in a 3G area - useful).

However, it appears to work. Great!

So, need to use usb_modeswitch with the settings for the MF628+ and add the device information so HAL recognises it as a modem. I just need to work out how to make a file into a patch now; patching 10-modem.fdi would make most sense as the information is already there for other ZTE modems.

Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :

OK - so ignore the bit about the SIM card. Of course, my mobile SIM had a PIN request enabled. Disabling this means everything works. The LED on the modem changes from red to blue, meaning it's found a network, and once switched it will connect - tested and it receives data.

Phew.

References:
http://www.draisberghof.de/usb_modeswitch/
http://blog.ufsoft.org/2007/11/30/zte-mf622-usb-modem-under-linux
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/259028
https://answers.launchpad.net/ubuntu/+source/network-manager/+question/48520

description: updated
Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :

I've put together a how-to for reference.

http://ubuntuforums.org/showthread.php?t=1017630

description: updated
Revision history for this message
Liam Green-Hughes (liamgh) wrote :

I've put together a package and put it in my PPA to enable the ZTE MF627 to be detected by Network Manager. Hope this helps. Details at:
http://www.greenhughes.com/content/zte-mf627-easy-way

Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :

This would most likely be fixed by a patch to 10-modem.fdi:

https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/407679

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.