Ubuntu
modemmanager package

  1. Precise (12.04)
  2. Bug #868034
  3. Comment #76

Comment 76 for bug 868034

Revision history for this message
Josua Dietze (digidietze) wrote : Re: Huawei E220 can't connect on Ubuntu 11.10

> Is it possible for an E220 to be left in the "wrong"
> state when it's switched off?

Not that I know of. Power gone = back to install mode. Always. No known exceptions.

This would not make sense anyway: the point of the whole process is to have the (Windows) drivers available at *every* plugin. The device does not know if the machine it is plugged into has the drivers installed already.

The problem of this bug lies somewhere in the interaction between software (Network Manager) and modem device. The mode switch will happen all the time, but maybe the modem registration of Network/Modem Manager will persist during the re-plug and the probing of the port will be skipped the second time.

You can try to find out if there are differences between your first plug and the second (plus the reset) by looking at dmesg/modem-manager/networkmanager logs.

The way I see it, the bug appears first in the networkmanager.log from comment #2:

NetworkManager[5781]: <info> Activation (ttyUSB0) starting connection 'Dialog GSM Postpaid'
NetworkManager[5781]: <info> (ttyUSB0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[5781]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager[5781]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
NetworkManager[5781]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager[5781]: <info> WWAN now enabled by management service
NetworkManager[5781]: <warn> GSM connection failed: (32) Serial command timed out
NetworkManager[5781]: <info> (ttyUSB0): device state change: prepare -> failed (reason 'unknown') [40 120 1]
NetworkManager[5781]: <warn> Activation (ttyUSB0) failed.

There is no indication of the problem in modem-manager.log (comment #1), but it shows the communication between the system and the modem.

Now, if we had a respective log from Natty, we could see any differences in this communication.

Annother thing to try is if access to storage interfaces is still possible after the modem problem becomes apparent (MicroSD card slot). This would rule out that the storage driver is the culprit by making the device hang somehow.