can't connect with 3g internal modem using network-manager

Bug #1005436 reported by osprey
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ModemManager
Expired
Medium
modemmanager (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I have an internal sierra 3g modem in my dell laptop

Manufacturer: Sierra Wireless, Inc.
Model: MC8790
Revision: K1_0_2_18AP C:/WS/FW/K1_0_2_18AP/MSM6290/SRC 2008/12/29 14:49:54

The network manager correctly detects the modem and seems to initialize it. but when I try to connect it gives up saying "NO CARRIER".

I tried with wvdial, and the modem works like a charm, so I tried to track down where the problem is. Probably there is some AT command missing somewere but without luck. The mess of layers between network-manager, udev, modem-manager screwed me up, also because modem-manager is completely undocumented and seems to don't have any configuration file. Also, I could not find anywhere how to manually set options in the system connections for network manager.

But triying to debug the situation I discovered that opening a minicom session to the modem command port and simply entering a reset (ATZ) solves the issue and after that the network manager connects successfully.

Maybe someone help in finding a solution for this problem?

The software versions are

ii modemmanager 0.5.2.0-0ubunt D-Bus service for managing modems
ii network-manage 0.9.4.0-0ubunt network management framework (daemon and use
LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch

Francesco

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: modemmanager 0.5.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
Uname: Linux 3.2.0-24-generic-pae i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Mon May 28 10:08:21 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
osprey (theosprey) wrote :
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in modemmanager (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
osprey (theosprey) wrote :

Added to upstream. The bug link is
https://bugzilla.gnome.org/show_bug.cgi?id=679182

Changed in modemmanager:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Hmm. I think this was "silently" addressed in git MM_06 (so in the 0.6 release)... Would you be able to try the package from Quantal (12.10) development release, it should be installable easily and is downloadable from https://launchpad.net/ubuntu/quantal/+source/modemmanager. Look under "binary packages" for your architecture for the 'modemmanager' package (don't need -dbg), and click the first (most recent) version number on the resulting "Publishing history" page.

Changed in modemmanager (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
osprey (theosprey) wrote :

I've tried with the package from Quantal, but I get exactly the same behaviour, resetting the modem with atz several times leads the connection to work with modem-manager. wvdial still works correctly without any reset command needed.

Changed in modemmanager:
status: New → Expired
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.